From owner-freebsd-stable@FreeBSD.ORG Thu Aug 16 08:24:55 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 92267106566B for ; Thu, 16 Aug 2012 08:24:55 +0000 (UTC) (envelope-from kamikaze@bsdforen.de) Received: from mail.server1.bsdforen.de (bsdforen.de [82.193.243.81]) by mx1.freebsd.org (Postfix) with ESMTP id 4C69E8FC08 for ; Thu, 16 Aug 2012 08:24:54 +0000 (UTC) Received: from mobileKamikaze.norad (iz-aix-213a.HS-Karlsruhe.DE [193.196.64.213]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mail.server1.bsdforen.de (Postfix) with ESMTPSA id 7049C86187; Thu, 16 Aug 2012 10:24:46 +0200 (CEST) Message-ID: <502CAE4E.70402@bsdforen.de> Date: Thu, 16 Aug 2012 10:24:46 +0200 From: Dominic Fandrey User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:14.0) Gecko/20120807 Thunderbird/14.0 MIME-Version: 1.0 To: Ian Smith References: <502B5F7D.6000909@bsdforen.de> <502B61B8.4040304@bsdforen.de> <502B68EA.5040907@daemonic.se> <502B6E8A.5080601@bsdforen.de> <20120816150334.C93465@sola.nimnet.asn.au> In-Reply-To: <20120816150334.C93465@sola.nimnet.asn.au> Content-Type: text/plain; charset=ascii; format=flowed Content-Transfer-Encoding: 7bit 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 08:24:55 -0000 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. 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. 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. > 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. > > > 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 Regards -- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail?