From owner-freebsd-acpi@FreeBSD.ORG Tue Nov 29 21:19:32 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 DC39016A420 for ; Tue, 29 Nov 2005 21:19:32 +0000 (GMT) (envelope-from dkelly@Grumpy.DynDNS.org) Received: from smtp.knology.net (smtp.knology.net [24.214.63.101]) by mx1.FreeBSD.org (Postfix) with SMTP id E5DB443D6B for ; Tue, 29 Nov 2005 21:19:29 +0000 (GMT) (envelope-from dkelly@Grumpy.DynDNS.org) Received: (qmail 30586 invoked by uid 0); 29 Nov 2005 21:18:06 -0000 Received: from user-69-73-60-132.knology.net (HELO Grumpy.DynDNS.org) (69.73.60.132) by smtp5.knology.net with SMTP; 29 Nov 2005 21:18:06 -0000 Received: by Grumpy.DynDNS.org (Postfix, from userid 928) id 5F110649D; Tue, 29 Nov 2005 15:19:28 -0600 (CST) Date: Tue, 29 Nov 2005 15:19:28 -0600 From: David Kelly To: John Baldwin Message-ID: <20051129211928.GE4935@Grumpy.DynDNS.org> References: <20051127010724.GA1161@Grumpy.DynDNS.org> <200511280813.59911.jhb@freebsd.org> <804E027B-1274-40E2-8691-F6B6D057BC0A@hiwaay.net> <200511291452.35400.jhb@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200511291452.35400.jhb@freebsd.org> User-Agent: Mutt/1.4.2.1i Cc: 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: Tue, 29 Nov 2005 21:19:33 -0000 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. > > Oh, and apparently the dmesg buffer isn't big enough to hold > > everything "boot -v" wants to say. Surely there is a way to make it > > bigger? > > Well, using a serial console is the best method, but there is also a > kernel option for increasing the message buffer size documented in > sys/conf/NOTES. I can work the problem both ways tonight when I can put my hands on the physical machine. -- David Kelly N4HHE, dkelly@HiWAAY.net ======================================================================== Whom computers would destroy, they must first drive mad.