I just saw a strange panic on a dual CPU x86:
(kernel from Tuesday)
panic: uma_zalloc_arg: Returning an empty bucket.
cpuid = 0; lapic.id = 00000000
Debugger("panic")
Stopped at Debugger+0x55: xchgl %ebx,in_Debugger.0
db> tr
Debugger(c03477a6,0,c035a2ba,d69b6bc0,1) at Debugger+0x55
panic(c035a2ba,0,c035a07d,54c,0) at panic+0x11f
uma_zalloc_arg(c082da00,0,5,4b,c082da00) at uma_zalloc_arg+0x241
malloc(78,c0376da0,5,4,d69b6c48) at malloc+0x75
g_new_bio(4b,d69b6c5c,c01e0000,c03aae88,4) at g_new_bio+0x37
g_clone_bio(c4559980,c03aae80,d69b6cb0,d69b6c74,c01b794c) at g_clone_bio+0x14
g_slice_start(c4559980,d69b6d0c,c01b8278,c1581c30,d69b6cb0) at g_slice_start+0x6f
g_io_schedule_down(c1581c30,d69b6cb0,4c,c0342e7a,a) at g_io_schedule_down+0x2e
g_down_procbody(0,d69b6d48,c0344f96,34c,90140004) at g_down_procbody+0x88
fork_exit(c01b81f0,0,d69b6d48) at fork_exit+0xa5
fork_trampoline() at fork_trampoline+0x1a
--- trap 0x1, eip = 0, esp = 0xd69b6d7c, ebp = 0 ---
db> show locks
exclusive sleep mutex 128 (UMA zone) r = 0 (0xc082da24) locked @
../../../vm/uma_core.c:1356
exclusive sleep mutex PCPU 128 (UMA cpu) r = 0 (0xc082dae8) locked @
../../../vm/uma_core.c:1312
exclusive sleep mutex g_down r = 0 (0xd69b6cb0) locked @ ../../../geom/geom_kern.c:113
db> sho pcpu
cpuid = 0
curthread = 0xc1581c30: pid 4 "g_down"
curpcb = 0xd69b6da0
fpcurthread = none
idlethread = 0xc1580a90: pid 12 "idle: cpu0"
currentldt = 0x28
spin locks held:
db> c
boot() called on cpu#1
syncing disks... panic: KSE not on run queue
cpuid = 0; lapic.id = 00000000
Debugger("panic")
<hardlock, bad freebsd, no dump>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
