I provoked a kernel panic on another machine. panic: page fault
GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "amd64-marcel-freebsd"... Cannot access memory at address 0xffffff019dffffe0 (kgdb) #0 0x0000000000000000 in ?? () Cannot access memory at address 0x0 (kgdb) 29.08.2010 16:33, v...@freebsd.org wrote: > Old Synopsis: Panic when starting ladvd > New Synopsis: [panic] when starting net/ladvd > > State-Changed-From-To: open->feedback > State-Changed-By: vwe > State-Changed-When: Sun Aug 29 13:26:03 UTC 2010 > State-Changed-Why: > Vladislav, > w/o a backtrace or any other information, it's quite hard to tell where > the problem might come from. > > Your screenshot suggests, there's a NULL pointer causing the trouble. > > Can you please try at first the following command and post us it's output: > addr2line -e /boot/kernel/kernel.symbols 0xffffffff806aa114 > > If your kernel config is near GENERIC, the problem might be in > sys/net80211/ieee80211_node.c:2328 > > Having a backtrace would make things simpler. If you're brave enough, you > may try to get the kernel dump onto a usb thumb drive (I'm using this for > embedded machines, where I don't have the space to store dumps). > It works find, just take a look at dumpon(8). > > If you got a dump, please use the kernel debugger to get the backtrace. > > > http://www.freebsd.org/cgi/query-pr.cgi?pr=149948 > > > _______________________________________________ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
