|Summary:||Battery gives me now two batterys, but only one is present|
|Product:||ACPI||Reporter:||Patrick Matthäi (patrick)|
|Component:||Power-Battery||Assignee:||Zhang Rui (rui.zhang)|
|Bug Depends on:|
My Kernel config
Description Patrick Matthäi 2008-02-13 12:00:10 UTC
Comment 1 Patrick Matthäi 2008-02-13 12:03:41 UTC
Created attachment 14798 [details] My Kernel config
Comment 2 Anonymous Emailer 2008-02-13 12:31:14 UTC
Reply-To: firstname.lastname@example.org On Wed, 13 Feb 2008 12:00:11 -0800 (PST) email@example.com wrote: > http://bugzilla.kernel.org/show_bug.cgi?id=9957 > > Summary: Battery gives me now two batterys, but only one is > present yeah, I'm seeing this on the t61p as well, but have thus far ignored it amongst the storm of other problems. > Product: ACPI > Version: 2.5 > KernelVersion: 126.96.36.199 > Platform: All > OS/Version: Linux > Tree: Mainline > Status: NEW > Severity: normal > Priority: P1 > Component: Power-Battery > AssignedTo: firstname.lastname@example.org > ReportedBy: email@example.com > > > Latest working kernel version: 188.8.131.52 > Earliest failing kernel version: 2.6.24 And it's a regression.
Comment 3 Anonymous Emailer 2008-02-14 06:05:41 UTC
Reply-To: firstname.lastname@example.org On Wed, Feb 13, 2008 at 12:31:12PM -0800, Andrew Morton wrote: > And it's a regression. No, it's a feature. You've configured in both the legacy and the sysfs interfaces for the battery, and hal is picking up both of them. There's a patch upstream to make hal realise that they're the same device, but the alternative is just to disable one of the options.
Comment 4 ykzhao 2008-02-14 17:24:14 UTC
Hi, Patrick Will you please attach the acpidump output? Thanks.
Comment 5 Patrick Matthäi 2008-02-14 23:55:52 UTC
Created attachment 14849 [details] ACPIDUMP
Comment 6 Patrick Matthäi 2008-02-14 23:56:24 UTC
Sure, and here it is :)
Comment 7 Rafael J. Wysocki 2008-02-17 14:20:15 UTC
On Thursday, 14 of February 2008, Matthew Garrett wrote: > On Wed, Feb 13, 2008 at 12:31:12PM -0800, Andrew Morton wrote: > > > And it's a regression. > > No, it's a feature. You've configured in both the legacy and the sysfs > interfaces for the battery, and hal is picking up both of them. There's > a patch upstream to make hal realise that they're the same device, but > the alternative is just to disable one of the options. Can you point me to the patch, please? I'm running the current mainline and seeing this as well. Thanks, Rafael
Comment 8 Anonymous Emailer 2008-02-17 14:37:06 UTC
Reply-To: email@example.com On Sun, Feb 17, 2008 at 11:18:23PM +0100, Rafael J. Wysocki wrote: > Can you point me to the patch, please? > > I'm running the current mainline and seeing this as well. http://cgit.freedesktop.org/hal/commit/?id=4541abd23fd02118a1a7f8b825aed338d2a5d638
Comment 9 Zhang Rui 2008-02-17 19:49:51 UTC
(In reply to comment #0) > me@gnu:~$ dmesg|grep battery > ACPI: Battery Slot [C1ED] (battery present) > ACPI: Battery Slot [C1EC] (battery absent) > It should be clear, that kpowersave (or some backend which it uses) > calculates > this informations wrong, yes, and it should be fixed by the patch referred in comment #8. > but I think the new way (if it's not a bug) to show > each potential battery, unless it's connected or not (and I think I don't > have > an second battery slot ;)) is wrong. No. In fact, it always works like this. ie. for your laptop, /proc always reports two batteries. > It's confusing for me, too, that in /proc/acpi/battery are C1EC and C1ED > reoported and in /sys/class/power_supply/ C1EB and C1ED. This seems wrong for > me. this is really weird, would you please make a double check?
Comment 10 Patrick Matthäi 2008-02-17 22:44:50 UTC
me@gnu:~$ ls /proc/acpi/battery/ C1EC C1ED me@gnu:~$ ls /sys/class/power_supply/ C1EB C1ED me@gnu:~$ Okay, two different names.
Comment 11 Zhang Rui 2008-02-18 21:49:30 UTC
hah, I see. C1ED is the working battery and C1EB is the AC adapter. C1EC is not registered as a power supply device because the battery does not present.
Comment 12 Zhang Rui 2008-02-18 21:53:45 UTC
hmm, so the real problem is fixed. Close this bug and mark it as PATCH_ALREADY_AVAILABLE. Patrick, please re-open it if you still have any problems.