From: <Valdis.Kletnieks-PjAqaU27lzQ@public.gmane.org>
To: Administrator-fARf8FLM0JdLN7wammbJVlpr/1R2p/CL@public.gmane.org
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: ACPI battery issues on Dell C840 - OK in -test11-mm1, broken in 2.6.0-mm1.
Date: Mon, 29 Mar 2004 16:45:44 +0100 [thread overview]
Message-ID: <040301c415a4$e5cdb4e0$d100000a@sbs2003.local> (raw)
[-- Attachment #1: Type: text/plain, Size: 3838 bytes --]
(acpi-devel readers please cc: me, am only on lkml list)
Summary: Battery support was working ok for me in -test11-mm1 and earlier,
but is broken in 2.6.0-mm1 and later. I suspect 2.6.0-mm1's inclusion of
acpi-20031203.patch, but I haven't found where in the 154K of patch it goes
astray yet.
Symptoms:
At boot, the batteries are found:
Jan 5 14:53:12 turing-police kernel: ACPI: Battery Slot [BAT0] (battery present)
Jan 5 14:53:12 turing-police kernel: ACPI: Battery Slot [BAT1] (battery present)
and files created:
% ls -lR /proc/acpi/battery
/proc/acpi/battery:
total 0
dr-xr-xr-x 2 root root 0 Jan 5 18:33 BAT0
dr-xr-xr-x 2 root root 0 Jan 5 18:33 BAT1
/proc/acpi/battery/BAT0:
total 0
-rw-r--r-- 1 root root 0 Jan 5 18:33 alarm
-r--r--r-- 1 root root 0 Jan 5 18:33 info
-r--r--r-- 1 root root 0 Jan 5 18:33 state
/proc/acpi/battery/BAT1:
total 0
-rw-r--r-- 1 root root 0 Jan 5 18:33 alarm
-r--r--r-- 1 root root 0 Jan 5 18:33 info
-r--r--r-- 1 root root 0 Jan 5 18:33 state
but the contents are broken:
% cat /proc/acpi/battery/BAT0/info
present: yes
design capacity: 0 mWh
last full capacity: 0 mWh
battery technology: non-rechargeable
design voltage: 0 mV
design capacity warning: 0 mWh
design capacity low: 0 mWh
capacity granularity 1: 0 mWh
capacity granularity 2: 0 mWh
model number:
serial number:
battery type:
OEM info:
% cat /proc/acpi/battery/BAT0/state
present: yes
capacity state: ok
charging state: unknown
present rate: 0 mA
remaining capacity: 0 mAh
present voltage: 0 mV
under -test11-mm1, we had in 'info':
present: yes
design capacity: 66000 mWh
last full capacity: 62400 mWh
battery technology: rechargeable
design voltage: 14800 mV
design capacity warning: 3000 mWh
design capacity low: 1000 mWh
capacity granularity 1: 200 mWh
capacity granularity 2: 200 mWh
model number: 0004M778
serial number: 1084
battery type: LION
OEM info: SANYO
and 'state':
present: yes
capacity state: ok
charging state: unknown
present rate: unknown
remaining capacity: 66000 mWh
present voltage: 16682 mV
Even while booted on 2.6.1-rc1-mm2, dmidecode 2.2 can find the info:
Handle 0x1600
DMI type 22, 26 bytes.
Portable Battery
Location: Left Module Bay
Manufacturer: SANYO
Name: 0004M778
Design Capacity: 66000 mWh
Design Voltage: 14800 mV
SBDS Version: 1.0
Maximum Error: 4%
SBDS Serial Number: 043C
SBDS Manufacture Date: 2002-04-12
SBDS Chemistry: LION
OEM-specific Information: 0x00000001
Handle 0x1601
DMI type 22, 26 bytes.
Portable Battery
Location: Right Module Bay
Manufacturer: SANYO
Name: 0001J433
Design Capacity: 66000 mWh
Design Voltage: 14800 mV
SBDS Version: 1.0
Maximum Error: 4%
SBDS Serial Number: 014F
SBDS Manufacture Date: 2002-03-26
SBDS Chemistry: LION
OEM-specific Information: 0x00000001
So my acpi can't be TOO insane, right?
I'd be happy to debug further - the kernel(s) in question already have
CONFIG_ACPI_DEBUG built in, but I'm at a loss as to what to echo
onto the /proc/acpi/debug_layer and debug_level files to actually toggle
the printk's to something useful.
Any comments/hints/ideas/patches? ;)
[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]
next reply other threads:[~2004-03-29 15:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-29 15:45 Valdis.Kletnieks-PjAqaU27lzQ [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-01-05 23:42 ACPI battery issues on Dell C840 - OK in -test11-mm1, broken in 2.6.0-mm1 Valdis.Kletnieks-PjAqaU27lzQ
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='040301c415a4$e5cdb4e0$d100000a@sbs2003.local' \
--to=valdis.kletnieks-pjaqau27lzq@public.gmane.org \
--cc=Administrator-fARf8FLM0JdLN7wammbJVlpr/1R2p/CL@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox