Bug 1370528

Summary: [kernel] fan control by IBM ACPI extensions leads to overheating of Lenovo ThinkPad T400
Product: [Fedora] Fedora Reporter: Joachim Frieben <jfrieben>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 31CC: gansalmon, ichavero, itamar, jfrieben, jonathan, kernel-maint, madhu.chinakonda, mchehab
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-11-24 16:55:45 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Joachim Frieben 2016-08-26 14:50:06 UTC
Description of problem:
Current Fedora 25 installed on a Lenovo ThinkPad T400 shows a poor fan control managed by the IBM ACPI extensions of the Linux kernel. The default mode "auto" keeps the fan speed around 3500 RPM regardless of the CPU temperature reported by the "sensors" command. When running the syetem under full load for a while, emergency shutdown caused by overheating of the CPU can happen.

Version-Release number of selected component (if applicable):
kernel-4.8.0-0.rc2.git3.1.fc25

How reproducible:
Always

Steps to Reproduce:
1. Run "sensors" when system is idle.
2. Run "sensors" when system is running under full load.

Actual results:
CPU temperature increases by about 35 °C, but the fan speed remains almost constant.

Expected results:
Fan speed is increased in order to attenuate temperature increase.

Additional info:
- This issue has been around for years, see bug 675433 where the reporter claims that the issue was absent before upgrading to Fedora 14 in early 2011 which means that we are actually dealing with a regression.
- It is not related to using a a debugging kernel such as 4.8.0-0.rc2.git3.1.fc25 or not.

Comment 1 Joachim Frieben 2016-08-26 14:55:13 UTC
- Output of 'sensors' when system is idle:

coretemp-isa-0000
Adapter: ISA adapter
Core 0:       +50.0°C  (high = +105.0°C, crit = +105.0°C)
Core 1:       +50.0°C  (high = +105.0°C, crit = +105.0°C)

acpitz-virtual-0
Adapter: Virtual device
temp1:        +50.0°C  (crit = +127.0°C)
temp2:        +51.0°C  (crit = +100.0°C)

thinkpad-isa-0000
Adapter: ISA adapter
fan1:        3435 RPM
temp1:        +50.0°C  
temp2:        +45.0°C  
temp3:        +34.0°C  
temp4:        +63.0°C  
temp5:        +38.0°C  
temp6:            N/A  
temp7:        +35.0°C  
temp8:            N/A  
temp9:        +36.0°C  
temp10:       +45.0°C  
temp11:       +40.0°C  
temp12:           N/A  
temp13:           N/A  
temp14:           N/A  
temp15:           N/A  
temp16:           N/A  

- Output of 'sensors' when system is running under full load:

coretemp-isa-0000
Adapter: ISA adapter
Core 0:       +85.0°C  (high = +105.0°C, crit = +105.0°C)
Core 1:       +84.0°C  (high = +105.0°C, crit = +105.0°C)

acpitz-virtual-0
Adapter: Virtual device
temp1:        +89.0°C  (crit = +127.0°C)
temp2:        +85.0°C  (crit = +100.0°C)

thinkpad-isa-0000
Adapter: ISA adapter
fan1:        3434 RPM
temp1:        +89.0°C  
temp2:        +51.0°C  
temp3:        +39.0°C  
temp4:        +81.0°C  
temp5:        +38.0°C  
temp6:            N/A  
temp7:        +36.0°C  
temp8:            N/A  
temp9:        +42.0°C  
temp10:       +53.0°C  
temp11:       +55.0°C  
temp12:           N/A  
temp13:           N/A  
temp14:           N/A  
temp15:           N/A  
temp16:           N/A  

Output of 'cat /proc/acpi/ibm/fan':
status:		enabled
speed:		3446
level:		auto

Comment 2 Laura Abbott 2017-01-17 01:18:22 UTC
*********** MASS BUG UPDATE **************
We apologize for the inconvenience.  There is 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 25 kernel bugs.
 
Fedora 25 has now been rebased to 4.9.3-200.fc25.  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 26, and are still experiencing this issue, please change the version to Fedora 26.
 
If you experience different issues, please open a new bug report for those.

Comment 3 Joachim Frieben 2017-01-17 18:41:45 UTC
(In reply to Laura Abbott from comment #2)
The issue persists even after upgrading to kernel-4.9.3-200.fc25.

Comment 4 Justin M. Forbes 2017-04-11 14:47:47 UTC
*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There is 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 25 kernel bugs.

Fedora 25 has now been rebased to 4.10.9-200.fc25.  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 26, and are still experiencing this issue, please change the version to Fedora 26.

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

Comment 5 Justin M. Forbes 2017-04-28 17:04:46 UTC
*********** MASS BUG UPDATE **************
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 2 weeks. If you are still experiencing this issue, please reopen and attach the 
relevant data from the latest kernel you are running and any data that might have been requested previously.

Comment 6 Joachim Frieben 2017-04-28 18:37:17 UTC
(In reply to Justin M. Forbes from comment #4)
No change for current Fedora 25 including package kernel-4.10.12-200.fc25.

Comment 7 Fedora End Of Life 2017-11-16 19:28:33 UTC
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.

Comment 8 Fedora End Of Life 2017-12-12 10:24:17 UTC
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 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.

Comment 9 Joachim Frieben 2018-05-14 07:27:24 UTC
This issue continues to affect all supported Fedora releases including Fedora 28 with kernel package kernel-4.16.7-300.fc28. For the latter, command 'sensors' returns the following output for a Lenovo ThinkPad 400 running under full load:

coretemp-isa-0000
Adapter: ISA adapter
Core 0:       +84.0°C  (high = +105.0°C, crit = +105.0°C)
Core 1:       +85.0°C  (high = +105.0°C, crit = +105.0°C)

acpitz-virtual-0
Adapter: Virtual device
temp1:        +90.0°C  (crit = +127.0°C)
temp2:        +85.0°C  (crit = +100.0°C)

thinkpad-isa-0000
Adapter: ISA adapter
fan1:        3434 RPM
temp1:        +90.0°C  
temp2:        +52.0°C  
temp3:        +42.0°C  
temp4:        +81.0°C  
temp5:        +37.0°C  
temp6:            N/A  
temp7:        +34.0°C  
temp8:            N/A  
temp9:        +44.0°C  
temp10:       +54.0°C  
temp11:       +59.0°C  
temp12:           N/A  
temp13:           N/A  
temp14:           N/A  
temp15:           N/A  
temp16:           N/A

Comment 10 Justin M. Forbes 2018-07-23 14:53:01 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 28 kernel bugs.

Fedora 28 has now been rebased to 4.17.7-200.fc28.  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 experience different issues, please open a new bug report for those.

Comment 11 Joachim Frieben 2018-08-11 09:09:18 UTC
Issue persists on a Lenovo ThinkPad T400 with a discrete AMD Radeon RV620 video device. In this case, up to kernel 4.17.12-200.fc28, the fan speed is locked at about 3440 RPM and temperatures easily reach 90 °C.
Interestingly, when the chipset-integrated video device Intel GMA 4500MHD is used instead, then the fan speed is adjusted dynamically albeit always running at RPM values below that mentioned above.

Comment 12 Laura Abbott 2018-10-01 21:25:02 UTC
We apologize for the inconvenience.  There is 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 28 kernel bugs.
 
Fedora 28 has now been rebased to 4.18.10-300.fc28.  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 29, and are still experiencing this issue, please change the version to Fedora 29.
 
If you experience different issues, please open a new bug report for those.

Comment 13 Joachim Frieben 2018-10-02 09:50:16 UTC
Situation remains the same as described in comment 11 for kernel-4.18.10-300.fc28.

Comment 14 Justin M. Forbes 2019-01-29 16:25:34 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 28 kernel bugs.

Fedora 28 has now been rebased to 4.20.5-100.fc28.  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 29, and are still experiencing this issue, please change the version to Fedora 29.

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

Comment 15 Justin M. Forbes 2019-08-20 17:42:43 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 29 kernel bugs.

Fedora 29 has now been rebased to 5.2.9-100.fc29.  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 30, and are still experiencing this issue, please change the version to Fedora 30.

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

Comment 16 Justin M. Forbes 2019-09-17 20:08:15 UTC
*********** MASS BUG UPDATE **************
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 3 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.

Comment 17 Joachim Frieben 2020-02-06 18:48:01 UTC
(In reply to Justin M. Forbes from comment #15)
As of current Fedora 31 including kernel-5.4.12-200.fc31, temperatures still reach about 80°C which might be slightly lower than above because of the winter season with lower room temperatures. Anyway, the fan speed ist still constant, the fan spinning at about 3400 rpm when the discrete AMD Radeon video device is enabled.
When the low power chipset graphics with a lower thermal footprint is used instead, however, the fan speed is changing depending on the system load at speeds lower than those reported above.

Comment 18 Justin M. Forbes 2020-03-03 16:21:56 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 31 kernel bugs.

Fedora 31 has now been rebased to 5.5.7-200.fc31.  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 32, and are still experiencing this issue, please change the version to Fedora 32.

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

Comment 19 Joachim Frieben 2020-03-17 17:18:50 UTC
I do not see any improvement with kernel-5.5.7-200.fc31.

Comment 20 Ben Cotton 2020-11-03 14:57:50 UTC
This message is a reminder that Fedora 31 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24.
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 '31'.

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 31 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 21 Ben Cotton 2020-11-24 16:55:45 UTC
Fedora 31 changed to end-of-life (EOL) status on 2020-11-24. Fedora 31 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.