Public bug reported: I'm seeing this 2-3 times per week. My system is configured with "Linux Suspend" in the BIOS (not the Windows/Modern setting). Furthermore, when plugged in, my system does not sleep.
When I come up to my laptop after inactivity, the screens are dark (but as noted above, it is not suspended). If I click on a key and wait for both external monitors to light up, I can generally hit enter at that point, type my password and get in. If, however, I'm in a hurry or not thinking about it and just walk up to the machine, hit enter, type my password and hit enter a second time, I can generally reproduce the problem. The screen either goes to a backlit entirely black view, or (more commonly) a light grey (not the same color of grey as the Ubuntu login screen, much more white in the crashed state). The system is completely unresponsive and cannot be pinged or ssh'ed into from the outside. The only cure is to long-press the power button until it powers down, wait a moment and press it again to restart. Upon suggestions from the #Ubuntu mattermost channel, I ran: # journalctl -xe -b -1 That generated the following data: Sep 23 11:35:35 T14 kernel: RIP: 0010:update_config+0x11b/0x280 [amdgpu] Sep 23 11:35:35 T14 kernel: Code: 13 0f 00 00 41 0f b6 44 24 03 88 83 1e 0f 00 > Sep 23 11:35:35 T14 kernel: RSP: 0018:ffff9b4743bab618 EFLAGS: 00010202 Sep 23 11:35:35 T14 kernel: RAX: 0000000000000000 RBX: ffff8a578653cf88 RCX: ff> Sep 23 11:35:35 T14 kernel: RDX: ffff8a578653dea0 RSI: ffff9b4743bab668 RDI: ff> Sep 23 11:35:35 T14 kernel: RBP: ffff9b4743bab658 R08: 00000000ffff0000 R09: 00> Sep 23 11:35:35 T14 kernel: R10: 0000000000005649 R11: 0000000000000010 R12: ff> Sep 23 11:35:35 T14 kernel: R13: ffff8a57a5eda000 R14: 0000000000000001 R15: ff> Sep 23 11:35:35 T14 kernel: FS: 00007fb5f59a35c0(0000) GS:ffff8a5e4f040000(000> Sep 23 11:35:35 T14 kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Sep 23 11:35:35 T14 kernel: CR2: 0000000000000000 CR3: 00000001704d6000 CR4: 00> Sep 23 11:35:35 T14 kernel: PKRU: 55555554 Sep 23 11:35:38 T14 kernel: input: PLT V5200 Series (AVRCP) as /devices/virtual> Sep 23 11:35:38 T14 pulseaudio[3488]: Battery Level: 90% Sep 23 11:35:38 T14 pulseaudio[3488]: Dock Status: undocked Sep 23 11:35:38 T14 systemd-logind[1832]: Watching system buttons on /dev/input> Sep 23 11:35:39 T14 bluetoothd[1809]: /org/bluez/hci0/dev_BC_F2_92_A0_AC_33/sep> Sep 23 11:35:39 T14 rtkit-daemon[2111]: Supervising 9 threads of 4 processes of> Sep 23 11:35:39 T14 rtkit-daemon[2111]: Successfully made thread 41544 of proce> Sep 23 11:35:39 T14 rtkit-daemon[2111]: Supervising 10 threads of 4 processes o> Sep 23 11:35:39 T14 pulseaudio[3488]: org.freedesktop.DBus.Properties.Get /org/> Sep 23 11:35:41 T14 audit[4797]: SECCOMP auid=1000 uid=1000 gid=1000 ses=3 subj> Sep 23 11:35:41 T14 kernel: audit: type=1326 audit(1663947341.195:578): auid=10> ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1990697 Title: Crash on resume from sleep - 22.04, Thinkpad T14 (AMD) Gen 2 Status in linux package in Ubuntu: New Bug description: I'm seeing this 2-3 times per week. My system is configured with "Linux Suspend" in the BIOS (not the Windows/Modern setting). Furthermore, when plugged in, my system does not sleep. When I come up to my laptop after inactivity, the screens are dark (but as noted above, it is not suspended). If I click on a key and wait for both external monitors to light up, I can generally hit enter at that point, type my password and get in. If, however, I'm in a hurry or not thinking about it and just walk up to the machine, hit enter, type my password and hit enter a second time, I can generally reproduce the problem. The screen either goes to a backlit entirely black view, or (more commonly) a light grey (not the same color of grey as the Ubuntu login screen, much more white in the crashed state). The system is completely unresponsive and cannot be pinged or ssh'ed into from the outside. The only cure is to long-press the power button until it powers down, wait a moment and press it again to restart. Upon suggestions from the #Ubuntu mattermost channel, I ran: # journalctl -xe -b -1 That generated the following data: Sep 23 11:35:35 T14 kernel: RIP: 0010:update_config+0x11b/0x280 [amdgpu] Sep 23 11:35:35 T14 kernel: Code: 13 0f 00 00 41 0f b6 44 24 03 88 83 1e 0f 00 > Sep 23 11:35:35 T14 kernel: RSP: 0018:ffff9b4743bab618 EFLAGS: 00010202 Sep 23 11:35:35 T14 kernel: RAX: 0000000000000000 RBX: ffff8a578653cf88 RCX: ff> Sep 23 11:35:35 T14 kernel: RDX: ffff8a578653dea0 RSI: ffff9b4743bab668 RDI: ff> Sep 23 11:35:35 T14 kernel: RBP: ffff9b4743bab658 R08: 00000000ffff0000 R09: 00> Sep 23 11:35:35 T14 kernel: R10: 0000000000005649 R11: 0000000000000010 R12: ff> Sep 23 11:35:35 T14 kernel: R13: ffff8a57a5eda000 R14: 0000000000000001 R15: ff> Sep 23 11:35:35 T14 kernel: FS: 00007fb5f59a35c0(0000) GS:ffff8a5e4f040000(000> Sep 23 11:35:35 T14 kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Sep 23 11:35:35 T14 kernel: CR2: 0000000000000000 CR3: 00000001704d6000 CR4: 00> Sep 23 11:35:35 T14 kernel: PKRU: 55555554 Sep 23 11:35:38 T14 kernel: input: PLT V5200 Series (AVRCP) as /devices/virtual> Sep 23 11:35:38 T14 pulseaudio[3488]: Battery Level: 90% Sep 23 11:35:38 T14 pulseaudio[3488]: Dock Status: undocked Sep 23 11:35:38 T14 systemd-logind[1832]: Watching system buttons on /dev/input> Sep 23 11:35:39 T14 bluetoothd[1809]: /org/bluez/hci0/dev_BC_F2_92_A0_AC_33/sep> Sep 23 11:35:39 T14 rtkit-daemon[2111]: Supervising 9 threads of 4 processes of> Sep 23 11:35:39 T14 rtkit-daemon[2111]: Successfully made thread 41544 of proce> Sep 23 11:35:39 T14 rtkit-daemon[2111]: Supervising 10 threads of 4 processes o> Sep 23 11:35:39 T14 pulseaudio[3488]: org.freedesktop.DBus.Properties.Get /org/> Sep 23 11:35:41 T14 audit[4797]: SECCOMP auid=1000 uid=1000 gid=1000 ses=3 subj> Sep 23 11:35:41 T14 kernel: audit: type=1326 audit(1663947341.195:578): auid=10> To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990697/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp