From owner-freebsd-current@FreeBSD.ORG Mon Feb 2 14:36:04 2004 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 E0AB016A4CE for ; Mon, 2 Feb 2004 14:36:03 -0800 (PST) Received: from mail2.speakeasy.net (mail2.speakeasy.net [216.254.0.202]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7935843D45 for ; Mon, 2 Feb 2004 14:36:02 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: (qmail 19724 invoked from network); 2 Feb 2004 22:36:01 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 2 Feb 2004 22:36:01 -0000 Received: from 10.50.40.205 (gw1.twc.weather.com [216.133.140.1]) by server.baldwin.cx (8.12.10/8.12.10) with ESMTP id i12MZYMA096425; Mon, 2 Feb 2004 17:35:56 -0500 (EST) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: Ian Freislich Date: Mon, 2 Feb 2004 17:24:25 -0500 User-Agent: KMail/1.5.4 References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200402021724.25419.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) cc: FreeBSD-current@FreeBSD.org Subject: Re: Panic at boot time 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: Mon, 02 Feb 2004 22:36:05 -0000 On Saturday 31 January 2004 09:29 am, Ian Freislich wrote: > John Baldwin wrote: > > On Thursday 29 January 2004 12:42 pm, Ian Freislich wrote: > > > Hi > > > > > > I've been getting this panic at boot time for last few weeks. The > > > last kernel that works is of around Wed Jan 7 15:23:38 SAST 2004. > > > > > > Random datapoints: > > > Gigabyte 686DLX motherboard with 2 PentiumII CPUs > > > I've noticed that ACPI has been working more and more poorly > > > with this motherboard. > > > I think this is related to ACPI brokenness because the working > > > kernel panics in exactly the same way if I set > > > hint.acpi.0.disabled="1". > > > > That means your working kernel doesn't work if ACPI is disabled which is > > what you are seeing here. Can you try kernels without SMP and see if > > ACPI and !ACPI both work? > > Yes, UP kernels work with and without ACPI. So ACPI is broken for > SMP (on this particular board)? No, you get the panic when you don't use ACPI when using SMP. See if your system has an MADT table via 'acpidump -t'. If it doesn't, see if there is a BIOS update for your BIOS. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org