Bug 2004903 - Fans do not spin up after waking from standby on Linux 5.14
Summary: Fans do not spin up after waking from standby on Linux 5.14
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 34
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-09-16 11:55 UTC by Robin Jacobs
Modified: 2021-09-24 20:29 UTC (History)
19 users (show)

Fixed In Version: kernel-5.14.6-300.fc35
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-09-24 20:29:44 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
journalctl --no-hostname -k (113.79 KB, text/plain)
2021-09-16 11:55 UTC, Robin Jacobs
no flags Details

Description Robin Jacobs 2021-09-16 11:55:41 UTC
Created attachment 1823553 [details]
journalctl --no-hostname -k

Created attachment 1823553 [details]
journalctl --no-hostname -k

1. Please describe the problem:

With Linux 5.14.4, on my HP Envy x360 13-ay0003nd laptop, when putting the system to sleep (either through Gnome or `systemctl suspend`), everything switches off as you would expect. Upon waking the system, however, there 2 are issues that persist until the system is rebooted:
- Brightness controls no longer work (these are the F2 and F3 keys), though volume controls work fine.
- The system fans do not spin up, ever, even when the system reaches critical temperatures. This is potentially dangerous to the hardware (... and to my lap, as it turns out.) 


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

5.14.4-300.fc34.x86_64


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 :

This issue was not present in Linux 5.13, as suspend simply did not work (due to s2idle compatibility problems with AMD CPUs, to my understanding). As such, this problem is new to Linux 5.14 in that this state could not be reached before.


4. Can you reproduce this issue? If so, please provide the steps to reproduce
   the issue below:

1. Boot up laptop.
2. `systemctl suspend`
3. Wake and unlock system.
4. Launch a game and watch temperatures rise to above 100°C without the fans ever spinning up.


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``:

This pulled in 5.15.0-0.rc1.12.fc36.x86_64.
I can confirm that on 5.15-rc1 this bug does not occur. Both brightness controls and system fans appear to work correctly after resuming from suspend.

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

Not that I'm aware.

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.

Attached.

More info:
- Fedora 34
- Linux kernel 5.14.4-300.fc34.x86_64 (downloaded with Koji as part of kernel test week)
- HP Envy x360 13-ay0003nd convertible laptop
- AMD Ryzen 4700U

I'm marking this as high priority due to the potential hardware damage resulting from fans not spinning up, as regular users who do not keep an eye on this may not even notice. I hope this is considered appropriate.

Comment 1 Robin Jacobs 2021-09-16 16:51:12 UTC
I just pulled in 5.15-rc1 (5.15.0-0.rc1.12.fc36.x86_64) from Fedora Rawhide and can confirm that this bug appears to be fixed in 5.15.

This appears to be related to these relatively simple-looking patches that as far as I can tell are merged in 5.15-rc1: https://gitlab.freedesktop.org/drm/amd/-/issues/1629#note_1063590

I'll ask the same thing I asked on that ticket on freedesktop's Gitlab;
Can I petition for this (relatively simple-looking) fix to be backported to 5.14? I am comfortable enough running 5.15 RC on my own machine, but I fear for damage to the hardware of people who might not even notice that this is happening.

I don't know what the right channels are to make these sort of requests, but system fans ceasing to function seems like a rather critical issue to me.

Comment 2 Justin M. Forbes 2021-09-16 18:22:45 UTC
Yes, that patch is queued to stable, but is not in the 5.14.5 kernel building right now. It should appear in 5.14.6 for Fedora, and I think 5.14.7 upstream.  As the 5.14 kernels for F34/33 are just test kernels right now, it will be there before anything is ever submitted to updates-testing for stable releases.

Comment 3 Robin Jacobs 2021-09-16 21:13:07 UTC
(In reply to Justin M. Forbes from comment #2)
> Yes, that patch is queued to stable, but is not in the 5.14.5 kernel
> building right now. It should appear in 5.14.6 for Fedora, and I think
> 5.14.7 upstream.  As the 5.14 kernels for F34/33 are just test kernels right
> now, it will be there before anything is ever submitted to updates-testing
> for stable releases.

Wonderful, thank you! Given the fix will be released before 5.14 ends up being pushed out to regular users, I guess this issue is resolved :)

Comment 4 Fedora Update System 2021-09-19 15:57:11 UTC
FEDORA-2021-db15e04083 has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2021-db15e04083

Comment 5 Fedora Update System 2021-09-20 05:11:03 UTC
FEDORA-2021-db15e04083 has been pushed to the Fedora 35 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-db15e04083`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-db15e04083

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 6 Fedora Update System 2021-09-24 20:29:44 UTC
FEDORA-2021-db15e04083 has been pushed to the Fedora 35 stable repository.
If problem still persists, please make note of it in this bug report.


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