weird crashes on the newest tumbleweed snapshot

hey people on the internet, I updated my tumbleweed to 20241002 and since then, the system would randomly freeze and crash, and automatically reboot after a short while. It also happens when waking from suspend. Does this happen to anyone else?

6 points · 6 comments · view on lemmy.world

6 Comments

Archaeopteryx@lemmy.nz · 3 pts · 1y (2 replies)

Hey,

No issues from my side so far. Have you tried to rollback to see if it's related to the update? Could also be a hardware error that just happened to occur at the same time as the update.

toothbrush@lemmy.blahaj.zone · 3 pts · 1y (1 reply)

Thanks for writing! Little update: I rolled it back to an old snapshot, the problem is gone. It really seems to be the update! My guess is a bug in the AMD graphics driver, because there were rare visual artifacts too. I hope they fix it soon!

Archaeopteryx@lemmy.nz · 3 pts · 1y

Glad to hear that a snapshot saved your day. Probably the most usefull feature in TW.

sugar_in_your_tea@sh.itjust.works · 2 pts · 1y (1 reply)

What kind of hardware are you running on?

I had some really weird behavior recently (like a week before this post; in my case, the external display would disconnect), but it got fixed with an update. I've also had weird freezing/crashing issues ever since getting my 1st gen Ryzen (bought at launch; probably a HW issue that I never bothered to RMA), and it can be stable for weeks or months or crash multiple times in a day.

If you can post the HW you have, maybe someone has a similar issue.

toothbrush@lemmy.blahaj.zone · 2 pts · 1y

thanks for the response, I have a Vega 64 GPU, a MSI B650 motherboard and a Ryzen 7800X3D cpu. It probably is a bug in the AMD driver, there are some reports of similar problems on the opensuse forums. I hope it gets fixed without me having to file a bug report.

toothbrush@lemmy.blahaj.zone · 1 pts · 1y

To everyone finding this post, the problem was my mainboard (MSI something something gaming+wifi). I had to disable bluetooth(using kde settings). It works now.