Problem with kernel memory dump after panic

Ruslan Mahmatkhanov cvs-src at
Sun Nov 13 06:33:26 UTC 2011


I'm getting if_bwn panics with high traffic on -CURRENT:

And now i realize that it probably may be also reproduced on earlier
FreeBSD versions, because i didn't do such high-trafficking before, so i
got an illusion that this is -CURRENT-specific problem - it's an
assumption nevertheless.

I'm tried to investigate the causes (well, actually Adrian (adrian)
tried :)), and i got some problem when i try to show backtrace to him:

smeshariki3# kgdb -q -c /var/crash/vmcore.1 /boot/kernel/kernel
(no debugging symbols found)...#0  0xc06f6aad in doadump ()
(kgdb) bt
#0  0xc06f6aad in doadump ()
#1  0xc0af42e0 in show_busybufs ()
#2  0xefd25620 in ?? ()
#3  0xc06f7012 in kern_reboot ()
Previous frame inner to this frame (corrupt stack?)

I have all the debugging disabled in my kernel, but Adrian claims that
it still should carry some valuable data in backtrace, that is missed
now, and he suggested me to ask freebsd-current@ about this.
So I'm here. "Where is my backtrace, dude?" (C)

PS. I have system sources, my kernel is in sync with world and
third-party modules.


Tinderboxing kills... the drives.

More information about the freebsd-current mailing list