From owner-freebsd-stable@FreeBSD.ORG Fri Nov 7 21:43:29 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 919024EE for ; Fri, 7 Nov 2014 21:43:29 +0000 (UTC) Received: from mail-oi0-x232.google.com (mail-oi0-x232.google.com [IPv6:2607:f8b0:4003:c06::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5027EB4 for ; Fri, 7 Nov 2014 21:43:29 +0000 (UTC) Received: by mail-oi0-f50.google.com with SMTP id v63so3022776oia.37 for ; Fri, 07 Nov 2014 13:43:28 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=0MsZvUk8pA++x9C56JcLsMaCzvMO+54BMHujT6FrIdY=; b=s2zsQWkNaSGHTmE6Rb8DW8ybY4nSGAuapqwaxmNWlEDgVthz1obn+h+bB11nyo9MJc TzNEb/MV3YD4Uow+WU19SNxfwtefoBvEtOpoXjM+De1pJieccCdUp2hbaiA9FBAdvkr6 5YpxUorZDW5E5NCBJPQHX8SZFwzvZKlDadiuwx+PcmTsVaJgxRmLENfhpbJajwdBl3Bs 0rBnfOubKr6RRkto1wUe55GddMwz4jIWc34xWWJ93j+ohcHoReDhRIZokmDA10NomvtW dRhE9+dQxpVSj++Bk/G5KjvrJedxPiJvJwjOuv068B/J+BX7/mI/ImhHYOD5tXQQHSzX SbBw== MIME-Version: 1.0 X-Received: by 10.60.133.49 with SMTP id oz17mr11846639oeb.39.1415396608507; Fri, 07 Nov 2014 13:43:28 -0800 (PST) Received: by 10.202.208.150 with HTTP; Fri, 7 Nov 2014 13:43:28 -0800 (PST) In-Reply-To: <502D1E8C.7060406@bsdforen.de> 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> <20120816203444.F93465@sola.nimnet.asn.au> <502D1E8C.7060406@bsdforen.de> Date: Fri, 7 Nov 2014 22:43:28 +0100 Message-ID: Subject: Re: battery state From: Oliver Pinter To: Dominic Fandrey Content-Type: text/plain; charset=ISO-8859-1 Cc: Niclas Zeising , freebsd-stable@freebsd.org, Ian Smith , Andreas Nilsson X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Nov 2014 21:43:29 -0000 On 8/16/12, Dominic Fandrey wrote: > On 16/08/2012 12:41, Ian Smith wrote:> 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 > > That never progressed to a technical level so it only suffices to reduce > the time frame. I don't remember any more. I know I'm made this more > difficult by not having written a PR right when it happened. I appologize > for this. I don't see what I can do to mitigate it, though. > >> >> > 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 > > Nothing like this occurs. > >> See also kern/162859 mentioned in the above thread, which seems similar. > > It looks like it's exactly my problem. > >> >> > 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 .. > > I just sent the dmesg to kern/162859. > >> > > Someone then worked around some EC issue using debug.acpi.ec.polled >> mode >> > > rather than relying on notifications, I vaguely recall. ... > > I also tried that. It works exactly once. I.e. the system polls one new > battery state. Which then becomes permanent. Turning it off and on > repeatedly doesn't win me new states. > > Regards > Hi! If the problem still occurs, then try to add "options ACPI_DEBUG" to kernel config, and recompile the kernel. In my case, this fixed this "dead" battery status on HP Probook 430. > > -- > 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? > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" >