From owner-freebsd-current@FreeBSD.ORG Thu Sep 25 11:54:41 2003 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 5EDAD16A4B3 for ; Thu, 25 Sep 2003 11:54:41 -0700 (PDT) Received: from rootlabs.com (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id D931C43FF3 for ; Thu, 25 Sep 2003 11:54:40 -0700 (PDT) (envelope-from nate@rootlabs.com) Received: (qmail 60053 invoked by uid 1000); 25 Sep 2003 18:54:41 -0000 Date: Thu, 25 Sep 2003 11:54:41 -0700 (PDT) From: Nate Lawson To: Jeremy Bingham Message-ID: <20030925114945.Y59820@root.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: current@freebsd.org Subject: Re: Problem w/ ACPI in -CURRENT 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: Thu, 25 Sep 2003 18:54:41 -0000 > So, after running this laptop with debugging stuff and INVARIANTS on all > day and having it work fine, I decided to try taking the INVARIANTS > options out of the kernel. Lo and behold, it now hangs again when I try > to boot. I can't even get it to respond when I hit Ctrl-Alt-Esc and try > to get it to go into debugging mode and get a stack trace. When I was > looking at where it was dying before with verbose logging turned on, it > seemed to be dying when it was trying to initialize the battery. I > looked at the ACPI stuff in the kernel, and I think I may have found > where it stops working. (It's where the kernel tries to initialize the > battery - somewhere in sys/dev/acpia/acpi_cmbat.c.) Interesting. Try turning on ACPI_LV_FUNCTIONS (see the email I just sent to -current) as well as ACPI_DEBUG and let me know the last 3-4 prints before it hangs. Not blaming anyone here, but could you also try without ATAng? I am unable to use ATAng on my laptop. -Nate