From owner-freebsd-current@FreeBSD.ORG Sun May 4 07:03:18 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 CB19337B401 for ; Sun, 4 May 2003 07:03:18 -0700 (PDT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id D4F2043F85 for ; Sun, 4 May 2003 07:03:17 -0700 (PDT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.12.9/8.12.9) with SMTP id h44E3T9S001975; Sun, 4 May 2003 10:03:31 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Sun, 4 May 2003 10:03:28 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: "Cliff L. Biffle" In-Reply-To: <200305040004.40214.cbiffle@safety.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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 14:03:19 -0000 On Sun, 4 May 2003, Cliff L. Biffle wrote: > I'd like to attach my kernel configuration, but have no working kernel on the > machine. Yay. It's basically GENERIC configured for I586 with at least the > following added: > options GEOM_AES, GEOM_BDE, GEOM_BSD, GEOM_GPT, GEOM_MBR, GEOM_VOL > options PSM_RESETAFTERSUSPEND > options CPU_SUSP_HLT, CPU_WT_ALLOC, NO_F00F_HACK, NO_MEMORY_HOLE > > The machine is a K6-2; I've uncommented the CFLAGS and COPTFLAGS in > make.conf but left them unchanged, and set cputype to k6-2. > > While I am using ccache, I've cleared and reset my caches and the > problem still occurs. > > Please, help! Now I get to see if I remember how to revert the entire > tree to a couple days ago. :-) Recognizing that this is made difficult by the lack of a good kernel on the box, could you build the same kernel configuration with the addition of "options DDB"? This will permit you to get a stack trace for the problem -- it's a NULL pointer dereference, but without a stack trace, it could be fairly hard to track down. If you choose to revert a kernel, revert to before April 26, or after May 3 to avoid possibly bumping into the ffs_blkfree() issue. :-) Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Network Associates Laboratories