On Wed, Feb 09, 2005 at 10:11:35PM -0600, Eric Anderson wrote: > After rebooting (with a console plugged in), I get this: > Fast boot: skipping disk checks. > panic: panic: thread 100079(cp):2 holds Giant but isn't blocked on a lock > > cpuid = 0 > KDB: enter: panic > [thread pid 27 tid 100001 ] > Stopped at kdb_enter+0x30: leave > > Backtrace: > Tracing pid 27 tid 100001 td 0xc2211170 > kdb_enter(c0979fd7,0,c097b542,311,c2211170) at kdb_enter+0x30 > panic(c097d225,186ef,c255d57c,2,c098bfd2) at panic+0x14e > propagate_priority(c2211170,0,c097d184,254,c0a4b950) at > propagate_priority+0x158 > > turnstile_wait(c0a44e00,c255ecf0,c09793e7,216,c0a44e00) at > turnstile_wait+0x39d > _mtx_lock_sleep(c0a44e00,c2211170,0,c097b054,106) at _mtx_lock_sleep+0x191 > _mtx_lock_flags(c0a44e00,0,c097b054,106,c07588b0) at _mtx_lock_flags+0xc0 > softclock(0,0,c0977972,256,c0a44dc0) at softclock+0x1c4 > ithread_loop(c224e580,dc848d48,c097775d,30e,0) at ithread_loop+0x172 > fork_exit(c06c4580,c224e580,dc848d48) at fork_exit+0xc6 > fork_trampoline() at fork_trampoline+0x8 > --- trap 0x1, eip = 0, esp = 0xdc848d7c, ebp = 0 --- > > Hope that helps.. Anything else I can give you? That's actually not the real panic. Look at the backtraces of other processes to find the first panic. If you can examine the core in gdb to obtain source code line numbers, that would help too. Kris
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:28 UTC