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):
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.
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.ā)
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.
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.
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?
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
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.
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.
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.
but I know others who have this issue,