With the new Debian Stable (Buster, kernel 4.19.0-5-amd64) the system reported wrong battery status on ASUS eeePC 1005PG. When discharging, it shows always 100% charge and voltage 65V instead of 12V. I made some tests with different kernel versions. The bug is in kernel 4.18 (Ubuntu 18.04.02) and 4.19 (Debian Stable). Not affected kernels are 4.9 (Debian Oldstable), 4.15 (Ubuntu 18.04.01) and 5.0 (Ubuntu 19.04). root@localhost:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/PNP0C0A:00/power_supply/BAT0$ cat manufacturer ASUS root@localhost:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/PNP0C0A:00/power_supply/BAT0$ cat model_name 1005PG Affected Kernel: uname -a Linux localhost.localdomain 4.19.0-5-amd64 #1 SMP Debian 4.19.37-5+deb10u1 (2019-07-19) x86_64 GNU/Linux root@localhost:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/PNP0C0A:00/power_supply/BAT0# cat status Discharging root@localhost:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/PNP0C0A:00/power_supply/BAT0# cat current_now 1000 root@localhost:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/PNP0C0A:00/power_supply/BAT0# cat charge_now 4200000 root@localhost:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/PNP0C0A:00/power_supply/BAT0# cat voltage_now 65535000 Not affected Kernel: root@localhost:~$ uname -a Linux localhost.localdomain 4.9.0-9-amd64 #1 SMP Debian 4.9.168-1+deb9u4 (2019-07-19) x86_64 GNU/Linux root@localhost:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/PNP0C0A:00/power_supply/BAT0$ cat status Discharging root@localhost:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/PNP0C0A:00/power_supply/BAT0$ cat current_now 657000 root@localhost:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/PNP0C0A:00/power_supply/BAT0$ cat charge_now 3794000 root@localhost:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/PNP0C0A:00/power_supply/BAT0$ cat voltage_now 12183000 Please can you fix this issue.
please attach the dmesg output after boot, as well as acpidump output.
Created attachment 285491 [details] acpidump-acpica.txt
Created attachment 285493 [details] dmesg.txt
Sorry for the late response. Please see the attached files. Regards, J. Mueller
Created attachment 296679 [details] Proposed fix I believe this is the same problem as https://bugzilla.kernel.org/show_bug.cgi?id=203563 Can you try to apply the proposed patch and check if it fixes the problem for you
Created attachment 297183 [details] attachment-17534-0.html Hello, i am sorry but i am not familar with kernel patching and compiling. I found out that the kernel from the backports for debian 10 (buster) is not affected (5.10.0-0.bpo.5-amd64 at the moment). So i am using the backports kernel for a longer time and it works very well. Thank you for your efforts. Regards J. Mueller On Thu, 6 May, 2021 at 11:34 PM, bugzilla-daemon@bugzilla.kernel.org <bugzilla-daemon@bugzilla.kernel.org> wrote: To: jmuell@mail2world.com https://bugzilla.kernel.org/show_bug.cgi?id=204303 Bjarki Geir Benediktsson (BjarkiGeirBenediktsson@gmail.com<mailto:BjarkiGeirBenediktsson@gmail.com>) changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |BjarkiGeirBenediktsson@gmai | |l.com --- Comment #5 from Bjarki Geir Benediktsson (BjarkiGeirBenediktsson@gmail.com<mailto:BjarkiGeirBenediktsson@gmail.com>) --- Created attachment 296679 [details] --> https://bugzilla.kernel.org/attachment.cgi?id=296679&action=edit Proposed fix I believe this is the same problem as https://bugzilla.kernel.org/show_bug.cgi?id=203563 Can you try to apply the proposed patch and check if it fixes the problem for you
Closed because newer Debian kernel from backports not affected.