Date: Mon, 27 Sep 1999 06:55:42 -0500 (CDT) From: Mike Pritchard <mpp@FreeBSD.org> To: dillon@apollo.backplane.com (Matthew Dillon) Cc: mpp@FreeBSD.ORG (Mike Pritchard), current@FreeBSD.ORG Subject: Re: -current panic w/linux netscape Message-ID: <199909271155.GAA00719@mpp.pro-ns.net> In-Reply-To: <199909261632.JAA66523@apollo.backplane.com> from Matthew Dillon at "Sep 26, 1999 09:32:19 am"
next in thread | previous in thread | raw e-mail | index | archive | help
> :I finally saw my first -current panic in more than 5 months (not a bad > :track record). > : > :I have a panic that I can duplicate with a 24 hour old "make world" > :and a 4 hour old -current kernel. If I run the linux netscape (installed > :from ports less than a week ago), the kernel panics in copystr(). > :Minimal gdb output follows. I'll have to generate a kernel with > :debug info for more information. > : > :The linux netscape worked fine with my old kernel from 9/16. > :I'm willing to try and track this down, but I hope someone > :will pop up and have an idea what is wrong. > : > :-Mike I must have caught two badly timed cvsups in a row. After doing another cvsup and recompiling/installing a kernel and modules (which I had done before), everything is working fine. I usually ignore any glitches after a fresh "cvsup/make world", except in this case it took me 3 cvsup's to get a fully-functional system. I'm still not sure exactly what was out of sync here, but after examing the crash dump with full symbols, it really looked like something wasn't in sync (i386/trap.c:syscall() had some very odd values it was trying to use). I know how to debug kernels, I just haven't had to do so for such a long time, so I wasn't prepared :-)!!!! And doing it this time, just reminds me how lacking gdb is in some respects compared to other kernel debugging tools I've used in the past in some areas. In other areas it is much better. Thanks for taking the time to respond. -Mike > Compile your kernel with debugging. In the kernel configuration file > in /usr/src/sys/i386/conf/YOURCONFIGFILE, add: > > makeoptions DEBUG="-g" > > Then config the kernel and rebuild. > > When you make install, the non-debug version will be installed and the > debug version will be sitting in the compile directory as 'kernel.debug'. > > Then reboot, then cause the crash again and get another core (be sure > to clear out space from /var/crash if necessary). > > Now bring the system up again, and use this for your gdb: > > cd /var/crash > gdb -k /usr/src/sys/compile/YOURCONFIGNAME/kernel.debug vmcore.XX > > And do the 'back' again to get the stack backtrace. You should see a > whole lot more information. > > -Matt -- Mike Pritchard mpp@FreeBSD.org or mpp@mpp.pro-ns.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199909271155.GAA00719>