From owner-freebsd-acpi@FreeBSD.ORG Mon Apr 18 19:36:19 2005 Return-Path: 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 4261516A4CE; Mon, 18 Apr 2005 19:36:19 +0000 (GMT) Received: from www.cryptography.com (li-22.members.linode.com [64.5.53.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id D6E6943D45; Mon, 18 Apr 2005 19:36:18 +0000 (GMT) (envelope-from nate@root.org) Received: from [10.0.0.34] (adsl-67-119-74-222.dsl.sntc01.pacbell.net [67.119.74.222]) by www.cryptography.com (8.12.8/8.12.8) with ESMTP id j3IJaGLS018278 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 18 Apr 2005 12:36:18 -0700 Message-ID: <42640C2B.20100@root.org> Date: Mon, 18 Apr 2005 12:36:11 -0700 From: Nate Lawson User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Guy Brand References: <20050417205230.GC837@chimie.u-strasbg.fr> <4263E9BF.4050501@root.org> <20050418192235.GA867@chimie.u-strasbg.fr> In-Reply-To: <20050418192235.GA867@chimie.u-strasbg.fr> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-acpi@freebsd.org cc: freebsd-current@freebsd.org Subject: Re: hw.acpi.battery.life alway at 100 X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Apr 2005 19:36:19 -0000 Guy Brand wrote: > On 18 avril at 10:09, Nate Lawson wrote: >>> hw.acpi.battery.time: 94 >> >>You'll have to do more investigating. There were no MFCs that I can see >>to acpi between those two dates. First, compare the output of dmesg >>between the working and non-working kernels and see if anything has changed. > > OK. So as shown only hw.acpi.battery.life is wrong in sysctl output. > An other symptom is related to this problem: just after a boot the > system is weird, the keyboard is reactive (changing ttyv ok, typing > commands ok) but answers to commands are very very slow. This > strange state lasts around 5 minutes during which > > hw.acpi.battery.life: -1 > hw.acpi.battery.time: -1 > hw.acpi.battery.state: 7 > hw.acpi.battery.units: 1 > hw.acpi.battery.info_expire: 5 > > after this delay, the logs shows a line: > > acpi_cmbat0: battery initialization done, tried 1 times > > and the system is responsive as usual, but the life status is wrong > (sticked to 100) as written in my previous mail. > > I diffed the dmesg outputs, here is it: > > --- mm-prerelease Mon Apr 18 21:14:47 2005 > +++ mm-stable Mon Apr 18 21:17:07 2005 > @@ -587,3 +586,9 @@ > kernel: Mounting root from ufs:/dev/ad0s1a > kernel: start_init: trying /sbin/init > kernel: splash: image decoder found: logo_saver > +kernel: acpi_ec0: info: new max delay is 610 us > +kernel: acpi_ec0: info: new max delay is 630 us > +kernel: acpi_ec0: info: new max delay is 820 us > +kernel: acpi_cmbat0: battery initialization failed, giving up > +kernel: acpi_ec0: info: new max delay is 930 us Ok, the EC delays are the likely culprit. The battery driver is not getting a response from the EC and so you get no battery info. I'm adding -current to the CC since a change elsewhere in the kernel may have triggered this. Is anyone aware why it appears interrupts are now disabled for a while just after launching init? The change appeared in 5-STABLE between March 17 and April 17. Guy, can you try disabling usb? Also, can you cvsup to dates between March 17 and April 17 to try to narrow down the exact date this started occurring? -- Nate