A new regression for AMD APU’s is present in kernel 6.10 that wil cause intermittent full system crashes in combination with Mesa 24.1.5. The only option is to power down and restart the machine.
Kernel 6.9 is unaffected.
There are patches for both the kernel and Mesa available upstream, how would one go about to best report this on our local bugtrackers?
Since that discussion appears to be the upstream with the fix the only thing I would suggest is wait. Since everything from upstream flows down to the fedora packagers and then is pushed out after testing it should normally arrive here soon.
Gitlab is on a biweekly update schedule and fedora usually does a release after about a weeks testing time. This means there is always a delay between the fix being available and the time we receive it.
You can be one of the testers if you know the package name and then use dnf to update (that package or all) using the updates-testing repo
I’m hitting this crash too. I don’t see any reason to report it downstream. The people with the right expertise to debug and resolve the issue will be on the upstream issue tracker. Reporting downstream might be useful to encourage adoption of the fix after a fix exists.
In the upstream issue, I see a patch that’s labeled a workaround not fit to land upstream, and a suggestion that the problem might be fixed in a mesa update. But userspace should not be able to corrupt kernel memory. If this problem could be fixed via a mesa update, that would indicate a security vulnerability in the kernel.
So it kinda looks like this is not on track to be fixed.