Date: Sun, 4 May 2003 13:21:07 -0700 From: "Cliff L. Biffle" <cbiffle@safety.net> To: Terry Lambert <tlambert2@mindspring.com> Cc: current@freebsd.org Subject: Re: Reproduceable kernel panic on boot Message-ID: <200305041321.07162.cbiffle@safety.net> In-Reply-To: <3EB56147.A4CBEB0A@mindspring.com> References: <200305040004.40214.cbiffle@safety.net> <3EB56147.A4CBEB0A@mindspring.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sunday 04 May 2003 11:51 am, Terry Lambert wrote: > If you have a debug kernel available, you probably want to gdb -k > it, and then look at the code at 0xc1c1bd75; that will give you > the exact line with the error. Believe it or not, no debug kernel was generated, either. So for some reason, a kernel config that has always generated a kernel.debug and an install process that have always backed up my kernel did neither. Something must be seriously hosed here. Any ideas as to what that could be? > It's generally a bad idea to set the CPU type (see the recent > discussion on -current about the guy who shot his foot off). > In general, GCC tends to generate buggy code if you set the > CPU type; of course, if you can live with buggy code... I've been running with the closest CPUTYPE I can since I switched to FreeBSD (which was ~2yrs ago), and haven't had any bugginess to speak of, much less panics. I'll try backing that out all the same. > (to know for sure, you would have to post a traceback). I've got a semiworking kernel on the machine now, and I'm working on recompiling the errant kernel with DDB enabled. I'll post the results. Thanks very much! -Cliff L. Biffle
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200305041321.07162.cbiffle>