CPU Fan speeds going very fast at random

Hi there,

I am just wondering what is the correct process for logging a bug in Beta releases.

AFAIK Fedora 36 is still technically in Beta and I am getting some odd issues,

I am unsure if I am permitted to log a bug here

https://qa.fedoraproject.org/blockerbugs/propose_bug

I am at this page:

but I know ordinarily bugs are reported with this process here:

https://docs.fedoraproject.org/en-US/quick-docs/howto-file-a-bug/#_step_0_create_a_bugzilla_account

But I beleive thats for stable releases.

Since I am not an engineer on the Fedora team I dont think I have the authority to log bugs as beta blockers right?

2 Likes

The bug filing process is for all supported Fedora releases and releases in development (rawhide and beta etc.)—so you should certainly file a bug.

The app in the screenshot is for proposing “blocker bugs”, i.e., bugs that are severe enough to need fixing in order for a beta release to be considered for stable release. So, once you file your bug, if you believe it should be a release blocker, you use this app to submit your bug for consideration. The QA and release engineering teams will then review your bug to decide what should be done—whether it should block the release based on the release criteria that is set out, or if it can be fixed as an update later in the release cycle and so on.

Edit: more information on the blocker bugs process here in the SOP (standard operating procedure):

https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process

3 Likes

Thank you kindly Ankur very much for clarifying, I logged a bug in the correct area.

I will try to log this bug in the beta blocker area too as I have heard in the fedora IRC chats on matrix that others have similar issues but have not reported them.

In your opinion would this bug

be considered “freeze exception” category since its quite serious as my fans sometimes get stuck on.

I dont want to hold up the beta from being released :face_with_hand_over_mouth: but I know others who have this issue,

1 Like

Your bug is marked as “private”, so we won’t be able to see it. Please change it to “public”, otherwise it can’t be looked at.

If not yet done, please also state which unmet Release Criterion makes this bug a Blocker bug.

FAQ on hardware-specific bugs: Blocker Bug FAQ - Fedora Project Wiki

2 Likes

Did you check whether temperatures are rising and there is a good reason for the fan to spin up?

watch -n 2 sensors

also, it would be important which fan is spinning up. (sensors will show you).

Another hint, review your the bug severity, this bug is certainly not urgent (advise: just leave it unspecified): Bug Fields

1 Like

You should include information about the hardware you’re running please and thanks.

2 Likes

Okay thanks I didn’t know it was set that way, i’m looking in there and cannot see how to change the setting from private to non private.

1 Like

Yes I linked the bug that I reported to the neofetch output it should be showing,

There should be a link in there. I will try to edit that now thanks

the bug report has been made public already: Issue #799: [kernel] CPU Fan speeds going very fast at random | rhbz#2080720 - blocker-review - Pagure.io

Comment 3 of the bug report says what outputs are requested. Quoting kparal in 2080720 – CPU Fan speeds going very fast at random

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.

1 Like

This is lspci :

[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]


[isaiah@fedora ~]$ lscpu | grep ‘Model name’
Model name: Intel(R) Core™ i5-3570K CPU @ 3.40GHz





I tried to upload the journalctl text file though it says only image files can be uploaded...:frowning: 


How do we upload text files here in the chat
1 Like

Please add / upload the information to the bug tracker, that’s where the bug is triaged and the information was requested.

.txt can be uploaded as attachment there.

Independent of the bug not being a release blocker, it’s still worth investigating and fixing the issue.

1 Like

I have heard from @kparal and he mentions it is a GPU issue for RADEON video cards.

Can I asked would this issue go away if I rolled back the kernel to an older release? The fans are very noisy when it happens.

He suggests a seperate bug should be created as it seems to be a GPU power management issue.

I have uploaded the journalctl in there it should be there now

I have taken the case off the PC box and checked and it is indeed the video card making all the noise.

2 Likes

I understood that he suggested to file the resume error as a separate bug (“I believe resume failure will be a different problem than the fan issue, so a separate bug should probably be created.”)

Didn’t see it.

2 Likes

Hmm it should be there now.

I just re uploaded it.

I also am running sensors now after installing it I will try to see what happens. Problem is it only happens when the screen goes blank or the screen locks.

Can you please provide some more information, it is hard to understand what is happening and what you are doing - please understand that we cannot see/hear your system so you need to be very descriptive.

  1. Starting off, your bug report says it’s the CPU fan, but “possibly GPU fans I need to verify this”. Have you verified which of these fans it is exactly? If so, please update the bug report with that relevant information.

  2. Your report has some conflicting infomation. Can you please be more clear on the order of the events - does the fan go to full speed right after the screen goes off? After the system suspends? After the system wakes from suspends? After the screen is turned back on by the system?

  • “when I let the system lock and screen turn off, the CPU fan turns on full noise” - is it right after screen off?
  • “When the screen starts to get back the CPU/GPU fans go into full speed mode” - or is it right after system is woken?
  1. Please help us read your journal log.
  • How did you collect the log? E.g. - Wait until system turns off monitor, hear fans speed up, wake up screen, open terminal and run journal -b > journal.txt?
  • Can you tell us the timestamp of when the fans sped up? If not, next time use a watch/phone to note the time that the fans speed up. That way we can correlate the time to the timestamps in the journal file.
    As of now, it’s too hard to know where in the log file we should look if we don’t have a timestamp and don’t know the sequence of events that occurred.

That being said, it looks like there was a coredump near the end of the journal. But without knowing the timeline of events, it’s hard to know whether it’s related or not.

Core Dump
May 04 00:35:37 fedora systemd-coredump[7366]: Process 7362 (nfsrahead) of user 0 dumped core.
                                               
                                               Module linux-vdso.so.1 with build-id 04b708c7c91e947d7413a24109a43e4cc798e340
                                               Module libpcre2-8.so.0 with build-id 2827cb8b86a0a697fa6e6646690d1b01de9b6fba
                                               Metadata for module libpcre2-8.so.0 owned by FDO found: {
                                                       "type" : "rpm",
                                                       "name" : "pcre2",
                                                       "version" : "10.39-1.fc36.1",
                                                       "architecture" : "x86_64",
                                                       "osCpe" : "cpe:/o:fedoraproject:fedora:36"
                                               }
                                               
                                               Module ld-linux-x86-64.so.2 with build-id 997994d4535f8c791738540c3e6ee8e46a752603
                                               Module libselinux.so.1 with build-id 9ee47929aa5779a0fe6469346be26bfa6426a516
                                               Metadata for module libselinux.so.1 owned by FDO found: {
                                                       "type" : "rpm",
                                                       "name" : "libselinux",
                                                       "version" : "3.3-4.fc36",
                                                       "architecture" : "x86_64",
                                                       "osCpe" : "cpe:/o:fedoraproject:fedora:36"
                                               }
                                               
                                               Module libblkid.so.1 with build-id 9e58123c73f92b29e14b080448cade11b65edde2
                                               Metadata for module libblkid.so.1 owned by FDO found: {
                                                       "type" : "rpm",
                                                       "name" : "util-linux",
                                                       "version" : "2.38-0.2.fc36",
                                                       "architecture" : "x86_64",
                                                       "osCpe" : "cpe:/o:fedoraproject:fedora:36"
                                               }
                                               
                                               Module libc.so.6 with build-id 6e7b96dfb83f0bdcb6a410469b82f86415e5ada3
                                               Module libmount.so.1 with build-id 598330551ee15a053368f71ffc841cc243654899
                                               Metadata for module libmount.so.1 owned by FDO found: {
                                                       "type" : "rpm",
                                                       "name" : "util-linux",
                                                       "version" : "2.38-0.2.fc36",
                                                       "architecture" : "x86_64",
                                                       "osCpe" : "cpe:/o:fedoraproject:fedora:36"
                                               }
                                               
                                               Module nfsrahead with build-id 5216b3d441a8d01b3b7eec51431e6a9336864cc1
                                               Metadata for module nfsrahead owned by FDO found: {
                                                       "type" : "rpm",
                                                       "name" : "nfs-utils",
                                                       "version" : "2.6.1-1.rc4.fc36",
                                                       "architecture" : "x86_64",
                                                       "osCpe" : "cpe:/o:fedoraproject:fedora:36"
                                               }
                                               
                                               Stack trace of thread 7362:
                                               #0  0x000055b89fd528ac main (nfsrahead + 0x28ac)
                                               #1  0x00007fc483556590 __libc_start_call_main (libc.so.6 + 0x2d590)
                                               #2  0x00007fc483556649 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2d649)
                                               #3  0x000055b89fd52be5 _start (nfsrahead + 0x2be5)
                                               ELF object binary architecture: AMD x86-64
1 Like

I’ve changed the title of this thread to better describe the problem.

okay forgive my ignorance.

  1. First I have confirmed as earlier noted it is indeed the GPU fans not CPU fans. I will amend this in the logged bug report.

  2. Yes correct the fan goes to full speed right after the screen goes black @kparal mentions the same issue in the bug report as a comment. Apparently this was a bug with Radeon GPU’s. It also goes to full speed right after the screen locks or screen goes to sleep.

  3. Correct I waited untill the system turns off monitor, hear fansspeed up, then I woke up the screen and ran the command journal -b > journal.txt

the journal timestamp was the exact moment it happened was when the last occurance happened. I.e it should be the last thing in the log I would presume.

I thought I mentioned that,. I will change that.

1 Like