Description of problem: I am having an odd thing happen when my screen locks (due to inactivity). Specifically, when I let the system lock and screen turn off, the CPU fan turns on full noise (top speed), or possibly GPU fans I need to verify this. Then turns off, though it feels as though it could go on and stay stuck permanently on. I am also having other power management issues (unable to wake it up when it hibernates/sleeps). I have recently updated from Fedora 35 to 36 Beta Workstation edition, I didn’t have this issue earlier. I noticed there are newer kernel versions available :slightly_smiling_face: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. If I wait my system will go into a lock screen state or standby mode 2. When the screen starts to get back the CPU/GPU fans go into full speed mode. 3.After a while they turn off. If I wake up the system sometimes the fans go into high speed mode again but then turn on once in the system again
I am sorry if this is a poor descirption, I am not too sure if this is enough info. I will be able to clarify whether the CPU fans are the ones going at high speed or the video card tomorrow when I get the case off and inspect the hardware.
Proposed as a Blocker for 36-final by Fedora user bennyisaiah using the blocker tracking app because: Please see above Bug logged and support request from community here https://ask.fedoraproject.org/t/recommended-process-for-logging-a-bug-on-beta-releases/21746/2 I am proposing to block release as I have spoken to numerous people in the Fedora community on the Matrix IRC chat and they report a similar issue yet unsure if its kernel related or (Shell) Gnome related. I also am unable to wake up the system from hiberate or sleep mode. I did not have these issues so much with Fedora 34 or 35. I do not want to hold up the release and I can get a new computer soon, but I love Fedora and dont want any other system. Please help me troubleshoot. I have scanned through journalctl to detemine possible causes and tried to rollback to earlier kernel version to determine if it is indeed a kernel fault.
Benny, at minimum you need to provide your hardware details. Please provide output of `lspci -nn` and `lscpu | grep 'Model name'`. When this fan issue occurs, save a system journal by `journalctl -b > journal.txt` and upload it here. Also look into your computer, if it is a desktop, and see whether it's the CPU fan or GPU fan. Anyone else affected can follow the same steps. FWIW, I see something similar or same on my desktop with Radeon 580. When hibernating, the GPU fan spins up to 100% (very loud) for a few seconds, before the system powers down. I also saw it often when the monitor turned off due to an idle session, some months back, but I no longer see it (I'm still on F35, though). I believe there is some problem in gpu power management during those events, probably located in radeon drivers. However, it never had a negative impact on the system itself, it was just a fan ramping up to 100% for a few seconds, from time to time. I believe resume failure will be a different problem than the fan issue, so a separate bug should probably be created.
Discussed during the 2022-05-02 blocker review meeting: [0] The decision to classify this bug as a "RejectedBlocker (Final)" was made as the way this bug is currently described is too vague and does not demonstrate any kind of impact on any broader class of hardware than just this reporter's system. [0] https://meetbot.fedoraproject.org/fedora-blocker-review/2022-05-02/f36-blocker-review.2022-05-02-16.00.txt
Hi there sorry for the poor description, I feel like a fool now I forgot the hardware specs. You are correct Kamil it is a Radeon I am running. I am considering rolling back to Fedora 35 but I love this Gnome 42 its so great. Specs are as follows: [isaiah@fedora ~]$ lscpu | grep 'Model name' Model name: Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz [isaiah@fedora ~]$ lspci -nn 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor DRAM Controller [8086:0150] (rev 09) 00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor PCI Express Root Port [8086:0151] (rev 09) 00:14.0 USB controller [0c03]: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller [8086:1e31] (rev 04) 00:16.0 Communication controller [0780]: Intel Corporation 7 Series/C216 Chipset Family MEI Controller #1 [8086:1e3a] (rev 04) 00:1a.0 USB controller [0c03]: Intel Corporation 7 Series/C216 Chipset Family USB Enhanced Host Controller #2 [8086:1e2d] (rev 04) 00:1b.0 Audio device [0403]: Intel Corporation 7 Series/C216 Chipset Family High Definition Audio Controller [8086:1e20] (rev 04) 00:1c.0 PCI bridge [0604]: Intel Corporation 7 Series/C216 Chipset Family PCI Express Root Port 1 [8086:1e10] (rev c4) 00:1c.4 PCI bridge [0604]: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 5 [8086:1e18] (rev c4) 00:1c.5 PCI bridge [0604]: Intel Corporation 82801 PCI Bridge [8086:244e] (rev c4) 00:1c.6 PCI bridge [0604]: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 7 [8086:1e1c] (rev c4) 00:1c.7 PCI bridge [0604]: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 8 [8086:1e1e] (rev c4) 00:1d.0 USB controller [0c03]: Intel Corporation 7 Series/C216 Chipset Family USB Enhanced Host Controller #1 [8086:1e26] (rev 04) 00:1f.0 ISA bridge [0601]: Intel Corporation Z77 Express Chipset LPC Controller [8086:1e44] (rev 04) 00:1f.2 SATA controller [0106]: Intel Corporation 7 Series/C210 Series Chipset Family 6-port SATA Controller [AHCI mode] [8086:1e02] (rev 04) 00:1f.3 SMBus [0c05]: Intel Corporation 7 Series/C216 Chipset Family SMBus Controller [8086:1e22] (rev 04) 01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [1002:67df] (rev ef) 01:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere HDMI Audio [Radeon RX 470/480 / 570/580/590] [1002:aaf0] 03:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 09) 04:00.0 PCI bridge [0604]: ASMedia Technology Inc. ASM1083/1085 PCIe to PCI Bridge [1b21:1080] (rev 03) 06:00.0 Network controller [0280]: Intel Corporation Wi-Fi 6 AX200 [8086:2723] (rev 1a) 07:00.0 USB controller [0c03]: ASMedia Technology Inc. ASM1042 SuperSpeed USB Host Controller [1b21:1042]
Created attachment 1876776 [details] Output of the systemd (journalctl output) Please see attached a copy of the log journal of my system. I ensured that the last function of the system should be the fans spinning up.
This message is a reminder that Fedora Linux 36 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 36 on 2023-05-16. 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 'version' of '36'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 36 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 Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 36 entered end-of-life (EOL) status on 2023-05-16. Fedora Linux 36 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 Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.