You are not logged in.
Pages: 1
Hello dear Arch users,
Since a long time, after I put my laptop in Sleep mode, I get a freeze.
When I open the lid screen, the keyboard backlight switched on, and the FANs switched on as well, but the screen is OFF.
I tried to sue the CTRL+BACKSPACE and CTRL+DELETE several times to restart, but it does not work, therefore I have to press the power button during 5 second to swich off then reboot.
Sorry that I only tell the community now about this issue.
I should have tell you as soon as the problem appeared so that it is easier to bissect.
My system is up to date.
NOTE : if I put the system in Sleep mode a couple of minutes, it MAY BE that I am able then to move out successuflly from the Sleep.
But if I stay in Sleep mode let's say more than 10 minutes, the I am likely to be out of luck wwhen trying to go out of the Sleep mode.
Please find below the log of the command "journalctl -b -1 >> log.txt" :
-- Journal begins at Mon 2021-12-13 17:44:57 UTC, ends at Fri 2021-12-24 16:56:20 UTC. --
Dec 24 12:24:09 zoulou kernel: Linux version 5.15.11-arch2-1 (linux@archlinux) (gcc (GCC) 11.1.0, GNU ld (GNU Binutils) 2.36.1) #1 SMP PREEMPT Wed, 22 Dec 2021 09:23:54 +0000
Dec 24 12:24:09 zoulou kernel: Command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=c97b6628-f326-4cbb-bc8e-cff3ba9dd301 rw cryptdevice=/dev/nvme0n1p2:cryptroot:allow-discards root=/dev/mapper/cryptroot mem_encrypt=off
Dec 24 12:24:09 zoulou kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
Dec 24 12:24:09 zoulou kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
Dec 24 12:24:09 zoulou kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
Dec 24 12:24:09 zoulou kernel: x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256
Dec 24 12:24:09 zoulou kernel: x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'compacted' format.
Dec 24 12:24:09 zoulou kernel: signal: max sigframe size: 1776
.
.
.
.
Dec 24 15:47:47 zoulou systemd[1]: Reached target Sleep.
Dec 24 15:47:47 zoulou systemd[1]: Starting System Suspend...
Dec 24 15:47:47 zoulou systemd[1]: Stopping Atop advanced performance monitor...
Dec 24 15:47:48 zoulou systemd[1]: atop.service: Deactivated successfully.
Dec 24 15:47:48 zoulou systemd[1]: Stopped Atop advanced performance monitor.
Dec 24 15:47:48 zoulou audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=atop comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dec 24 15:47:48 zoulou kernel: audit: type=1131 audit(1640360868.019:178): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=atop comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dec 24 15:47:48 zoulou systemd-sleep[22685]: Entering sleep state 'suspend'...
Dec 24 15:47:48 zoulou kernel: PM: suspend entry (deep)
Dec 24 15:47:48 zoulou kernel: Filesystems sync: 0.002 seconds
Dec 24 16:50:19 zoulou kernel: Freezing user space processes ... (elapsed 0.002 seconds) done.
Dec 24 16:50:19 zoulou kernel: OOM killer disabled.
Dec 24 16:50:19 zoulou kernel: Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
Dec 24 16:50:19 zoulou kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Dec 24 16:50:19 zoulou kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Dec 24 16:50:19 zoulou kernel: sd 0:0:0:0: [sda] Stopping disk
Dec 24 16:50:19 zoulou kernel: ACPI: EC: interrupt blocked
Dec 24 16:50:19 zoulou kernel: amdgpu 0000:0c:00.0: can't change power state from D0 to D3hot (config space inaccessible)
Dec 24 16:50:19 zoulou kernel: ACPI: PM: Preparing to enter system sleep state S3
Dec 24 16:50:19 zoulou kernel: ACPI: EC: event blocked
Dec 24 16:50:19 zoulou kernel: ACPI: EC: EC stopped
Dec 24 16:50:19 zoulou kernel: ACPI: PM: Saving platform NVS memory
Dec 24 16:50:19 zoulou kernel: Disabling non-boot CPUs ...
Dec 24 16:50:19 zoulou kernel: smpboot: CPU 1 is now offline
Dec 24 16:50:19 zoulou kernel: smpboot: CPU 2 is now offline
Dec 24 16:50:19 zoulou kernel: smpboot: CPU 3 is now offline
Dec 24 16:50:19 zoulou kernel: smpboot: CPU 4 is now offline
Dec 24 16:50:19 zoulou kernel: smpboot: CPU 5 is now offline
Dec 24 16:50:19 zoulou kernel: smpboot: CPU 6 is now offline
Dec 24 16:50:19 zoulou kernel: smpboot: CPU 7 is now offline
Dec 24 16:50:19 zoulou kernel: smpboot: CPU 8 is now offline
Dec 24 16:50:19 zoulou kernel: smpboot: CPU 9 is now offline
Dec 24 16:50:19 zoulou kernel: smpboot: CPU 10 is now offline
Dec 24 16:50:19 zoulou kernel: smpboot: CPU 11 is now offline
Dec 24 16:50:19 zoulou kernel: smpboot: CPU 12 is now offline
Dec 24 16:50:19 zoulou kernel: smpboot: CPU 13 is now offline
Dec 24 16:50:19 zoulou kernel: smpboot: CPU 14 is now offline
Dec 24 16:50:19 zoulou kernel: smpboot: CPU 15 is now offline
Dec 24 16:50:19 zoulou kernel: ACPI: PM: Low-level resume complete
Dec 24 16:50:19 zoulou kernel: ACPI: EC: EC started
Dec 24 16:50:19 zoulou kernel: ACPI: PM: Restoring platform NVS memory
Dec 24 16:50:19 zoulou kernel: Enabling non-boot CPUs ...
Dec 24 16:50:19 zoulou kernel: x86: Booting SMP configuration:
Dec 24 16:50:19 zoulou kernel: smpboot: Booting Node 0 Processor 1 APIC 0x1
Dec 24 16:50:19 zoulou kernel: microcode: CPU1: patch_level=0x08001137
Dec 24 16:50:19 zoulou kernel: ACPI: \_PR_.P001: Found 2 idle states
Dec 24 16:50:19 zoulou kernel: CPU1 is up
Dec 24 16:50:19 zoulou kernel: smpboot: Booting Node 0 Processor 2 APIC 0x2
Dec 24 16:50:19 zoulou kernel: microcode: CPU2: patch_level=0x08001137
Dec 24 16:50:19 zoulou kernel: ACPI: \_PR_.P002: Found 2 idle states
Dec 24 16:50:19 zoulou kernel: CPU2 is up
Dec 24 16:50:19 zoulou kernel: smpboot: Booting Node 0 Processor 3 APIC 0x3
Dec 24 16:50:19 zoulou kernel: microcode: CPU3: patch_level=0x08001137
Dec 24 16:50:19 zoulou kernel: ACPI: \_PR_.P003: Found 2 idle states
Dec 24 16:50:19 zoulou kernel: CPU3 is up
Dec 24 16:50:19 zoulou kernel: smpboot: Booting Node 0 Processor 4 APIC 0x4
Dec 24 16:50:19 zoulou kernel: microcode: CPU4: patch_level=0x08001137
Dec 24 16:50:19 zoulou kernel: ACPI: \_PR_.P004: Found 2 idle states
Dec 24 16:50:19 zoulou kernel: CPU4 is up
Dec 24 16:50:19 zoulou kernel: smpboot: Booting Node 0 Processor 5 APIC 0x5
Dec 24 16:50:19 zoulou kernel: microcode: CPU5: patch_level=0x08001137
Dec 24 16:50:19 zoulou kernel: ACPI: \_PR_.P005: Found 2 idle states
Dec 24 16:50:19 zoulou kernel: CPU5 is up
Dec 24 16:50:19 zoulou kernel: smpboot: Booting Node 0 Processor 6 APIC 0x6
Dec 24 16:50:19 zoulou kernel: microcode: CPU6: patch_level=0x08001137
Dec 24 16:50:19 zoulou kernel: ACPI: \_PR_.P006: Found 2 idle states
Dec 24 16:50:19 zoulou kernel: CPU6 is up
Dec 24 16:50:19 zoulou kernel: smpboot: Booting Node 0 Processor 7 APIC 0x7
Dec 24 16:50:19 zoulou kernel: microcode: CPU7: patch_level=0x08001137
Dec 24 16:50:19 zoulou kernel: ACPI: \_PR_.P007: Found 2 idle states
Dec 24 16:50:19 zoulou kernel: CPU7 is up
Dec 24 16:50:19 zoulou kernel: smpboot: Booting Node 0 Processor 8 APIC 0x8
Dec 24 16:50:19 zoulou kernel: microcode: CPU8: patch_level=0x08001137
Dec 24 16:50:19 zoulou kernel: ACPI: \_PR_.P008: Found 2 idle states
Dec 24 16:50:19 zoulou kernel: CPU8 is up
Dec 24 16:50:19 zoulou kernel: smpboot: Booting Node 0 Processor 9 APIC 0x9
Dec 24 16:50:19 zoulou kernel: microcode: CPU9: patch_level=0x08001137
Dec 24 16:50:19 zoulou kernel: ACPI: \_PR_.P009: Found 2 idle states
Dec 24 16:50:19 zoulou kernel: CPU9 is up
Dec 24 16:50:19 zoulou kernel: smpboot: Booting Node 0 Processor 10 APIC 0xa
Dec 24 16:50:19 zoulou kernel: microcode: CPU10: patch_level=0x08001137
Dec 24 16:50:19 zoulou kernel: ACPI: \_PR_.P00A: Found 2 idle states
Dec 24 16:50:19 zoulou kernel: CPU10 is up
Dec 24 16:50:19 zoulou kernel: smpboot: Booting Node 0 Processor 11 APIC 0xb
Dec 24 16:50:19 zoulou kernel: microcode: CPU11: patch_level=0x08001137
Dec 24 16:50:19 zoulou kernel: ACPI: \_PR_.P00B: Found 2 idle states
Dec 24 16:50:19 zoulou kernel: CPU11 is up
Dec 24 16:50:19 zoulou kernel: smpboot: Booting Node 0 Processor 12 APIC 0xc
Dec 24 16:50:19 zoulou kernel: microcode: CPU12: patch_level=0x08001137
Dec 24 16:50:19 zoulou kernel: ACPI: \_PR_.P00C: Found 2 idle states
Dec 24 16:50:19 zoulou kernel: CPU12 is up
Dec 24 16:50:19 zoulou kernel: smpboot: Booting Node 0 Processor 13 APIC 0xd
Dec 24 16:50:19 zoulou kernel: microcode: CPU13: patch_level=0x08001137
Dec 24 16:50:19 zoulou kernel: ACPI: \_PR_.P00D: Found 2 idle states
Dec 24 16:50:19 zoulou kernel: CPU13 is up
Dec 24 16:50:19 zoulou kernel: smpboot: Booting Node 0 Processor 14 APIC 0xe
Dec 24 16:50:19 zoulou kernel: microcode: CPU14: patch_level=0x08001137
Dec 24 16:50:19 zoulou kernel: ACPI: \_PR_.P00E: Found 2 idle states
Dec 24 16:50:19 zoulou kernel: CPU14 is up
Dec 24 16:50:19 zoulou kernel: smpboot: Booting Node 0 Processor 15 APIC 0xf
Dec 24 16:50:19 zoulou kernel: microcode: CPU15: patch_level=0x08001137
Dec 24 16:50:19 zoulou kernel: ACPI: \_PR_.P00F: Found 2 idle states
Dec 24 16:50:19 zoulou kernel: CPU15 is up
Dec 24 16:50:19 zoulou kernel: ACPI: PM: Waking up from system sleep state S3
Dec 24 16:50:19 zoulou kernel: ACPI: EC: interrupt unblocked
Dec 24 16:50:19 zoulou kernel: iommu ivhd0: AMD-Vi: Event logged [INVALID_DEVICE_REQUEST device=00:00.0 pasid=0x00000 address=0xfffffffdf8000000 flags=0x0a00]
Dec 24 16:50:19 zoulou kernel: ACPI: EC: event unblocked
Dec 24 16:50:19 zoulou kernel: usb usb1: root hub lost power or was reset
Dec 24 16:50:19 zoulou kernel: usb usb2: root hub lost power or was reset
Dec 24 16:50:19 zoulou kernel: sd 0:0:0:0: [sda] Starting disk
Dec 24 16:50:19 zoulou kernel: nvme nvme0: 16/0/0 default/read/poll queues
Dec 24 16:50:19 zoulou kernel: amdgpu 0000:0c:00.0: amdgpu: Wait for MC idle timedout !
Dec 24 16:50:19 zoulou kernel: ata2: SATA link down (SStatus 0 SControl 300)
Dec 24 16:50:19 zoulou kernel: ata6: SATA link down (SStatus 0 SControl 330)
Dec 24 16:50:19 zoulou kernel: ata9: SATA link down (SStatus 0 SControl 300)
Dec 24 16:50:19 zoulou kernel: usb 1-8: reset high-speed USB device number 2 using xhci_hcd
Dec 24 16:50:19 zoulou kernel: amdgpu 0000:0c:00.0: amdgpu: Wait for MC idle timedout !
Dec 24 16:50:19 zoulou kernel: [drm] PCIE GART of 256M enabled (table at 0x000000F400000000).
Dec 24 16:50:19 zoulou kernel: amdgpu:
last message was failed ret is 65535
Dec 24 16:50:19 zoulou kernel: amdgpu:
failed to send message 100 ret is 65535
Dec 24 16:50:19 zoulou kernel: amdgpu: SMC address must be 4 byte aligned.
Dec 24 16:50:19 zoulou kernel: amdgpu: [AVFS][Polaris10_SetupGfxLvlStruct] Problems copying VRConfig value over to SMC
Dec 24 16:50:19 zoulou kernel: amdgpu: [AVFS][Polaris10_AVFSEventMgr] Could not Copy Graphics Level table over to SMU
Dec 24 16:50:19 zoulou kernel: amdgpu:
last message was failed ret is 65535
Dec 24 16:50:19 zoulou kernel: amdgpu:
failed to send message 252 ret is 65535
Dec 24 16:50:19 zoulou kernel: amdgpu:
last message was failed ret is 65535
Dec 24 16:50:19 zoulou kernel: amdgpu:
failed to send message 253 ret is 65535
Dec 24 16:50:19 zoulou kernel: amdgpu:
last message was failed ret is 65535
Dec 24 16:50:19 zoulou kernel: amdgpu:
failed to send message 250 ret is 65535
Dec 24 16:50:19 zoulou kernel: amdgpu:
last message was failed ret is 65535
Dec 24 16:50:19 zoulou kernel: amdgpu:
failed to send message 251 ret is 65535
Dec 24 16:50:19 zoulou kernel: amdgpu:
last message was failed ret is 65535
Dec 24 16:50:19 zoulou kernel: amdgpu:
failed to send message 254 ret is 65535
Dec 24 16:50:19 zoulou kernel: usb 1-9: reset full-speed USB device number 3 using xhci_hcd
Dec 24 16:50:19 zoulou kernel: [drm] Timeout wait for RLC serdes 0,0
Dec 24 16:50:19 zoulou kernel: amdgpu 0000:0c:00.0: [drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring gfx test failed (-110)
Dec 24 16:50:19 zoulou kernel: [drm:amdgpu_device_ip_resume_phase2 [amdgpu]] *ERROR* resume of IP block <gfx_v8_0> failed -110
Dec 24 16:50:19 zoulou kernel: amdgpu 0000:0c:00.0: amdgpu: amdgpu_device_ip_resume failed (-110).
Dec 24 16:50:19 zoulou kernel: PM: dpm_run_callback(): pci_pm_resume+0x0/0xe0 returns -110
Dec 24 16:50:19 zoulou kernel: amdgpu 0000:0c:00.0: PM: failed to resume async: error -110
Dec 24 16:50:19 zoulou kernel: usb 1-10: reset full-speed USB device number 4 using xhci_hcd
Dec 24 16:50:19 zoulou kernel: ata5: failed to resume link (SControl 0)
Dec 24 16:50:19 zoulou kernel: ata5: SATA link down (SStatus 0 SControl 0)
Dec 24 16:50:19 zoulou kernel: OOM killer enabled.
Dec 24 16:50:19 zoulou kernel: Restarting tasks ... done.
Dec 24 16:50:19 zoulou kernel: Bluetooth: hci0: RTL: examining hci_ver=07 hci_rev=000b lmp_ver=07 lmp_subver=8822
Dec 24 16:50:19 zoulou kernel: Bluetooth: hci0: RTL: rom_version status=0 version=2
Dec 24 16:50:19 zoulou kernel: Bluetooth: hci0: RTL: loading rtl_bt/rtl8822b_fw.bin
Dec 24 16:50:19 zoulou kernel: Bluetooth: hci0: RTL: loading rtl_bt/rtl8822b_config.bin
Dec 24 16:50:19 zoulou kernel: Bluetooth: hci0: RTL: cfg_sz 14, total sz 20270
Dec 24 16:50:19 zoulou kernel: PM: suspend exit
Dec 24 16:50:19 zoulou systemd[1]: Starting Load/Save RF Kill Switch Status...
Dec 24 16:50:19 zoulou systemd-sleep[22685]: System returned from sleep state.
Dec 24 16:50:19 zoulou systemd[1]: Starting Atop advanced performance monitor...
Dec 24 16:50:19 zoulou upowerd[1045]: treating change event as add on /sys/devices/pci0000:00/0000:00:01.3/0000:03:00.0/usb1/1-9
Dec 24 16:50:19 zoulou upowerd[1045]: treating change event as add on /sys/devices/pci0000:00/0000:00:01.3/0000:03:00.0/usb1/1-10
Dec 24 16:50:19 zoulou upowerd[1045]: treating change event as add on /sys/devices/pci0000:00/0000:00:01.3/0000:03:00.0/usb1/1-9
Dec 24 16:50:19 zoulou upowerd[1045]: treating change event as add on /sys/devices/pci0000:00/0000:00:01.3/0000:03:00.0/usb1/1-10
Dec 24 16:50:19 zoulou systemd[802]: Stopped target Bluetooth.
Dec 24 16:50:19 zoulou audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=atop comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dec 24 16:50:19 zoulou systemd[1]: Started Atop advanced performance monitor.
Dec 24 16:50:19 zoulou systemd[1]: Started Load/Save RF Kill Switch Status.
Dec 24 16:50:19 zoulou 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'
Dec 24 16:50:19 zoulou systemd[802]: Reached target Bluetooth.
Dec 24 16:50:19 zoulou kernel: audit: type=1130 audit(1640364619.346:179): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=atop comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dec 24 16:50:19 zoulou kernel: audit: type=1130 audit(1640364619.346:180): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-rfkill comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dec 24 16:50:19 zoulou kernel: Process accounting resumed
Dec 24 16:50:19 zoulou systemd[1]: systemd-suspend.service: Deactivated successfully.
Dec 24 16:50:19 zoulou systemd[1]: Finished System Suspend.
Dec 24 16:50:19 zoulou 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'
Dec 24 16:50:19 zoulou 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'
Dec 24 16:50:19 zoulou kernel: audit: type=1130 audit(1640364619.349:181): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dec 24 16:50:19 zoulou kernel: audit: type=1131 audit(1640364619.349:182): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dec 24 16:50:19 zoulou systemd[1]: Stopped target Bluetooth Support.
Dec 24 16:50:19 zoulou systemd[1]: Stopped target Sleep.
Dec 24 16:50:19 zoulou systemd[1]: Reached target Suspend.
Dec 24 16:50:19 zoulou systemd-logind[700]: Operation 'sleep' finished.
Dec 24 16:50:19 zoulou systemd[1]: Stopped target Suspend.
Dec 24 16:50:19 zoulou NetworkManager[697]: <info> [1640364619.3561] manager: sleep: wake requested (sleeping: yes enabled: yes)
Dec 24 16:50:19 zoulou NetworkManager[697]: <info> [1640364619.3562] device (enp6s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Dec 24 16:50:19 zoulou kernel: Generic FE-GE Realtek PHY r8169-0-600:00: attached PHY driver (mii_bus:phy_addr=r8169-0-600:00, irq=MAC)
Dec 24 16:50:19 zoulou NetworkManager[697]: <info> [1640364619.4954] device (wlp7s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Dec 24 16:50:19 zoulou NetworkManager[697]: <info> [1640364619.4962] device (wlp7s0): set-hw-addr: set MAC address to C2:19:F9:A5:FA:06 (scanning)
Dec 24 16:50:19 zoulou NetworkManager[697]: <info> [1640364619.4969] manager: NetworkManager state is now DISCONNECTED
Dec 24 16:50:19 zoulou kernel: r8169 0000:06:00.0 enp6s0: Link is Down
Dec 24 16:50:20 zoulou kernel: asus_wmi: Unknown key cf pressed
Dec 24 16:50:20 zoulou kernel: Bluetooth: hci0: RTL: fw version 0xab6b705c
Dec 24 16:50:20 zoulou kernel: amdgpu: Move buffer fallback to memcpy unavailable
Dec 24 16:50:20 zoulou kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to process the buffer list -19!
Dec 24 16:50:21 zoulou kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Dec 24 16:50:21 zoulou kernel: ata1.00: ATA Identify Device Log not supported
Dec 24 16:50:21 zoulou kernel: ata1.00: ATA Identify Device Log not supported
Dec 24 16:50:21 zoulou kernel: ata1.00: configured for UDMA/133
Dec 24 16:50:24 zoulou systemd[1]: systemd-rfkill.service: Deactivated successfully.
Dec 24 16:50:24 zoulou 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'
Dec 24 16:50:24 zoulou kernel: audit: type=1131 audit(1640364624.353:183): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-rfkill comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'May be
"[drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to process the buffer list -19!"is involved ?
Could you please help ?
I am willing to try special kernel that you might prepare to troubleshoot, also I am willing to boot with BOOT OPTIONS if needed.
Regards,
InstruKtor
Offline
Hi Instruktor,
Could you tell us what hardware you are using?
And are you sure this issue was not present some time in the past? About how long ago?
Offline
Hi TheStroyer,
Hardware is:
[root@zoulou xx]# dmesg | grep GL702
[ 0.000000] DMI: ASUSTeK COMPUTER INC. GL702ZC/GL702ZC, BIOS GL702ZC.306 07/05/2019
[root@zoulou xx]# dmesg | grep 1700
[ 0.114397] smpboot: CPU0: AMD Ryzen 7 1700 Eight-Core Processor (family: 0x17, model: 0x1, stepping: 0x1)and:
[root@zoulou xx]# lspci
00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Root Complex
00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) I/O Memory Management Unit
00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge
00:01.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe GPP Bridge
00:01.3 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe GPP Bridge
00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge
00:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge
00:03.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe GPP Bridge
00:04.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge
00:07.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge
00:07.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Internal PCIe GPP Bridge 0 to Bus B
00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge
00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Internal PCIe GPP Bridge 0 to Bus B
00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 59)
00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 51)
00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 0
00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 1
00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 2
00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 3
00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 4
00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 5
00:18.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 6
00:18.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 7
01:00.0 Non-Volatile memory controller: Sandisk Corp WD Blue SN550 NVMe SSD (rev 01)
03:00.0 USB controller: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset USB 3.1 xHCI Controller (rev 02)
03:00.1 SATA controller: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset SATA Controller (rev 02)
03:00.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 43b2 (rev 02)
04:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02)
04:01.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02)
04:04.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02)
04:05.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02)
04:06.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02)
04:07.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02)
04:08.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02)
06:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 10)
07:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8822BE 802.11a/b/g/n/ac WiFi adapter
0c:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] (rev c1)
0c:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere HDMI Audio [Radeon RX 470/480 / 570/580/590]
11:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Zeppelin/Raven/Raven2 PCIe Dummy Function
11:00.2 Encryption controller: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Platform Security Processor
11:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) USB 3.0 Host Controller
12:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Zeppelin/Renoir PCIe Dummy Function
12:00.2 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 51)
12:00.3 Audio device: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) HD Audio ControllerI think I remember that a couple of years ago there was no such a problem.
But I cannot provide any "warranty".
And for information, when I boot with hardened kernel, I get some error messages:
[root@zoulou xx]# dmesg | grep amdgpu
[ 20.742467] [drm] amdgpu kernel modesetting enabled.
[ 20.749398] amdgpu: Ignoring ACPI CRAT on non-APU system
[ 20.749405] amdgpu: Virtual CRAT table created for CPU
[ 20.749415] amdgpu: Topology: Add CPU node
[ 20.749531] fb0: switching to amdgpu from VESA VGA
[ 20.749675] amdgpu 0000:0c:00.0: vgaarb: deactivate vga console
[ 20.749776] amdgpu 0000:0c:00.0: amdgpu: Trusted Memory Zone (TMZ) feature not supported
[ 20.750000] amdgpu 0000:0c:00.0: No more image in the PCI ROM
[ 20.750035] amdgpu 0000:0c:00.0: amdgpu: Fetched VBIOS from ROM BAR
[ 20.750037] amdgpu: ATOM BIOS: SWBRT25190.001
[ 20.750658] amdgpu 0000:0c:00.0: amdgpu: VRAM: 4096M 0x000000F400000000 - 0x000000F4FFFFFFFF (4096M used)
[ 20.750661] amdgpu 0000:0c:00.0: amdgpu: GART: 256M 0x000000FF00000000 - 0x000000FF0FFFFFFF
[ 20.750963] [drm] amdgpu: 4096M of VRAM memory ready
[ 20.750965] [drm] amdgpu: 4096M of GTT memory ready.
[ 20.764473] amdgpu: hwmgr_sw_init smu backed is polaris10_smu
[ 20.857591] snd_hda_intel 0000:0c:00.1: bound 0000:0c:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu])
[ 21.036625] kfd kfd: amdgpu: Allocated 3969056 bytes on gart
[ 21.036734] amdgpu: SRAT table not found
[ 21.036735] amdgpu: Virtual CRAT table created for GPU
[ 21.036821] amdgpu: Topology: Add dGPU node [0x67df:0x1002]
[ 21.036825] kfd kfd: amdgpu: added device 1002:67df
[ 21.036842] amdgpu 0000:0c:00.0: amdgpu: SE 4, SH per SE 1, CU per SH 9, active_cu_number 36
[ 21.039721] fbcon: amdgpu (fb0) is primary device
[ 21.136726] amdgpu 0000:0c:00.0: [drm] fb0: amdgpu frame buffer device
[ 21.188663] [drm] Initialized amdgpu 3.42.0 20150101 for 0000:0c:00.0 on minor 0
[ 21.188670] [drm:amdgpu_debugfs_init [amdgpu]] *ERROR* unable to create amdgpu_preempt_ib debugsfs file
[ 21.188993] [drm:amdgpu_pci_probe [amdgpu]] *ERROR* Creating debugfs files failed (-1).
[root@zoulou xx]# uname -a
Linux zoulou 5.15.10-hardened1-1-hardened #1 SMP PREEMPT Fri, 17 Dec 2021 20:16:31 +0000 x86_64 GNU/LinuxAnd the same issue (screen OFF after sleep mode) occurs with the hardened kernel.
Regards
Last edited by THeBeelpy (2021-12-24 17:40:25)
Offline
https://gitlab.freedesktop.org/drm/amd/-/issues/1361 but there's no action on that bug.
Online
Hi,
Thanks a lot you two guys.
Hope this problem will be solved. :-(
Regards !
Offline
Hi guys,
I have played with the command
downgrade linux linux-headersto bissect the issue. All system is up to date, except of course the linux-kernel and linux-headers.
Each time my process is as below :
- I install a linux kernel and the headers as well (I think the headers are not usefull but I am not an expert so in dought I do it!)
- after starting the system with no BOOT options, I save the output of journalctl and dmesg output
- I put the system to sleep during a short time (arround 5 seconds), then I save the dmesg output (if the system is not hang-frozen already...)
- if the system is not HANG-frozen already, then I put the system again to sleep during a much longer time period,
- if the system is not HANG-frozen, I save the dmesg output.
NOTE : sometimes I did "dmesg >> blabla" so I suppose there is a replication of data in the log file. Sorry about that.
Please find below some results.
------------------------
LONG STORY SHORT :
------------------------
The issue seems to be located between 5.10.16 and 5.11.0.
I am willing to try some kernel 5.10.16-patchXXX if you can prepare one (or some) for me.
------------------------
LONG STORY... LONG:
------------------------
+ 113) linux 5.5.13.arch2 1 /var/cache/pacman/pkg
+ 113) linux-headers 5.5.13.arch2 1 /var/cache/pacman/pkg=> 5.5.13 : Unable to boot due to "initramfs unpacking failed: invalid magic at start of compress"
203) linux 5.10.16.arch1 1 /var/cache/pacman/pkg
201) linux-headers 5.10.16.arch1 1 remote=> 5.10.16 : It works fine!
I have captured dmesg output after 2 short sleeps and then after a long sleep.
- 259) linux 5.13.13.arch1 1 /var/cache/pacman/pkg
- 255) linux-headers 5.13.13.arch1 1 remote=> 5.13.13 : Even a short sleep (arround 5 seconds) lead to a screen HANG-freeze.
Had to presse the button during 5 seconds so that I can stop the laptop then restart.
CTRL+DEL and CTRL+BACKSPACE didn't help.
247) linux 5.12.15.arch1 1 /var/cache/pacman/pkg
244) linux-headers 5.12.15.arch1 1 remote=> 5.12.15 : Same as 5.13.13
(Even a short sleep (arround 5 seconds) lead to a screen HANG-freeze.
Had to presse the button during 5 seconds so that I can stop the laptop then restart.
CTRL+DEL and CTRL+BACKSPACE didn't help.)
225) linux 5.11.16.arch1 1 /var/cache/pacman/pkg
223) linux-headers 5.11.16.arch1 1 remote=> 5.11.16 : Same as 5.13.13 and 5.12.15
(Even a short sleep (arround 5 seconds) lead to a screen HANG-freeze.
Had to presse the button during 5 seconds so that I can stop the laptop then restart.
CTRL+DEL and CTRL+BACKSPACE didn't help.)
So let's bissect before the 5.10.16 because it works fine!
But 5.5.13 is not able to boot due to "initramfs unpacking failed: invalid magic at start of compress"
So let's try, let's say:
148) linux 5.7.12.arch1 1 /var/cache/pacman/pkg
147) linux-headers 5.7.12.arch1 1 /var/cache/pacman/pkg=> 5.7.12 : Unable to boot due to "initramfs unpacking failed: invalid magic at start of compress"
167) linux 5.8.14.arch1 1 /var/cache/pacman/pkg
166) linux-headers 5.8.14.arch1 1 /var/cache/pacman/pkg=> 5.8.14 : Unable to boot due to "initramfs unpacking failed: invalid magic at start of compress"
184) linux 5.9.14.arch1 1 /var/cache/pacman/pkg
183) linux-headers 5.9.14.arch1 1 /var/cache/pacman/pkg=> 5.9.14 : it works fine!
I tried two short duration sleeps (arround 5 seconds).
Then I tried a much longer sleep time duration. It still works!
So the issue seems to be between inside the 5.11 serie.
204) linux 5.11.arch1 1 remote
203) linux-headers 5.11.arch1 1 remote=> 5.11 : Same as 5.13.13 and 5.12.15, and 5.11.16
(Even a short sleep (arround 5 seconds) lead to a screen HANG-freeze.
Had to presse the button during 5 seconds so that I can stop the laptop then restart.
CTRL+DEL and CTRL+BACKSPACE didn't help.)
So the issue seems to be located between 5.10.16 and 5.11.0
I am willing to try some kernel 5.10.16-patchXXX if you can prepare one (or some) for me.
Regards !
Offline
Pages: 1