Subject: Re: Bogus ACPI battery information in recent current
To: None <current-users@netbsd.org>
From: Juan RP <juan@xtrarom.org>
List: current-users
Date: 12/13/2007 22:38:38
On Thu, 13 Dec 2007 14:27:50 -0700
Sverre Froyen <sverre@viewmark.com> wrote:
> Hi,
>
> With the latest current, I'm seeing bogus values for the battery information.
> An example (4.99.42 from this morning):
>
> # envstat
> [acpiacad0]
> connected: ON
> [acpibat0]
> present: ON
> design cap: 164.010 Wh
> last full cap: 492.800 Wh
> technology: 1
> design voltage: 10.772 V
> warn cap: 24.640 Wh ( 5.00%)
> low cap: 0.200 Wh ( 0.04%)
> voltage: 12.417 V
> charge rate: N/A
> discharge rate: N/A
> charge: 44.690 Wh ( 9.07%)
> charging: OFF
> charge state: NORMAL
> [acpitz0]
> temperature: 52.000 degC
> [aps0]
> aps0 X_ACCEL: 476
> aps0 Y_ACCEL: 514
> aps0 X_VAR: 476
> aps0 Y_VAR: 514
> aps0 TEMP_1: 44.000 degC
> aps0 TEMP_2: 44.000 degC
> aps0 Keyboard Active: ON
> aps0 Mouse Active: OFF
> aps0 Lid Open: ON
>
> Notice the "last full cap" and the "design cap" values. There is also a very
> noticable delay before the output appears. With my latest good kernel
> (4.99.40 from 6 Dec), I get
>
> # envstat
> [acpiacad0]
> connected: ON
> [acpibat0]
> present: ON
> design cap: 51.840 Wh
> last full cap: 45.440 Wh
> technology: 1
> design voltage: 10.800 V
> warn cap: 2.272 Wh ( 5.00%)
> low cap: 0.200 Wh ( 0.44%)
> voltage: 12.417 V
> charge rate: N/A
> discharge rate: N/A
> charge: 44.690 Wh (98.35%)
> charging: OFF
> charge state: NORMAL
> [acpitz0]
> temperature: 54.000 degC
> [aps0]
> aps0 X_ACCEL: 477
> aps0 Y_ACCEL: 515
> aps0 X_VAR: 477
> aps0 Y_VAR: 515
> aps0 TEMP_1: 46.000 degC
> aps0 TEMP_2: 46.000 degC
> aps0 Keyboard Active: OFF
> aps0 Mouse Active: OFF
> aps0 Lid Open: ON
>
> I've attached the dmesg from 4.99.42, below. I suspect a pertinent line is:
>
> acpiec0 at acpi0 (EC, PNP0C09-0): ACPI Embedded Controller (disabled)
>
> The dmesg diffs the working 4.99.40 kernel are:
The acpiec code was rewritten by joerg in the jmcneill-pm branch, and all
those wrong values are there because there's some problem with the new acpiec.
Joerg, do you want to investigate this issue?
--
Juan Romero Pardines - The NetBSD Project
http://plog.xtrarom.org - NetBSD/pkgsrc news in Spanish