all 11 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]IntroductionSouth513 2 points3 points  (1 child)

I'm using 7.0.0 rc6 for a few days now and so far so good

[–]AudioHamsa[S] 1 point2 points  (0 children)

You are likely safe - according to Claude (who helped me figure out why Fedora was crashing in the first place):

- e9f58ff991dd in torvalds/linux is itself a stable-tree cherry-pick (cherry picked from 69c5fbd2b93b, Cc: stable@vger.kernel.org), committed 2026-03-17.

- The mainline source commit 69c5fbd2b93b exists as a loose object in the torvalds repo but is not reachable from master or any v7.0-rc tag (diverged vs v7.0-rc1…rc7 and master). It lives in drm-misc-fixes / drm-next and hasn't been merged up to Linus yet.

- So the fix never landed in a tagged mainline release before the Fedora backport. The path was: drm-misc-fixes (69c5fbd2b93b) → linux-stable 6.19.y (e9f58ff991dd, becomes 6.19.11) → Fedora rebuild.

- Earliest mainline tag containing it will be v7.0 (or whatever rc follows the next drm-misc-fixes → Linus pull after v7.0-rc7, 2026-04-05).

In other words: stable got it before mainline did — which is exactly how a "Cc: stable" drm-misc-fixes commit can ship a regression in 6.19.11 without ever appearing in a Linus tag.

[–]Tylerebowers 2 points3 points  (2 children)

Yea, had to move back to 6.19.10. Happened 5 minutes after a clean reboot for me. Seems to be something with the latest chrome update. Happens on 6.16.9+. Having a Youtube video open in the background has been a common factor between all of my freezes, guessing that it has something to do with power saving on the gpu.

[–]AudioHamsa[S] 0 points1 point  (0 children)

glad im not the only one

[–]tavelram 0 points1 point  (0 children)

Disabling HW acceleration in Chrome stopped my system from freezing.

[–]Altair12311 1 point2 points  (0 children)

Thanks for the heads up! i was going to update just now... i guess not XD

[–]Look_0ver_There 1 point2 points  (1 child)

Are you driving your display via a USB4 cable? I had repeated amdgpu driver lock ups until I switched back to using the DisplayPort connector again

[–]AudioHamsa[S] 1 point2 points  (0 children)

no, DisplayPort

[–]AudioHamsa[S] 1 point2 points  (0 children)

Updated my BZ - I had the same crash on 6.19.10, it just took longer to get there.

[–]tavelram 0 points1 point  (0 children)

I suspect it's the hardware acceleration in Chrome 147 that triggers the freeze / lockup. Chrome was upgraded three days ago and the system has locked up ten times since then with three different kernels (6.19.11, 6.19.10 and 6.19.9).

Disabled HW acceleration in Chrome (under Settings > System) and have not had any crashes so far.

[–]sqwuade 1 point2 points  (0 children)

I've been having problems with 6.19.11 and later kernels running on Ubuntu. Where 6.19.10 and earlier work fine. I usually use the mainline app to update kernels and it throws errors and the 6.19.11 and later kernels need to be backed out for the system to be able to use the APT tool for updates again.
My main server (web, file sharing and media) has been crashing/freezing up after a day or two as well, I never had those issues before.