From owner-freebsd-acpi@FreeBSD.ORG Sat Apr 1 19:27:33 2006 Return-Path: X-Original-To: freebsd-acpi@freebsd.org Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7A22F16A401 for ; Sat, 1 Apr 2006 19:27:33 +0000 (UTC) (envelope-from nate@root.org) Received: from ylpvm01.prodigy.net (ylpvm01-ext.prodigy.net [207.115.57.32]) by mx1.FreeBSD.org (Postfix) with ESMTP id 01B5C43D49 for ; Sat, 1 Apr 2006 19:27:30 +0000 (GMT) (envelope-from nate@root.org) Received: from pimout5-ext.prodigy.net (pimout5-int.prodigy.net [207.115.4.21]) by ylpvm01.prodigy.net (8.12.10 outbound/8.12.10) with ESMTP id k31JRRag009856 for ; Sat, 1 Apr 2006 14:27:27 -0500 X-ORBL: [71.139.114.10] Received: from [10.0.5.51] (ppp-71-139-114-10.dsl.snfc21.pacbell.net [71.139.114.10]) by pimout5-ext.prodigy.net (8.13.4 outbound domainkey aix/8.13.4) with ESMTP id k31JRSPo073240; Sat, 1 Apr 2006 14:27:28 -0500 Message-ID: <442ED3FB.6030904@root.org> Date: Sat, 01 Apr 2006 11:26:51 -0800 From: Nate Lawson User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: Scott Lipcon References: <580cd3b30603312143o4edc0dd7q667e7e3c578a114c@mail.gmail.com> In-Reply-To: <580cd3b30603312143o4edc0dd7q667e7e3c578a114c@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-acpi@freebsd.org Subject: Re: ACPI blacklist - important? X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 01 Apr 2006 19:27:33 -0000 Scott Lipcon wrote: > Hi, > > I've got a question, and I have to admit I really don't know much about > ACPI, but I'd appreciate any advice. > > My email server was an Athlon XP running FreeBSD 5.4-STABLE, and the > motherboard died. I put the disks in an old machine, which is an ASUS P2D-B > board, dual 350Mhz PII. It panic'ed on boot, saying the ACPI implementation > was on the blacklist. I was able to figure out how to disable the blacklist > check ("set hint.acpi.0.disabled=0") and it booted up and seems to be > running OK. If you upgrade the BIOS, the message will likely go away. The blacklist check should NOT panic, it should just boot with acpi disabled. So please give the panic message and any associated info (i.e. trap frame). > My question is - what is the side-effect of having this blacklisted ACPI > implementation running? My kernel is a single CPU kernel (since my Athlon > was only single CPU) so if the lack of SMP has any effect I'd like to know. > Specifically, is this setup likely to be stable? I'm certainly planning on > replacing the Athlon motherboard with a new board/CPU, but I'm going out of > town this week and probably wont have time to get replacement parts before I > leave, and I'd really like to have some confidence that my email server will > stay up while I'm gone. Different machines are blacklisted for various reasons. I believe the ASUS P2* series had a bad interrupt routing table, possibly for the SCI. That would mean that it could be unstable with acpi *enabled*. So disabling acpi should be perfectly safe, stable, etc. That's what the blacklist entry is supposed to do. We need to fix the panic problem, so please provide that info when you get a chance. -- Nate