https://bugzilla.kernel.org/show_bug.cgi?id=24492
--- Comment #31 from Lorenzo Masellis <masel...@fastwebnet.it> 2011-06-24
07:55:58 ---
New test with your latest patch. dmesg attached.
- Battery is discharging at boot. upower --monitor-detail running in
background. upower gets regular updates every 30 s, but it indicates
"energy-rate: 0 W", so it doesn't provide any estimate for discharge time.
Status and rate of discharge is sysfs appear to be correct and coherent with
procfs:
lorenzo@castor:~$ cat /proc/uptime; cat /sys/class/power_supply/BAT0/status;
cat /sys/class/power_supply/BAT0/power_now; cat /proc/acpi/battery/BAT0/state
897.25 714.53
Discharging
15285000
present: yes
capacity state: ok
charging state: discharging
present rate: 15285 mW
remaining capacity: 18660 mWh
present voltage: 15507 mV
- At t=1012 the charger is connected and the charging led goes on; this time
the battery is correctly reported as charging:
lorenzo@castor:~$ cat /proc/uptime; cat /sys/class/power_supply/BAT0/status;
cat /proc/acpi/battery/BAT0/state
1101.55 905.46
Charging
present: yes
capacity state: ok
charging state: charging
present rate: 16224 mW
remaining capacity: 18510 mWh
present voltage: 16707 mV
...but upower is still wrong and reports "fully charged" and still zero rate;
also, it stops receiving any more updates:
[09:44:52.906] device changed:
/org/freedesktop/UPower/devices/battery_BAT0
native-path:
/sys/devices/LNXSYSTM:00/device:00/PNP0A03:00/device:0a/PNP0C09:00/ACPI0001:00/ACPI0002:00/power_supply/BAT0
vendor: Lezinn
model: 01ZA
power supply: yes
updated: Fri Jun 24 09:44:52 2011 (0 seconds ago)
has history: yes
has statistics: yes
battery
present: yes
rechargeable: yes
state: fully-charged
energy: 18.14 Wh
energy-empty: 0 Wh
energy-full: 23.29 Wh
energy-full-design: 65.12 Wh
energy-rate: 0 W
voltage: 15.97 V
percentage: 77.8875%
capacity: 35.7647%
technology: lithium-ion
History (charge):
1308901487 77.888 fully-charged
1308901460 78.317 discharging
1308901430 78.918 discharging
1308901400 79.519 discharging
- In the meanwhile, sysfs continues to get updated:
lorenzo@castor:~$ cat /proc/uptime; cat /sys/class/power_supply/BAT0/status;
cat /sys/class/power_supply/BAT0/power_now; cat /proc/acpi/battery/BAT0/state
1390.74 1170.10
Charging
11376000
present: yes
capacity state: ok
charging state: charging
present rate: 11376 mW
remaining capacity: 19500 mWh
present voltage: 16750 mV
Conclusions:
- rate and detection of charging by sysfs seem to be correct;
- something prevents upower from getting the right power value;
- something prevents upower from getting updates after charger connection.
--
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.
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense..
http://p.sf.net/sfu/splunk-d2d-c1
_______________________________________________
acpi-bugzilla mailing list
acpi-bugzilla@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla
