Bug 26092 - /sys/devices/LNXSYSTM:00/LNXSYBUS:00/ACPI0003:00/power_supply/ACAD doesn't update always.
Summary: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/ACPI0003:00/power_supply/ACAD doesn't up...
Status: CLOSED DUPLICATE of bug 21722
Alias: None
Product: ACPI
Classification: Unclassified
Component: Power-Battery (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: Zhang Rui
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-01-04 19:09 UTC by TAXI
Modified: 2011-03-03 01:05 UTC (History)
3 users (show)

See Also:
Kernel Version:
Subsystem:
Regression: No
Bisected commit-id:


Attachments
Config File of the Kernel. (57.82 KB, text/plain)
2011-01-04 19:09 UTC, TAXI
Details

Description TAXI 2011-01-04 19:09:52 UTC
Created attachment 42362 [details]
Config File of the Kernel.

When I plug out my AC-Adapter and then run "cat /sys/devices/LNXSYSTM:00/LNXSYBUS:00/ACPI0003:00/power_supply/ACAD" at about 75% it still gives me a value of 1.
Cause of that for example cpufreqd doesn't recognize the change of the power source.

This is on a Lenovo IdeaPad S10 Netbook.

P.S. Sorry for my bad english.
Comment 1 Zhang Rui 2011-01-06 01:38:15 UTC
I have a patch shipped in upstream kernel recently, which fixes a similar problem.

commit 3151dbb04ad5a5bd6358371c0bfb457216d00205
Author: Zhang Rui <rui.zhang@intel.com>
Date:   Wed Dec 8 10:40:45 2010 +0800

    ACPI ac: update AC status upon sysfs query
    
    http://marc.info/?l=linux-acpi&m=128855015826728&w=2
    https://bugzilla.kernel.org/show_bug.cgi?id=21722
    
    Tested_by: Seblu <seblu@seblu.net>
    Signed-off-by: Zhang Rui <rui.zhang@intel.com>
    Signed-off-by: Len Brown <len.brown@intel.com>

would you please try the 2.6.37 kernel and verify if the problem still exists?
Comment 2 TAXI 2011-01-06 03:27:02 UTC
I applied the patch from https://bugzilla.kernel.org/show_bug.cgi?id=21722#c2 in my 2.6.36 kernel and it seems to work.

If the problem reappears later I will reopen this bug.

*** This bug has been marked as a duplicate of bug 21722 ***

Note You need to log in before you can comment on or make changes to this bug.