Date: Fri, 23 Aug 2002 18:11:46 +0400 From: Ivan Albetkov <ivan_alb@agava.com> To: Patrick O'Reilly <bsd@perimeter.co.za> Cc: Andrew Gallatin <gallatin@cs.duke.edu>, freebsd-hackers@freebsd.org Subject: Re: Kernel Panic = System crash 8 times in 4 days Message-ID: <3D6642A2.3040102@agava.com> References: <15718.14981.573727.965999@grasshopper.cs.duke.edu> <054301c24aae$6b99ed50$b50d030a@PATRICK>
next in thread | previous in thread | raw e-mail | index | archive | help
Patrick O'Reilly wrote: > From: "Andrew Gallatin" <gallatin@cs.duke.edu> > > >>Patrick, >> >>Your problem appears to be happening in a loaded module. >>From the stack trace, it would seem to be a loaded module dealing with >>filesystems. My money is on vinum. >> >>However, its a bit difficult to get a meaningful stack trace from a >>loadable module. To try debugging the module, grab the "gdbmods" >>shells script from: http://people.freebsd.org/~gallatin/gdbmods You >>run it as root: >>gdbmods /sys/compile/KERNCONF/kernel.debug /var/crash/vmcore.0 >> > > Andrew, > > thanks for helping out. > > I seem to be getting a different problem with gdbmods: > > # ./gdbmods kernel.debug.200208211211 vmcore.2 > please be patient while loaded modules are resolved > gdbmods using kernel: kernel.debug.200208211211 > gdbmods using core: vmcore.2 > > gdb extra arguments: > if: Missing file name. > # > > >>That means that either your crashdump doesn't match the kernel.debug >>you told the script to use, or the kernel you told the script to use >>does not have debug symbols. >> >>If this does not work, or looks too complex, can you please compile >>vinum statically into your kernel. Then when you crash, you should >>see function names between spec_strategy() and trap() in the stack >>trace. > > > OK - It looks to me like I need to build with: > options VINUMDEBUG > > Is that it? Then "make kernel" and bounce her? No, no, no! Your vinum is loaded as module, not compiled in. By default it compiles with VINUMDEBUG. so if you left all antouched now you must have /modules/vinum.ko with debug symbols. And don't care about gdbmods :). All you need to debug vinum is in man 4 vinum "Debugging problems with vinum: kernel panics" > > Regards, > Patrick O'Reilly. > ___ _ __ > / _ )__ __ (_)_ __ ___ _/ /____ __ > / __/ -_) _) / ~ ) -_), ,-/ -_) _) > /_/ \__/_//_/_/~/_/\__/ \__/\__/_/ > http://www.perimeter.co.za > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > -- Ivan Albetkov AGAVA Software (http://www.agava.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3D6642A2.3040102>