For at least a month I’ve had frequent total freezes of my Framework 13 laptop and sometimes even 3 times in sequence after rebooting. It always requires a forceful shutdown.
At this point I’m getting worried that it might be a hardware failure. But I have no way of knowing.
Most of the time the crashes are random. Pretty much all scenarios of prolonged and short time use, high and low performance use and on an input or when just not doing anything.
But I’ve had it now multiple times that immediately after rebooting that the system freezes after logging in.
It wasn’t too long ago that I installed Fedora from scratch so everything is relatively fresh installed.
Any tips or pointers would be appreciated. Thanks!
Definitely check the temps. Have pets? It would be worth taking the machine apart and cleaning the fans and vents. If the machine can not cool down fast enough it will send itself into a panic and shutdown/lock up. Just some things to try.
Depending on how heavily the machine has been used it could be the processor and heatsink might need to be repasted if it has been a few years and had lots of heavy processor use.
To rule out the SSD, try booting from a LIVE USB and see if the same thing happens. Have seen things like this happen in the past and it was a faulty SSD that had not reported being bad yet.
I got another freeze and was able to investigate it a bit more.
I used journalctl -b -1 and looked for the timecode where it froze and I found this.
So it seems my AMD driver crashed. During the freeze I was still able to get sound and could change the brightness of the screen. And I got some more processes happening after the AMD driver crash so everything else seemed to still be running.
Ah, it could be that the fedora systemd messages are interspersed in the crash, and it’s the fedora kernel ones you actually want. I would probably next feed a bit of that text into a search engine or an AI chat-window, to see if you can get some hints on the cause. It is likely that someone has posted about it on the web before.
Googling for the error code I only got this and some much older reddit posts:
So not sure if this is the same issue. Overall this still leaves me a bit in the dark since this is not the same kernel version as I have and they didn’t find a solution either.
I wouldn’t trust a chatbot to give me anything usable if there are not even any clear posts/issues that I can find
So
Your logs are a bit partial, and if you can add some more (prior to these logs) then more detail might emerge;
Are you OK with editing the kernel entry at the boot menu? If so, you could try appending amdgpu.dcdebugmask=0x10 - the worst is that it does not improve stability, and you reboot to get rid of it.
I’ve been getting occasional freezes with the 7x40 series lately too. I found this thread on GitLab; I haven’t tried any of the kernel parameter stuff, but running:
…via an SSH session from my phone has (so far) led to a complete recovery every time, without rebooting or losing any application state. (Sometimes it freezes again a few minutes later, but SSHing in and running the command again fixes it again.)
I think there was something in that thread about a correlation with GNOME’s Night Light, which I have since disabled. I haven’t had a freeze since then, but it hasn’t been long enough to draw any conclusions. I see you’re using KDE, but do you have an equivalent filter set up?
It really does seem to be just the display that freezes—once I was in the middle of a web call when it happened, and I was able to carry on the conversation uninterrupted.
