System was cvsup'd yesterday afternoon:

FreeBSD 5.0-CURRENT #4: Sun Jul 21 23:43:59 EDT 2002

Background fsck was started and I waited a decent amount of time after 
the login: prompt showed up before logging into root.  Root (bash) 
prompt displayed after /etc/motd and immediately after the serial 
console gets the panic:

Starting background filesystem checks

Mon Jul 22 18:57:46 EDT 2002
lock order reversal
 1st 0xc034aee0 sysctl sysctllock (sysctl sysctllock) @ 
 2nd 0xc03179e0 Giant (Giant) @ /usr/src/sys/dev/isp/isp_freebsd.c:2065
dev = da0s1g, block = 6657576, fs = /usr
panic: ffs_blkfree: freeing free block
cpuid = 1; = 00000000
Stopped at      Debugger+0x46:  xchgl   %ebx,in_Debugger.0
db> trace
Debugger(c02e10fa) at Debugger+0x46
panic(c02f0e00,c02f0de0,c41ca44c,659628,0) at panic+0xde
ffs_blkfree(c41d0800,c41fa000,659628,0,4000) at ffs_blkfree+0x418
indir_trunc(c41a1a00,1966180,0,0,f600c,0,d6a3dc40) at indir_trunc+0x290
indir_trunc(c41a1a00,1964740,0,1,100c,0,d6a3dc40) at indir_trunc+0x26b
handle_workitem_freeblocks(c41a1a00,0) at handle_workitem_freeblocks+0x1d0
process_worklist_item(0,0) at process_worklist_item+0x170
softdep_process_worklist(0) at softdep_process_worklist+0xb4
sched_sync(0,d6a3dd48,c1585c00,c01f69f4,0) at sched_sync+0x17e
fork_exit(c01f69f4,0,d6a3dd48) at fork_exit+0x94
fork_trampoline() at fork_trampoline+0x1a
db> locks
No such command
db> show locks
exclusive sleep mutex Giant r = 0 (0xc03179e0) locked @ 

I just got my 2nd Athlon MP chip today, hopefully this is similar to the 
last time I crashed while in background fsck....  Let me know if any 
more info is needed, I'll play with the coredump a bit.

Anthony Jenkins

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to