Closed jadams closed 8 months ago
Can confirm, also on an all AMD host. It's basically unusably slow unfortunately.
+1 on Bazzite Gnome. AMD CPU and GPU, would love to see if others on intel cpus are effected aswell
Should be fixed soon, thanks for the reports. For the meantime I recommend pinning the previous image.
This is now fixed.
Sorry the correction took so long, I'm out sick atm and a number of maintainers are out for SCALE and similar events.
Fix is to version gate the fsync kernel, meaning we can conduct more testing of changes and very quickly revert should a situation like this arise again without asking users to pin a build.
Hopefully this is the last time an issue like this stays open as long as this one has, assuming it slips by testing in the first place.
Same on my Steam Deck.
Same on my Steam Deck.
If you update it'll be fixed.
Yes i updated, but no different
This would be a different issue then, is this an LCD deck or OLED?
This would be a different issue then, is this an LCD deck or OLED?
I had an update to kernel 6.7.4 2 hours ago. everything was fine there. Now I'm back on 6.7.9 and the performance got worse
Steam Deck LCD
Steam Deck LCD
Definitely unrelated then, the LCD deck has AMD p-state unavailable due to a firmware limitation, and this issue was a bug in the amd-pstate driver in the kernel. Please open a new issue and include all the detail you can.
OK thx i did a new issue for this
Describe the bug
All performance degraded when booting into latest update with 6.7.9-206.fsync.fc39.x86_64 kernel. Including soft locks and multiple seconds before apps load, running from nvme. GPU accelerated apps that previously ran at >100fps were running at <20fps
Kdiskmark speeds were >3000MB/s read and >2000MB/s write on 6.7.9-203.fsync.fc39.x86_64
Kdiskmark speeds were <2000MB/s read and <500MB/s write on 6.7.9-203.fsync.fc39.x86_64
What did you expect to happen?
No performance degradation
Output of
rpm-ostree status
Hardware
Extra information or context
Rolled back deployment, pinned current (203), and disabled auto update to stay on 203 until resolved.