arla-0.33 wedges NetBSD-1.4.1 machines
Dr. Lex Wennmacher
wennmach at geo.Uni-Koeln.DE
Fri Jul 14 16:10:21 CEST 2000
On Jul 14, 9:52am, Love wrote:
> When your computer
> hangs, do you have any chance break into ddb or generating a crash dump ?
O.k., so here we go:
(The machine froze again at Jul 14 15:05:59. I went to the console to invoked
ddb in order to produce a crash dump. I didn't manage to get into ddb, but the
machine did a crash dump all by itself. So, this situation is a bit different
from the wedged situations before ... Also, the last xfs debug messages are
different than the used to be.)
The panic message is:
"lockmgr: pid %d, not exclusive lock holder %d unlocking"
The kernel backtrace:
(gdb) target kcore /var/crash/netbsd.3.core
panic: lockmgr: pid %d, not exclusive lock holder %d unlocking
#0 0xf0121b3d in lockstatus (lkp=0xfa0ebce0)
at ../../../../kern/kern_lock.c:154
154 }
(gdb) bt
#0 0xf0121b3d in lockstatus (lkp=0xfa0ebce0)
at ../../../../kern/kern_lock.c:154
#1 0xf01d9bb3 in cpu_reboot (howto=256, bootstr=0x0)
at ../../../../arch/i386/i386/machdep.c:1350
#2 0xf012dbf1 in panic (
fmt=0xf0121b3d "lockmgr: pid %d, not exclusive lock holder %d unlocking")
at ../../../../kern/subr_prf.c:212
#3 0xf0122007 in lockmgr (lkp=0xf06876b0, flags=6, interlkp=0xfa04dae8)
at ../../../../kern/kern_lock.c:375
#4 0xfa06ce51 in ?? ()
#5 0xfa06c6d7 in ?? ()
#6 0xf0143e2c in lookup (ndp=0xfa0ebee0) at ../../../../sys/vnode_if.h:71
#7 0xf0143b1b in namei (ndp=0xfa0ebee0) at ../../../../kern/vfs_lookup.c:153
#8 0xf014a528 in vn_open (ndp=0xfa0ebee0, fmode=1, cmode=420)
at ../../../../kern/vfs_vnops.c:122
#9 0xf014787a in sys_open (p=0xfa0e9140, v=0xfa0ebf88, retval=0xfa0ebf80)
at ../../../../kern/vfs_syscalls.c:940
#10 0xf01e118a in syscall (frame={tf_es = -272695265, tf_ds = 1074266143,
tf_edi = 4, tf_esi = 1074357556, tf_ebp = -272639664,
tf_ebx = 1074311264, tf_edx = 16, tf_ecx = 0, tf_eax = 5, tf_trapno = 3,
tf_err = 2, tf_eip = 1074208091, tf_cs = 23, tf_eflags = 642,
tf_esp = -272639696, tf_ss = 31, tf_vm86_es = 0, tf_vm86_ds = 0,
tf_vm86_fs = 0, tf_vm86_gs = 0}) at ../../../../arch/i386/i386/trap.c:782
The processes:
othello# ps -ax -O paddr -M /var/crash/netbsd.3.core
PID PADDR TT STAT TIME COMMAND
0 f02496e0 ?? DLs 0:00.02 (swapper)
1 f9e91000 ?? Ss 0:00.03 (init)
2 f9e91138 ?? DL 0:00.01 (pagedaemon)
3 f9e91270 ?? DL 0:00.27 (reaper)
83 f9e91888 ?? Ss 0:00.05 (mount_mfs)
165 f9e91618 ?? Rs 1:32.93 (syslogd)
169 f9e91750 ?? Is 0:00.02 (portmap)
178 f9e91af8 ?? Rs 0:00.42 (ypbind)
224 f9e919c0 ?? Ss 0:00.20 (update)
226 f9e91c30 ?? Is 0:00.05 (cron)
228 f9e91d68 ?? R<s 0:00.95 (xntpd)
230 f9e91ea0 ?? Is 0:00.01 (lpd)
233 fa0b5004 ?? Ss 0:00.02 (sendmail)
237 fa0b5274 ?? Is 0:00.01 (inetd)
252 fa0b513c ?? Rs 1:01.84 (arlad)
256 fa0b54e4 ?? Is 0:00.02 (xdm-krb4)
264 fa0b53ac ?? Rs 0:49.25 (XF86_Mach64)
265 fa0b5754 ?? Is 0:00.34 (sshd1)
666 fa0b561c ?? R 0:08.69 (telnetd)
712 fa0b5d6c ?? Is 0:00.03 (xdm-krb4)
722 fa0e9b00 ?? R 1:49.67 (xconsole)
754 f9e914e0 ?? S 0:00.08 (telnetd)
362 fa0b5c34 p0- RN 247:01.62 (rc5des-netbsd-i3)
755 fa0b5ea4 p1 Is 0:00.11 (csh)
788 fa0b59c4 p1 S+ 0:03.93 (sh)
8586 fa0b588c p1 S+ 0:00.02 (sh)
8620 fa0e9140 p1 R+ 0:00.00 (sed)
8621 fa0e9758 p1 S+ 0:00.00 (sh)
8622 fa0e93b0 p1 S+ 0:00.00 (sh)
8623 fa0e9278 p1 D+ 0:00.00 (sed)
8624 fa0e9890 p1 S+ 0:00.00 (sed)
667 fa0b5afc p2 Is+ 0:00.04 (csh)
267 f9e913a8 E0 Is+ 0:00.01 (getty)
arlad:
(gdb) target kcore /var/crash/netbsd.3.core
panic: lockmgr: pid %d, not exclusive lock holder %d unlocking
#0 0xf0121b3d in lockstatus (lkp=0xfa0ebce0)
at ../../../../kern/kern_lock.c:154
154 }
(gdb) proc 0xfa0b513c
(gdb) bt
#0 mi_switch () at ../../../../kern/kern_synch.c:633
#1 0xf01e1257 in syscall (frame={tf_es = 720927, tf_ds = 458783,
tf_edi = 35996, tf_esi = 0, tf_ebp = 5160140, tf_ebx = 6, tf_edx = -1,
tf_ecx = 22, tf_eax = 24, tf_trapno = 3, tf_err = 2,
tf_eip = 1074681771, tf_cs = 23, tf_eflags = 582, tf_esp = 5160072,
tf_ss = 31, tf_vm86_es = 0, tf_vm86_ds = 0, tf_vm86_fs = 0,
tf_vm86_gs = 0}) at ../../../../arch/i386/i386/trap.c:194
The system log is in
ftp://gutemine.geo.Uni-Koeln.DE/pub/arla/messages.000714.gz
Please let me know what I can do more to debug.
Cheers
Lex
More information about the Arla-drinkers
mailing list