Prevent thermal shutdown during boot process
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
HWE Next |
Fix Released
|
Undecided
|
Unassigned | ||
linux (Ubuntu) |
Fix Released
|
Critical
|
Unassigned | ||
Focal |
Won't Fix
|
Undecided
|
Unassigned | ||
Groovy |
Fix Released
|
Critical
|
Unassigned | ||
Hirsute |
Fix Released
|
Critical
|
Unassigned | ||
linux-oem-5.10 (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Focal |
Fix Released
|
Critical
|
Unassigned | ||
linux-oem-5.6 (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Focal |
Fix Released
|
Critical
|
Unassigned |
Bug Description
[Impact]
Surprising thermal shutdown at boot on Intel based mobile workstations.
[Fix]
Since these thermal devcies are not in ACPI ThermalZone, OS shouldn't
shutdown the system.
These critial temperatures are for usespace to handle, so let kernel
know it shouldn't handle it.
SRU for stable kernels will be sent after the fix is in upstream.
[Test]
Use reboot stress as a reproducer. 5% chance to see a surprising
shutdown at boot.
With the fix applied, the thermal shutdown is no longer reproducible.
[Where problems could occur]
For ACPI based platforms, we still have "acpitz" to protect systems from
overheating. If these acpitz sensors don't work, then the system could
face real overheating issue.
CVE References
affects: | linux (Ubuntu) → linux-oem-5.6 (Ubuntu) |
Changed in linux-oem-5.6 (Ubuntu): | |
status: | New → Invalid |
Changed in linux-oem-5.6 (Ubuntu Focal): | |
status: | New → Confirmed |
importance: | Undecided → Critical |
tags: | added: oem-priority originate-from-1905514 stella |
no longer affects: | linux-oem-5.6 (Ubuntu Groovy) |
no longer affects: | linux-oem-5.6 (Ubuntu Hirsute) |
Changed in linux (Ubuntu Focal): | |
status: | New → Won't Fix |
Changed in linux-oem-5.6 (Ubuntu Focal): | |
status: | Confirmed → Fix Committed |
tags: |
added: verification-done-focal removed: verification-needed-focal |
Changed in linux-oem-5.10 (Ubuntu): | |
status: | New → Invalid |
Changed in linux (Ubuntu Groovy): | |
status: | New → Confirmed |
Changed in linux (Ubuntu Hirsute): | |
status: | Incomplete → Confirmed |
Changed in linux-oem-5.10 (Ubuntu Focal): | |
status: | New → Confirmed |
Changed in linux (Ubuntu Groovy): | |
importance: | Undecided → Critical |
Changed in linux (Ubuntu Hirsute): | |
importance: | Undecided → Critical |
Changed in linux-oem-5.10 (Ubuntu Focal): | |
importance: | Undecided → Critical |
Changed in linux-oem-5.10 (Ubuntu Focal): | |
status: | Confirmed → Fix Committed |
Changed in linux (Ubuntu Groovy): | |
status: | Confirmed → Fix Committed |
tags: |
added: verification-done-groovy removed: verification-needed-groovy |
Changed in hwe-next: | |
status: | New → Fix Released |
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
apport-collect 1906168
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the Ubuntu Kernel Team.