Thanks a lot, Mario, for pointing me in the right direction. It's definitely MCBP what causes it. I've been testing it for a few hours, and it was _very_ easy to trigger.
It seems to only be triggered (or at least _more frequently_) when using multiple outputs, and USB-C DP => HDMI through docks. That would explain why it slipped through testing while being so pervasive in my particular setup.
This seems to be an active topic atm both in the GNOME Mutter GitLab and Ubuntu side (and others as well). Some references for the record:
Thanks a lot, Mario, for pointing me in the right direction. It's definitely MCBP what causes it. I've been testing it for a few hours, and it was _very_ easy to trigger.
It seems to only be triggered (or at least _more frequently_) when using multiple outputs, and USB-C DP => HDMI through docks. That would explain why it slipped through testing while being so pervasive in my particular setup.
This seems to be an active topic atm both in the GNOME Mutter GitLab and Ubuntu side (and others as well). Some references for the record:
1. https:/ /unix.stackexch ange.com/ questions/ 756281/ kernel- 6-5-2-seems- to-have- amdgpu- crash-on- no-retry- page-fault /www.reddit. com/r/Fedora/ comments/ 16wzpup/ how_to_ mitigate_ amdgpu_ crash_caused_ by_bug_ in/?rdt= 47451 /gitlab. freedesktop. org/drm/ amd/-/issues/ 2830 /gitlab. freedesktop. org/drm/ amd/-/issues/ 2971 /gitlab. gnome.org/ GNOME/mutter/ -/issues/ 3151
2. https:/
3. https:/
4. https:/
5. https:/
I don't know how to close this bug.