Bug 1467289 - fans full speed and crash after resume on thinkpad
fans full speed and crash after resume on thinkpad
Status: NEW
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
x86_64 Linux
unspecified Severity medium
: ---
: ---
Assigned To: Kernel Maintainer List
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2017-07-03 06:06 EDT by Gabriele
Modified: 2017-11-16 14:54 EST (History)
7 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
system log (30.72 KB, text/plain)
2017-09-14 11:37 EDT, Gabriele
no flags Details

  None (edit)
Description Gabriele 2017-07-03 06:06:08 EDT
Description of problem:
In Lenovo Thinkpad E540 with kernel version 4.11.6-201 after resume from suspend, fans start going to full speed and after few seconds the pc shuts down. The problem is still here also with newer 4.11.7-200

Version-Release number of selected component (if applicable): 
4.11.6-201 (where starts the problem for me)

How reproducible:
install Fedora 25 on a Lenovo Thinkpad E540 (don't know if also with other thinkpad models), and dnf update all the components

Steps to Reproduce:
1. Fresh install Fedora 25
2. dnf update
3. close lid (or suspend it in any way you prefer)
4. open lid (or resume how you prefer)
5. wait few seconds

Actual results:
fans start going full speed and after a while the computer shuts down

Expected results:
continue working

Additional info:
Fedora installed with LUKS encryption and LVM partitioning system default as it is proposed from the installation environment.
To identify the problem in the kernel I tried starting fedora from grub with kernel 4.8.6-300 (the one installed with Fedora installation), it has graphic problems (flickering, it was an old bug) but the resume works well.
Updating the bios not helped. Windows 10 in dual boot resume perfectly. Everything installed with UEFI and secure boot. Shutting down secure boot doesn't solve the problem.
Comment 1 Gabriele 2017-07-19 08:16:56 EDT
The problem is still present even after the upgrade to Fedora 26.
Comment 2 Gabriele 2017-09-14 11:37 EDT
Created attachment 1326117 [details]
system log

this is the log from when I press the power button in order to suspend. until it resumes and crashes. I cannot find anything very strange but the problem is still here even after several updates.
Comment 3 Gabriele 2017-09-14 12:19:33 EDT
I've downgraded the kernel to the version 4.8.16-300.fc25.x86_64 and here everything works fine. I don't have the time now to try every version from 4.8.16-300 to the 4.11.6-201 to see where started the problem. But it is clearly a kernel issue.
Comment 4 Fedora End Of Life 2017-11-16 14:54:30 EST
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. 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 '25'.

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 25 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.

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