Re: Kernel Panic

On Sat, Apr 29, 2006 at 01:03:12AM -0400, Steve Douville wrote:
My server is rebooting frequently throughout the day. No apparent rhyme or reason, different applications can cause it. The following is what I get from one of the backtraces.

a) You're not using the kernel.debug, and b) it's not a sensible
backtrace. Perhaps it's a side-effect of a) (i.e. you're not running
kgdb against the same kernel that panicked).

(kgdb) backtrace
#0 0xc055c5e2 in doadump ()
#1 0xc055cb82 in boot ()
#2 0xc055ce18 in panic ()
#3 0xc068502c in trap_fatal ()
#4 0xc06847d5 in trap ()
#5 0xc0674baa in calltrap ()
#6 0xc26d0018 in ?? ()
#7 0xef230010 in ?? ()
#8 0xef230010 in ?? ()
#9 0x00000002 in ?? ()
#10 0xc2b7b300 in ?? ()
#11 0xef23c900 in ?? ()
#12 0xef23c8e8 in ?? ()
#13 0xc2837440 in ?? ()
#14 0xc2837440 in ?? ()
#15 0x00000000 in ?? ()
#16 0xc2b7b320 in ?? ()
#17 0x0000000c in ?? ()
#18 0x00000000 in ?? ()
#19 0xc057a8f9 in turnstile_setowner ()
#20 0xc057abbb in turnstile_wait ()
#21 0xc0554565 in _mtx_lock_sleep ()
#22 0xc05543dc in _mtx_lock_flags ()

It seems that pretty much every time I've traced the dump, it's always the turnstile_setowner that causes the panic. Or am I reading this wrong?

Any thoughts or further debugging tips would be appreciated.

TIA,
Steve
_______________________________________________
freebsd-questions@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscribe@xxxxxxxxxxx"

Attachment: pgp63IOFpcMJO.pgp
Description: PGP signature

Relevant Pages

  • Re: FreeBSD 7.0 crashed when running super-smack upon PostgreSQL
    ... This is the backtrace output in the culprit thread: ... Is there any chance I can get remote access to a box holding the synchronized kernel, kernel debugging symbols, source code, and core dump? ... We need to track down the original thread and figure out why it's sleeping while holding that lock -- perhaps it's a user thread performing a copyin/copyout holding the lock, or perhaps an ithread or other software interrupt thread acquiring a lock of an inappropriate type while holding the lock. ...
    (freebsd-stable)
  • Re: panic with tcpdrop
    ... An other panic ocurred, but on other area, is on snp.ko module but can't get backtrace. ... page fault while in kernel mode ... Previous frame inner to this frame ...
    (freebsd-current)
  • Re: panic with tcpdrop
    ... An other panic ocurred, but on other area, is on snp.ko module but can't get backtrace. ... page fault while in kernel mode ... Previous frame inner to this frame ...
    (freebsd-current)
  • Re: Unexplained kernel panic on 5-STABLE
    ... #34 0xc0801907 in syscall (frame= ... (this will output the 'pid' of the misbehaving thread) ...
    (freebsd-stable)
  • Re: ffs snapshot lockup
    ... then running kgdb on the core may show ... and backtrace of the paniced thread. ... YOu can also do 'show msgbuf' from DDB. ... locked the kernel and we broke to debugger from the watchdog timeout ...
    (freebsd-stable)