From owner-freebsd-acpi@FreeBSD.ORG Wed Nov 30 00:55:47 2005 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 CEF3C16A423; Wed, 30 Nov 2005 00:55:47 +0000 (GMT) (envelope-from nate@root.org) Received: from www.cryptography.com (li-22.members.linode.com [64.5.53.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id 72DBE43D9A; Wed, 30 Nov 2005 00:55:33 +0000 (GMT) (envelope-from nate@root.org) Received: from [10.0.0.33] (adsl-67-119-74-222.dsl.sntc01.pacbell.net [67.119.74.222]) by www.cryptography.com (8.12.8/8.12.8) with ESMTP id jAU0t2ZM003307 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 29 Nov 2005 16:55:03 -0800 Message-ID: <438CF858.7020005@root.org> Date: Tue, 29 Nov 2005 16:54:48 -0800 From: Nate Lawson User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: John Baldwin References: <20051127010724.GA1161@Grumpy.DynDNS.org> <200511291452.35400.jhb@freebsd.org> <20051129211928.GE4935@Grumpy.DynDNS.org> <200511291647.02056.jhb@freebsd.org> In-Reply-To: <200511291647.02056.jhb@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: David Kelly , freebsd-acpi@freebsd.org Subject: Re: Worked in RELENG_5, fails in RELENG_6 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: Wed, 30 Nov 2005 00:55:48 -0000 John Baldwin wrote: > On Tuesday 29 November 2005 04:19 pm, David Kelly wrote: > >>On Tue, Nov 29, 2005 at 02:52:34PM -0500, John Baldwin wrote: >> >>>On Monday 28 November 2005 10:46 pm, David Kelly wrote: >>> >>>>Downloaded and FLASHed BIOS from A06 to Dell's latest, A09 this >>>>evening. No improvement. Also built and installed a new kernel from >>>>cvsup this afternoon. No improvement. >>> >>>But 5.4 works fine with ACPI enabled? This is the machine that even >>>acpidump chokes on, yes? Does acpidump work ok on 5.4? >> >>"acpidump -t -d" stops after 31 lines and says, "acpidump: FACS is >>corrupt" on stderr. See >>http://home.hiwaay.net/~dkelly/opus-acpidump-d-t.txt >> >>"acpidump -d" runs without error and emits 2754 lines. See >>http://home.hiwaay.net/~dkelly/opus-acpidump-d.txt >> >>ACPI worked with 5.4 so I never had a reason to acpidump then. Could I >>boot a 5.4 CDROM to test ACPI? Without much effort have put my hands on >>a "5.3-RELEASE Live Filesystem" CDROM that should make a good test. >> >>There was an issue briefly with ACPI in 5.0 or 5.1, very likely in a >>prerelease. >> >>Absolultely certain ACPI worked prior to 6.0 because among other things >>ACPI installed a power button handler which performed a clean shutdown >>(same as ctl-alt-del) rather than brute force yank-the-plug crash. > > > Ok. BTW, FACS is an ACPI 2.0 table that replaces the FADT (I think), so if > your BIOS has an option to only do ACPI 1.0, you can try that to see if it > fixes the problem. No, FACS is the firmware control struct. It was in 1.x. It includes the waking vector, among other things. It might be useful to patch acpidump to print a more detailed error (like how the checksum failed). I have no clue why it would work in RELENG_5 but have a problem in RELENG_6. -- Nate