https://bugzilla.kernel.org/show_bug.cgi?id=24492
--- Comment #27 from Lorenzo Masellis <masel...@fastwebnet.it> 2011-06-22 09:44:23 --- The secon version of the Revome-etcetc.patch was applied to kernel 3.0.0-rc3. The previous patch (add_get_etcetc.patch) was not applied since I noticed it is included in the new one. Attached comes the output of dmesg. Below I describe the steps I used to reproduce the bug; each command is timed using /proc/uptime, for easier reference to the dmesg output. - Battery is discharging at boot. Discharging state is indicated correctly in sysfs: lorenzo@castor:~$ cat /proc/uptime; cat /sys/class/power_supply/BAT0/status 395.77 280.46 Discharging - Anyway, the rate of discharge in sysfs is wrong (seems to be current multiplied by 1 instead of voltage), while in procfs it makes sense; reading the procfs doesn't cause the sysfs to change its rate value to the correct one. lorenzo@castor:~$ cat /proc/uptime; cat /sys/class/power_supply/BAT0/power_now; cat /proc/acpi/battery/BAT0/state 655.94 528.29 1024000 present: yes capacity state: ok charging state: discharging present rate: 15360 mW remaining capacity: 18600 mWh present voltage: 15636 mV lorenzo@castor:~$ cat /proc/uptime; cat /sys/class/power_supply/BAT0/power_now 663.71 535.88 1041000 - Reloading the SBS module doesn't correct the problem: lorenzo@castor:~$ cat /proc/uptime; sudo rmmod sbs 831.79 695.63 [sudo] password for lorenzo: lorenzo@castor:~$ cat /proc/uptime; sudo modprobe sbs 861.92 724.80 lorenzo@castor:~$ cat /proc/uptime; cat /sys/class/power_supply/BAT0/power_now 881.26 743.19 1046000 - At t=1028 the charger is connected and the charging led goes on; this is not detected by the kernel, which instead reports the battery as full: lorenzo@castor:~$ cat /proc/uptime; cat /sys/class/power_supply/BAT0/status 1010.63 866.60 Discharging lorenzo@castor:~$ cat /proc/uptime; cat /sys/class/power_supply/BAT0/status 1037.76 893.13 Full - Differently from what I reported previously, now sysfs updates the value of charge regularly, but apparently the fact that the battery is wrongly indicated as full prevents upower and gnome-power-manager to catch the updates; after some time the sysfs reports again "charging" but mysteriously enough upower doesn't notice the change and monitoring upower waits forever without any updates: lorenzo@castor:~$ cat /proc/uptime; cat /sys/class/power_supply/BAT0/status; upower --monitor-detail 1749.73 1568.61 Charging Monitoring activity from the power daemon. Press Ctrl+C to cancel. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. ------------------------------------------------------------------------------ Simplify data backup and recovery for your virtual environment with vRanger. Installation's a snap, and flexible recovery options mean your data is safe, secure and there when you need it. Data protection magic? Nope - It's vRanger. Get your free trial download today. http://p.sf.net/sfu/quest-sfdev2dev _______________________________________________ acpi-bugzilla mailing list acpi-bugzilla@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla
