Red Hat Bugzilla – Bug 1273547
Latest Fedora kernel 4.2.3-200.fc22 does not charge battery at all, on ThinkPad X1 Carbon
Last modified: 2016-07-19 15:20:27 EDT
Description of problem:
Latest Fedora kernel, 4.2.3-200.fc22, installed on stable track Fedora 22 machine.
Machine is Lenovo ThinkPad X1 Carbon
New kernel will not charge battery, ultimately, of course, leading to failed power state.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install Fedora 22 on ThinkPad X1 Carbon
2. Update to latest patch levels with `dnf update -y`
3. Observe battery depleting, and ultimately, laptop hibernating.
Battery does not charge.
Battery to charge, and power management to work as normal.
3rd Gen X1 Carbon; type 20BT
Does the battery charge with the machine powered off?
Good question; I haven't tested that. Presumably yes, but I'll verify later after work and get back to you. (This is my sole work machine I'm afraid).
FWIW, normal battery functionality exists when I'm running the previous kernel, in my case 4.1.8-200.fc22
I can confirm battery functions normally and charges when the laptop is powered off; also when running kernel 4.1.8-200.fc22.
The behavior only exhibits when running 4.2.3-200.fc22.
Please let me know what you need me to gather to help diagnose this; I'm happy to provide stuff! :-)
Can you attach the contents of /sys/class/power_supply/BAT*/uevent for me please?
I rebooted into the 4.2.3 kernel on full charge.
[dpeacock@frodo ~]$ cat /sys/class/power_supply/BAT0/uevent
Inexplicably, after a bunch of rebooting to test this, and no config changes, battery function appears to be working fine again!
Argh! I don't know if this is an intermittent bug or if something was out of whack immediately after the update, but I'll let you know if it occurs again.
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.