weird crash with a corrupt lock (?)
With nothing special going on (I think maybe a tar xfvz of the jdk 1.2.2
source), my system crashed inexplicably. I have no idea why a lock would
look like this does, no clue whether I should be replacing my hardware or
the system is just getting more and more unstable.
(kgdb) p *lkp
$1 = {
lk_interlock = {
lock_data = 0x0
},
lk_flags = 0x,
lk_sharecount = 0x10001,
lk_waitcount = 0x,
lk_exclusivecount = 0x,
lk_prio = 0x,
lk_wmesg = 0x10001 Address 0x10001 out of bounds,
lk_timo = 0x,
lk_lockholder = 0x0
}
(kgdb) bt
#0 dumpsys () at ../../kern/kern_shutdown.c:461
#1 0xc016873f in boot (howto=0x100) at ../../kern/kern_shutdown.c:302
#2 0xc0168ae1 in panic (fmt=0xc02696c0 "lockmgr: pid %d, not %s %d unlocking") at
../../kern/kern_shutdown.c:550
#3 0xc0163280 in lockmgr (lkp=0xc0f12000, flags=0x6, interlkp=0xd048fdec,
p=0xd05f7ac0) at ../../kern/kern_lock.c:382
#4 0xc0198cef in vop_stdunlock (ap=0xd0606b40) at ../../kern/vfs_default.c:250
#5 0xc02149c9 in ufs_vnoperate (ap=0xd0606b40) at ../../ufs/ufs/ufs_vnops.c:2263
#6 0xc019bfbe in vclean (vp=0xd048fd80, flags=0x8, p=0xd05f7ac0) at vnode_if.h:865
#7 0xc019c153 in vgonel (vp=0xd048fd80, p=0xd05f7ac0) at ../../kern/vfs_subr.c:1864
#8 0xc019a8e1 in getnewvnode (tag=VT_UFS, mp=0xc0d1c200, vops=0xc0cbc700,
vpp=0xd0606be8) at ../../kern/vfs_subr.c:510
#9 0xc020ccff in ffs_vget (mp=0xc0d1c200, ino=0x49f56, vpp=0xd0606c34) at
../../ufs/ffs/ffs_vfsops.c:1049
#10 0xc01ff5bb in ffs_valloc (pvp=0xd03ccd40, mode=0x8124, cred=0xc15eea80,
vpp=0xd0606c34)
at ../../ufs/ffs/ffs_alloc.c:604
#11 0xc021480f in ufs_makeinode (mode=0x8124, dvp=0xd03ccd40, vpp=0xd0606e80,
cnp=0xd0606e94)
at ../../ufs/ufs/ufs_vnops.c:2057
#12 0xc021222c in ufs_create (ap=0xd0606d94) at ../../ufs/ufs/ufs_vnops.c:186
#13 0xc02149c9 in ufs_vnoperate (ap=0xd0606d94) at ../../ufs/ufs/ufs_vnops.c:2263
#14 0xc01a29bb in vn_open (ndp=0xd0606e6c, flagp=0xd0606e38, cmode=0x124) at
vnode_if.h:106
#15 0xc019e5c1 in open (p=0xd05f7ac0, uap=0xd0606f80) at ../../kern/vfs_syscalls.c:1037
#16 0xc024f1dd in syscall2 (frame={tf_fs = 0x2f, tf_es = 0x2f, tf_ds = 0x2f, tf_edi =
0x80b4f3f, tf_esi = 0x1d,
tf_ebp = 0xbfbff858, tf_isp = 0xd0606fd4, tf_ebx = 0x60d, tf_edx = 0x1d, tf_ecx
= 0xffe0, tf_eax = 0x5,
tf_trapno = 0x7, tf_err = 0x2, tf_eip = 0x808099c, tf_cs = 0x1f, tf_eflags =
0x202, tf_esp = 0xbfbff6ec,
tf_ss = 0x2f}) at ../../i386/i386/trap.c:1150
#17 0xc0243185 in Xint0x80_syscall ()
#18 0x80509f9 in ?? ()
#19 0x8052c5a in ?? ()
#20 0x8048139 in ?? ()
--
Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! /
[EMAIL PROTECTED]`--'
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
weird crash
Hi, just today I got this error, never had it before in all those months I have been tracking CURRENT now. Jun 6 17:15:26 daemon /kernel: sio0: 65 more tty-level buffer overflows (total 65) Jun 6 17:15:28 daemon /kernel: sio0: 131 more tty-level buffer overflows (total 196) Jun 6 17:15:29 daemon /kernel: sio0: 38 more tty-level buffer overflows (total 234) until I interrupted it with CTRL-ALT-ESC to drop into DDB. This is some info I got from DDB: [ please bear with me if I didn't get all I need, but it's the first `crash' I intercepted and I think I got all the relevant data, comments appreciated though ] dbtrace Debugger(0c255518) at Debugger+0x37 scgetc(c0294020,2,124bca,c0294020,850ff2c) at scgetc+ox5ec sckdbevent(c0294020,0,0,124bca,850ff2c) at sckbdevent+0x1c4 atkbd_intr(c0294020,0,bfbfd4bc,c0211c92,c06773f0) at atkbd_intr+ox1f atkbd_isa_intr(c06773f0,0,2f,2f,2f) at atkbd_isa_intr+0x1b Xresume1() at Xresume+0x2b --- interrupt, eip=0x28078509, esp=0xc5b6dfe0, ebp=0xbfbfd4bc --- I also have results from show registers, print, show page if those are deemed interesting. What I was able to glance from ps what that the 0xc5b6dfe0 range lay in an xterm memory range... I am not 100% sure about this though. some relevant system information: [asmo...@daemon] (81) $ uname -a FreeBSD daemon.ninth-circle.org 4.0-CURRENT FreeBSD 4.0-CURRENT #3: Thu Jun 3 16:59:10 CEST 1999 asmo...@daemon.ninth-circle.org:/work/FreeBSD/src/sys/compile/DAEMON i386 Jun 2 10:57:38 daemon /kernel: isab0: Intel 82371SB PCI to ISA bridge at device 7.0 on pci0 Jun 2 10:57:38 daemon /kernel: atkbdc0: keyboard controller (i8042) at port 0x60-0x6f on isa0 Jun 2 10:57:38 daemon /kernel: atkbd0: AT Keyboard irq 1 on atkbdc0 Jun 2 10:57:38 daemon /kernel: atkbd: the current kbd controller command byte 0047 Jun 2 10:57:38 daemon /kernel: atkbd: keyboard ID 0x41ab (2) Jun 2 10:57:38 daemon /kernel: kbdc: RESET_KBD return code:00fa Jun 2 10:57:38 daemon /kernel: kbdc: RESET_KBD status:00aa Jun 2 10:57:38 daemon /kernel: kbd0: atkbd0, AT 101/102 (2), config:0x0, flags:0x3d Jun 2 10:57:38 daemon /kernel: vga0: Generic ISA VGA on isa0 Jun 2 10:57:38 daemon /kernel: fb0: vga0, vga, type:VGA (5), flags:0x7007f Jun 2 10:57:38 daemon /kernel: fb0: port:0x3b0-0x3df, crtc:0x3d4, mem:0xa 0x2 Jun 2 10:57:38 daemon /kernel: fb0: init mode:24, bios mode:3, current mode:24 Jun 2 10:57:38 daemon /kernel: fb0: window:0xc00b8000 size:32k gran:32k, buf:0x0 size:0k Jun 2 10:57:38 daemon /kernel: VGA parameters upon power-up Jun 2 10:57:38 daemon /kernel: 50 18 10 00 00 00 03 00 02 67 5f 4f 50 82 55 81 Jun 2 10:57:38 daemon /kernel: bf 1f 00 4f 0e 0f 00 00 07 80 9c 8e 8f 28 1f 96 Jun 2 10:57:38 daemon /kernel: b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c Jun 2 10:57:38 daemon /kernel: 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff Jun 2 10:57:38 daemon /kernel: VGA parameters in BIOS for mode 24 Jun 2 10:57:38 daemon /kernel: 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 Jun 2 10:57:38 daemon /kernel: bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 Jun 2 10:57:38 daemon /kernel: b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c Jun 2 10:57:38 daemon /kernel: 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff Jun 2 10:57:38 daemon /kernel: EGA/VGA parameters to be used for mode 24 Jun 2 10:57:38 daemon /kernel: 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 Jun 2 10:57:38 daemon /kernel: bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 Jun 2 10:57:38 daemon /kernel: b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c Jun 2 10:57:38 daemon /kernel: 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff Jun 2 10:57:38 daemon /kernel: sc0: System console on isa0 Jun 2 10:57:38 daemon /kernel: sc0: fb0 kbd0 Jun 2 10:57:38 daemon /kernel: sc0: VGA color 16 virtual consoles, flags=0x0 Jun 2 10:57:38 daemon /kernel: sio0: irq maps: 0x41 0x51 0x41 0x41 Jun 2 10:57:38 daemon /kernel: sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 Jun 2 10:57:38 daemon /kernel: sio0: type 16550A Jun 2 10:57:38 daemon /kernel: sio1: irq maps: 0x41 0x49 0x41 0x41 Jun 2 10:57:38 daemon /kernel: sio1 at port 0x2f8-0x2ff irq 3 on isa0 Jun 2 10:57:38 daemon /kernel: sio1: type 16550A The system itself is a simple DFI-based motherboard with Intel Pentium 200 MMX and 96 MB RAM. The keyboard is not one of them ps/2's, but a the older type (I don't think that DIN is the correct name though). the device on sio0 is my serial MouseMan: controller isa0 controller atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 device vga0at isa? port ? conflicts device sc0 at isa? If any more information is required, please tell me and I will see if I can dig it up. 'gards, -- Jeroen Ruigrok van der Wervenasmodai(at)wxs.nl The FreeBSD Programmer's Documentation Project Network/Security Specialist http://home.wxs.nl/~asmodai *BSD: Accept no limitations... To
