I was ready to update with the fact that Kernel 5.9 and 5.10 have seemed largely stable when the first full release of 5.10, which I had been running for a while without problems, managed to lock up. For the first time it has provided an error message that may be useful though. I am attaching a photo of the screen, but the message text was:
♦♦♦♦♦♦♦♦♦♦[50545.326736] [drm:amdgpu_job_timeout [amdgpu]] *ERROR* ring sdma0 timeout, signaled seq=283155, emitted seq=283157 [50545.326825] [drm:amdgpu_job_timeout [amdgpu]] *ERROR* Process information: process pid 0 thread pid 0 I've grabbed dmesg, dmesg.0, syslog, syslog.1 and the outputs of journalctl -b-1 and journalctl | grep systemd-sleep in case they are needed, but systemd-analyze blame is failing because apport- autoreport.service is still running for some reason (not that the output of that is captured in my script for this). ** Attachment added: "Error message screenshot" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928600/+attachment/5509158/+files/amdgpu_error.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928600 Title: [amdgpu] Gnome locks up with artifacts on screen and [drm:amdgpu_dm_commit_planes [amdgpu]] *ERROR* Waiting for fences timed out! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928600/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
