https://bugzilla.kernel.org/show_bug.cgi?id=24492
--- Comment #38 from Lorenzo Masellis <masel...@fastwebnet.it> 2011-06-27 07:54:07 --- I use upower version 0.9.5 (stock debian stable package). I don't think it actually depends on current_now, since the patch removed it and and still the rate is correct. Seems that upower (at least in the version I use) gets the rate information directly from power_now, since once the value was corrected in sysfs upower began to report the correct rate. The problem, from my point of view, is: what triggers upower to read status and rate from sysfs every 30 s during discharge? And what causes it to stop triggering after charger reconnection? Is it something inside the kernel or something inside upower? If it could continue to update, it would notice the state change from full to charging. By the way, thanks much for your help and sorry if I can contribute only with testing and reporting. -- 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 of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 _______________________________________________ acpi-bugzilla mailing list acpi-bugzilla@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla
