Hi, i run Fedora on a Lenovo Thinkpad P15v Gen2 with a i7-11800H CPU. I started with Fedora 35 but the issues began only a few months ago.
Most of the time the symptoms began directly after booting the machine or never. There were different type of bugs:
Qemu virtmanager hangs and the process ends.
Firefox freezes on rightclick or whenever any dialog should open (e.g. “do you want to uninstall this extension?”)
Thunderbird freezes completely without any activity.
If any of these negative events occourd it was impossible to shutdown the machine. The shutdown never finished, only a hard power off made it possible to try a new run.
The firefox event was more reproducable. Most of the time, if i open 1-2 apps like file explorer and terminal and firefox directly after logging in and rightclick into firefox, i hit the freeze most of the time. That’s how i was debugging this in the last days with different combinations of devices plugged in.
The error did not occour in battery mode what made me look into the bios where i found the speedstep option. Since I disabled the function, the error never occoured again (only one day but it looks good).
So why am I here? I want to dive deeper and find out if there is a better solution for this problem. Maybe there is a kernel parameter that makes it possible to use this feature without bugs.
Or maybe there is some bug in fedora or the kernel, since the problems began only some months ago.
And even if I don’t find a better solution, maybe I can learn some new stuff trying out your ideas!
Is the problem still present with f39?
You might want to run a memory test just in case the problem is RAM.
Oh and check if there is newer firmware for your machine.
Two common sources of errors associated with higher CPU speeds need ruling out: overheating, possibly due to accumulated dust on cooling fins and fans, and memory errors. Some laptop models are better at collecting dust than others, so it is worth searching reports of dust buildup and cleaning for your model. Use memtest86plus version 6.20 or later running all cores and watching temperatures.
The SMART disk monitoring (in Gnome Disks or smartmontools for command-line) may provide historical peak temperatures of your storage devices which can tell you if the system has overheated in the past.
The problem primarily occours after (re-)booting without unusual high power usage. once everything is fine, thy system runs and runs, regardless what i do. there is no correlation with possible overheating.