Thanks. It *looks* like the amdgpu kernel driver didn't survive sleeping/resuming and then nothing could use the GPU anymore:
Mär 17 08:00:57 MOONBASE kernel: [drm] free PSP TMR buffer Mär 17 08:01:02 MOONBASE kernel: [drm] PCIE GART of 512M enabled (table at 0x0000008000000000). Mär 17 08:01:02 MOONBASE kernel: [drm] PSP is resuming... Mär 17 08:01:02 MOONBASE kernel: [drm] reserve 0xa00000 from 0x800f400000 for PSP TMR Mär 17 08:01:02 MOONBASE kernel: amdgpu 0000:03:00.0: amdgpu: RAS: optional ras ta ucode is not available Mär 17 08:01:02 MOONBASE kernel: amdgpu 0000:03:00.0: amdgpu: RAP: optional rap ta ucode is not available Mär 17 08:01:02 MOONBASE kernel: amdgpu 0000:03:00.0: amdgpu: SECUREDISPLAY: securedisplay ta ucode is not available Mär 17 08:01:02 MOONBASE kernel: amdgpu 0000:03:00.0: amdgpu: SMU is resuming... Mär 17 08:01:05 MOONBASE gnome-shell[2532]: amdgpu: The CS has been rejected, see dmesg for more information (-62). Mär 17 08:01:05 MOONBASE gnome-shell[2532]: amdgpu: The CS has been rejected, see dmesg for more information (-22). Mär 17 08:01:05 MOONBASE kernel: amdgpu 0000:03:00.0: amdgpu: RunBtc failed! Mär 17 08:01:05 MOONBASE kernel: amdgpu 0000:03:00.0: amdgpu: Failed to setup smc hw! Mär 17 08:01:05 MOONBASE kernel: [drm:amdgpu_device_ip_resume_phase2 [amdgpu]] *ERROR* resume of IP block <smu> failed -62 Mär 17 08:01:05 MOONBASE kernel: amdgpu 0000:03:00.0: amdgpu: amdgpu_device_ip_resume failed (-62). Mär 17 08:01:06 MOONBASE tracker-store[6301]: OK Mär 17 08:01:06 MOONBASE systemd[2205]: tracker-store.service: Succeeded. Mär 17 08:01:06 MOONBASE /usr/lib/gdm3/gdm-x-session[2319]: amdgpu: The CS has been rejected, see dmesg for more information (-22). Mär 17 08:02:00 MOONBASE gnome-shell[2532]: amdgpu: The CS has been rejected, see dmesg for more information (-22). Mär 17 08:02:01 MOONBASE /usr/lib/gdm3/gdm-x-session[2319]: amdgpu: The CS has been rejected, see dmesg for more information (-22). So I suggest this is a kernel bug in the 'amdgpu' driver. Your best options might be to try: * Ubuntu 22.04 (preview) http://cdimage.ubuntu.com/daily-live/current/ or * Other kernels: https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=M;O=D ** Summary changed: - Locked Ubuntu is frozen and cannot be unlocked + [amdgpu] Locked Ubuntu is frozen and cannot be unlocked ** Tags added: amdgpu ** Package changed: ubuntu => linux-hwe-5.13 (Ubuntu) ** Changed in: linux-hwe-5.13 (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1964711 Title: [amdgpu] Locked Ubuntu is frozen and cannot be unlocked Status in linux-hwe-5.13 package in Ubuntu: New Bug description: After locking Ubuntu and leaving it unattended for a while, the operating system cannot be unlocked anymore. No means of user input (e.g. typing on the keyboard, moving the mouse) produce the lock screen and I have to shut down my computer by pressing down the power button. The attached monitor does not receive a signal from the computer during these attempts. This started to happen several weeks ago and worked without a problem before then. Due to the nature of this issue, I can neither report any errors occurring nor can I observe any other out of the ordinary things from happening. Thus, I don’t know which package is causing the issue. Also, this issue happens every time I leave the computer unattended for a longer time and lock it. However, locking it and triggering an input immediately after does produce the lock screen, so the lock screen seems to work in principle. Description: Ubuntu 20.04.4 LTS Release: 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1964711/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
