Bug 1748936 - Fedora with kernel 5.2.9 drains battery during suspend and remains warm
Summary: Fedora with kernel 5.2.9 drains battery during suspend and remains warm
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 30
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-09-04 13:52 UTC by Guy Marom
Modified: 2020-05-26 18:28 UTC (History)
21 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2020-05-26 18:28:04 UTC
Type: Bug
Embargoed:
marom.guy: needinfo+


Attachments (Terms of Use)
Kernel logs (214.92 KB, text/plain)
2019-09-04 17:36 UTC, Guy Marom
no flags Details

Description Guy Marom 2019-09-04 13:52:23 UTC
1. Please describe the problem: battery is drained while computer is suspended and the computer remains warm
My machine is a Lenovo P1 Gen2

2. What is the Version-Release number of the kernel: 5.2.9


3. Did it work previously in Fedora? If so, what kernel version did the issue
   *first* appear?  Old kernels are available for download at
   https://koji.fedoraproject.org/koji/packageinfo?packageID=8 : not sure


4. Can you reproduce this issue? If so, please provide the steps to reproduce
   the issue below:
a. Close computer lid so it will go to suspend (or user `systemctl suspend`)
b. Go to sleep
c. Wake up, touch computer - lid is warm. Resume from suspend and notice battery drained 30-40%

Reverting to kernel 5.1.20 solved this issue



5. Does this problem occur with the latest Rawhide kernel? To install the
   Rawhide kernel, run ``sudo dnf install fedora-repos-rawhide`` followed by
   ``sudo dnf update --enablerepo=rawhide kernel``: haven't tried


6. Are you running any modules that not shipped with directly Fedora's kernel?: nvidia drivers


7. Please attach the kernel logs. You can get the complete kernel log
   for a boot with ``journalctl --no-hostname -k > dmesg.txt``. If the
   issue occurred on a previous boot, use the journalctl ``-b`` flag.

Comment 1 Guy Marom 2019-09-04 13:55:52 UTC
I tried attaching the kernel logs but I receive an "ERR_ACCESS_DENIED"

Comment 2 Guy Marom 2019-09-04 17:36:23 UTC
Created attachment 1611606 [details]
Kernel logs

Comment 3 Alex Mason 2019-10-02 15:49:56 UTC
seeing the same issue on my P1 gen 2 under archlinux (5.3.1-arch1-1-ARCH). i noticed the same thing in my logs that "ACPI: Preparing to enter system sleep state S3" and "ACPI: Waking up from system sleep state S3" occur after resume within milliseconds of eachother
currently running the machine with dedicated graphics set in bios, if that matters

Comment 4 Tilen Leban 2019-10-03 07:29:13 UTC
I have the exactly same issue on my P1 gen 1 on Fedora 30 and I'm also running on the dedicated graphic card with proprietary drivers. The last kernel without this issue is 5.1.20.

Comment 5 anton tiniakov 2019-10-07 20:48:12 UTC
I had exactly the same issue with my "X1 Extreme Gen2"(which is almost identical to P1). After suspend the laptop was warm. And battery was draining at a rate around 10% in one hour. In my case removing all `acpi_osi` from kernel command line helped. I had 
"'acpi_osi=! acpi_osi=\"Windows 2009\" acpi_osi=Linux".  Now laptop is cold during the suspend and battery draining at the rate 1% per hour.

Kernel: 5.2.15
Lenovo Bios: 1.25

Comment 6 Tilen Leban 2019-10-26 15:32:13 UTC
I have no such command line kernel parameters. Anyway I've tried the latest kernel 5.3.7 and the issue still persists.

Comment 7 Tilen Leban 2019-11-12 09:15:28 UTC
It seems the issue was related to the proprietary nVidia driver as I can confirm that upgrading the driver to 440.31 solves the issue. Tested on kernel 5.3.9. You can read more about it here: https://www.nvidia.com/Download/driverResults.aspx/153226/en-us . The last release highlights bullet point states: "Fixed a bug that prevented NVIDIA GPUs from entering the low-power D3 state when entering suspend-to-idle (s2idle). [...]"

Comment 8 Tilen Leban 2019-12-02 09:04:42 UTC
It seems my comment above was a bit premature as the issue is not completely solved yet as with the latest kernels (tested up to 5.3.13) and latest nvidia drivers it only works some times but other times there's still battery drain in suspend. :/

Comment 9 Justin M. Forbes 2020-03-03 16:33:13 UTC
*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There are a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 30 kernel bugs.

Fedora 30 has now been rebased to 5.5.7-100.fc30.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you have moved on to Fedora 31, and are still experiencing this issue, please change the version to Fedora 31.

If you experience different issues, please open a new bug report for those.

Comment 10 Tilen Leban 2020-03-03 19:02:57 UTC
I'm still experiencing the issue with kernel 5.5.7 on Fedora 31

Comment 11 Guy Marom 2020-03-09 03:48:18 UTC
I'm no longer using Fedora so I can't say if this is still happening.

Comment 12 Ben Cotton 2020-04-30 20:20:19 UTC
This message is a reminder that Fedora 30 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-26.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '30'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 30 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 13 Ben Cotton 2020-05-26 18:28:04 UTC
Fedora 30 changed to end-of-life (EOL) status on 2020-05-26. Fedora 30 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
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.