From owner-freebsd-stable@FreeBSD.ORG Thu Aug 16 10:41:49 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A9AC1106564A for ; Thu, 16 Aug 2012 10:41:49 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Received: from sola.nimnet.asn.au (paqi.nimnet.asn.au [115.70.110.159]) by mx1.freebsd.org (Postfix) with ESMTP id 0708A8FC12 for ; Thu, 16 Aug 2012 10:41:48 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by sola.nimnet.asn.au (8.14.2/8.14.2) with ESMTP id q7GAfWIa084548; Thu, 16 Aug 2012 20:41:33 +1000 (EST) (envelope-from smithi@nimnet.asn.au) Date: Thu, 16 Aug 2012 20:41:32 +1000 (EST) From: Ian Smith To: Dominic Fandrey In-Reply-To: <502CAE4E.70402@bsdforen.de> Message-ID: <20120816203444.F93465@sola.nimnet.asn.au> References: <502B5F7D.6000909@bsdforen.de> <502B61B8.4040304@bsdforen.de> <502B68EA.5040907@daemonic.se> <502B6E8A.5080601@bsdforen.de> <20120816150334.C93465@sola.nimnet.asn.au> <502CAE4E.70402@bsdforen.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: Niclas Zeising , freebsd-stable@freebsd.org, Andreas Nilsson Subject: Re: battery state X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Aug 2012 10:41:49 -0000 On Thu, 16 Aug 2012 10:24:46 +0200, Dominic Fandrey wrote: > On 16/08/2012 07:39, Ian Smith wrote: > > On Wed, 15 Aug 2012 11:40:26 +0200, Dominic Fandrey wrote: > > ... > > I found your correspondence here last December about that, "Re: battery > > display broken". Looks like it's still the same problem, you were on > > 9-stable then too. When did it used to work? > > Hmm, I switched to RELENG_9 shortly before the 9.0 release. It had > worked then, or I'd have PRed a regression. I was referring to this thread, which I then also had a stab at: http://lists.freebsd.org/pipermail/freebsd-stable/2011-December/064953.html > It stopped working around the beginning of this FSAE season. Probably > between September and December. > > > On either normal or verbose boot messages, are there any ACPI errors > > logged? This smells a bit like some of the Embedded Controller issues > > that were coming up late 2010, most resolved by some patches by avg@. > > This is from the verbose dmesg: > # dmesg | grep -i bat > battery0: on acpi0 > battery1: on acpi0 > battery0: battery initialization start > battery1: battery initialization start > battery0: battery initialization done, tried 1 times > battery1: battery initialization failed, giving up > > Looks right to me. Greping for acpi or fail doesn't yield anything > interesting. Ok. Several others reported things like: ACPI Error: Method parse/execution failed [\\_SB_.BAT0._BST] (Node 0xc43284e0), AE_NO_HARDWARE_RESPONSE (20100915/psparse-633) acpi_ec0: EcRead: failed waiting to get data See also kern/162859 mentioned in the above thread, which seems similar. > There is a bunch of errors during shutdown, I have a dmesg with verbose > boot, shutdown and normal boot prepared, for whoever wants to look at it. If you take it any further, that might be handy .. > > Someone then worked around some EC issue using debug.acpi.ec.polled mode > > rather than relying on notifications, I vaguely recall. You said then > > you run only one battery, so hw.acpi.battery.units is also still wrong? > > Yes, it's wrong. There is an option to swap out the optical drive for a > battery, I think. But I still have my optical drive. Just more grist for the mill. My Thinkpad also can take another battery in the optical drive bay, but only shows one battery unless it's fitted. > > > > Are you > > > > running the latest current? I haven't updated in a while, so perhaps > > > > the issue has been resolved... > > > > > > Nay, I stick to the RELENG_ branches. I'll switch to RELENG_10 > > > shortly before a 10.0 release. > > > > If there's any indication of ACPI errors on boot (or later) this would > > be worthy of a PR, especially as you're not alone in this, on HP gear. > > I suppose you've checked HP for any more recent BIOS &/or EC updates? > > The bios version reported by dmidecode matches the latest download > from HP: > Vendor: Hewlett-Packard > Version: 68DDU Ver. F.15 > Release Date: 01/15/2009 Ah well, it was woth a shot :) cheers, Ian