From owner-freebsd-questions@FreeBSD.ORG Wed Nov 17 10:42:57 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E6E8A16A4DF for ; Wed, 17 Nov 2004 10:42:57 +0000 (GMT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 93B2B43D2D for ; Wed, 17 Nov 2004 10:42:57 +0000 (GMT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.13.1/8.13.1) with ESMTP id iAHAfTkf071150; Wed, 17 Nov 2004 05:41:29 -0500 (EST) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)iAHAfTI6071147; Wed, 17 Nov 2004 10:41:29 GMT (envelope-from robert@fledge.watson.org) Date: Wed, 17 Nov 2004 10:41:29 +0000 (GMT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Gordon McKee In-Reply-To: <035901c4cc88$e817f800$c800a8c0@gdmckee.home> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-questions@freebsd.org Subject: Re: Kernel Panic X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Nov 2004 10:42:58 -0000 On Wed, 17 Nov 2004, Gordon McKee wrote: > I am running 6-CURRENT just as a test server - it is not doing anything > really. Now when the systems boots it gets to the login prompt the I > get the following error: > > panic: free: address 0xd4d91cb0(0xd4d91000) has not been allocated. > > Does any one have any ideas how to fix this? I have tried with and > without ACPI. > > I could just reformat I guess. > > Thanks in advance If you're running 6-CURRENT, you want to become familiar with the kernel debugging section of the FreeBSD handbook, as the -CURRENT branch is intended for those who are interested in working with pre-release FreeBSD code that may (or may not) be stable at any given moment. The above looks like a kernel bug; if you could generate a stack trace, that would probably be the most helpful thing to send to the freebsd-current mailing list. You may want to make sure you're running the most recent 6.x code as bugs appear (and are fixed) with relative frequency. Make sure you follow that mailing list so you can get warnings of new features being added, etc, which can help minimize the risk of grabbing source from a bad day, or help you identify when a problem you're experiencing is already being worked on. It could be that re-installing will fix it, but it's more likely that the panic is a result of something about your system configuration (hardware, software) that isn't the case on a FreeBSD developer's system, so they haven't yet seen the bug (meaning that a report would be helpful). Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Principal Research Scientist, McAfee Research