FS#72105 - [dkms] suspend broken (causes hard hang) on ASUS Flow X13

Attached to Project: Arch Linux
Opened by Jed Brown (jedbrown) - Saturday, 11 September 2021, 18:55 GMT
Last edited by Sébastien Luttringer (seblu) - Tuesday, 09 November 2021, 10:14 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Sébastien Luttringer (seblu)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
Suspend had been working flawlessly until I installed dkms, after which it caused my system to hang (unresponsive to all keys including normal short-press of power button). The fan spun up and it stayed hot until I held power to hard shutdown. This happened multiple times. I removed dkms and suspend has been reliable since.

Additional info:

linux-5.14.2.arch1-2
dkms-2.8.6-1
amd-ucode-20210818.c46b8c3-1
nvidia-470.63.01-7

asusctl graphics mode: "hybrid"

journalctl -xe -b -1:
░░ Subject: A start job for unit sleep.target has finished successfully
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit sleep.target has finished successfully.
░░
░░ The job identifier is 1586.
Sep 11 12:14:30 kichatna systemd[1]: Starting System Suspend...
░░ Subject: A start job for unit systemd-suspend.service has begun execution
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit systemd-suspend.service has begun execution.
░░
░░ The job identifier is 1585.
Sep 11 12:14:30 kichatna systemd-sleep[2705]: Entering sleep state 'suspend'...
░░ Subject: System sleep state suspend entered
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ The system has now entered the suspend sleep state.
Sep 11 12:14:30 kichatna kernel: PM: suspend entry (s2idle)
Sep 11 12:14:30 kichatna kernel: Filesystems sync: 0.046 seconds
Sep 11 12:14:30 kichatna kernel: rfkill: input handler enabled
Sep 11 12:14:32 kichatna kernel: Freezing user space processes ... (elapsed 0.003 seconds) don>
Sep 11 12:14:32 kichatna kernel: OOM killer disabled.
Sep 11 12:14:32 kichatna kernel: Freezing remaining freezable tasks ... (elapsed 0.001 seconds>
Sep 11 12:14:32 kichatna kernel: printk: Suspending console(s) (use no_console_suspend to debu>
Sep 11 12:14:32 kichatna kernel: wlan0: deauthenticating from 02:6a:e3:88:49:22 by local choic>
Sep 11 12:14:32 kichatna kernel: amd_pmc AMDI0005:00: SMU response timed out
Sep 11 12:14:32 kichatna kernel: amd_pmc AMDI0005:00: suspend failed
Sep 11 12:14:32 kichatna kernel: PM: dpm_run_callback(): acpi_subsys_suspend_noirq+0x0/0x40 re>
Sep 11 12:14:32 kichatna kernel: amd_pmc AMDI0005:00: PM: failed to suspend noirq: error -110
Sep 11 12:14:32 kichatna kernel: PM: noirq suspend of devices failed
Sep 11 12:14:32 kichatna kernel: pci 0000:00:00.2: can't derive routing for PCI INT A
Sep 11 12:14:32 kichatna kernel: pci 0000:00:00.2: PCI INT A: no GSI
Sep 11 12:14:32 kichatna kernel: [drm] PCIE GART of 1024M enabled.
Sep 11 12:14:32 kichatna kernel: [drm] PTB located at 0x000000F400900000
Sep 11 12:14:32 kichatna kernel: amdgpu 0000:04:00.0: amdgpu: SMU is resuming...
Sep 11 12:14:32 kichatna kernel: amdgpu 0000:04:00.0: amdgpu: dpm has been disabled
Sep 11 12:14:32 kichatna kernel: amdgpu 0000:04:00.0: amdgpu: failed send message: SetGfx>
Sep 11 12:14:32 kichatna kernel: amdgpu 0000:04:00.0: amdgpu: SMU is resumed successfully!
Sep 11 12:14:32 kichatna kernel: amdgpu 0000:04:00.0: amdgpu: Msg issuing pre-check failed(0xf>
Sep 11 12:14:32 kichatna kernel: amdgpu 0000:04:00.0: amdgpu: Failed to power ungate SDMA!

Steps to reproduce:
Install dkms, attempt to suspend (force hang), hold power button to force shutdown, boot and examine journalctl -xe -b -1.
This task depends upon

Closed by  Sébastien Luttringer (seblu)
Tuesday, 09 November 2021, 10:14 GMT
Reason for closing:  Not a bug
Comment by Sébastien Luttringer (seblu) - Tuesday, 09 November 2021, 10:13 GMT
DKMS allows you to build out-of-tree kernel modules, which may cause kernel issues like the one you are experiencing.
So, without more evidence of DKMS being the issue, I suggest you to look at a kernel module built via dkms which could cause this trouble.
Install/removing dkms maybe only install/uninstall a module which make your kernel unhappy.

Loading...