You are not logged in.

#1 2019-09-24 15:34:22

snailman153624
Member
Registered: 2019-09-24
Posts: 11

System Crash on Resume from Sleep

This issue started occurring intermittently about 5 months ago, and does not happen every time.  First, system specs:

ASUS Crosshair Hero VII
Ryzen 2700x (standard clocks)
AMD RX580 (Sapphire Nitro+) GPU, stock clocks
16 GB 3Ghz RAM (XMP profile)
XPG SX8200 Pro 512GB SSD for OS/programs
750GB WD green platter drive for random files

Arch Linux
Cinammon desktop
Standard amdgpu drivers
Freesync capable displays x2 (2560x1440p each) connected via DP


The symptoms are as follows:
Use the computer for hours no real issues.  Use the menu in Cinammon to suspend, and seemingly randomly, the system will fail to resume normally later (usually suspend overnight or at least a few hours).  This is usually the 3rd or 4th sleep, so I am forced to hard boot the machine once or twice a week now.  When it resumes, the keyboard lights up, as does the HDD and power indicators on the case, so it's not totally dead, but the screens are blank.  Re-plugging the monitors doesn't work, and I seemingly can't get to a console (will keep trying).

Here is journal output from the failed resumes....what's interesting is it seems the system suspends BEFORE it is done preparing for suspend...so when it resumes, it continues the suspend process....and then it seems like this snowballs into a hung GPU:


Sep 24 01:26:39 MKPC2 NetworkManager[678]: <info>  [1569306399.5895] manager: sleep: sleep requested (sleeping: no  enabled: yes)
Sep 24 01:26:39 MKPC2 NetworkManager[678]: <info>  [1569306399.5896] device (88:79:7E:5C:16:4C): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Sep 24 01:26:39 MKPC2 NetworkManager[678]: <info>  [1569306399.5898] manager: NetworkManager state is now ASLEEP
Sep 24 01:26:39 MKPC2 systemd[1]: Reached target Sleep.
-- 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 2627.
Sep 24 01:26:39 MKPC2 systemd[1]: Starting 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 2624.
Sep 24 01:26:39 MKPC2 systemd-sleep[70654]: Suspending system...
-- 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 24 01:26:39 MKPC2 kernel: PM: suspend entry (deep)
Sep 24 09:51:02 MKPC2 kernel: Filesystems sync: 0.005 seconds
Sep 24 09:51:02 MKPC2 kernel: Freezing user space processes ... (elapsed 0.001 seconds) done.
Sep 24 09:51:02 MKPC2 kernel: OOM killer disabled.
Sep 24 09:51:02 MKPC2 kernel: Freezing remaining freezable tasks ... (elapsed 5.242 seconds) done.
Sep 24 09:51:02 MKPC2 kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Sep 24 09:51:02 MKPC2 kernel: sd 1:0:0:0: [sda] Synchronizing SCSI cache
Sep 24 09:51:02 MKPC2 kernel: sd 1:0:0:0: [sda] Stopping disk
Sep 24 09:51:02 MKPC2 kernel: ACPI: EC: interrupt blocked
Sep 24 09:51:02 MKPC2 kernel: ACPI: Preparing to enter system sleep state S3
Sep 24 09:51:02 MKPC2 kernel: ACPI: EC: event blocked
Sep 24 09:51:02 MKPC2 kernel: ACPI: EC: EC stopped
Sep 24 09:51:02 MKPC2 kernel: PM: Saving platform NVS memory
Sep 24 09:51:02 MKPC2 kernel: Disabling non-boot CPUs ...
Sep 24 09:51:02 MKPC2 kernel: smpboot: CPU 1 is now offline
Sep 24 09:51:02 MKPC2 kernel: smpboot: CPU 2 is now offline
Sep 24 09:51:02 MKPC2 kernel: smpboot: CPU 3 is now offline
Sep 24 09:51:02 MKPC2 kernel: smpboot: CPU 4 is now offline
Sep 24 09:51:02 MKPC2 kernel: smpboot: CPU 5 is now offline
Sep 24 09:51:02 MKPC2 kernel: smpboot: CPU 6 is now offline
Sep 24 09:51:02 MKPC2 kernel: smpboot: CPU 7 is now offline
Sep 24 09:51:02 MKPC2 kernel: smpboot: CPU 8 is now offline
Sep 24 09:51:02 MKPC2 kernel: smpboot: CPU 9 is now offline
Sep 24 09:51:02 MKPC2 kernel: smpboot: CPU 10 is now offline
Sep 24 09:51:02 MKPC2 kernel: smpboot: CPU 11 is now offline
Sep 24 09:51:02 MKPC2 kernel: smpboot: CPU 12 is now offline
Sep 24 09:51:02 MKPC2 kernel: smpboot: CPU 13 is now offline
Sep 24 09:51:02 MKPC2 kernel: smpboot: CPU 14 is now offline
Sep 24 09:51:02 MKPC2 kernel: smpboot: CPU 15 is now offline
Sep 24 09:51:02 MKPC2 kernel: ACPI: Low-level resume complete
Sep 24 09:51:02 MKPC2 kernel: ACPI: EC: EC started
Sep 24 09:51:02 MKPC2 kernel: PM: Restoring platform NVS memory
Sep 24 09:51:02 MKPC2 kernel: Enabling non-boot CPUs ...
Sep 24 09:51:02 MKPC2 kernel: x86: Booting SMP configuration:
Sep 24 09:51:02 MKPC2 kernel: smpboot: Booting Node 0 Processor 1 APIC 0x2
Sep 24 09:51:02 MKPC2 kernel: microcode: CPU1: patch_level=0x0800820d
Sep 24 09:51:02 MKPC2 kernel: CPU1 is up
Sep 24 09:51:02 MKPC2 kernel: smpboot: Booting Node 0 Processor 2 APIC 0x4
Sep 24 09:51:02 MKPC2 kernel: microcode: CPU2: patch_level=0x0800820d
Sep 24 09:51:02 MKPC2 kernel: CPU2 is up
Sep 24 09:51:02 MKPC2 kernel: smpboot: Booting Node 0 Processor 3 APIC 0x6
Sep 24 09:51:02 MKPC2 kernel: microcode: CPU3: patch_level=0x0800820d
Sep 24 09:51:02 MKPC2 kernel: CPU3 is up
Sep 24 09:51:02 MKPC2 kernel: smpboot: Booting Node 0 Processor 4 APIC 0x8
Sep 24 09:51:02 MKPC2 kernel: microcode: CPU4: patch_level=0x0800820d
Sep 24 09:51:02 MKPC2 kernel: CPU4 is up
Sep 24 09:51:02 MKPC2 kernel: smpboot: Booting Node 0 Processor 5 APIC 0xa
Sep 24 09:51:02 MKPC2 kernel: microcode: CPU5: patch_level=0x0800820d
Sep 24 09:51:02 MKPC2 kernel: CPU5 is up
Sep 24 09:51:02 MKPC2 kernel: smpboot: Booting Node 0 Processor 6 APIC 0xc
Sep 24 09:51:02 MKPC2 kernel: microcode: CPU6: patch_level=0x0800820d
Sep 24 09:51:02 MKPC2 kernel: CPU6 is up
Sep 24 09:51:02 MKPC2 kernel: smpboot: Booting Node 0 Processor 7 APIC 0xe
Sep 24 09:51:02 MKPC2 kernel: microcode: CPU7: patch_level=0x0800820d
Sep 24 09:51:02 MKPC2 kernel: CPU7 is up
Sep 24 09:51:02 MKPC2 kernel: smpboot: Booting Node 0 Processor 8 APIC 0x1
Sep 24 09:51:02 MKPC2 kernel: microcode: CPU8: patch_level=0x0800820d
Sep 24 09:51:02 MKPC2 kernel: CPU8 is up
Sep 24 09:51:02 MKPC2 kernel: smpboot: Booting Node 0 Processor 9 APIC 0x3
Sep 24 09:51:02 MKPC2 kernel: microcode: CPU9: patch_level=0x0800820d
Sep 24 09:51:02 MKPC2 kernel: CPU9 is up
Sep 24 09:51:02 MKPC2 kernel: smpboot: Booting Node 0 Processor 10 APIC 0x5
Sep 24 09:51:02 MKPC2 kernel: microcode: CPU10: patch_level=0x0800820d
Sep 24 09:51:02 MKPC2 kernel: CPU10 is up
Sep 24 09:51:02 MKPC2 kernel: smpboot: Booting Node 0 Processor 11 APIC 0x7
Sep 24 09:51:02 MKPC2 kernel: microcode: CPU11: patch_level=0x0800820d
Sep 24 09:51:02 MKPC2 kernel: CPU11 is up
Sep 24 09:51:02 MKPC2 kernel: smpboot: Booting Node 0 Processor 12 APIC 0x9
Sep 24 09:51:02 MKPC2 kernel: microcode: CPU12: patch_level=0x0800820d
Sep 24 09:51:02 MKPC2 kernel: CPU12 is up
Sep 24 09:51:02 MKPC2 kernel: smpboot: Booting Node 0 Processor 13 APIC 0xb
Sep 24 09:51:02 MKPC2 kernel: microcode: CPU13: patch_level=0x0800820d
Sep 24 09:51:02 MKPC2 kernel: CPU13 is up
Sep 24 09:51:02 MKPC2 kernel: smpboot: Booting Node 0 Processor 14 APIC 0xd
Sep 24 09:51:02 MKPC2 kernel: microcode: CPU14: patch_level=0x0800820d
Sep 24 09:51:02 MKPC2 kernel: CPU14 is up
Sep 24 09:51:02 MKPC2 kernel: smpboot: Booting Node 0 Processor 15 APIC 0xf
Sep 24 09:51:02 MKPC2 kernel: microcode: CPU15: patch_level=0x0800820d
Sep 24 09:51:02 MKPC2 kernel: CPU15 is up
Sep 24 09:51:02 MKPC2 kernel: ACPI: Waking up from system sleep state S3
Sep 24 09:51:02 MKPC2 kernel: ACPI: EC: interrupt unblocked
Sep 24 09:51:02 MKPC2 kernel: ACPI: EC: event unblocked
Sep 24 09:51:02 MKPC2 kernel: usb usb1: root hub lost power or was reset
Sep 24 09:51:02 MKPC2 kernel: usb usb2: root hub lost power or was reset
Sep 24 09:51:02 MKPC2 kernel: sd 1:0:0:0: [sda] Starting disk
Sep 24 09:51:02 MKPC2 kernel: [drm] PCIE GART of 256M enabled (table at 0x000000F400000000).
Sep 24 09:51:02 MKPC2 kernel: nvme nvme0: 15/0/0 default/read/poll queues
Sep 24 09:51:02 MKPC2 kernel: ata9: SATA link down (SStatus 0 SControl 300)
Sep 24 09:51:02 MKPC2 kernel: ata8: SATA link down (SStatus 0 SControl 330)
Sep 24 09:51:02 MKPC2 kernel: ata3: SATA link down (SStatus 0 SControl 330)
Sep 24 09:51:02 MKPC2 kernel: ata7: SATA link down (SStatus 0 SControl 330)
Sep 24 09:51:02 MKPC2 kernel: ata6: SATA link down (SStatus 0 SControl 330)
Sep 24 09:51:02 MKPC2 kernel: ata1: SATA link down (SStatus 0 SControl 300)
Sep 24 09:51:02 MKPC2 kernel: ata4: SATA link down (SStatus 0 SControl 330)
Sep 24 09:51:02 MKPC2 kernel: ata5: SATA link down (SStatus 0 SControl 330)
Sep 24 09:51:02 MKPC2 kernel: amdgpu 0000:09:00.0: [drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring gfx test failed (-110)
Sep 24 09:51:02 MKPC2 kernel: [drm:amdgpu_device_ip_resume_phase2 [amdgpu]] *ERROR* resume of IP block <gfx_v8_0> failed -110
Sep 24 09:51:02 MKPC2 kernel: [drm:amdgpu_device_resume [amdgpu]] *ERROR* amdgpu_device_ip_resume failed (-110).
Sep 24 09:51:02 MKPC2 kernel: PM: dpm_run_callback(): pci_pm_resume+0x0/0x90 returns -110
Sep 24 09:51:02 MKPC2 kernel: PM: Device 0000:09:00.0 failed to resume async: error -110
Sep 24 09:51:02 MKPC2 kernel: usb 1-6: reset high-speed USB device number 4 using xhci_hcd
Sep 24 09:51:02 MKPC2 kernel: usb 1-2: reset full-speed USB device number 2 using xhci_hcd
Sep 24 09:51:02 MKPC2 kernel: usb 1-5: reset full-speed USB device number 3 using xhci_hcd
Sep 24 09:51:02 MKPC2 kernel: usb 1-14: reset low-speed USB device number 8 using xhci_hcd
Sep 24 09:51:02 MKPC2 kernel: usb 1-12: reset full-speed USB device number 6 using xhci_hcd
Sep 24 09:51:02 MKPC2 kernel: igb 0000:05:00.0 enp5s0: igb: enp5s0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
Sep 24 09:51:02 MKPC2 kernel: usb 1-13: reset low-speed USB device number 7 using xhci_hcd
Sep 24 09:51:02 MKPC2 kernel: usb 1-9: reset full-speed USB device number 5 using xhci_hcd
Sep 24 09:51:02 MKPC2 kernel: OOM killer enabled.
Sep 24 09:51:02 MKPC2 kernel: Restarting tasks ... done.
Sep 24 09:51:02 MKPC2 kernel: PM: suspend exit
Sep 24 09:51:02 MKPC2 kernel: Bluetooth: hci0: RTL: rtl: examining hci_ver=07 hci_rev=000b lmp_ver=07 lmp_subver=8822
Sep 24 09:51:02 MKPC2 kernel: audit: type=1130 audit(1569336662.976:84): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Sep 24 09:51:02 MKPC2 kernel: audit: type=1131 audit(1569336662.976:85): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Sep 24 09:51:02 MKPC2 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Sep 24 09:51:02 MKPC2 audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Sep 24 09:51:02 MKPC2 bluetoothd[675]: Endpoint unregistered: sender=:1.91 path=/MediaEndpoint/A2DPSink/sbc
Sep 24 09:51:02 MKPC2 pulseaudio[978]: W: [alsa-source-ALC1220 Analog] alsa-util.c: Could not recover alsa device from SUSPENDED state, trying to restart PCM
Sep 24 09:51:02 MKPC2 systemd-sleep[70654]: System resumed.
-- Subject: System sleep state suspend left
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- The system has now left the suspend sleep state.
Sep 24 09:51:02 MKPC2 bluetoothd[675]: Endpoint unregistered: sender=:1.91 path=/MediaEndpoint/A2DPSource/sbc
Sep 24 09:51:02 MKPC2 systemd[1]: systemd-suspend.service: Succeeded.
-- Subject: Unit succeeded
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- The unit systemd-suspend.service has successfully entered the 'dead' state.
Sep 24 09:51:02 MKPC2 rtkit-daemon[1067]: The canary thread is apparently starving. Taking action.
Sep 24 09:51:02 MKPC2 systemd[1]: Started Suspend.
-- Subject: A start job for unit systemd-suspend.service has finished successfully
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A start job for unit systemd-suspend.service has finished successfully.
-- 
-- The job identifier is 2624.
Sep 24 09:51:02 MKPC2 rtkit-daemon[1067]: Demoting known real-time threads.
Sep 24 09:51:02 MKPC2 systemd[1]: Stopped target Sleep.
-- Subject: A stop job for unit sleep.target has finished
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A stop job for unit sleep.target has finished.
-- 
-- The job identifier is 2636 and the job result is done.
Sep 24 09:51:02 MKPC2 rtkit-daemon[1067]: Successfully demoted thread 64052 of process 64023.
Sep 24 09:51:02 MKPC2 systemd[1]: Reached target Suspend.
-- Subject: A start job for unit suspend.target has finished successfully
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A start job for unit suspend.target has finished successfully.
-- 
-- The job identifier is 2623.
Sep 24 09:51:02 MKPC2 rtkit-daemon[1067]: Successfully demoted thread 64051 of process 64023.
Sep 24 09:51:02 MKPC2 NetworkManager[678]: <info>  [1569336662.9801] bluez5: NAP: removed interface D0:C5:D3:47:33:4C
Sep 24 09:51:02 MKPC2 rtkit-daemon[1067]: Successfully demoted thread 48843 of process 48808.
Sep 24 09:51:02 MKPC2 systemd[1]: Starting Load/Save RF Kill Switch Status...
-- Subject: A start job for unit systemd-rfkill.service has begun execution
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A start job for unit systemd-rfkill.service has begun execution.
-- 
-- The job identifier is 2628.
Sep 24 09:51:02 MKPC2 rtkit-daemon[1067]: Successfully demoted thread 48842 of process 48808.
Sep 24 09:51:02 MKPC2 rtkit-daemon[1067]: Successfully demoted thread 48778 of process 48744.
Sep 24 09:51:02 MKPC2 rtkit-daemon[1067]: Successfully demoted thread 48779 of process 48744.
Sep 24 09:51:02 MKPC2 systemd[1]: Stopped target Suspend.
-- Subject: A stop job for unit suspend.target has finished
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A stop job for unit suspend.target has finished.
-- 
-- The job identifier is 2639 and the job result is done.
Sep 24 09:51:02 MKPC2 rtkit-daemon[1067]: Successfully demoted thread 48684 of process 48658.
Sep 24 09:51:02 MKPC2 rtkit-daemon[1067]: Successfully demoted thread 48683 of process 48658.
Sep 24 09:51:02 MKPC2 rtkit-daemon[1067]: Successfully demoted thread 44980 of process 44953.
Sep 24 09:51:02 MKPC2 rtkit-daemon[1067]: Successfully demoted thread 44979 of process 44953.
Sep 24 09:51:02 MKPC2 rtkit-daemon[1067]: Successfully demoted thread 1601 of process 1565.
Sep 24 09:51:02 MKPC2 rtkit-daemon[1067]: Successfully demoted thread 1602 of process 1565.
Sep 24 09:51:02 MKPC2 rtkit-daemon[1067]: Successfully demoted thread 1497 of process 1470.
Sep 24 09:51:02 MKPC2 rtkit-daemon[1067]: Successfully demoted thread 1498 of process 1470.
Sep 24 09:51:02 MKPC2 rtkit-daemon[1067]: Successfully demoted thread 1399 of process 1359.
Sep 24 09:51:02 MKPC2 rtkit-daemon[1067]: Successfully demoted thread 62752 of process 978.
Sep 24 09:51:02 MKPC2 rtkit-daemon[1067]: Successfully demoted thread 1132 of process 978.
Sep 24 09:51:02 MKPC2 rtkit-daemon[1067]: Successfully demoted thread 1129 of process 978.
Sep 24 09:51:02 MKPC2 rtkit-daemon[1067]: Successfully demoted thread 1128 of process 978.
Sep 24 09:51:02 MKPC2 rtkit-daemon[1067]: Successfully demoted thread 978 of process 978.
Sep 24 09:51:02 MKPC2 rtkit-daemon[1067]: Demoted 20 threads.
Sep 24 09:51:02 MKPC2 kernel: Bluetooth: hci0: RTL: rom_version status=0 version=2
Sep 24 09:51:02 MKPC2 kernel: Bluetooth: hci0: RTL: rtl: loading rtl_bt/rtl8822b_fw.bin
Sep 24 09:51:02 MKPC2 kernel: Bluetooth: hci0: RTL: rtl: loading rtl_bt/rtl8822b_config.bin
Sep 24 09:51:02 MKPC2 kernel: Bluetooth: hci0: RTL: cfg_sz 14, total sz 20270
Sep 24 09:51:02 MKPC2 systemd[751]: Stopped target Bluetooth.
-- Subject: A stop job for unit UNIT has finished
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A stop job for unit UNIT has finished.
-- 
-- The job identifier is 353 and the job result is done.
Sep 24 09:51:02 MKPC2 systemd-logind[733]: Operation 'sleep' finished.
Sep 24 09:51:02 MKPC2 NetworkManager[678]: <info>  [1569336662.9854] manager: sleep: wake requested (sleeping: yes  enabled: yes)
Sep 24 09:51:02 MKPC2 NetworkManager[678]: <info>  [1569336662.9855] device (enp5s0): state change: activated -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Sep 24 09:51:02 MKPC2 NetworkManager[678]: <info>  [1569336662.9856] dhcp4 (enp5s0): canceled DHCP transaction
Sep 24 09:51:02 MKPC2 NetworkManager[678]: <info>  [1569336662.9857] dhcp4 (enp5s0): state changed bound -> done
Sep 24 09:51:02 MKPC2 avahi-daemon[674]: Withdrawing address record for 192.168.100.110 on enp5s0.
Sep 24 09:51:02 MKPC2 avahi-daemon[674]: Leaving mDNS multicast group on interface enp5s0.IPv4 with address 192.168.100.110.
Sep 24 09:51:02 MKPC2 avahi-daemon[674]: Interface enp5s0.IPv4 no longer relevant for mDNS.
Sep 24 09:51:02 MKPC2 avahi-daemon[674]: Withdrawing address record for fe80::9148:24f4:714a:7b17 on enp5s0.
Sep 24 09:51:02 MKPC2 avahi-daemon[674]: Leaving mDNS multicast group on interface enp5s0.IPv6 with address fe80::9148:24f4:714a:7b17.
Sep 24 09:51:02 MKPC2 avahi-daemon[674]: Interface enp5s0.IPv6 no longer relevant for mDNS.
Sep 24 09:51:02 MKPC2 systemd[1]: Reached target Bluetooth.
-- Subject: A start job for unit bluetooth.target has finished successfully
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A start job for unit bluetooth.target has finished successfully.
-- 
-- The job identifier is 2640.
Sep 24 09:51:02 MKPC2 systemd[751]: Reached target Bluetooth.
-- Subject: A start job for unit UNIT has finished successfully
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A start job for unit UNIT has finished successfully.
-- 
-- The job identifier is 354.
Sep 24 09:51:02 MKPC2 NetworkManager[678]: <info>  [1569336662.9895] manager: NetworkManager state is now CONNECTED_GLOBAL
Sep 24 09:51:02 MKPC2 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-rfkill comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Sep 24 09:51:02 MKPC2 systemd[1]: Started Load/Save RF Kill Switch Status.
-- Subject: A start job for unit systemd-rfkill.service has finished successfully
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A start job for unit systemd-rfkill.service has finished successfully.
-- 
-- The job identifier is 2628.
Sep 24 09:51:02 MKPC2 kernel: audit: type=1130 audit(1569336662.986:86): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-rfkill comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Sep 24 09:51:02 MKPC2 rtkit-daemon[1067]: Supervising 0 threads of 0 processes of 0 users.
Sep 24 09:51:02 MKPC2 rtkit-daemon[1067]: Recovering from system lockup, not allowing further RT threads.
Sep 24 09:51:02 MKPC2 rtkit-daemon[1067]: Supervising 0 threads of 0 processes of 0 users.
Sep 24 09:51:02 MKPC2 rtkit-daemon[1067]: Recovering from system lockup, not allowing further RT threads.
Sep 24 09:51:02 MKPC2 rtkit-daemon[1067]: Supervising 0 threads of 0 processes of 0 users.
Sep 24 09:51:03 MKPC2 rtkit-daemon[1067]: Recovering from system lockup, not allowing further RT threads.
Sep 24 09:51:03 MKPC2 rtkit-daemon[1067]: Supervising 0 threads of 0 processes of 0 users.
Sep 24 09:51:03 MKPC2 rtkit-daemon[1067]: Recovering from system lockup, not allowing further RT threads.
Sep 24 09:51:03 MKPC2 rtkit-daemon[1067]: Supervising 0 threads of 0 processes of 0 users.
Sep 24 09:51:03 MKPC2 rtkit-daemon[1067]: Recovering from system lockup, not allowing further RT threads.
Sep 24 09:51:03 MKPC2 kernel: [drm] schedsdma0 is not ready, skipping
Sep 24 09:51:03 MKPC2 kernel: [drm] schedsdma1 is not ready, skipping
Sep 24 09:51:03 MKPC2 kernel: BUG: kernel NULL pointer dereference, address: 0000000000000008
Sep 24 09:51:03 MKPC2 kernel: #PF: supervisor read access in kernel mode
Sep 24 09:51:03 MKPC2 kernel: #PF: error_code(0x0000) - not-present page
Sep 24 09:51:03 MKPC2 kernel: PGD 0 P4D 0 
Sep 24 09:51:03 MKPC2 kernel: Oops: 0000 [#1] PREEMPT SMP NOPTI
Sep 24 09:51:03 MKPC2 kernel: CPU: 11 PID: 749 Comm: Xorg Tainted: G        W         5.3.0-arch1-1-ARCH #1
Sep 24 09:51:03 MKPC2 kernel: Hardware name: System manufacturer System Product Name/ROG CROSSHAIR VII HERO (WI-FI), BIOS 2703 08/20/2019
Sep 24 09:51:03 MKPC2 kernel: RIP: 0010:amdgpu_vm_sdma_commit+0x4e/0x120 [amdgpu]
Sep 24 09:51:03 MKPC2 kernel: Code: 00 00 48 89 44 24 08 31 c0 48 8b 47 08 48 c7 04 24 00 00 00 00 4c 8b a2 88 01 00 00 4c 8b a8 80 00 00 00 48 8b 80 c8 00 00 00 <4c> 8b 70 08 41 8b 44 24 08 4d 8d 7e 88 85 c0 0f 84 38 54 1f 00 49
Sep 24 09:51:03 MKPC2 kernel: RSP: 0018:ffffbe2ac0b27ae8 EFLAGS: 00010246
Sep 24 09:51:03 MKPC2 kernel: RAX: 0000000000000000 RBX: ffffbe2ac0b27b30 RCX: 00000000001016e7
Sep 24 09:51:03 MKPC2 kernel: RDX: ffff9e0f478f6400 RSI: ffffbe2ac0b27bb8 RDI: ffffbe2ac0b27b30
Sep 24 09:51:03 MKPC2 kernel: RBP: ffffbe2ac0b27bb8 R08: 0000000000001000 R09: 0000000000000000
Sep 24 09:51:03 MKPC2 kernel: R10: 000000000000009d R11: 000000000000007d R12: ffff9e0f478f65f8
Sep 24 09:51:03 MKPC2 kernel: R13: ffff9e0f4c27a000 R14: ffff9e0f4c27b800 R15: ffff9e0f4b896f60
Sep 24 09:51:03 MKPC2 kernel: FS:  00007fdaa6fccdc0(0000) GS:ffff9e0f4e8c0000(0000) knlGS:0000000000000000
Sep 24 09:51:03 MKPC2 kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Sep 24 09:51:03 MKPC2 kernel: CR2: 0000000000000008 CR3: 00000003fc9cc000 CR4: 00000000003406e0
Sep 24 09:51:03 MKPC2 kernel: Call Trace:
Sep 24 09:51:03 MKPC2 kernel:  amdgpu_vm_bo_update_mapping+0xcd/0xe0 [amdgpu]
Sep 24 09:51:03 MKPC2 kernel:  amdgpu_vm_clear_freed+0xc0/0x190 [amdgpu]
Sep 24 09:51:03 MKPC2 kernel:  amdgpu_gem_va_ioctl+0x47a/0x5a0 [amdgpu]
Sep 24 09:51:03 MKPC2 kernel:  ? amdgpu_gem_metadata_ioctl+0x190/0x190 [amdgpu]
Sep 24 09:51:03 MKPC2 kernel:  drm_ioctl_kernel+0xb8/0x100 [drm]
Sep 24 09:51:03 MKPC2 kernel:  drm_ioctl+0x23d/0x3d0 [drm]
Sep 24 09:51:03 MKPC2 kernel:  ? amdgpu_gem_metadata_ioctl+0x190/0x190 [amdgpu]
Sep 24 09:51:03 MKPC2 kernel:  amdgpu_drm_ioctl+0x49/0x80 [amdgpu]
Sep 24 09:51:03 MKPC2 kernel:  do_vfs_ioctl+0x43d/0x6c0
Sep 24 09:51:03 MKPC2 kernel:  ? __do_munmap+0x280/0x420
Sep 24 09:51:03 MKPC2 kernel:  ? syscall_trace_enter+0x1f2/0x2e0
Sep 24 09:51:03 MKPC2 kernel:  ksys_ioctl+0x5e/0x90
Sep 24 09:51:03 MKPC2 kernel:  __x64_sys_ioctl+0x16/0x20
Sep 24 09:51:03 MKPC2 kernel:  do_syscall_64+0x5f/0x1c0
Sep 24 09:51:03 MKPC2 kernel:  entry_SYSCALL_64_after_hwframe+0x44/0xa9
Sep 24 09:51:03 MKPC2 kernel: RIP: 0033:0x7fdaa820521b
Sep 24 09:51:03 MKPC2 kernel: Code: 0f 1e fa 48 8b 05 75 8c 0c 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 45 8c 0c 00 f7 d8 64 89 01 48
Sep 24 09:51:03 MKPC2 kernel: RSP: 002b:00007ffffe39a9e8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
Sep 24 09:51:03 MKPC2 kernel: RAX: ffffffffffffffda RBX: 00007ffffe39aa30 RCX: 00007fdaa820521b
Sep 24 09:51:03 MKPC2 kernel: RDX: 00007ffffe39aa30 RSI: 00000000c0286448 RDI: 000000000000000e
Sep 24 09:51:03 MKPC2 kernel: RBP: 00000000c0286448 R08: 00000001012e7000 R09: 000000000000000e
Sep 24 09:51:03 MKPC2 kernel: R10: 0000000000000034 R11: 0000000000000246 R12: 0000000000000000
Sep 24 09:51:03 MKPC2 kernel: R13: 000000000000000e R14: 0000000000000002 R15: 000056233f844de0
Sep 24 09:51:03 MKPC2 kernel: Modules linked in: uas usb_storage rfcomm md4 nls_utf8 cifs dns_resolver fscache cmac bnep amdgpu rtwpci rtw88 gpu_sched edac_mce_amd mac80211 kvm_amd ttm eeepc_wmi asus_wmi sparse_keymap kvm drm_kms_helper snd_hda_codec_realtek snd_hda_codec_generic btusb btrtl nls_iso8859_1 wmi_bmof m>
Sep 24 09:51:03 MKPC2 kernel:  xt_recent xt_limit xt_addrtype xt_tcpudp xt_conntrack ip6table_filter ip6_tables nf_conntrack_netbios_ns nf_conntrack_broadcast nf_nat_ftp nf_nat nf_conntrack_ftp nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c iptable_filter fuse sg crypto_user ip_tables x_tables ext4 crc32c_gene>
Sep 24 09:51:03 MKPC2 kernel: CR2: 0000000000000008
Sep 24 09:51:03 MKPC2 kernel: ---[ end trace dca5be5f8c7aa734 ]---
Sep 24 09:51:03 MKPC2 kernel: RIP: 0010:amdgpu_vm_sdma_commit+0x4e/0x120 [amdgpu]
Sep 24 09:51:03 MKPC2 kernel: Code: 00 00 48 89 44 24 08 31 c0 48 8b 47 08 48 c7 04 24 00 00 00 00 4c 8b a2 88 01 00 00 4c 8b a8 80 00 00 00 48 8b 80 c8 00 00 00 <4c> 8b 70 08 41 8b 44 24 08 4d 8d 7e 88 85 c0 0f 84 38 54 1f 00 49
Sep 24 09:51:03 MKPC2 kernel: RSP: 0018:ffffbe2ac0b27ae8 EFLAGS: 00010246
Sep 24 09:51:03 MKPC2 kernel: RAX: 0000000000000000 RBX: ffffbe2ac0b27b30 RCX: 00000000001016e7
Sep 24 09:51:03 MKPC2 kernel: RDX: ffff9e0f478f6400 RSI: ffffbe2ac0b27bb8 RDI: ffffbe2ac0b27b30
Sep 24 09:51:03 MKPC2 kernel: RBP: ffffbe2ac0b27bb8 R08: 0000000000001000 R09: 0000000000000000
Sep 24 09:51:03 MKPC2 kernel: R10: 000000000000009d R11: 000000000000007d R12: ffff9e0f478f65f8
Sep 24 09:51:03 MKPC2 kernel: R13: ffff9e0f4c27a000 R14: ffff9e0f4c27b800 R15: ffff9e0f4b896f60
Sep 24 09:51:03 MKPC2 kernel: FS:  00007fdaa6fccdc0(0000) GS:ffff9e0f4e8c0000(0000) knlGS:0000000000000000
Sep 24 09:51:03 MKPC2 kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Sep 24 09:51:03 MKPC2 kernel: CR2: 0000000000000008 CR3: 00000003fc9cc000 CR4: 00000000003406e0
Sep 24 09:51:03 MKPC2 NetworkManager[678]: <info>  [1569336663.0189] manager: NetworkManager state is now DISCONNECTED
Sep 24 09:51:03 MKPC2 NetworkManager[678]: <info>  [1569336663.0198] device (wlp6s0): state change: unavailable -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Sep 24 09:51:03 MKPC2 NetworkManager[678]: <info>  [1569336663.0200] device (wlp6s0): set-hw-addr: reset MAC address to D0:C5:D3:47:33:4D (unmanage)
Sep 24 09:51:03 MKPC2 NetworkManager[678]: <info>  [1569336663.0203] device (enp5s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'managed')
Sep 24 09:51:03 MKPC2 dbus-daemon[676]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.15' (uid=0 pid=678 comm="/usr/bin/NetworkManager --no-daemon ")
Sep 24 09:51:03 MKPC2 systemd[1]: Starting Network Manager Script Dispatcher Service...
-- Subject: A start job for unit NetworkManager-dispatcher.service has begun execution
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A start job for unit NetworkManager-dispatcher.service has finished successfully.
-- 
-- The job identifier is 2717.
Sep 24 09:51:03 MKPC2 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Sep 24 09:51:03 MKPC2 kernel: audit: type=1130 audit(1569336663.023:87): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Sep 24 09:51:03 MKPC2 kernel: [drm] schedsdma0 is not ready, skipping
Sep 24 09:51:03 MKPC2 NetworkManager[678]: <info>  [1569336663.0439] device (wlp6s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'managed')
Sep 24 09:51:03 MKPC2 NetworkManager[678]: <info>  [1569336663.0442] device (wlp6s0): set-hw-addr: set MAC address to 16:EB:33:43:74:3D (scanning)
Sep 24 09:51:03 MKPC2 kernel: [drm] schedsdma1 is not ready, skipping
Sep 24 09:51:03 MKPC2 kernel: Move buffer fallback to memcpy unavailable
Sep 24 09:51:03 MKPC2 kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to process the buffer list -19!
Sep 24 09:51:04 MKPC2 kernel: ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Sep 24 09:51:04 MKPC2 NetworkManager[678]: <info>  [1569336664.2466] bluez5: NAP: added interface D0:C5:D3:47:33:4C
Sep 24 09:51:04 MKPC2 bluetoothd[675]: Endpoint registered: sender=:1.91 path=/MediaEndpoint/A2DPSink/sbc
Sep 24 09:51:04 MKPC2 bluetoothd[675]: Endpoint registered: sender=:1.91 path=/MediaEndpoint/A2DPSource/sbc
Sep 24 09:51:04 MKPC2 NetworkManager[678]: <info>  [1569336664.2705] bluez: BT device Moto G (4) (88:79:7E:5C:16:4C) added (NAP)
Sep 24 09:51:04 MKPC2 NetworkManager[678]: <info>  [1569336664.2708] manager: (88:79:7E:5C:16:4C): new Bluetooth device (/org/freedesktop/NetworkManager/Devices/6)
Sep 24 09:51:04 MKPC2 NetworkManager[678]: <info>  [1569336664.2712] device (88:79:7E:5C:16:4C): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Sep 24 09:51:04 MKPC2 NetworkManager[678]: <info>  [1569336664.2725] device (88:79:7E:5C:16:4C): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'managed')
Sep 24 09:51:05 MKPC2 kernel: ata2.00: configured for UDMA/133
Sep 24 09:51:05 MKPC2 kernel: check: Corrupted low memory at 00000000fec5bd93 (2aa8 phys) = 00550000
Sep 24 09:51:05 MKPC2 kernel: check: Corrupted low memory at 00000000c6764a39 (5550 phys) = f00000000000
Sep 24 09:51:05 MKPC2 kernel: igb 0000:05:00.0 enp5s0: igb: enp5s0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
Sep 24 09:51:05 MKPC2 NetworkManager[678]: <info>  [1569336665.8468] device (enp5s0): carrier: link connected
Sep 24 09:51:05 MKPC2 NetworkManager[678]: <info>  [1569336665.8470] device (enp5s0): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed')
Sep 24 09:51:05 MKPC2 NetworkManager[678]: <info>  [1569336665.8481] policy: auto-activating connection 'Wired connection 1' (d23e2485-11ef-3da0-8474-24b7a1c1cfe5)
Sep 24 09:51:05 MKPC2 NetworkManager[678]: <info>  [1569336665.8486] device (enp5s0): Activation: starting connection 'Wired connection 1' (d23e2485-11ef-3da0-8474-24b7a1c1cfe5)
Sep 24 09:51:05 MKPC2 NetworkManager[678]: <info>  [1569336665.8488] device (enp5s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Sep 24 09:51:05 MKPC2 NetworkManager[678]: <info>  [1569336665.8491] manager: NetworkManager state is now CONNECTING
Sep 24 09:51:05 MKPC2 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): enp5s0: link becomes ready
Sep 24 09:51:05 MKPC2 NetworkManager[678]: <info>  [1569336665.8962] device (enp5s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Sep 24 09:51:05 MKPC2 NetworkManager[678]: <info>  [1569336665.8970] device (enp5s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Sep 24 09:51:05 MKPC2 NetworkManager[678]: <info>  [1569336665.8973] dhcp4 (enp5s0): activation: beginning transaction (timeout in 45 seconds)
Sep 24 09:51:05 MKPC2 avahi-daemon[674]: Joining mDNS multicast group on interface enp5s0.IPv6 with address fe80::9148:24f4:714a:7b17.
Sep 24 09:51:05 MKPC2 avahi-daemon[674]: New relevant interface enp5s0.IPv6 for mDNS.
Sep 24 09:51:05 MKPC2 avahi-daemon[674]: Registering new address record for fe80::9148:24f4:714a:7b17 on enp5s0.*.
Sep 24 09:51:07 MKPC2 systemd[1]: systemd-rfkill.service: Succeeded.
-- Subject: Unit succeeded
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- The unit systemd-rfkill.service has successfully entered the 'dead' state.
Sep 24 09:51:07 MKPC2 audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-rfkill comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Sep 24 09:51:07 MKPC2 kernel: audit: type=1131 audit(1569336667.993:88): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-rfkill comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Sep 24 09:51:08 MKPC2 kernel: igb 0000:05:00.0 enp5s0: igb: enp5s0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
Sep 24 09:51:09 MKPC2 NetworkManager[678]: <info>  [1569336669.0666] device (enp5s0): carrier: link connected
Sep 24 09:51:09 MKPC2 NetworkManager[678]: <info>  [1569336669.6430] dhcp4 (enp5s0): state changed unknown -> bound
Sep 24 09:51:09 MKPC2 avahi-daemon[674]: Joining mDNS multicast group on interface enp5s0.IPv4 with address 192.168.100.110.
Sep 24 09:51:09 MKPC2 avahi-daemon[674]: New relevant interface enp5s0.IPv4 for mDNS.
Sep 24 09:51:09 MKPC2 avahi-daemon[674]: Registering new address record for 192.168.100.110 on enp5s0.IPv4.
Sep 24 09:51:09 MKPC2 NetworkManager[678]: <info>  [1569336669.6442] device (enp5s0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Sep 24 09:51:09 MKPC2 NetworkManager[678]: <info>  [1569336669.6476] device (enp5s0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Sep 24 09:51:09 MKPC2 NetworkManager[678]: <info>  [1569336669.6479] device (enp5s0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Sep 24 09:51:09 MKPC2 NetworkManager[678]: <info>  [1569336669.6484] manager: NetworkManager state is now CONNECTED_LOCAL
Sep 24 09:51:09 MKPC2 NetworkManager[678]: <info>  [1569336669.6494] manager: NetworkManager state is now CONNECTED_SITE
Sep 24 09:51:09 MKPC2 NetworkManager[678]: <info>  [1569336669.6495] policy: set 'Wired connection 1' (enp5s0) as default for IPv4 routing and DNS
Sep 24 09:51:09 MKPC2 NetworkManager[678]: <info>  [1569336669.6510] device (enp5s0): Activation: successful, device activated.
Sep 24 09:51:09 MKPC2 NetworkManager[678]: <info>  [1569336669.9810] manager: NetworkManager state is now CONNECTED_GLOBAL
Sep 24 09:51:13 MKPC2 systemd[1]: NetworkManager-dispatcher.service: Succeeded.
-- Subject: Unit succeeded
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- The unit NetworkManager-dispatcher.service has successfully entered the 'dead' state.
Sep 24 09:51:13 MKPC2 audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Sep 24 09:51:13 MKPC2 kernel: audit: type=1131 audit(1569336673.260:89): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Sep 24 09:51:31 MKPC2 kernel: [UFW BLOCK] IN=enp5s0 OUT= MAC=01:00:5e:00:00:01:ec:22:80:20:75:9a:08:00 SRC=192.168.100.12 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0xC0 TTL=2 ID=60297 PROTO=2 
Sep 24 09:53:36 MKPC2 kernel: [UFW BLOCK] IN=enp5s0 OUT= MAC=01:00:5e:00:00:01:ec:22:80:20:75:9a:08:00 SRC=192.168.100.12 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0xC0 TTL=2 ID=65372 PROTO=2 

Offline

#2 2019-09-24 21:19:30

seth
Member
Registered: 2012-09-03
Posts: 50,012

Re: System Crash on Resume from Sleep

Sep 24 09:51:02 MKPC2 kernel: amdgpu 0000:09:00.0: [drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring gfx test failed (-110)
Sep 24 09:51:02 MKPC2 kernel: [drm:amdgpu_device_ip_resume_phase2 [amdgpu]] *ERROR* resume of IP block <gfx_v8_0> failed -110
Sep 24 09:51:02 MKPC2 kernel: [drm:amdgpu_device_resume [amdgpu]] *ERROR* amdgpu_device_ip_resume failed (-110).
Sep 24 09:51:02 MKPC2 kernel: PM: dpm_run_callback(): pci_pm_resume+0x0/0x90 returns -110
Sep 24 09:51:02 MKPC2 kernel: PM: Device 0000:09:00.0 failed to resume async: error -110

The usual suspects:

amdgpu.dc=0 amdgpu.dpm=0 amdgpu.aspm=0 amdgpu.runpm=0 amdgpu.bapm=0

https://wiki.archlinux.org/index.php/Kernel_parameters

Offline

#3 2019-10-27 18:19:27

WFV
Member
From: ☭USSA⛧⭒⭒⭒⭒
Registered: 2013-04-23
Posts: 288

Re: System Crash on Resume from Sleep

@ snailman153624 - so long as everything else lights up but no display, if you have another machine available to ssh in shutdown pc normal to avoid hard reboot. I have same resume problems Asus M5A88-M with Radeon RX550 randomly, obviously error messages applicable to RX550 slightly different from RX580. As seth mentioned the usual suspects (some I've tried in the past but haven't been using any of them for several kernel updates now), read up on what they do and perhaps try to see if situation improves.

Last edited by WFV (2019-10-27 18:19:57)


∞ hard times make the strong, the strong make good times, good times make the weak, the weak make hard times ∞

Offline

#4 2019-10-29 05:48:04

snailman153624
Member
Registered: 2019-09-24
Posts: 11

Re: System Crash on Resume from Sleep

No luck despite several kernel and amdgpu updates, I haven't tried disabling some of the power management features either, I'm not going to sacrifice DPM to avoid a hung suspend, that seems like it defeats the purpose.  May as well just leave the computer idle.

As for the remote console, etc., more trouble than it's worth.  I don't believe I have SSHD enabled, and it would take more time to attempt it than it's worth.  Most of the apps I use are graphical, and as such the GPU crash forces the desktop environment to crash, and all the apps with it.  It reboots in 5 seconds or less, but have to re-open some files/apps, etc.  Interestingly, even local consoles don't work (some sort of indirect dependency on graphics?)...e.g. I try the hotkeys to switch to a native terminal and blindly try to login and issue shutdown or reboot commands, and nothing happens.

I have similar (but different) issues on the AMD GPU (Vega 8) in my R5 3500u laptop....it attempts to resume, and has similar GPU errors in the log, but it does come up....however, the login screen isn't quite right...the field to type in your password never appears, and if I leave it for a few minutes the whole machine locks up...but if I switch to a console really quick, and restart lightdm I'm able to resume normal usage with no (apparent) lingering issues.

I'm convinced some of the embedded devices have gotten too complex to manage with software effectively.

Offline

#5 2019-10-29 07:03:29

seth
Member
Registered: 2012-09-03
Posts: 50,012

Re: System Crash on Resume from Sleep

I haven't tried disabling some of the power management features either, I'm not going to sacrifice DPM to avoid a hung suspend

The basic idea is to isolate the cause …

As for the remote console, etc., more trouble than it's worth.  I don't believe I have SSHD enabled, and it would take more time to attempt it than it's worth.

What distro do you actually use?

Offline

#6 2019-10-30 03:07:26

snailman153624
Member
Registered: 2019-09-24
Posts: 11

Re: System Crash on Resume from Sleep

seth wrote:

I haven't tried disabling some of the power management features either, I'm not going to sacrifice DPM to avoid a hung suspend

The basic idea is to isolate the cause …

As for the remote console, etc., more trouble than it's worth.  I don't believe I have SSHD enabled, and it would take more time to attempt it than it's worth.

What distro do you actually use?

Well, while your first post may have been well intended, all you listed was a bunch of kernel parameters.  It wasn't clear that you were suggesting trying each one individually, or as a group, or what.  I don't know what the "usual" suspects are with the AMDGPU driver, as I couldn't find other posts with this same issue on any of the various Linux message boards or wikis.  I read through the documentation and Arch wiki pretty thoroughly, and at the time anyway, the wiki didn't mention any of those in the troubleshooting steps.

Also, I'm running Arch....(these are the Arch forums....do folks running other distros routinely post here for help?)....stock/unmodified kernel.

Last edited by snailman153624 (2019-10-30 03:16:55)

Offline

#7 2019-10-30 07:11:45

seth
Member
Registered: 2012-09-03
Posts: 50,012

Re: System Crash on Resume from Sleep

You pass them all, check whether that improves the situation, then narrow down a culprit (bisecting or sequential)
Those parameters are the "usual suspects" because these features cause amdgpu issues all the time and yes: many people running esp. Arch derivates show up here and usually they don't know fundamental things about their system, eg. whether sshd.service is enabled (so they rather guess or "believe" about the system condition - hence my question) and feel it's a like exhausting hassle to eg. enable a service because they've never done that nor took a look into any of the basic wiki pages and thus don't know that enabling eg. sshd is no effort at all…

Offline

#8 2019-10-31 04:38:37

snailman153624
Member
Registered: 2019-09-24
Posts: 11

Re: System Crash on Resume from Sleep

seth wrote:

You pass them all, check whether that improves the situation, then narrow down a culprit (bisecting or sequential)
Those parameters are the "usual suspects" because these features cause amdgpu issues all the time and yes: many people running esp. Arch derivates show up here and usually they don't know fundamental things about their system, eg. whether sshd.service is enabled (so they rather guess or "believe" about the system condition - hence my question) and feel it's a like exhausting hassle to eg. enable a service because they've never done that nor took a look into any of the basic wiki pages and thus don't know that enabling eg. sshd is no effort at all…

I don't remember if I disabled sshd when I first installed Arch over a year ago on this particular machine, sorry to disappoint you that I don't know this "fundamental to my system" random fact (really?).  More than likely I turned it off, because I never use it at home, and having services enabled is a security vulnerability.  Further, I would never just turn on a service like SSHD without first poring over the config, so no, it's not as simple as systemctl enable.  Either way, it's not really relevant to my issue.

Thanks for the suggestions re: the kps, but being that the issue is intermittent it will likely take over a month spitballing through a laundry list of random KPs.  I was hoping someone else had this particular issue, guess not.

Last edited by snailman153624 (2019-10-31 04:46:49)

Offline

#9 2019-11-01 14:58:52

Varrenlad
Member
Registered: 2019-10-31
Posts: 1

Re: System Crash on Resume from Sleep

snailman153624 wrote:

I was hoping someone else had this particular issue, guess not.

I suppose, you are not the only one: https://bugzilla.kernel.org/show_bug.cgi?id=204241

Offline

#10 2019-11-01 15:56:30

zaxdan69
Member
Registered: 2016-06-04
Posts: 271

Re: System Crash on Resume from Sleep

I also had in the past problems with resume from suspend with different graphics cards. As @seth has mention, these problems are usaly related to gpu drivers.
I had this problem again before some months in my current system(which has RX570 graphics cart and I'm using AMDGPU driver). I've tried to disable amdgpu's futures but I this doesn't fix the issue.
It turns out that the problem was the system overclocking. I had overclocked my cpu about 5% from bios by auto overclocking options. I didn't have any other problem when the system was running, but I decided to test it with the default cpu clocking.
And this seems that solved the issue. Now the only problem I have some times is that when I resume from suspend, the system goes again to suspend and need to resume it for one more time. But I never have crashes or other problems(which I have mentioned at least) the last months with the default cpu speed.
So, if it happens to also have overclocked your machine, maybe this causes the problem for you too.

Offline

#11 2019-11-01 19:44:04

loqs
Member
Registered: 2014-03-06
Posts: 17,197

Offline

#12 2019-11-01 23:53:18

snailman153624
Member
Registered: 2019-09-24
Posts: 11

Re: System Crash on Resume from Sleep

Now we're cooking!  I may give this patch a try, since it's still just in the staging repo and thus may be a month or two before it hits mainline...I haven't figured out how one gets bugfix closure, in that these bug reports never tell you which commit they hit mainline with.

For whatever reason, when I did my searching through the bug reports, I didn't find this one (it is relatively recent)...perhaps because all of the users in there have an RX550 or a Vega 10.  I searched for many combinations (AMDGPU, RX580, RX480, RX570, etc.), but I must not have stumbled on the right one.

I am not overclocking anything, other than technically the RAM, which is running the certified/advertised XMP profile @ 3 GHz.  I have not come across an application (that I use) yet that has really stressed my 2700x to the point I think I'd notice!

As to the double resume issue, I have seen some bug reports related to that; I believe there was a patch for that issue as well, had something to do with a systemd script having some commands out of order, thus inducing a race condition...if I come across it again I will post back.

Offline

#13 2019-11-02 01:52:47

loqs
Member
Registered: 2014-03-06
Posts: 17,197

Re: System Crash on Resume from Sleep

Commit is in 5.3.8 as ca8e0e7fdb88d806d2f4b4876769be43bbbdf75f see release notes https://cdn.kernel.org/pub/linux/kernel … eLog-5.3.8

Offline

#14 2019-11-02 05:09:29

snailman153624
Member
Registered: 2019-09-24
Posts: 11

Re: System Crash on Resume from Sleep

Sadly, after updating to this kernel, the issue now occurs on my laptop as well (very similar error logs), Ryzen 3500u with Vega 8.  It used to wake up from suspend, but lightdm would hang...now the display doesn't even turn on and it hangs during the suspend.  Joy.

Offline

Board footer

Powered by FluxBB