Date: Mon, 11 Nov 2002 19:41:42 -0800 From: Juli Mallett <jmallett@FreeBSD.org> To: current@FreeBSD.org Subject: Two panics... One ffs related, one lockmgr. Message-ID: <20021111194142.A31849@FreeBSD.org>
next in thread | raw e-mail | index | archive | help
Unfortunately I can't provide much useful information, just the two panic messages. At least in the trap case, the dmesg buffer will include the trap stuff, but in plain panic cases, I don't have any way to copy the trace stuff rom the box I saw these on, sigh. Anyway... In both cases, the filesystem where stuff was going on which appeared to lead to the panic was UFS2. I got this one, the first one, when I was just running my normal everyday stuff, and a kse test app. panic: allocdirect_merge: old blkno 1236712 != new 1381064 || old size 4096 != new 8192 And this one, when running a kse test app shoving lots of info into a file, while background fsck was going. panic: lockmgr: locking against myself And of course, the subsequent fun. syncing disks... panic: bdwrite: buffer is not busy Uptime: 5m5s pfs_vncache_unload(): 1 entries remaining Dumping 63 MB ata0: resetting devices .. wi0: wi_cmd: busy bit won't clear. panic: bwrite: buffer is not busy??? Uptime: 5m25s pfs_vncache_unload(): 1 entries remaining cbb0: bad Vcc request. ctrl=0xffffff88, status=0xffffffff cbb_power: CARD_VCC_0V and CARD_VPP_0V [44] cbb1: bad Vcc request. ctrl=0xffffff88, status=0xffffffff cbb_power: CARD_VCC_0V and CARD_VPP_0V [44] Automatic reboot in 15 seconds - press a key on the console to abort --> Press a key on the console to reboot, --> or switch off the system now. -- Juli Mallett <jmallett@FreeBSD.org> OpenDarwin, Mono, FreeBSD Developer. FreeBSD on MIPS-Anything on FreeBSD. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20021111194142.A31849>