From owner-freebsd-current@FreeBSD.ORG Sun May 4 13:21:02 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8C86137B401 for ; Sun, 4 May 2003 13:21:02 -0700 (PDT) Received: from ns3.safety.net (ns3.safety.net [216.40.201.32]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7324943F93 for ; Sun, 4 May 2003 13:21:01 -0700 (PDT) (envelope-from cbiffle@safety.net) Received: from localhost (rs.rackshack.net.safety.net [216.40.201.32]) by ns3.safety.net (8.10.2/8.10.2) with ESMTP id h44KL0A16802; Sun, 4 May 2003 13:21:00 -0700 From: "Cliff L. Biffle" To: Terry Lambert Date: Sun, 4 May 2003 13:21:07 -0700 User-Agent: KMail/1.5 References: <200305040004.40214.cbiffle@safety.net> <3EB56147.A4CBEB0A@mindspring.com> In-Reply-To: <3EB56147.A4CBEB0A@mindspring.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200305041321.07162.cbiffle@safety.net> cc: current@freebsd.org Subject: Re: Reproduceable kernel panic on boot X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 May 2003 20:21:02 -0000 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