http://bugzilla.kernel.org/show_bug.cgi?id=9341
Summary: /proc/acpi/battery displays Incorrect voltages
Product: ACPI
Version: 2.5
KernelVersion: 2.6.23.1
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Power-Battery
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
Most recent kernel where this bug did not occur: Not sure. It might have been
present in previous kernels, however after this latest kernel update I also
have a hal issue where this bug causes a flood of BAT events to hald (which I
think is another issue)... Hoping that correcting this, will indirectly
resolve the other.
Distribution: Ubuntu Gutsy
Hardware Environment: Gateway 450ROG Laptop. PentM.
Problem Description:
ACPI is reporting some conflicting battery information.
/proc/acpi/battery/BAT1/info:design voltage: 14800 mV
/proc/acpi/battery/BAT1/state:present voltage: 44800 mV
The present voltage is being reported incorrectly. I have tried this with a
different battery and also a second battery in the battery bay. All report
higher than expected present voltage values which I beleive is causing the
following event to occur.
This is causing hald to flood with.
[9229]: 13:27:37.905 [D] addon-acpi.c:142: battery event
13:27:37.918 [I] hald_dbus.c:2287: entering, local_interface=1
13:27:37.918 [D] hald_dbus.c:2296: udi=/org/freedesktop/Hal/devices/acpi_BAT1
13:27:37.921 [D] acpi.c:162: Current voltage is unknown, smaller than
501001765435r greater than design
[9229]: 13:27:37.927 [D] addon-acpi.c:113: event is 'battery BAT1 00000000
00000001
#:/proc/acpi/battery/BAT1$ grep . /proc/acpi/battery/BAT1/*
/proc/acpi/battery/BAT1/alarm:alarm: unsupported
/proc/acpi/battery/BAT1/info:present: yes
/proc/acpi/battery/BAT1/info:design capacity: 4000 mAh
/proc/acpi/battery/BAT1/info:last full capacity: 1864 mAh
/proc/acpi/battery/BAT1/info:battery technology: rechargeable
/proc/acpi/battery/BAT1/info:design voltage: 14800 mV
/proc/acpi/battery/BAT1/info:design capacity warning: 250 mAh
/proc/acpi/battery/BAT1/info:design capacity low: 100 mAh
/proc/acpi/battery/BAT1/info:capacity granularity 1: 10 mAh
/proc/acpi/battery/BAT1/info:capacity granularity 2: 25 mAh
/proc/acpi/battery/BAT1/info:model number: OAL4$
/proc/acpi/battery/BAT1/info:serial number:
/proc/acpi/battery/BAT1/info:battery type: LION
/proc/acpi/battery/BAT1/info:OEM info: SANYO
/proc/acpi/battery/BAT1/state:present: yes
/proc/acpi/battery/BAT1/state:capacity state: ok
/proc/acpi/battery/BAT1/state:charging state: charging
/proc/acpi/battery/BAT1/state:present rate: 2252 mA
/proc/acpi/battery/BAT1/state:remaining capacity: 754 mAh
Steps to reproduce:
Happens everytime. If I have a single battery installed, I only see the hald
error messages come across 4 times, no major impact. However, if I have two
batteries installed the events stream in from each battery in succession.
Causes hald to consume 50% cpu responding to all the events.
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
acpi-bugzilla mailing list
acpi-bugzilla@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla
