Skip to content

Instantly share code, notes, and snippets.

@nyanpasu64

nyanpasu64/journalctl --system.txt Secret

Last active October 12, 2023 21:27
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save nyanpasu64/6e1b19fc36190d145ecbdb57079e2d79 to your computer and use it in GitHub Desktop.
Save nyanpasu64/6e1b19fc36190d145ecbdb57079e2d79 to your computer and use it in GitHub Desktop.
Download ZIP
journalctl -b a5fc0caaa1a145f88498becad4835c3b
Raw
journalctl --system.txt
This file has been truncated, but you can view the full file.
Oct 11 17:22:50 ryzen kernel: Linux version 6.5.6-arch2-1 (linux@archlinux) (gcc (GCC) 13.2.1 20230801, GNU ld (GNU Binutils) 2.41.0) #3 SMP PREEMPT_DYNAMIC Tue, 10 Oct 2023 03:20:16 +0000
Oct 11 17:22:50 ryzen kernel: Command line: initrd=\amd-ucode.img initrd=\initramfs-linux.img root=PARTUUID=af314c7d-401b-4f6b-9a0b-ef1eafa9e228 rw acpi_enforce_resources=lax systemd.debug_shell no_console_suspend console=tty1 console=ttyS0,115200
Oct 11 17:22:50 ryzen kernel: BIOS-provided physical RAM map:
Oct 11 17:22:50 ryzen kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009ffff] usable
Oct 11 17:22:50 ryzen kernel: BIOS-e820: [mem 0x00000000000a0000-0x00000000000fffff] reserved
Oct 11 17:22:50 ryzen kernel: BIOS-e820: [mem 0x0000000000100000-0x0000000009ccefff] usable
Oct 11 17:22:50 ryzen kernel: BIOS-e820: [mem 0x0000000009ccf000-0x0000000009ffffff] reserved
Oct 11 17:22:50 ryzen kernel: BIOS-e820: [mem 0x000000000a000000-0x000000000a1fffff] usable
Oct 11 17:22:50 ryzen kernel: BIOS-e820: [mem 0x000000000a200000-0x000000000a20dfff] ACPI NVS
Oct 11 17:22:50 ryzen kernel: BIOS-e820: [mem 0x000000000a20e000-0x000000000affffff] usable
Oct 11 17:22:50 ryzen kernel: BIOS-e820: [mem 0x000000000b000000-0x000000000b01ffff] reserved
Oct 11 17:22:50 ryzen kernel: BIOS-e820: [mem 0x000000000b020000-0x00000000b9d45fff] usable
Oct 11 17:22:50 ryzen kernel: BIOS-e820: [mem 0x00000000b9d46000-0x00000000bc88afff] reserved
Oct 11 17:22:50 ryzen kernel: BIOS-e820: [mem 0x00000000bc88b000-0x00000000bc9f2fff] ACPI data
Oct 11 17:22:50 ryzen kernel: BIOS-e820: [mem 0x00000000bc9f3000-0x00000000bd0d4fff] ACPI NVS
Oct 11 17:22:50 ryzen kernel: BIOS-e820: [mem 0x00000000bd0d5000-0x00000000bddfefff] reserved
Oct 11 17:22:50 ryzen kernel: BIOS-e820: [mem 0x00000000bddff000-0x00000000beffffff] usable
Oct 11 17:22:50 ryzen kernel: BIOS-e820: [mem 0x00000000bf000000-0x00000000bfffffff] reserved
Oct 11 17:22:50 ryzen kernel: BIOS-e820: [mem 0x00000000f0000000-0x00000000f7ffffff] reserved
Oct 11 17:22:50 ryzen kernel: BIOS-e820: [mem 0x00000000fd200000-0x00000000fd2fffff] reserved
Oct 11 17:22:50 ryzen kernel: BIOS-e820: [mem 0x00000000fd600000-0x00000000fd7fffff] reserved
Oct 11 17:22:50 ryzen kernel: BIOS-e820: [mem 0x00000000fea00000-0x00000000fea0ffff] reserved
Oct 11 17:22:50 ryzen kernel: BIOS-e820: [mem 0x00000000feb80000-0x00000000fec01fff] reserved
Oct 11 17:22:50 ryzen kernel: BIOS-e820: [mem 0x00000000fec10000-0x00000000fec10fff] reserved
Oct 11 17:22:50 ryzen kernel: BIOS-e820: [mem 0x00000000fec30000-0x00000000fec30fff] reserved
Oct 11 17:22:50 ryzen kernel: BIOS-e820: [mem 0x00000000fed00000-0x00000000fed00fff] reserved
Oct 11 17:22:50 ryzen kernel: BIOS-e820: [mem 0x00000000fed40000-0x00000000fed44fff] reserved
Oct 11 17:22:50 ryzen kernel: BIOS-e820: [mem 0x00000000fed80000-0x00000000fed8ffff] reserved
Oct 11 17:22:50 ryzen kernel: BIOS-e820: [mem 0x00000000fedc2000-0x00000000fedcffff] reserved
Oct 11 17:22:50 ryzen kernel: BIOS-e820: [mem 0x00000000fedd4000-0x00000000fedd5fff] reserved
Oct 11 17:22:50 ryzen kernel: BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Oct 11 17:22:50 ryzen kernel: BIOS-e820: [mem 0x0000000100000000-0x000000043f37ffff] usable
Oct 11 17:22:50 ryzen kernel: BIOS-e820: [mem 0x000000043f380000-0x000000043fffffff] reserved
Oct 11 17:22:50 ryzen kernel: NX (Execute Disable) protection: active
Oct 11 17:22:50 ryzen kernel: e820: update [mem 0xb48e4018-0xb48f2057] usable ==> usable
Oct 11 17:22:50 ryzen kernel: e820: update [mem 0xb48e4018-0xb48f2057] usable ==> usable
Oct 11 17:22:50 ryzen kernel: e820: update [mem 0xb343c018-0xb3459657] usable ==> usable
Oct 11 17:22:50 ryzen kernel: e820: update [mem 0xb343c018-0xb3459657] usable ==> usable
Oct 11 17:22:50 ryzen kernel: extended physical RAM map:
Oct 11 17:22:50 ryzen kernel: reserve setup_data: [mem 0x0000000000000000-0x000000000009ffff] usable
Oct 11 17:22:50 ryzen kernel: reserve setup_data: [mem 0x00000000000a0000-0x00000000000fffff] reserved
Oct 11 17:22:50 ryzen kernel: reserve setup_data: [mem 0x0000000000100000-0x0000000009ccefff] usable
Oct 11 17:22:50 ryzen kernel: reserve setup_data: [mem 0x0000000009ccf000-0x0000000009ffffff] reserved
Oct 11 17:22:50 ryzen kernel: reserve setup_data: [mem 0x000000000a000000-0x000000000a1fffff] usable
Oct 11 17:22:50 ryzen kernel: reserve setup_data: [mem 0x000000000a200000-0x000000000a20dfff] ACPI NVS
Oct 11 17:22:50 ryzen kernel: reserve setup_data: [mem 0x000000000a20e000-0x000000000affffff] usable
Oct 11 17:22:50 ryzen kernel: reserve setup_data: [mem 0x000000000b000000-0x000000000b01ffff] reserved
Oct 11 17:22:50 ryzen kernel: reserve setup_data: [mem 0x000000000b020000-0x00000000b343c017] usable
Oct 11 17:22:50 ryzen kernel: reserve setup_data: [mem 0x00000000b343c018-0x00000000b3459657] usable
Oct 11 17:22:50 ryzen kernel: reserve setup_data: [mem 0x00000000b3459658-0x00000000b48e4017] usable
Oct 11 17:22:50 ryzen kernel: reserve setup_data: [mem 0x00000000b48e4018-0x00000000b48f2057] usable
Oct 11 17:22:50 ryzen kernel: reserve setup_data: [mem 0x00000000b48f2058-0x00000000b9d45fff] usable
Oct 11 17:22:50 ryzen kernel: reserve setup_data: [mem 0x00000000b9d46000-0x00000000bc88afff] reserved
Oct 11 17:22:50 ryzen kernel: reserve setup_data: [mem 0x00000000bc88b000-0x00000000bc9f2fff] ACPI data
Oct 11 17:22:50 ryzen kernel: reserve setup_data: [mem 0x00000000bc9f3000-0x00000000bd0d4fff] ACPI NVS
Oct 11 17:22:50 ryzen kernel: reserve setup_data: [mem 0x00000000bd0d5000-0x00000000bddfefff] reserved
Oct 11 17:22:50 ryzen kernel: reserve setup_data: [mem 0x00000000bddff000-0x00000000beffffff] usable
Oct 11 17:22:50 ryzen kernel: reserve setup_data: [mem 0x00000000bf000000-0x00000000bfffffff] reserved
Oct 11 17:22:50 ryzen kernel: reserve setup_data: [mem 0x00000000f0000000-0x00000000f7ffffff] reserved
Oct 11 17:22:50 ryzen kernel: reserve setup_data: [mem 0x00000000fd200000-0x00000000fd2fffff] reserved
Oct 11 17:22:50 ryzen kernel: reserve setup_data: [mem 0x00000000fd600000-0x00000000fd7fffff] reserved
Oct 11 17:22:50 ryzen kernel: reserve setup_data: [mem 0x00000000fea00000-0x00000000fea0ffff] reserved
Oct 11 17:22:50 ryzen kernel: reserve setup_data: [mem 0x00000000feb80000-0x00000000fec01fff] reserved
Oct 11 17:22:50 ryzen kernel: reserve setup_data: [mem 0x00000000fec10000-0x00000000fec10fff] reserved
Oct 11 17:22:50 ryzen kernel: reserve setup_data: [mem 0x00000000fec30000-0x00000000fec30fff] reserved
Oct 11 17:22:50 ryzen kernel: reserve setup_data: [mem 0x00000000fed00000-0x00000000fed00fff] reserved
Oct 11 17:22:50 ryzen kernel: reserve setup_data: [mem 0x00000000fed40000-0x00000000fed44fff] reserved
Oct 11 17:22:50 ryzen kernel: reserve setup_data: [mem 0x00000000fed80000-0x00000000fed8ffff] reserved
Oct 11 17:22:50 ryzen kernel: reserve setup_data: [mem 0x00000000fedc2000-0x00000000fedcffff] reserved
Oct 11 17:22:50 ryzen kernel: reserve setup_data: [mem 0x00000000fedd4000-0x00000000fedd5fff] reserved
Oct 11 17:22:50 ryzen kernel: reserve setup_data: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Oct 11 17:22:50 ryzen kernel: reserve setup_data: [mem 0x0000000100000000-0x000000043f37ffff] usable
Oct 11 17:22:50 ryzen kernel: reserve setup_data: [mem 0x000000043f380000-0x000000043fffffff] reserved
Oct 11 17:22:50 ryzen kernel: efi: EFI v2.7 by American Megatrends
Oct 11 17:22:50 ryzen kernel: efi: ACPI=0xbd0be000 ACPI 2.0=0xbd0be014 TPMFinalLog=0xbd088000 SMBIOS=0xbdc24000 SMBIOS 3.0=0xbdc23000 MEMATTR=0xb4b92018 ESRT=0xb7fd1f18 RNG=0xbc9d5f18 INITRD=0xb66e0e18 TPMEventLog=0xb6686018
Oct 11 17:22:50 ryzen kernel: random: crng init done
Oct 11 17:22:50 ryzen kernel: efi: Remove mem310: MMIO range=[0xf0000000-0xf7ffffff] (128MB) from e820 map
Oct 11 17:22:50 ryzen kernel: e820: remove [mem 0xf0000000-0xf7ffffff] reserved
Oct 11 17:22:50 ryzen kernel: efi: Remove mem311: MMIO range=[0xfd200000-0xfd2fffff] (1MB) from e820 map
Oct 11 17:22:50 ryzen kernel: e820: remove [mem 0xfd200000-0xfd2fffff] reserved
Oct 11 17:22:50 ryzen kernel: efi: Remove mem312: MMIO range=[0xfd600000-0xfd7fffff] (2MB) from e820 map
Oct 11 17:22:50 ryzen kernel: e820: remove [mem 0xfd600000-0xfd7fffff] reserved
Oct 11 17:22:50 ryzen kernel: efi: Not removing mem313: MMIO range=[0xfea00000-0xfea0ffff] (64KB) from e820 map
Oct 11 17:22:50 ryzen kernel: efi: Remove mem314: MMIO range=[0xfeb80000-0xfec01fff] (0MB) from e820 map
Oct 11 17:22:50 ryzen kernel: e820: remove [mem 0xfeb80000-0xfec01fff] reserved
Oct 11 17:22:50 ryzen kernel: efi: Not removing mem315: MMIO range=[0xfec10000-0xfec10fff] (4KB) from e820 map
Oct 11 17:22:50 ryzen kernel: efi: Not removing mem316: MMIO range=[0xfec30000-0xfec30fff] (4KB) from e820 map
Oct 11 17:22:50 ryzen kernel: efi: Not removing mem317: MMIO range=[0xfed00000-0xfed00fff] (4KB) from e820 map
Oct 11 17:22:50 ryzen kernel: efi: Not removing mem318: MMIO range=[0xfed40000-0xfed44fff] (20KB) from e820 map
Oct 11 17:22:50 ryzen kernel: efi: Not removing mem319: MMIO range=[0xfed80000-0xfed8ffff] (64KB) from e820 map
Oct 11 17:22:50 ryzen kernel: efi: Not removing mem320: MMIO range=[0xfedc2000-0xfedcffff] (56KB) from e820 map
Oct 11 17:22:50 ryzen kernel: efi: Not removing mem321: MMIO range=[0xfedd4000-0xfedd5fff] (8KB) from e820 map
Oct 11 17:22:50 ryzen kernel: efi: Remove mem322: MMIO range=[0xff000000-0xffffffff] (16MB) from e820 map
Oct 11 17:22:50 ryzen kernel: e820: remove [mem 0xff000000-0xffffffff] reserved
Oct 11 17:22:50 ryzen kernel: SMBIOS 3.3.0 present.
Oct 11 17:22:50 ryzen kernel: DMI: Gigabyte Technology Co., Ltd. B550M DS3H/B550M DS3H, BIOS F17f 06/01/2023
Oct 11 17:22:50 ryzen kernel: tsc: Fast TSC calibration using PIT
Oct 11 17:22:50 ryzen kernel: tsc: Detected 3692.838 MHz processor
Oct 11 17:22:50 ryzen kernel: e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Oct 11 17:22:50 ryzen kernel: e820: remove [mem 0x000a0000-0x000fffff] usable
Oct 11 17:22:50 ryzen kernel: last_pfn = 0x43f380 max_arch_pfn = 0x400000000
Oct 11 17:22:50 ryzen kernel: total RAM covered: 3071M
Oct 11 17:22:50 ryzen kernel: Found optimal setting for mtrr clean up
Oct 11 17:22:50 ryzen kernel: gran_size: 64K chunk_size: 64M num_reg: 3 lose cover RAM: 0G
Oct 11 17:22:50 ryzen kernel: MTRR map: 7 entries (3 fixed + 4 variable; max 20), built from 9 variable MTRRs
Oct 11 17:22:50 ryzen kernel: x86/PAT: Configuration [0-7]: WB WC UC- UC WB WP UC- WT
Oct 11 17:22:50 ryzen kernel: e820: update [mem 0xbcb60000-0xbcb6ffff] usable ==> reserved
Oct 11 17:22:50 ryzen kernel: e820: update [mem 0xc0000000-0xffffffff] usable ==> reserved
Oct 11 17:22:50 ryzen kernel: last_pfn = 0xbf000 max_arch_pfn = 0x400000000
Oct 11 17:22:50 ryzen kernel: esrt: Reserving ESRT space from 0x00000000b7fd1f18 to 0x00000000b7fd1f50.
Oct 11 17:22:50 ryzen kernel: e820: update [mem 0xb7fd1000-0xb7fd1fff] usable ==> reserved
Oct 11 17:22:50 ryzen kernel: Using GB pages for direct mapping
Oct 11 17:22:50 ryzen kernel: Secure boot disabled
Oct 11 17:22:50 ryzen kernel: RAMDISK: [mem 0xb345a000-0xb3e9bfff]
Oct 11 17:22:50 ryzen kernel: ACPI: Early table checksum verification disabled
Oct 11 17:22:50 ryzen kernel: ACPI: RSDP 0x00000000BD0BE014 000024 (v02 ALASKA)
Oct 11 17:22:50 ryzen kernel: ACPI: XSDT 0x00000000BD0BD728 0000E4 (v01 ALASKA A M I 01072009 AMI 01000013)
Oct 11 17:22:50 ryzen kernel: ACPI: FACP 0x00000000BC9D9000 000114 (v06 ALASKA A M I 01072009 AMI 00010013)
Oct 11 17:22:50 ryzen kernel: ACPI: DSDT 0x00000000BC9B4000 0069CC (v02 ALASKA A M I 01072009 INTL 20190509)
Oct 11 17:22:50 ryzen kernel: ACPI: FACS 0x00000000BD0B8000 000040
Oct 11 17:22:50 ryzen kernel: ACPI: SSDT 0x00000000BC9E8000 00AF41 (v02 GBT GSWApp 00000001 INTL 20190509)
Oct 11 17:22:50 ryzen kernel: ACPI: SSDT 0x00000000BC9DF000 008CE9 (v02 AMD AmdTable 00000002 MSFT 04000000)
Oct 11 17:22:50 ryzen kernel: ACPI: SSDT 0x00000000BC9DB000 003D7C (v02 AMD AMD AOD 00000001 INTL 20190509)
Oct 11 17:22:50 ryzen kernel: ACPI: SSDT 0x00000000BC9DA000 0001AD (v02 ALASKA CPUSSDT 01072009 AMI 01072009)
Oct 11 17:22:50 ryzen kernel: ACPI: FIDT 0x00000000BC9D2000 00009C (v01 ALASKA A M I 01072009 AMI 00010013)
Oct 11 17:22:50 ryzen kernel: ACPI: MCFG 0x00000000BC9D1000 00003C (v01 ALASKA A M I 01072009 MSFT 00010013)
Oct 11 17:22:50 ryzen kernel: ACPI: HPET 0x00000000BC9D0000 000038 (v01 ALASKA A M I 01072009 AMI 00000005)
Oct 11 17:22:50 ryzen kernel: ACPI: IVRS 0x00000000BC9CF000 0000D0 (v02 AMD AmdTable 00000001 AMD 00000001)
Oct 11 17:22:50 ryzen kernel: ACPI: FPDT 0x00000000BC9CE000 000044 (v01 ALASKA A M I 01072009 AMI 01000013)
Oct 11 17:22:50 ryzen kernel: ACPI: BGRT 0x00000000BC9CD000 000038 (v01 ALASKA A M I 01072009 AMI 00010013)
Oct 11 17:22:50 ryzen kernel: ACPI: TPM2 0x00000000BC9CC000 00004C (v04 ALASKA A M I 00000001 AMI 00000000)
Oct 11 17:22:50 ryzen kernel: ACPI: PCCT 0x00000000BC9CB000 00006E (v02 AMD AmdTable 00000001 AMD 00000001)
Oct 11 17:22:50 ryzen kernel: ACPI: SSDT 0x00000000BC9C7000 0030FB (v02 AMD AmdTable 00000001 AMD 00000001)
Oct 11 17:22:50 ryzen kernel: ACPI: CRAT 0x00000000BC9C6000 000B90 (v01 AMD AmdTable 00000001 AMD 00000001)
Oct 11 17:22:50 ryzen kernel: ACPI: CDIT 0x00000000BC9C5000 000029 (v01 AMD AmdTable 00000001 AMD 00000001)
Oct 11 17:22:50 ryzen kernel: ACPI: SSDT 0x00000000BC9C4000 000625 (v02 AMD ArticDGP 00000001 INTL 20190509)
Oct 11 17:22:50 ryzen kernel: ACPI: SSDT 0x00000000BC9C2000 001512 (v02 AMD ArticTPX 00000001 INTL 20190509)
Oct 11 17:22:50 ryzen kernel: ACPI: SSDT 0x00000000BC9C1000 000788 (v02 AMD ArticNOI 00000001 INTL 20190509)
Oct 11 17:22:50 ryzen kernel: ACPI: SSDT 0x00000000BC9BD000 003A23 (v02 AMD ArticN 00000001 INTL 20190509)
Oct 11 17:22:50 ryzen kernel: ACPI: WSMT 0x00000000BC9BC000 000028 (v01 ALASKA A M I 01072009 AMI 00010013)
Oct 11 17:22:50 ryzen kernel: ACPI: APIC 0x00000000BC9BB000 00015E (v04 ALASKA A M I 01072009 AMI 00010013)
Oct 11 17:22:50 ryzen kernel: ACPI: SSDT 0x00000000BC9D7000 00147F (v02 AMD ArticC 00000001 INTL 20190509)
Oct 11 17:22:50 ryzen kernel: ACPI: SSDT 0x00000000BC9D6000 0000BF (v01 AMD AmdTable 00001000 INTL 20190509)
Oct 11 17:22:50 ryzen kernel: ACPI: Reserving FACP table memory at [mem 0xbc9d9000-0xbc9d9113]
Oct 11 17:22:50 ryzen kernel: ACPI: Reserving DSDT table memory at [mem 0xbc9b4000-0xbc9ba9cb]
Oct 11 17:22:50 ryzen kernel: ACPI: Reserving FACS table memory at [mem 0xbd0b8000-0xbd0b803f]
Oct 11 17:22:50 ryzen kernel: ACPI: Reserving SSDT table memory at [mem 0xbc9e8000-0xbc9f2f40]
Oct 11 17:22:50 ryzen kernel: ACPI: Reserving SSDT table memory at [mem 0xbc9df000-0xbc9e7ce8]
Oct 11 17:22:50 ryzen kernel: ACPI: Reserving SSDT table memory at [mem 0xbc9db000-0xbc9ded7b]
Oct 11 17:22:50 ryzen kernel: ACPI: Reserving SSDT table memory at [mem 0xbc9da000-0xbc9da1ac]
Oct 11 17:22:50 ryzen kernel: ACPI: Reserving FIDT table memory at [mem 0xbc9d2000-0xbc9d209b]
Oct 11 17:22:50 ryzen kernel: ACPI: Reserving MCFG table memory at [mem 0xbc9d1000-0xbc9d103b]
Oct 11 17:22:50 ryzen kernel: ACPI: Reserving HPET table memory at [mem 0xbc9d0000-0xbc9d0037]
Oct 11 17:22:50 ryzen kernel: ACPI: Reserving IVRS table memory at [mem 0xbc9cf000-0xbc9cf0cf]
Oct 11 17:22:50 ryzen kernel: ACPI: Reserving FPDT table memory at [mem 0xbc9ce000-0xbc9ce043]
Oct 11 17:22:50 ryzen kernel: ACPI: Reserving BGRT table memory at [mem 0xbc9cd000-0xbc9cd037]
Oct 11 17:22:50 ryzen kernel: ACPI: Reserving TPM2 table memory at [mem 0xbc9cc000-0xbc9cc04b]
Oct 11 17:22:50 ryzen kernel: ACPI: Reserving PCCT table memory at [mem 0xbc9cb000-0xbc9cb06d]
Oct 11 17:22:50 ryzen kernel: ACPI: Reserving SSDT table memory at [mem 0xbc9c7000-0xbc9ca0fa]
Oct 11 17:22:50 ryzen kernel: ACPI: Reserving CRAT table memory at [mem 0xbc9c6000-0xbc9c6b8f]
Oct 11 17:22:50 ryzen kernel: ACPI: Reserving CDIT table memory at [mem 0xbc9c5000-0xbc9c5028]
Oct 11 17:22:50 ryzen kernel: ACPI: Reserving SSDT table memory at [mem 0xbc9c4000-0xbc9c4624]
Oct 11 17:22:50 ryzen kernel: ACPI: Reserving SSDT table memory at [mem 0xbc9c2000-0xbc9c3511]
Oct 11 17:22:50 ryzen kernel: ACPI: Reserving SSDT table memory at [mem 0xbc9c1000-0xbc9c1787]
Oct 11 17:22:50 ryzen kernel: ACPI: Reserving SSDT table memory at [mem 0xbc9bd000-0xbc9c0a22]
Oct 11 17:22:50 ryzen kernel: ACPI: Reserving WSMT table memory at [mem 0xbc9bc000-0xbc9bc027]
Oct 11 17:22:50 ryzen kernel: ACPI: Reserving APIC table memory at [mem 0xbc9bb000-0xbc9bb15d]
Oct 11 17:22:50 ryzen kernel: ACPI: Reserving SSDT table memory at [mem 0xbc9d7000-0xbc9d847e]
Oct 11 17:22:50 ryzen kernel: ACPI: Reserving SSDT table memory at [mem 0xbc9d6000-0xbc9d60be]
Oct 11 17:22:50 ryzen kernel: No NUMA configuration found
Oct 11 17:22:50 ryzen kernel: Faking a node at [mem 0x0000000000000000-0x000000043f37ffff]
Oct 11 17:22:50 ryzen kernel: NODE_DATA(0) allocated [mem 0x43f37b000-0x43f37ffff]
Oct 11 17:22:50 ryzen kernel: Zone ranges:
Oct 11 17:22:50 ryzen kernel: DMA [mem 0x0000000000001000-0x0000000000ffffff]
Oct 11 17:22:50 ryzen kernel: DMA32 [mem 0x0000000001000000-0x00000000ffffffff]
Oct 11 17:22:50 ryzen kernel: Normal [mem 0x0000000100000000-0x000000043f37ffff]
Oct 11 17:22:50 ryzen kernel: Device empty
Oct 11 17:22:50 ryzen kernel: Movable zone start for each node
Oct 11 17:22:50 ryzen kernel: Early memory node ranges
Oct 11 17:22:50 ryzen kernel: node 0: [mem 0x0000000000001000-0x000000000009ffff]
Oct 11 17:22:50 ryzen kernel: node 0: [mem 0x0000000000100000-0x0000000009ccefff]
Oct 11 17:22:50 ryzen kernel: node 0: [mem 0x000000000a000000-0x000000000a1fffff]
Oct 11 17:22:50 ryzen kernel: node 0: [mem 0x000000000a20e000-0x000000000affffff]
Oct 11 17:22:50 ryzen kernel: node 0: [mem 0x000000000b020000-0x00000000b9d45fff]
Oct 11 17:22:50 ryzen kernel: node 0: [mem 0x00000000bddff000-0x00000000beffffff]
Oct 11 17:22:50 ryzen kernel: node 0: [mem 0x0000000100000000-0x000000043f37ffff]
Oct 11 17:22:50 ryzen kernel: Initmem setup node 0 [mem 0x0000000000001000-0x000000043f37ffff]
Oct 11 17:22:50 ryzen kernel: On node 0, zone DMA: 1 pages in unavailable ranges
Oct 11 17:22:50 ryzen kernel: On node 0, zone DMA: 96 pages in unavailable ranges
Oct 11 17:22:50 ryzen kernel: On node 0, zone DMA32: 817 pages in unavailable ranges
Oct 11 17:22:50 ryzen kernel: On node 0, zone DMA32: 14 pages in unavailable ranges
Oct 11 17:22:50 ryzen kernel: On node 0, zone DMA32: 32 pages in unavailable ranges
Oct 11 17:22:50 ryzen kernel: On node 0, zone DMA32: 16569 pages in unavailable ranges
Oct 11 17:22:50 ryzen kernel: On node 0, zone Normal: 4096 pages in unavailable ranges
Oct 11 17:22:50 ryzen kernel: On node 0, zone Normal: 3200 pages in unavailable ranges
Oct 11 17:22:50 ryzen kernel: ACPI: PM-Timer IO Port: 0x808
Oct 11 17:22:50 ryzen kernel: ACPI: LAPIC_NMI (acpi_id[0xff] high edge lint[0x1])
Oct 11 17:22:50 ryzen kernel: IOAPIC[0]: apic_id 13, version 33, address 0xfec00000, GSI 0-23
Oct 11 17:22:50 ryzen kernel: IOAPIC[1]: apic_id 14, version 33, address 0xfec01000, GSI 24-55
Oct 11 17:22:50 ryzen kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Oct 11 17:22:50 ryzen kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 low level)
Oct 11 17:22:50 ryzen kernel: ACPI: Using ACPI (MADT) for SMP configuration information
Oct 11 17:22:50 ryzen kernel: ACPI: HPET id: 0x10228201 base: 0xfed00000
Oct 11 17:22:50 ryzen kernel: e820: update [mem 0xb51b6000-0xb51fafff] usable ==> reserved
Oct 11 17:22:50 ryzen kernel: smpboot: Allowing 32 CPUs, 20 hotplug CPUs
Oct 11 17:22:50 ryzen kernel: PM: hibernation: Registered nosave memory: [mem 0x00000000-0x00000fff]
Oct 11 17:22:50 ryzen kernel: PM: hibernation: Registered nosave memory: [mem 0x000a0000-0x000fffff]
Oct 11 17:22:50 ryzen kernel: PM: hibernation: Registered nosave memory: [mem 0x09ccf000-0x09ffffff]
Oct 11 17:22:50 ryzen kernel: PM: hibernation: Registered nosave memory: [mem 0x0a200000-0x0a20dfff]
Oct 11 17:22:50 ryzen kernel: PM: hibernation: Registered nosave memory: [mem 0x0b000000-0x0b01ffff]
Oct 11 17:22:50 ryzen kernel: PM: hibernation: Registered nosave memory: [mem 0xb343c000-0xb343cfff]
Oct 11 17:22:50 ryzen kernel: PM: hibernation: Registered nosave memory: [mem 0xb3459000-0xb3459fff]
Oct 11 17:22:50 ryzen kernel: PM: hibernation: Registered nosave memory: [mem 0xb48e4000-0xb48e4fff]
Oct 11 17:22:50 ryzen kernel: PM: hibernation: Registered nosave memory: [mem 0xb48f2000-0xb48f2fff]
Oct 11 17:22:50 ryzen kernel: PM: hibernation: Registered nosave memory: [mem 0xb51b6000-0xb51fafff]
Oct 11 17:22:50 ryzen kernel: PM: hibernation: Registered nosave memory: [mem 0xb7fd1000-0xb7fd1fff]
Oct 11 17:22:50 ryzen kernel: PM: hibernation: Registered nosave memory: [mem 0xb9d46000-0xbc88afff]
Oct 11 17:22:50 ryzen kernel: PM: hibernation: Registered nosave memory: [mem 0xbc88b000-0xbc9f2fff]
Oct 11 17:22:50 ryzen kernel: PM: hibernation: Registered nosave memory: [mem 0xbc9f3000-0xbd0d4fff]
Oct 11 17:22:50 ryzen kernel: PM: hibernation: Registered nosave memory: [mem 0xbd0d5000-0xbddfefff]
Oct 11 17:22:50 ryzen kernel: PM: hibernation: Registered nosave memory: [mem 0xbf000000-0xbfffffff]
Oct 11 17:22:50 ryzen kernel: PM: hibernation: Registered nosave memory: [mem 0xc0000000-0xfe9fffff]
Oct 11 17:22:50 ryzen kernel: PM: hibernation: Registered nosave memory: [mem 0xfea00000-0xfea0ffff]
Oct 11 17:22:50 ryzen kernel: PM: hibernation: Registered nosave memory: [mem 0xfea10000-0xfec0ffff]
Oct 11 17:22:50 ryzen kernel: PM: hibernation: Registered nosave memory: [mem 0xfec10000-0xfec10fff]
Oct 11 17:22:50 ryzen kernel: PM: hibernation: Registered nosave memory: [mem 0xfec11000-0xfec2ffff]
Oct 11 17:22:50 ryzen kernel: PM: hibernation: Registered nosave memory: [mem 0xfec30000-0xfec30fff]
Oct 11 17:22:50 ryzen kernel: PM: hibernation: Registered nosave memory: [mem 0xfec31000-0xfecfffff]
Oct 11 17:22:50 ryzen kernel: PM: hibernation: Registered nosave memory: [mem 0xfed00000-0xfed00fff]
Oct 11 17:22:50 ryzen kernel: PM: hibernation: Registered nosave memory: [mem 0xfed01000-0xfed3ffff]
Oct 11 17:22:50 ryzen kernel: PM: hibernation: Registered nosave memory: [mem 0xfed40000-0xfed44fff]
Oct 11 17:22:50 ryzen kernel: PM: hibernation: Registered nosave memory: [mem 0xfed45000-0xfed7ffff]
Oct 11 17:22:50 ryzen kernel: PM: hibernation: Registered nosave memory: [mem 0xfed80000-0xfed8ffff]
Oct 11 17:22:50 ryzen kernel: PM: hibernation: Registered nosave memory: [mem 0xfed90000-0xfedc1fff]
Oct 11 17:22:50 ryzen kernel: PM: hibernation: Registered nosave memory: [mem 0xfedc2000-0xfedcffff]
Oct 11 17:22:50 ryzen kernel: PM: hibernation: Registered nosave memory: [mem 0xfedd0000-0xfedd3fff]
Oct 11 17:22:50 ryzen kernel: PM: hibernation: Registered nosave memory: [mem 0xfedd4000-0xfedd5fff]
Oct 11 17:22:50 ryzen kernel: PM: hibernation: Registered nosave memory: [mem 0xfedd6000-0xffffffff]
Oct 11 17:22:50 ryzen kernel: [mem 0xc0000000-0xfe9fffff] available for PCI devices
Oct 11 17:22:50 ryzen kernel: Booting paravirtualized kernel on bare hardware
Oct 11 17:22:50 ryzen kernel: clocksource: refined-jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 6370452778343963 ns
Oct 11 17:22:50 ryzen kernel: setup_percpu: NR_CPUS:320 nr_cpumask_bits:32 nr_cpu_ids:32 nr_node_ids:1
Oct 11 17:22:50 ryzen kernel: percpu: Embedded 64 pages/cpu s225280 r8192 d28672 u262144
Oct 11 17:22:50 ryzen kernel: pcpu-alloc: s225280 r8192 d28672 u262144 alloc=1*2097152
Oct 11 17:22:50 ryzen kernel: pcpu-alloc: [0] 00 01 02 03 04 05 06 07 [0] 08 09 10 11 12 13 14 15
Oct 11 17:22:50 ryzen kernel: pcpu-alloc: [0] 16 17 18 19 20 21 22 23 [0] 24 25 26 27 28 29 30 31
Oct 11 17:22:50 ryzen kernel: Kernel command line: initrd=\amd-ucode.img initrd=\initramfs-linux.img root=PARTUUID=af314c7d-401b-4f6b-9a0b-ef1eafa9e228 rw acpi_enforce_resources=lax systemd.debug_shell no_console_suspend console=tty1 console=ttyS0,115200
Oct 11 17:22:50 ryzen kernel: printk: log_buf_len individual max cpu contribution: 4096 bytes
Oct 11 17:22:50 ryzen kernel: printk: log_buf_len total cpu_extra contributions: 126976 bytes
Oct 11 17:22:50 ryzen kernel: printk: log_buf_len min size: 131072 bytes
Oct 11 17:22:50 ryzen kernel: printk: log_buf_len: 262144 bytes
Oct 11 17:22:50 ryzen kernel: printk: early log buf free: 112000(85%)
Oct 11 17:22:50 ryzen kernel: Dentry cache hash table entries: 2097152 (order: 12, 16777216 bytes, linear)
Oct 11 17:22:50 ryzen kernel: Inode-cache hash table entries: 1048576 (order: 11, 8388608 bytes, linear)
Oct 11 17:22:50 ryzen kernel: Fallback order for Node 0: 0
Oct 11 17:22:50 ryzen kernel: Built 1 zonelists, mobility grouping on. Total pages: 4104170
Oct 11 17:22:50 ryzen kernel: Policy zone: Normal
Oct 11 17:22:50 ryzen kernel: mem auto-init: stack:all(zero), heap alloc:on, heap free:off
Oct 11 17:22:50 ryzen kernel: software IO TLB: area num 32.
Oct 11 17:22:50 ryzen kernel: Memory: 16152540K/16677916K available (16384K kernel code, 2123K rwdata, 12956K rodata, 3384K init, 3916K bss, 525116K reserved, 0K cma-reserved)
Oct 11 17:22:50 ryzen kernel: SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=32, Nodes=1
Oct 11 17:22:50 ryzen kernel: ftrace: allocating 48464 entries in 190 pages
Oct 11 17:22:50 ryzen kernel: ftrace: allocated 190 pages with 6 groups
Oct 11 17:22:50 ryzen kernel: Dynamic Preempt: full
Oct 11 17:22:50 ryzen kernel: rcu: Preemptible hierarchical RCU implementation.
Oct 11 17:22:50 ryzen kernel: rcu: RCU restricting CPUs from NR_CPUS=320 to nr_cpu_ids=32.
Oct 11 17:22:50 ryzen kernel: rcu: RCU priority boosting: priority 1 delay 500 ms.
Oct 11 17:22:50 ryzen kernel: Trampoline variant of Tasks RCU enabled.
Oct 11 17:22:50 ryzen kernel: Rude variant of Tasks RCU enabled.
Oct 11 17:22:50 ryzen kernel: Tracing variant of Tasks RCU enabled.
Oct 11 17:22:50 ryzen kernel: rcu: RCU calculated value of scheduler-enlistment delay is 30 jiffies.
Oct 11 17:22:50 ryzen kernel: rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=32
Oct 11 17:22:50 ryzen kernel: NR_IRQS: 20736, nr_irqs: 1224, preallocated irqs: 16
Oct 11 17:22:50 ryzen kernel: rcu: srcu_init: Setting srcu_struct sizes based on contention.
Oct 11 17:22:50 ryzen kernel: kfence: initialized - using 2097152 bytes for 255 objects at 0x(____ptrval____)-0x(____ptrval____)
Oct 11 17:22:50 ryzen kernel: Console: colour dummy device 80x25
Oct 11 17:22:50 ryzen kernel: printk: console [tty1] enabled
Oct 11 17:22:50 ryzen kernel: printk: console [ttyS0] enabled
Oct 11 17:22:50 ryzen kernel: ACPI: Core revision 20230331
Oct 11 17:22:50 ryzen kernel: clocksource: hpet: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 133484873504 ns
Oct 11 17:22:50 ryzen kernel: APIC: Switch to symmetric I/O mode setup
Oct 11 17:22:50 ryzen kernel: AMD-Vi: Using global IVHD EFR:0x0, EFR2:0x0
Oct 11 17:22:50 ryzen kernel: x2apic: IRQ remapping doesn't support X2APIC mode
Oct 11 17:22:50 ryzen kernel: Switched APIC routing to physical flat.
Oct 11 17:22:50 ryzen kernel: ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Oct 11 17:22:50 ryzen kernel: clocksource: tsc-early: mask: 0xffffffffffffffff max_cycles: 0x6a75d274011, max_idle_ns: 881590938525 ns
Oct 11 17:22:50 ryzen kernel: Calibrating delay loop (skipped), value calculated using timer frequency.. 7388.41 BogoMIPS (lpj=12309460)
Oct 11 17:22:50 ryzen kernel: x86/cpu: User Mode Instruction Prevention (UMIP) activated
Oct 11 17:22:50 ryzen kernel: LVT offset 1 assigned for vector 0xf9
Oct 11 17:22:50 ryzen kernel: LVT offset 2 assigned for vector 0xf4
Oct 11 17:22:50 ryzen kernel: process: using mwait in idle threads
Oct 11 17:22:50 ryzen kernel: Last level iTLB entries: 4KB 512, 2MB 512, 4MB 256
Oct 11 17:22:50 ryzen kernel: Last level dTLB entries: 4KB 2048, 2MB 2048, 4MB 1024, 1GB 0
Oct 11 17:22:50 ryzen kernel: Spectre V1 : Mitigation: usercopy/swapgs barriers and __user pointer sanitization
Oct 11 17:22:50 ryzen kernel: Spectre V2 : Mitigation: Retpolines
Oct 11 17:22:50 ryzen kernel: Spectre V2 : Spectre v2 / SpectreRSB mitigation: Filling RSB on context switch
Oct 11 17:22:50 ryzen kernel: Spectre V2 : Spectre v2 / SpectreRSB : Filling RSB on VMEXIT
Oct 11 17:22:50 ryzen kernel: Spectre V2 : Enabling Restricted Speculation for firmware calls
Oct 11 17:22:50 ryzen kernel: Spectre V2 : mitigation: Enabling conditional Indirect Branch Prediction Barrier
Oct 11 17:22:50 ryzen kernel: Spectre V2 : User space: Mitigation: STIBP always-on protection
Oct 11 17:22:50 ryzen kernel: Speculative Store Bypass: Mitigation: Speculative Store Bypass disabled via prctl
Oct 11 17:22:50 ryzen kernel: Speculative Return Stack Overflow: IBPB-extending microcode not applied!
Oct 11 17:22:50 ryzen kernel: Speculative Return Stack Overflow: WARNING: See https://kernel.org/doc/html/latest/admin-guide/hw-vuln/srso.html for mitigation options.
Oct 11 17:22:50 ryzen kernel: Speculative Return Stack Overflow: Mitigation: safe RET, no microcode
Oct 11 17:22:50 ryzen kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
Oct 11 17:22:50 ryzen kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
Oct 11 17:22:50 ryzen kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
Oct 11 17:22:50 ryzen kernel: x86/fpu: Supporting XSAVE feature 0x200: 'Protection Keys User registers'
Oct 11 17:22:50 ryzen kernel: x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256
Oct 11 17:22:50 ryzen kernel: x86/fpu: xstate_offset[9]: 832, xstate_sizes[9]: 8
Oct 11 17:22:50 ryzen kernel: x86/fpu: Enabled xstate features 0x207, context size is 840 bytes, using 'compacted' format.
Oct 11 17:22:50 ryzen kernel: Freeing SMP alternatives memory: 40K
Oct 11 17:22:50 ryzen kernel: pid_max: default: 32768 minimum: 301
Oct 11 17:22:50 ryzen kernel: LSM: initializing lsm=capability,landlock,lockdown,yama,bpf,integrity
Oct 11 17:22:50 ryzen kernel: landlock: Up and running.
Oct 11 17:22:50 ryzen kernel: Yama: becoming mindful.
Oct 11 17:22:50 ryzen kernel: LSM support for eBPF active
Oct 11 17:22:50 ryzen kernel: Mount-cache hash table entries: 32768 (order: 6, 262144 bytes, linear)
Oct 11 17:22:50 ryzen kernel: Mountpoint-cache hash table entries: 32768 (order: 6, 262144 bytes, linear)
Oct 11 17:22:50 ryzen kernel: smpboot: CPU0: AMD Ryzen 5 5600X 6-Core Processor (family: 0x19, model: 0x21, stepping: 0x0)
Oct 11 17:22:50 ryzen kernel: RCU Tasks: Setting shift to 5 and lim to 1 rcu_task_cb_adjust=1.
Oct 11 17:22:50 ryzen kernel: RCU Tasks Rude: Setting shift to 5 and lim to 1 rcu_task_cb_adjust=1.
Oct 11 17:22:50 ryzen kernel: RCU Tasks Trace: Setting shift to 5 and lim to 1 rcu_task_cb_adjust=1.
Oct 11 17:22:50 ryzen kernel: Performance Events: Fam17h+ core perfctr, AMD PMU driver.
Oct 11 17:22:50 ryzen kernel: ... version: 0
Oct 11 17:22:50 ryzen kernel: ... bit width: 48
Oct 11 17:22:50 ryzen kernel: ... generic registers: 6
Oct 11 17:22:50 ryzen kernel: ... value mask: 0000ffffffffffff
Oct 11 17:22:50 ryzen kernel: ... max period: 00007fffffffffff
Oct 11 17:22:50 ryzen kernel: ... fixed-purpose events: 0
Oct 11 17:22:50 ryzen kernel: ... event mask: 000000000000003f
Oct 11 17:22:50 ryzen kernel: signal: max sigframe size: 3376
Oct 11 17:22:50 ryzen kernel: rcu: Hierarchical SRCU implementation.
Oct 11 17:22:50 ryzen kernel: rcu: Max phase no-delay instances is 1000.
Oct 11 17:22:50 ryzen kernel: NMI watchdog: Enabled. Permanently consumes one hw-PMU counter.
Oct 11 17:22:50 ryzen kernel: smp: Bringing up secondary CPUs ...
Oct 11 17:22:50 ryzen kernel: smpboot: x86: Booting SMP configuration:
Oct 11 17:22:50 ryzen kernel: .... node #0, CPUs: #1 #2 #3 #4 #5 #6 #7 #8 #9 #10 #11
Oct 11 17:22:50 ryzen kernel: Spectre V2 : Update user space SMT mitigation: STIBP always-on
Oct 11 17:22:50 ryzen kernel: smp: Brought up 1 node, 12 CPUs
Oct 11 17:22:50 ryzen kernel: smpboot: Max logical packages: 3
Oct 11 17:22:50 ryzen kernel: smpboot: Total of 12 processors activated (88663.95 BogoMIPS)
Oct 11 17:22:50 ryzen kernel: devtmpfs: initialized
Oct 11 17:22:50 ryzen kernel: x86/mm: Memory block size: 128MB
Oct 11 17:22:50 ryzen kernel: ACPI: PM: Registering ACPI NVS region [mem 0x0a200000-0x0a20dfff] (57344 bytes)
Oct 11 17:22:50 ryzen kernel: ACPI: PM: Registering ACPI NVS region [mem 0xbc9f3000-0xbd0d4fff] (7217152 bytes)
Oct 11 17:22:50 ryzen kernel: clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 6370867519511994 ns
Oct 11 17:22:50 ryzen kernel: futex hash table entries: 8192 (order: 7, 524288 bytes, linear)
Oct 11 17:22:50 ryzen kernel: pinctrl core: initialized pinctrl subsystem
Oct 11 17:22:50 ryzen kernel: PM: RTC time: 00:22:42, date: 2023-10-12
Oct 11 17:22:50 ryzen kernel: NET: Registered PF_NETLINK/PF_ROUTE protocol family
Oct 11 17:22:50 ryzen kernel: DMA: preallocated 2048 KiB GFP_KERNEL pool for atomic allocations
Oct 11 17:22:50 ryzen kernel: DMA: preallocated 2048 KiB GFP_KERNEL|GFP_DMA pool for atomic allocations
Oct 11 17:22:50 ryzen kernel: DMA: preallocated 2048 KiB GFP_KERNEL|GFP_DMA32 pool for atomic allocations
Oct 11 17:22:50 ryzen kernel: audit: initializing netlink subsys (disabled)
Oct 11 17:22:50 ryzen kernel: audit: type=2000 audit(1697070162.173:1): state=initialized audit_enabled=0 res=1
Oct 11 17:22:50 ryzen kernel: thermal_sys: Registered thermal governor 'fair_share'
Oct 11 17:22:50 ryzen kernel: thermal_sys: Registered thermal governor 'bang_bang'
Oct 11 17:22:50 ryzen kernel: thermal_sys: Registered thermal governor 'step_wise'
Oct 11 17:22:50 ryzen kernel: thermal_sys: Registered thermal governor 'user_space'
Oct 11 17:22:50 ryzen kernel: thermal_sys: Registered thermal governor 'power_allocator'
Oct 11 17:22:50 ryzen kernel: cpuidle: using governor ladder
Oct 11 17:22:50 ryzen kernel: cpuidle: using governor menu
Oct 11 17:22:50 ryzen kernel: Detected 1 PCC Subspaces
Oct 11 17:22:50 ryzen kernel: Registering PCC driver as Mailbox controller
Oct 11 17:22:50 ryzen kernel: acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Oct 11 17:22:50 ryzen kernel: PCI: MMCONFIG for domain 0000 [bus 00-7f] at [mem 0xf0000000-0xf7ffffff] (base 0xf0000000)
Oct 11 17:22:50 ryzen kernel: PCI: not using MMCONFIG
Oct 11 17:22:50 ryzen kernel: PCI: Using configuration type 1 for base access
Oct 11 17:22:50 ryzen kernel: PCI: Using configuration type 1 for extended access
Oct 11 17:22:50 ryzen kernel: kprobes: kprobe jump-optimization is enabled. All kprobes are optimized if possible.
Oct 11 17:22:50 ryzen kernel: HugeTLB: registered 1.00 GiB page size, pre-allocated 0 pages
Oct 11 17:22:50 ryzen kernel: HugeTLB: 16380 KiB vmemmap can be freed for a 1.00 GiB page
Oct 11 17:22:50 ryzen kernel: HugeTLB: registered 2.00 MiB page size, pre-allocated 0 pages
Oct 11 17:22:50 ryzen kernel: HugeTLB: 28 KiB vmemmap can be freed for a 2.00 MiB page
Oct 11 17:22:50 ryzen kernel: ACPI: Added _OSI(Module Device)
Oct 11 17:22:50 ryzen kernel: ACPI: Added _OSI(Processor Device)
Oct 11 17:22:50 ryzen kernel: ACPI: Added _OSI(3.0 _SCP Extensions)
Oct 11 17:22:50 ryzen kernel: ACPI: Added _OSI(Processor Aggregator Device)
Oct 11 17:22:50 ryzen kernel: ACPI: 12 ACPI AML tables successfully acquired and loaded
Oct 11 17:22:50 ryzen kernel: ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
Oct 11 17:22:50 ryzen kernel: ACPI: Interpreter enabled
Oct 11 17:22:50 ryzen kernel: ACPI: PM: (supports S0 S3 S4 S5)
Oct 11 17:22:50 ryzen kernel: ACPI: Using IOAPIC for interrupt routing
Oct 11 17:22:50 ryzen kernel: PCI: MMCONFIG for domain 0000 [bus 00-7f] at [mem 0xf0000000-0xf7ffffff] (base 0xf0000000)
Oct 11 17:22:50 ryzen kernel: PCI: MMCONFIG at [mem 0xf0000000-0xf7ffffff] reserved as ACPI motherboard resource
Oct 11 17:22:50 ryzen kernel: PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Oct 11 17:22:50 ryzen kernel: PCI: Ignoring E820 reservations for host bridge windows
Oct 11 17:22:50 ryzen kernel: ACPI: Enabled 8 GPEs in block 00 to 1F
Oct 11 17:22:50 ryzen kernel: ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff])
Oct 11 17:22:50 ryzen kernel: acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI EDR HPX-Type3]
Oct 11 17:22:50 ryzen kernel: acpi PNP0A08:00: _OSC: platform does not support [SHPCHotplug LTR DPC]
Oct 11 17:22:50 ryzen kernel: acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Oct 11 17:22:50 ryzen kernel: acpi PNP0A08:00: [Firmware Info]: MMCONFIG for domain 0000 [bus 00-7f] only partially covers this bridge
Oct 11 17:22:50 ryzen kernel: PCI host bridge to bus 0000:00
Oct 11 17:22:50 ryzen kernel: pci_bus 0000:00: root bus resource [io 0x0000-0x03af window]
Oct 11 17:22:50 ryzen kernel: pci_bus 0000:00: root bus resource [io 0x03e0-0x0cf7 window]
Oct 11 17:22:50 ryzen kernel: pci_bus 0000:00: root bus resource [io 0x03b0-0x03df window]
Oct 11 17:22:50 ryzen kernel: pci_bus 0000:00: root bus resource [io 0x0d00-0xffff window]
Oct 11 17:22:50 ryzen kernel: pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000dffff window]
Oct 11 17:22:50 ryzen kernel: pci_bus 0000:00: root bus resource [mem 0xc0000000-0xfec2ffff window]
Oct 11 17:22:50 ryzen kernel: pci_bus 0000:00: root bus resource [mem 0xfee00000-0xffffffff window]
Oct 11 17:22:50 ryzen kernel: pci_bus 0000:00: root bus resource [bus 00-ff]
Oct 11 17:22:50 ryzen kernel: pci 0000:00:00.0: [1022:1480] type 00 class 0x060000
Oct 11 17:22:50 ryzen kernel: pci 0000:00:00.2: [1022:1481] type 00 class 0x080600
Oct 11 17:22:50 ryzen kernel: pci 0000:00:01.0: [1022:1482] type 00 class 0x060000
Oct 11 17:22:50 ryzen kernel: pci 0000:00:01.1: [1022:1483] type 01 class 0x060400
Oct 11 17:22:50 ryzen kernel: pci 0000:00:01.1: enabling Extended Tags
Oct 11 17:22:50 ryzen kernel: pci 0000:00:01.1: PME# supported from D0 D3hot D3cold
Oct 11 17:22:50 ryzen kernel: pci 0000:00:01.2: [1022:1483] type 01 class 0x060400
Oct 11 17:22:50 ryzen kernel: pci 0000:00:01.2: enabling Extended Tags
Oct 11 17:22:50 ryzen kernel: pci 0000:00:01.2: PME# supported from D0 D3hot D3cold
Oct 11 17:22:50 ryzen kernel: pci 0000:00:02.0: [1022:1482] type 00 class 0x060000
Oct 11 17:22:50 ryzen kernel: pci 0000:00:03.0: [1022:1482] type 00 class 0x060000
Oct 11 17:22:50 ryzen kernel: pci 0000:00:03.1: [1022:1483] type 01 class 0x060400
Oct 11 17:22:50 ryzen kernel: pci 0000:00:03.1: PME# supported from D0 D3hot D3cold
Oct 11 17:22:50 ryzen kernel: pci 0000:00:04.0: [1022:1482] type 00 class 0x060000
Oct 11 17:22:50 ryzen kernel: pci 0000:00:05.0: [1022:1482] type 00 class 0x060000
Oct 11 17:22:50 ryzen kernel: pci 0000:00:07.0: [1022:1482] type 00 class 0x060000
Oct 11 17:22:50 ryzen kernel: pci 0000:00:07.1: [1022:1484] type 01 class 0x060400
Oct 11 17:22:50 ryzen kernel: pci 0000:00:07.1: enabling Extended Tags
Oct 11 17:22:50 ryzen kernel: pci 0000:00:07.1: PME# supported from D0 D3hot D3cold
Oct 11 17:22:50 ryzen kernel: pci 0000:00:08.0: [1022:1482] type 00 class 0x060000
Oct 11 17:22:50 ryzen kernel: pci 0000:00:08.1: [1022:1484] type 01 class 0x060400
Oct 11 17:22:50 ryzen kernel: pci 0000:00:08.1: enabling Extended Tags
Oct 11 17:22:50 ryzen kernel: pci 0000:00:08.1: PME# supported from D0 D3hot D3cold
Oct 11 17:22:50 ryzen kernel: pci 0000:00:14.0: [1022:790b] type 00 class 0x0c0500
Oct 11 17:22:50 ryzen kernel: pci 0000:00:14.3: [1022:790e] type 00 class 0x060100
Oct 11 17:22:50 ryzen kernel: pci 0000:00:18.0: [1022:1440] type 00 class 0x060000
Oct 11 17:22:50 ryzen kernel: pci 0000:00:18.1: [1022:1441] type 00 class 0x060000
Oct 11 17:22:50 ryzen kernel: pci 0000:00:18.2: [1022:1442] type 00 class 0x060000
Oct 11 17:22:50 ryzen kernel: pci 0000:00:18.3: [1022:1443] type 00 class 0x060000
Oct 11 17:22:50 ryzen kernel: pci 0000:00:18.4: [1022:1444] type 00 class 0x060000
Oct 11 17:22:50 ryzen kernel: pci 0000:00:18.5: [1022:1445] type 00 class 0x060000
Oct 11 17:22:50 ryzen kernel: pci 0000:00:18.6: [1022:1446] type 00 class 0x060000
Oct 11 17:22:50 ryzen kernel: pci 0000:00:18.7: [1022:1447] type 00 class 0x060000
Oct 11 17:22:50 ryzen kernel: pci 0000:01:00.0: [144d:a808] type 00 class 0x010802
Oct 11 17:22:50 ryzen kernel: pci 0000:01:00.0: reg 0x10: [mem 0xfcf00000-0xfcf03fff 64bit]
Oct 11 17:22:50 ryzen kernel: pci 0000:00:01.1: PCI bridge to [bus 01]
Oct 11 17:22:50 ryzen kernel: pci 0000:00:01.1: bridge window [mem 0xfcf00000-0xfcffffff]
Oct 11 17:22:50 ryzen kernel: pci 0000:02:00.0: [1022:43ee] type 00 class 0x0c0330
Oct 11 17:22:50 ryzen kernel: pci 0000:02:00.0: reg 0x10: [mem 0xfcda0000-0xfcda7fff 64bit]
Oct 11 17:22:50 ryzen kernel: pci 0000:02:00.0: enabling Extended Tags
Oct 11 17:22:50 ryzen kernel: pci 0000:02:00.0: PME# supported from D3hot D3cold
Oct 11 17:22:50 ryzen kernel: pci 0000:02:00.1: [1022:43eb] type 00 class 0x010601
Oct 11 17:22:50 ryzen kernel: pci 0000:02:00.1: reg 0x24: [mem 0xfcd80000-0xfcd9ffff]
Oct 11 17:22:50 ryzen kernel: pci 0000:02:00.1: reg 0x30: [mem 0xfcd00000-0xfcd7ffff pref]
Oct 11 17:22:50 ryzen kernel: pci 0000:02:00.1: enabling Extended Tags
Oct 11 17:22:50 ryzen kernel: pci 0000:02:00.1: PME# supported from D3hot D3cold
Oct 11 17:22:50 ryzen kernel: pci 0000:02:00.2: [1022:43e9] type 01 class 0x060400
Oct 11 17:22:50 ryzen kernel: pci 0000:02:00.2: enabling Extended Tags
Oct 11 17:22:50 ryzen kernel: pci 0000:02:00.2: PME# supported from D3hot D3cold
Oct 11 17:22:50 ryzen kernel: pci 0000:00:01.2: PCI bridge to [bus 02-04]
Oct 11 17:22:50 ryzen kernel: pci 0000:00:01.2: bridge window [io 0xf000-0xffff]
Oct 11 17:22:50 ryzen kernel: pci 0000:00:01.2: bridge window [mem 0xfcc00000-0xfcdfffff]
Oct 11 17:22:50 ryzen kernel: pci 0000:03:09.0: [1022:43ea] type 01 class 0x060400
Oct 11 17:22:50 ryzen kernel: pci 0000:03:09.0: enabling Extended Tags
Oct 11 17:22:50 ryzen kernel: pci 0000:03:09.0: PME# supported from D3hot D3cold
Oct 11 17:22:50 ryzen kernel: pci 0000:02:00.2: PCI bridge to [bus 03-04]
Oct 11 17:22:50 ryzen kernel: pci 0000:02:00.2: bridge window [io 0xf000-0xffff]
Oct 11 17:22:50 ryzen kernel: pci 0000:02:00.2: bridge window [mem 0xfcc00000-0xfccfffff]
Oct 11 17:22:50 ryzen kernel: pci 0000:04:00.0: [10ec:8168] type 00 class 0x020000
Oct 11 17:22:50 ryzen kernel: pci 0000:04:00.0: reg 0x10: [io 0xf000-0xf0ff]
Oct 11 17:22:50 ryzen kernel: pci 0000:04:00.0: reg 0x18: [mem 0xfcc04000-0xfcc04fff 64bit]
Oct 11 17:22:50 ryzen kernel: pci 0000:04:00.0: reg 0x20: [mem 0xfcc00000-0xfcc03fff 64bit]
Oct 11 17:22:50 ryzen kernel: pci 0000:04:00.0: supports D1 D2
Oct 11 17:22:50 ryzen kernel: pci 0000:04:00.0: PME# supported from D0 D1 D2 D3hot D3cold
Oct 11 17:22:50 ryzen kernel: pci 0000:03:09.0: PCI bridge to [bus 04]
Oct 11 17:22:50 ryzen kernel: pci 0000:03:09.0: bridge window [io 0xf000-0xffff]
Oct 11 17:22:50 ryzen kernel: pci 0000:03:09.0: bridge window [mem 0xfcc00000-0xfccfffff]
Oct 11 17:22:50 ryzen kernel: pci 0000:05:00.0: [1002:67df] type 00 class 0x030000
Oct 11 17:22:50 ryzen kernel: pci 0000:05:00.0: reg 0x10: [mem 0xd0000000-0xdfffffff 64bit pref]
Oct 11 17:22:50 ryzen kernel: pci 0000:05:00.0: reg 0x18: [mem 0xe0000000-0xe01fffff 64bit pref]
Oct 11 17:22:50 ryzen kernel: pci 0000:05:00.0: reg 0x20: [io 0xe000-0xe0ff]
Oct 11 17:22:50 ryzen kernel: pci 0000:05:00.0: reg 0x24: [mem 0xfce00000-0xfce3ffff]
Oct 11 17:22:50 ryzen kernel: pci 0000:05:00.0: reg 0x30: [mem 0xfce40000-0xfce5ffff pref]
Oct 11 17:22:50 ryzen kernel: pci 0000:05:00.0: BAR 0: assigned to efifb
Oct 11 17:22:50 ryzen kernel: pci 0000:05:00.0: Video device with shadowed ROM at [mem 0x000c0000-0x000dffff]
Oct 11 17:22:50 ryzen kernel: pci 0000:05:00.0: supports D1 D2
Oct 11 17:22:50 ryzen kernel: pci 0000:05:00.0: PME# supported from D1 D2 D3hot D3cold
Oct 11 17:22:50 ryzen kernel: pci 0000:05:00.1: [1002:aaf0] type 00 class 0x040300
Oct 11 17:22:50 ryzen kernel: pci 0000:05:00.1: reg 0x10: [mem 0xfce60000-0xfce63fff 64bit]
Oct 11 17:22:50 ryzen kernel: pci 0000:05:00.1: supports D1 D2
Oct 11 17:22:50 ryzen kernel: pci 0000:00:03.1: PCI bridge to [bus 05]
Oct 11 17:22:50 ryzen kernel: pci 0000:00:03.1: bridge window [io 0xe000-0xefff]
Oct 11 17:22:50 ryzen kernel: pci 0000:00:03.1: bridge window [mem 0xfce00000-0xfcefffff]
Oct 11 17:22:50 ryzen kernel: pci 0000:00:03.1: bridge window [mem 0xd0000000-0xe01fffff 64bit pref]
Oct 11 17:22:50 ryzen kernel: pci 0000:06:00.0: [1022:148a] type 00 class 0x130000
Oct 11 17:22:50 ryzen kernel: pci 0000:06:00.0: enabling Extended Tags
Oct 11 17:22:50 ryzen kernel: pci 0000:00:07.1: PCI bridge to [bus 06]
Oct 11 17:22:50 ryzen kernel: pci 0000:07:00.0: [1022:1485] type 00 class 0x130000
Oct 11 17:22:50 ryzen kernel: pci 0000:07:00.0: enabling Extended Tags
Oct 11 17:22:50 ryzen kernel: pci 0000:07:00.1: [1022:1486] type 00 class 0x108000
Oct 11 17:22:50 ryzen kernel: pci 0000:07:00.1: reg 0x18: [mem 0xfca00000-0xfcafffff]
Oct 11 17:22:50 ryzen kernel: pci 0000:07:00.1: reg 0x24: [mem 0xfcb08000-0xfcb09fff]
Oct 11 17:22:50 ryzen kernel: pci 0000:07:00.1: enabling Extended Tags
Oct 11 17:22:50 ryzen kernel: pci 0000:07:00.3: [1022:149c] type 00 class 0x0c0330
Oct 11 17:22:50 ryzen kernel: pci 0000:07:00.3: reg 0x10: [mem 0xfc900000-0xfc9fffff 64bit]
Oct 11 17:22:50 ryzen kernel: pci 0000:07:00.3: enabling Extended Tags
Oct 11 17:22:50 ryzen kernel: pci 0000:07:00.3: PME# supported from D0 D3hot D3cold
Oct 11 17:22:50 ryzen kernel: pci 0000:07:00.4: [1022:1487] type 00 class 0x040300
Oct 11 17:22:50 ryzen kernel: pci 0000:07:00.4: reg 0x10: [mem 0xfcb00000-0xfcb07fff]
Oct 11 17:22:50 ryzen kernel: pci 0000:07:00.4: enabling Extended Tags
Oct 11 17:22:50 ryzen kernel: pci 0000:07:00.4: PME# supported from D0 D3hot D3cold
Oct 11 17:22:50 ryzen kernel: pci 0000:00:08.1: PCI bridge to [bus 07]
Oct 11 17:22:50 ryzen kernel: pci 0000:00:08.1: bridge window [mem 0xfc900000-0xfcbfffff]
Oct 11 17:22:50 ryzen kernel: ACPI: PCI: Interrupt link LNKA configured for IRQ 0
Oct 11 17:22:50 ryzen kernel: ACPI: PCI: Interrupt link LNKB configured for IRQ 0
Oct 11 17:22:50 ryzen kernel: ACPI: PCI: Interrupt link LNKC configured for IRQ 0
Oct 11 17:22:50 ryzen kernel: ACPI: PCI: Interrupt link LNKD configured for IRQ 0
Oct 11 17:22:50 ryzen kernel: ACPI: PCI: Interrupt link LNKE configured for IRQ 0
Oct 11 17:22:50 ryzen kernel: ACPI: PCI: Interrupt link LNKF configured for IRQ 0
Oct 11 17:22:50 ryzen kernel: ACPI: PCI: Interrupt link LNKG configured for IRQ 0
Oct 11 17:22:50 ryzen kernel: ACPI: PCI: Interrupt link LNKH configured for IRQ 0
Oct 11 17:22:50 ryzen kernel: iommu: Default domain type: Translated
Oct 11 17:22:50 ryzen kernel: iommu: DMA domain TLB invalidation policy: lazy mode
Oct 11 17:22:50 ryzen kernel: SCSI subsystem initialized
Oct 11 17:22:50 ryzen kernel: libata version 3.00 loaded.
Oct 11 17:22:50 ryzen kernel: ACPI: bus type USB registered
Oct 11 17:22:50 ryzen kernel: usbcore: registered new interface driver usbfs
Oct 11 17:22:50 ryzen kernel: usbcore: registered new interface driver hub
Oct 11 17:22:50 ryzen kernel: usbcore: registered new device driver usb
Oct 11 17:22:50 ryzen kernel: pps_core: LinuxPPS API ver. 1 registered
Oct 11 17:22:50 ryzen kernel: pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
Oct 11 17:22:50 ryzen kernel: PTP clock support registered
Oct 11 17:22:50 ryzen kernel: EDAC MC: Ver: 3.0.0
Oct 11 17:22:50 ryzen kernel: efivars: Registered efivars operations
Oct 11 17:22:50 ryzen kernel: NetLabel: Initializing
Oct 11 17:22:50 ryzen kernel: NetLabel: domain hash size = 128
Oct 11 17:22:50 ryzen kernel: NetLabel: protocols = UNLABELED CIPSOv4 CALIPSO
Oct 11 17:22:50 ryzen kernel: NetLabel: unlabeled traffic allowed by default
Oct 11 17:22:50 ryzen kernel: mctp: management component transport protocol core
Oct 11 17:22:50 ryzen kernel: NET: Registered PF_MCTP protocol family
Oct 11 17:22:50 ryzen kernel: PCI: Using ACPI for IRQ routing
Oct 11 17:22:50 ryzen kernel: PCI: pci_cache_line_size set to 64 bytes
Oct 11 17:22:50 ryzen kernel: e820: reserve RAM buffer [mem 0x09ccf000-0x0bffffff]
Oct 11 17:22:50 ryzen kernel: e820: reserve RAM buffer [mem 0x0a200000-0x0bffffff]
Oct 11 17:22:50 ryzen kernel: e820: reserve RAM buffer [mem 0x0b000000-0x0bffffff]
Oct 11 17:22:50 ryzen kernel: e820: reserve RAM buffer [mem 0xb343c018-0xb3ffffff]
Oct 11 17:22:50 ryzen kernel: e820: reserve RAM buffer [mem 0xb48e4018-0xb7ffffff]
Oct 11 17:22:50 ryzen kernel: e820: reserve RAM buffer [mem 0xb51b6000-0xb7ffffff]
Oct 11 17:22:50 ryzen kernel: e820: reserve RAM buffer [mem 0xb7fd1000-0xb7ffffff]
Oct 11 17:22:50 ryzen kernel: e820: reserve RAM buffer [mem 0xb9d46000-0xbbffffff]
Oct 11 17:22:50 ryzen kernel: e820: reserve RAM buffer [mem 0xbf000000-0xbfffffff]
Oct 11 17:22:50 ryzen kernel: e820: reserve RAM buffer [mem 0x43f380000-0x43fffffff]
Oct 11 17:22:50 ryzen kernel: pci 0000:05:00.0: vgaarb: setting as boot VGA device
Oct 11 17:22:50 ryzen kernel: pci 0000:05:00.0: vgaarb: bridge control possible
Oct 11 17:22:50 ryzen kernel: pci 0000:05:00.0: vgaarb: VGA device added: decodes=io+mem,owns=io+mem,locks=none
Oct 11 17:22:50 ryzen kernel: vgaarb: loaded
Oct 11 17:22:50 ryzen kernel: hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0
Oct 11 17:22:50 ryzen kernel: hpet0: 3 comparators, 32-bit 14.318180 MHz counter
Oct 11 17:22:50 ryzen kernel: clocksource: Switched to clocksource tsc-early
Oct 11 17:22:50 ryzen kernel: VFS: Disk quotas dquot_6.6.0
Oct 11 17:22:50 ryzen kernel: VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Oct 11 17:22:50 ryzen kernel: pnp: PnP ACPI init
Oct 11 17:22:50 ryzen kernel: system 00:00: [mem 0xf0000000-0xf7ffffff] has been reserved
Oct 11 17:22:50 ryzen kernel: system 00:01: [mem 0xfd200000-0xfd2fffff] has been reserved
Oct 11 17:22:50 ryzen kernel: system 00:03: [io 0x0a00-0x0a2f] has been reserved
Oct 11 17:22:50 ryzen kernel: system 00:03: [io 0x0a30-0x0a3f] has been reserved
Oct 11 17:22:50 ryzen kernel: system 00:03: [io 0x0a40-0x0a4f] has been reserved
Oct 11 17:22:50 ryzen kernel: system 00:03: [mem 0xfe000000-0xfe00ffff] has been reserved
Oct 11 17:22:50 ryzen kernel: pnp 00:05: [dma 0 disabled]
Oct 11 17:22:50 ryzen kernel: system 00:06: [io 0x04d0-0x04d1] has been reserved
Oct 11 17:22:50 ryzen kernel: system 00:06: [io 0x040b] has been reserved
Oct 11 17:22:50 ryzen kernel: system 00:06: [io 0x04d6] has been reserved
Oct 11 17:22:50 ryzen kernel: system 00:06: [io 0x0c00-0x0c01] has been reserved
Oct 11 17:22:50 ryzen kernel: system 00:06: [io 0x0c14] has been reserved
Oct 11 17:22:50 ryzen kernel: system 00:06: [io 0x0c50-0x0c51] has been reserved
Oct 11 17:22:50 ryzen kernel: system 00:06: [io 0x0c52] has been reserved
Oct 11 17:22:50 ryzen kernel: system 00:06: [io 0x0c6c] has been reserved
Oct 11 17:22:50 ryzen kernel: system 00:06: [io 0x0c6f] has been reserved
Oct 11 17:22:50 ryzen kernel: system 00:06: [io 0x0cd8-0x0cdf] has been reserved
Oct 11 17:22:50 ryzen kernel: system 00:06: [io 0x0800-0x089f] has been reserved
Oct 11 17:22:50 ryzen kernel: system 00:06: [io 0x0b00-0x0b0f] has been reserved
Oct 11 17:22:50 ryzen kernel: system 00:06: [io 0x0b20-0x0b3f] has been reserved
Oct 11 17:22:50 ryzen kernel: system 00:06: [io 0x0900-0x090f] has been reserved
Oct 11 17:22:50 ryzen kernel: system 00:06: [io 0x0910-0x091f] has been reserved
Oct 11 17:22:50 ryzen kernel: system 00:06: [mem 0xfec00000-0xfec00fff] could not be reserved
Oct 11 17:22:50 ryzen kernel: system 00:06: [mem 0xfec01000-0xfec01fff] could not be reserved
Oct 11 17:22:50 ryzen kernel: system 00:06: [mem 0xfedc0000-0xfedc0fff] has been reserved
Oct 11 17:22:50 ryzen kernel: system 00:06: [mem 0xfee00000-0xfee00fff] has been reserved
Oct 11 17:22:50 ryzen kernel: system 00:06: [mem 0xfed80000-0xfed8ffff] could not be reserved
Oct 11 17:22:50 ryzen kernel: system 00:06: [mem 0xfec10000-0xfec10fff] has been reserved
Oct 11 17:22:50 ryzen kernel: system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Oct 11 17:22:50 ryzen kernel: pnp: PnP ACPI: found 7 devices
Oct 11 17:22:50 ryzen kernel: clocksource: acpi_pm: mask: 0xffffff max_cycles: 0xffffff, max_idle_ns: 2085701024 ns
Oct 11 17:22:50 ryzen kernel: NET: Registered PF_INET protocol family
Oct 11 17:22:50 ryzen kernel: IP idents hash table entries: 262144 (order: 9, 2097152 bytes, linear)
Oct 11 17:22:50 ryzen kernel: tcp_listen_portaddr_hash hash table entries: 8192 (order: 5, 131072 bytes, linear)
Oct 11 17:22:50 ryzen kernel: Table-perturb hash table entries: 65536 (order: 6, 262144 bytes, linear)
Oct 11 17:22:50 ryzen kernel: TCP established hash table entries: 131072 (order: 8, 1048576 bytes, linear)
Oct 11 17:22:50 ryzen kernel: TCP bind hash table entries: 65536 (order: 9, 2097152 bytes, linear)
Oct 11 17:22:50 ryzen kernel: TCP: Hash tables configured (established 131072 bind 65536)
Oct 11 17:22:50 ryzen kernel: MPTCP token hash table entries: 16384 (order: 6, 393216 bytes, linear)
Oct 11 17:22:50 ryzen kernel: UDP hash table entries: 8192 (order: 6, 262144 bytes, linear)
Oct 11 17:22:50 ryzen kernel: UDP-Lite hash table entries: 8192 (order: 6, 262144 bytes, linear)
Oct 11 17:22:50 ryzen kernel: NET: Registered PF_UNIX/PF_LOCAL protocol family
Oct 11 17:22:50 ryzen kernel: NET: Registered PF_XDP protocol family
Oct 11 17:22:50 ryzen kernel: pci 0000:00:01.1: PCI bridge to [bus 01]
Oct 11 17:22:50 ryzen kernel: pci 0000:00:01.1: bridge window [mem 0xfcf00000-0xfcffffff]
Oct 11 17:22:50 ryzen kernel: pci 0000:03:09.0: PCI bridge to [bus 04]
Oct 11 17:22:50 ryzen kernel: pci 0000:03:09.0: bridge window [io 0xf000-0xffff]
Oct 11 17:22:50 ryzen kernel: pci 0000:03:09.0: bridge window [mem 0xfcc00000-0xfccfffff]
Oct 11 17:22:50 ryzen kernel: pci 0000:02:00.2: PCI bridge to [bus 03-04]
Oct 11 17:22:50 ryzen kernel: pci 0000:02:00.2: bridge window [io 0xf000-0xffff]
Oct 11 17:22:50 ryzen kernel: pci 0000:02:00.2: bridge window [mem 0xfcc00000-0xfccfffff]
Oct 11 17:22:50 ryzen kernel: pci 0000:00:01.2: PCI bridge to [bus 02-04]
Oct 11 17:22:50 ryzen kernel: pci 0000:00:01.2: bridge window [io 0xf000-0xffff]
Oct 11 17:22:50 ryzen kernel: pci 0000:00:01.2: bridge window [mem 0xfcc00000-0xfcdfffff]
Oct 11 17:22:50 ryzen kernel: pci 0000:00:03.1: PCI bridge to [bus 05]
Oct 11 17:22:50 ryzen kernel: pci 0000:00:03.1: bridge window [io 0xe000-0xefff]
Oct 11 17:22:50 ryzen kernel: pci 0000:00:03.1: bridge window [mem 0xfce00000-0xfcefffff]
Oct 11 17:22:50 ryzen kernel: pci 0000:00:03.1: bridge window [mem 0xd0000000-0xe01fffff 64bit pref]
Oct 11 17:22:50 ryzen kernel: pci 0000:00:07.1: PCI bridge to [bus 06]
Oct 11 17:22:50 ryzen kernel: pci 0000:00:08.1: PCI bridge to [bus 07]
Oct 11 17:22:50 ryzen kernel: pci 0000:00:08.1: bridge window [mem 0xfc900000-0xfcbfffff]
Oct 11 17:22:50 ryzen kernel: pci_bus 0000:00: resource 4 [io 0x0000-0x03af window]
Oct 11 17:22:50 ryzen kernel: pci_bus 0000:00: resource 5 [io 0x03e0-0x0cf7 window]
Oct 11 17:22:50 ryzen kernel: pci_bus 0000:00: resource 6 [io 0x03b0-0x03df window]
Oct 11 17:22:50 ryzen kernel: pci_bus 0000:00: resource 7 [io 0x0d00-0xffff window]
Oct 11 17:22:50 ryzen kernel: pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000dffff window]
Oct 11 17:22:50 ryzen kernel: pci_bus 0000:00: resource 9 [mem 0xc0000000-0xfec2ffff window]
Oct 11 17:22:50 ryzen kernel: pci_bus 0000:00: resource 10 [mem 0xfee00000-0xffffffff window]
Oct 11 17:22:50 ryzen kernel: pci_bus 0000:01: resource 1 [mem 0xfcf00000-0xfcffffff]
Oct 11 17:22:50 ryzen kernel: pci_bus 0000:02: resource 0 [io 0xf000-0xffff]
Oct 11 17:22:50 ryzen kernel: pci_bus 0000:02: resource 1 [mem 0xfcc00000-0xfcdfffff]
Oct 11 17:22:50 ryzen kernel: pci_bus 0000:03: resource 0 [io 0xf000-0xffff]
Oct 11 17:22:50 ryzen kernel: pci_bus 0000:03: resource 1 [mem 0xfcc00000-0xfccfffff]
Oct 11 17:22:50 ryzen kernel: pci_bus 0000:04: resource 0 [io 0xf000-0xffff]
Oct 11 17:22:50 ryzen kernel: pci_bus 0000:04: resource 1 [mem 0xfcc00000-0xfccfffff]
Oct 11 17:22:50 ryzen kernel: pci_bus 0000:05: resource 0 [io 0xe000-0xefff]
Oct 11 17:22:50 ryzen kernel: pci_bus 0000:05: resource 1 [mem 0xfce00000-0xfcefffff]
Oct 11 17:22:50 ryzen kernel: pci_bus 0000:05: resource 2 [mem 0xd0000000-0xe01fffff 64bit pref]
Oct 11 17:22:50 ryzen kernel: pci_bus 0000:07: resource 1 [mem 0xfc900000-0xfcbfffff]
Oct 11 17:22:50 ryzen kernel: pci 0000:05:00.1: D0 power state depends on 0000:05:00.0
Oct 11 17:22:50 ryzen kernel: PCI: CLS 64 bytes, default 64
Oct 11 17:22:50 ryzen kernel: pci 0000:00:00.2: AMD-Vi: IOMMU performance counters supported
Oct 11 17:22:50 ryzen kernel: Trying to unpack rootfs image as initramfs...
Oct 11 17:22:50 ryzen kernel: pci 0000:00:01.0: Adding to iommu group 0
Oct 11 17:22:50 ryzen kernel: pci 0000:00:01.1: Adding to iommu group 1
Oct 11 17:22:50 ryzen kernel: pci 0000:00:01.2: Adding to iommu group 2
Oct 11 17:22:50 ryzen kernel: pci 0000:00:02.0: Adding to iommu group 3
Oct 11 17:22:50 ryzen kernel: pci 0000:00:03.0: Adding to iommu group 4
Oct 11 17:22:50 ryzen kernel: pci 0000:00:03.1: Adding to iommu group 5
Oct 11 17:22:50 ryzen kernel: pci 0000:00:04.0: Adding to iommu group 6
Oct 11 17:22:50 ryzen kernel: pci 0000:00:05.0: Adding to iommu group 7
Oct 11 17:22:50 ryzen kernel: pci 0000:00:07.0: Adding to iommu group 8
Oct 11 17:22:50 ryzen kernel: pci 0000:00:07.1: Adding to iommu group 9
Oct 11 17:22:50 ryzen kernel: pci 0000:00:08.0: Adding to iommu group 10
Oct 11 17:22:50 ryzen kernel: pci 0000:00:08.1: Adding to iommu group 11
Oct 11 17:22:50 ryzen kernel: pci 0000:00:14.0: Adding to iommu group 12
Oct 11 17:22:50 ryzen kernel: pci 0000:00:14.3: Adding to iommu group 12
Oct 11 17:22:50 ryzen kernel: pci 0000:00:18.0: Adding to iommu group 13
Oct 11 17:22:50 ryzen kernel: pci 0000:00:18.1: Adding to iommu group 13
Oct 11 17:22:50 ryzen kernel: pci 0000:00:18.2: Adding to iommu group 13
Oct 11 17:22:50 ryzen kernel: pci 0000:00:18.3: Adding to iommu group 13
Oct 11 17:22:50 ryzen kernel: pci 0000:00:18.4: Adding to iommu group 13
Oct 11 17:22:50 ryzen kernel: pci 0000:00:18.5: Adding to iommu group 13
Oct 11 17:22:50 ryzen kernel: pci 0000:00:18.6: Adding to iommu group 13
Oct 11 17:22:50 ryzen kernel: pci 0000:00:18.7: Adding to iommu group 13
Oct 11 17:22:50 ryzen kernel: pci 0000:01:00.0: Adding to iommu group 14
Oct 11 17:22:50 ryzen kernel: pci 0000:02:00.0: Adding to iommu group 15
Oct 11 17:22:50 ryzen kernel: pci 0000:02:00.1: Adding to iommu group 15
Oct 11 17:22:50 ryzen kernel: pci 0000:02:00.2: Adding to iommu group 15
Oct 11 17:22:50 ryzen kernel: pci 0000:03:09.0: Adding to iommu group 15
Oct 11 17:22:50 ryzen kernel: pci 0000:04:00.0: Adding to iommu group 15
Oct 11 17:22:50 ryzen kernel: pci 0000:05:00.0: Adding to iommu group 16
Oct 11 17:22:50 ryzen kernel: pci 0000:05:00.1: Adding to iommu group 16
Oct 11 17:22:50 ryzen kernel: pci 0000:06:00.0: Adding to iommu group 17
Oct 11 17:22:50 ryzen kernel: pci 0000:07:00.0: Adding to iommu group 18
Oct 11 17:22:50 ryzen kernel: pci 0000:07:00.1: Adding to iommu group 19
Oct 11 17:22:50 ryzen kernel: pci 0000:07:00.3: Adding to iommu group 20
Oct 11 17:22:50 ryzen kernel: pci 0000:07:00.4: Adding to iommu group 21
Oct 11 17:22:50 ryzen kernel: pci 0000:00:00.2: AMD-Vi: Found IOMMU cap 0x40
Oct 11 17:22:50 ryzen kernel: AMD-Vi: Extended features (0x58f77ef22294a5a, 0x0): PPR NX GT IA PC GA_vAPIC
Oct 11 17:22:50 ryzen kernel: AMD-Vi: Interrupt remapping enabled
Oct 11 17:22:50 ryzen kernel: PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Oct 11 17:22:50 ryzen kernel: software IO TLB: mapped [mem 0x00000000af43c000-0x00000000b343c000] (64MB)
Oct 11 17:22:50 ryzen kernel: LVT offset 0 assigned for vector 0x400
Oct 11 17:22:50 ryzen kernel: perf: AMD IBS detected (0x000003ff)
Oct 11 17:22:50 ryzen kernel: perf/amd_iommu: Detected AMD IOMMU #0 (2 banks, 4 counters/bank).
Oct 11 17:22:50 ryzen kernel: Initialise system trusted keyrings
Oct 11 17:22:50 ryzen kernel: Key type blacklist registered
Oct 11 17:22:50 ryzen kernel: workingset: timestamp_bits=41 max_order=22 bucket_order=0
Oct 11 17:22:50 ryzen kernel: zbud: loaded
Oct 11 17:22:50 ryzen kernel: integrity: Platform Keyring initialized
Oct 11 17:22:50 ryzen kernel: integrity: Machine keyring initialized
Oct 11 17:22:50 ryzen kernel: Key type asymmetric registered
Oct 11 17:22:50 ryzen kernel: Asymmetric key parser 'x509' registered
Oct 11 17:22:50 ryzen kernel: Block layer SCSI generic (bsg) driver version 0.4 loaded (major 242)
Oct 11 17:22:50 ryzen kernel: io scheduler mq-deadline registered
Oct 11 17:22:50 ryzen kernel: io scheduler kyber registered
Oct 11 17:22:50 ryzen kernel: io scheduler bfq registered
Oct 11 17:22:50 ryzen kernel: pcieport 0000:00:01.1: PME: Signaling with IRQ 27
Oct 11 17:22:50 ryzen kernel: pcieport 0000:00:01.1: AER: enabled with IRQ 27
Oct 11 17:22:50 ryzen kernel: pcieport 0000:00:01.2: PME: Signaling with IRQ 28
Oct 11 17:22:50 ryzen kernel: pcieport 0000:00:01.2: AER: enabled with IRQ 28
Oct 11 17:22:50 ryzen kernel: pcieport 0000:00:03.1: PME: Signaling with IRQ 29
Oct 11 17:22:50 ryzen kernel: pcieport 0000:00:03.1: AER: enabled with IRQ 29
Oct 11 17:22:50 ryzen kernel: pcieport 0000:00:07.1: PME: Signaling with IRQ 31
Oct 11 17:22:50 ryzen kernel: pcieport 0000:00:07.1: AER: enabled with IRQ 31
Oct 11 17:22:50 ryzen kernel: pcieport 0000:00:08.1: PME: Signaling with IRQ 32
Oct 11 17:22:50 ryzen kernel: pcieport 0000:00:08.1: AER: enabled with IRQ 32
Oct 11 17:22:50 ryzen kernel: shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Oct 11 17:22:50 ryzen kernel: input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input0
Oct 11 17:22:50 ryzen kernel: ACPI: button: Power Button [PWRB]
Oct 11 17:22:50 ryzen kernel: input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Oct 11 17:22:50 ryzen kernel: ACPI: button: Power Button [PWRF]
Oct 11 17:22:50 ryzen kernel: Estimated ratio of average max frequency by base frequency (times 1024): 1155
Oct 11 17:22:50 ryzen kernel: Monitor-Mwait will be used to enter C-1 state
Oct 11 17:22:50 ryzen kernel: ACPI: \_SB_.PLTF.C000: Found 2 idle states
Oct 11 17:22:50 ryzen kernel: ACPI: \_SB_.PLTF.C002: Found 2 idle states
Oct 11 17:22:50 ryzen kernel: ACPI: \_SB_.PLTF.C004: Found 2 idle states
Oct 11 17:22:50 ryzen kernel: ACPI: \_SB_.PLTF.C006: Found 2 idle states
Oct 11 17:22:50 ryzen kernel: ACPI: \_SB_.PLTF.C008: Found 2 idle states
Oct 11 17:22:50 ryzen kernel: ACPI: \_SB_.PLTF.C00A: Found 2 idle states
Oct 11 17:22:50 ryzen kernel: ACPI: \_SB_.PLTF.C001: Found 2 idle states
Oct 11 17:22:50 ryzen kernel: ACPI: \_SB_.PLTF.C003: Found 2 idle states
Oct 11 17:22:50 ryzen kernel: ACPI: \_SB_.PLTF.C005: Found 2 idle states
Oct 11 17:22:50 ryzen kernel: ACPI: \_SB_.PLTF.C007: Found 2 idle states
Oct 11 17:22:50 ryzen kernel: ACPI: \_SB_.PLTF.C009: Found 2 idle states
Oct 11 17:22:50 ryzen kernel: ACPI: \_SB_.PLTF.C00B: Found 2 idle states
Oct 11 17:22:50 ryzen kernel: Freeing initrd memory: 10504K
Oct 11 17:22:50 ryzen kernel: tsc: Refined TSC clocksource calibration: 3693.060 MHz
Oct 11 17:22:50 ryzen kernel: clocksource: tsc: mask: 0xffffffffffffffff max_cycles: 0x6a77744cfd5, max_idle_ns: 881590969987 ns
Oct 11 17:22:50 ryzen kernel: clocksource: Switched to clocksource tsc
Oct 11 17:22:50 ryzen kernel: ACPI: \_TZ_.TZ10: Invalid passive threshold
Oct 11 17:22:50 ryzen kernel: thermal LNXTHERM:00: registered as thermal_zone0
Oct 11 17:22:50 ryzen kernel: ACPI: thermal: Thermal Zone [TZ10] (17 C)
Oct 11 17:22:50 ryzen kernel: ACPI: \_TZ_.UAD0: Invalid passive threshold
Oct 11 17:22:50 ryzen kernel: thermal LNXTHERM:01: registered as thermal_zone1
Oct 11 17:22:50 ryzen kernel: ACPI: thermal: Thermal Zone [UAD0] (17 C)
Oct 11 17:22:50 ryzen kernel: Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Oct 11 17:22:50 ryzen kernel: 00:05: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Oct 11 17:22:50 ryzen kernel: Non-volatile memory driver v1.3
Oct 11 17:22:50 ryzen kernel: Linux agpgart interface v0.103
Oct 11 17:22:50 ryzen kernel: tpm_crb MSFT0101:00: Disabling hwrng
Oct 11 17:22:50 ryzen kernel: AMD-Vi: AMD IOMMUv2 loaded and initialized
Oct 11 17:22:50 ryzen kernel: ACPI: bus type drm_connector registered
Oct 11 17:22:50 ryzen kernel: [drm] Initialized simpledrm 1.0.0 20200625 for simple-framebuffer.0 on minor 0
Oct 11 17:22:50 ryzen kernel: fbcon: Deferring console take-over
Oct 11 17:22:50 ryzen kernel: simple-framebuffer simple-framebuffer.0: [drm] fb0: simpledrmdrmfb frame buffer device
Oct 11 17:22:50 ryzen kernel: ahci 0000:02:00.1: version 3.0
Oct 11 17:22:50 ryzen kernel: ahci 0000:02:00.1: SSS flag set, parallel bus scan disabled
Oct 11 17:22:50 ryzen kernel: ahci 0000:02:00.1: AHCI 0001.0301 32 slots 6 ports 6 Gbps 0x3f impl SATA mode
Oct 11 17:22:50 ryzen kernel: ahci 0000:02:00.1: flags: 64bit ncq sntf stag pm led clo only pmp pio slum part sxs deso sadm sds apst
Oct 11 17:22:50 ryzen kernel: scsi host0: ahci
Oct 11 17:22:50 ryzen kernel: scsi host1: ahci
Oct 11 17:22:50 ryzen kernel: scsi host2: ahci
Oct 11 17:22:50 ryzen kernel: scsi host3: ahci
Oct 11 17:22:50 ryzen kernel: scsi host4: ahci
Oct 11 17:22:50 ryzen kernel: scsi host5: ahci
Oct 11 17:22:50 ryzen kernel: ata1: SATA max UDMA/133 abar m131072@0xfcd80000 port 0xfcd80100 irq 36
Oct 11 17:22:50 ryzen kernel: ata2: SATA max UDMA/133 abar m131072@0xfcd80000 port 0xfcd80180 irq 36
Oct 11 17:22:50 ryzen kernel: ata3: SATA max UDMA/133 abar m131072@0xfcd80000 port 0xfcd80200 irq 36
Oct 11 17:22:50 ryzen kernel: ata4: SATA max UDMA/133 abar m131072@0xfcd80000 port 0xfcd80280 irq 36
Oct 11 17:22:50 ryzen kernel: ata5: SATA max UDMA/133 abar m131072@0xfcd80000 port 0xfcd80300 irq 36
Oct 11 17:22:50 ryzen kernel: ata6: SATA max UDMA/133 abar m131072@0xfcd80000 port 0xfcd80380 irq 36
Oct 11 17:22:50 ryzen kernel: usbcore: registered new interface driver usbserial_generic
Oct 11 17:22:50 ryzen kernel: usbserial: USB Serial support registered for generic
Oct 11 17:22:50 ryzen kernel: rtc_cmos 00:02: RTC can wake from S4
Oct 11 17:22:50 ryzen kernel: rtc_cmos 00:02: registered as rtc0
Oct 11 17:22:50 ryzen kernel: rtc_cmos 00:02: setting system clock to 2023-10-12T00:22:45 UTC (1697070165)
Oct 11 17:22:50 ryzen kernel: rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Oct 11 17:22:50 ryzen kernel: amd_pstate: driver load is disabled, boot with specific mode to enable this
Oct 11 17:22:50 ryzen kernel: ledtrig-cpu: registered to indicate activity on CPUs
Oct 11 17:22:50 ryzen kernel: hid: raw HID events driver (C) Jiri Kosina
Oct 11 17:22:50 ryzen kernel: drop_monitor: Initializing network drop monitor service
Oct 11 17:22:50 ryzen kernel: Initializing XFRM netlink socket
Oct 11 17:22:50 ryzen kernel: NET: Registered PF_INET6 protocol family
Oct 11 17:22:50 ryzen kernel: Segment Routing with IPv6
Oct 11 17:22:50 ryzen kernel: RPL Segment Routing with IPv6
Oct 11 17:22:50 ryzen kernel: In-situ OAM (IOAM) with IPv6
Oct 11 17:22:50 ryzen kernel: NET: Registered PF_PACKET protocol family
Oct 11 17:22:50 ryzen kernel: microcode: CPU0: patch_level=0x0a201025
Oct 11 17:22:50 ryzen kernel: microcode: CPU6: patch_level=0x0a201025
Oct 11 17:22:50 ryzen kernel: microcode: CPU2: patch_level=0x0a201025
Oct 11 17:22:50 ryzen kernel: microcode: CPU3: patch_level=0x0a201025
Oct 11 17:22:50 ryzen kernel: microcode: CPU1: patch_level=0x0a201025
Oct 11 17:22:50 ryzen kernel: microcode: CPU7: patch_level=0x0a201025
Oct 11 17:22:50 ryzen kernel: microcode: CPU5: patch_level=0x0a201025
Oct 11 17:22:50 ryzen kernel: microcode: CPU8: patch_level=0x0a201025
Oct 11 17:22:50 ryzen kernel: microcode: CPU11: patch_level=0x0a201025
Oct 11 17:22:50 ryzen kernel: microcode: CPU9: patch_level=0x0a201025
Oct 11 17:22:50 ryzen kernel: microcode: CPU10: patch_level=0x0a201025
Oct 11 17:22:50 ryzen kernel: microcode: CPU4: patch_level=0x0a201025
Oct 11 17:22:50 ryzen kernel: microcode: Microcode Update Driver: v2.2.
Oct 11 17:22:50 ryzen kernel: resctrl: L3 allocation detected
Oct 11 17:22:50 ryzen kernel: resctrl: MB allocation detected
Oct 11 17:22:50 ryzen kernel: resctrl: L3 monitoring detected
Oct 11 17:22:50 ryzen kernel: IPI shorthand broadcast: enabled
Oct 11 17:22:50 ryzen kernel: sched_clock: Marking stable (2543334478, 313613087)->(2860682398, -3734833)
Oct 11 17:22:50 ryzen kernel: registered taskstats version 1
Oct 11 17:22:50 ryzen kernel: Loading compiled-in X.509 certificates
Oct 11 17:22:50 ryzen kernel: Loaded X.509 cert 'Build time autogenerated kernel key: 5bd22cdbfed7f59d9bddd4aba6c2d6cb887120d5'
Oct 11 17:22:50 ryzen kernel: zswap: loaded using pool zstd/zsmalloc
Oct 11 17:22:50 ryzen kernel: Key type .fscrypt registered
Oct 11 17:22:50 ryzen kernel: Key type fscrypt-provisioning registered
Oct 11 17:22:50 ryzen kernel: PM: Magic number: 11:744:354
Oct 11 17:22:50 ryzen kernel: machinecheck machinecheck10: hash matches
Oct 11 17:22:50 ryzen kernel: input event0: hash matches
Oct 11 17:22:50 ryzen kernel: RAS: Correctable Errors collector initialized.
Oct 11 17:22:50 ryzen kernel: clk: Disabling unused clocks
Oct 11 17:22:50 ryzen kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Oct 11 17:22:50 ryzen kernel: ata1.00: ATA-9: WDC WD20EFRX-68AX9N0, 80.00A80, max UDMA/133
Oct 11 17:22:50 ryzen kernel: ata1.00: 3907029168 sectors, multi 16: LBA48 NCQ (depth 32), AA
Oct 11 17:22:50 ryzen kernel: ata1.00: configured for UDMA/133
Oct 11 17:22:50 ryzen kernel: scsi 0:0:0:0: Direct-Access ATA WDC WD20EFRX-68A 0A80 PQ: 0 ANSI: 5
Oct 11 17:22:50 ryzen kernel: sd 0:0:0:0: [sda] 3907029168 512-byte logical blocks: (2.00 TB/1.82 TiB)
Oct 11 17:22:50 ryzen kernel: sd 0:0:0:0: [sda] 4096-byte physical blocks
Oct 11 17:22:50 ryzen kernel: sd 0:0:0:0: [sda] Write Protect is off
Oct 11 17:22:50 ryzen kernel: sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
Oct 11 17:22:50 ryzen kernel: sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Oct 11 17:22:50 ryzen kernel: sd 0:0:0:0: [sda] Preferred minimum I/O size 4096 bytes
Oct 11 17:22:50 ryzen kernel: sda: sda1
Oct 11 17:22:50 ryzen kernel: sd 0:0:0:0: [sda] Attached SCSI disk
Oct 11 17:22:50 ryzen kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
Oct 11 17:22:50 ryzen kernel: ata2.00: ATAPI: HL-DT-ST DVDRAM GH22LS40, LL02, max UDMA/100
Oct 11 17:22:50 ryzen kernel: ata2.00: configured for UDMA/100
Oct 11 17:22:50 ryzen kernel: scsi 1:0:0:0: CD-ROM HL-DT-ST DVDRAM GH22LS40 LL02 PQ: 0 ANSI: 5
Oct 11 17:22:50 ryzen kernel: ata3: SATA link down (SStatus 0 SControl 330)
Oct 11 17:22:50 ryzen kernel: ata4: SATA link down (SStatus 0 SControl 330)
Oct 11 17:22:50 ryzen kernel: ata5: SATA link down (SStatus 0 SControl 330)
Oct 11 17:22:50 ryzen kernel: ata6: failed to resume link (SControl 0)
Oct 11 17:22:50 ryzen kernel: ata6: SATA link down (SStatus 0 SControl 0)
Oct 11 17:22:50 ryzen kernel: Freeing unused decrypted memory: 2036K
Oct 11 17:22:50 ryzen kernel: Freeing unused kernel image (initmem) memory: 3384K
Oct 11 17:22:50 ryzen kernel: Write protecting the kernel read-only data: 30720k
Oct 11 17:22:50 ryzen kernel: Freeing unused kernel image (rodata/data gap) memory: 1380K
Oct 11 17:22:50 ryzen kernel: x86/mm: Checked W+X mappings: passed, no W+X pages found.
Oct 11 17:22:50 ryzen kernel: rodata_test: all tests were successful
Oct 11 17:22:50 ryzen kernel: Run /init as init process
Oct 11 17:22:50 ryzen kernel: with arguments:
Oct 11 17:22:50 ryzen kernel: /init
Oct 11 17:22:50 ryzen kernel: with environment:
Oct 11 17:22:50 ryzen kernel: HOME=/
Oct 11 17:22:50 ryzen kernel: TERM=linux
Oct 11 17:22:50 ryzen kernel: raid6: skipped pq benchmark and selected avx2x4
Oct 11 17:22:50 ryzen kernel: raid6: using avx2x2 recovery algorithm
Oct 11 17:22:50 ryzen kernel: xor: automatically using best checksumming function avx
Oct 11 17:22:50 ryzen kernel: Btrfs loaded, zoned=yes, fsverity=yes
Oct 11 17:22:50 ryzen kernel: i8042: PNP: PS/2 Controller [PNP0303:PS2K] at 0x60,0x64 irq 1
Oct 11 17:22:50 ryzen kernel: i8042: PNP: PS/2 appears to have AUX port disabled, if this is incorrect please boot with i8042.nopnp
Oct 11 17:22:50 ryzen kernel: serio: i8042 KBD port at 0x60,0x64 irq 1
Oct 11 17:22:50 ryzen kernel: xhci_hcd 0000:02:00.0: xHCI Host Controller
Oct 11 17:22:50 ryzen kernel: xhci_hcd 0000:02:00.0: new USB bus registered, assigned bus number 1
Oct 11 17:22:50 ryzen kernel: nvme nvme0: pci function 0000:01:00.0
Oct 11 17:22:50 ryzen kernel: nvme nvme0: missing or invalid SUBNQN field.
Oct 11 17:22:50 ryzen kernel: nvme nvme0: Shutdown timeout set to 8 seconds
Oct 11 17:22:50 ryzen kernel: nvme nvme0: 32/0/0 default/read/poll queues
Oct 11 17:22:50 ryzen kernel: nvme0n1: p1 p2 p3 p4 p5 p6
Oct 11 17:22:50 ryzen kernel: xhci_hcd 0000:02:00.0: hcc params 0x0200ef81 hci version 0x110 quirks 0x0000000000000410
Oct 11 17:22:50 ryzen kernel: xhci_hcd 0000:02:00.0: xHCI Host Controller
Oct 11 17:22:50 ryzen kernel: xhci_hcd 0000:02:00.0: new USB bus registered, assigned bus number 2
Oct 11 17:22:50 ryzen kernel: xhci_hcd 0000:02:00.0: Host supports USB 3.1 Enhanced SuperSpeed
Oct 11 17:22:50 ryzen kernel: usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.05
Oct 11 17:22:50 ryzen kernel: usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Oct 11 17:22:50 ryzen kernel: usb usb1: Product: xHCI Host Controller
Oct 11 17:22:50 ryzen kernel: usb usb1: Manufacturer: Linux 6.5.6-arch2-1 xhci-hcd
Oct 11 17:22:50 ryzen kernel: usb usb1: SerialNumber: 0000:02:00.0
Oct 11 17:22:50 ryzen kernel: hub 1-0:1.0: USB hub found
Oct 11 17:22:50 ryzen kernel: hub 1-0:1.0: 10 ports detected
Oct 11 17:22:50 ryzen kernel: BTRFS: device label Arch Linux devid 1 transid 842781 /dev/nvme0n1p2 scanned by (udev-worker) (223)
Oct 11 17:22:50 ryzen kernel: usb usb2: We don't know the algorithms for LPM for this host, disabling LPM.
Oct 11 17:22:50 ryzen kernel: usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 6.05
Oct 11 17:22:50 ryzen kernel: usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Oct 11 17:22:50 ryzen kernel: usb usb2: Product: xHCI Host Controller
Oct 11 17:22:50 ryzen kernel: usb usb2: Manufacturer: Linux 6.5.6-arch2-1 xhci-hcd
Oct 11 17:22:50 ryzen kernel: usb usb2: SerialNumber: 0000:02:00.0
Oct 11 17:22:50 ryzen kernel: hub 2-0:1.0: USB hub found
Oct 11 17:22:50 ryzen kernel: hub 2-0:1.0: 4 ports detected
Oct 11 17:22:50 ryzen kernel: xhci_hcd 0000:07:00.3: xHCI Host Controller
Oct 11 17:22:50 ryzen kernel: xhci_hcd 0000:07:00.3: new USB bus registered, assigned bus number 3
Oct 11 17:22:50 ryzen kernel: xhci_hcd 0000:07:00.3: hcc params 0x0278ffe5 hci version 0x110 quirks 0x0000000000000410
Oct 11 17:22:50 ryzen kernel: xhci_hcd 0000:07:00.3: xHCI Host Controller
Oct 11 17:22:50 ryzen kernel: xhci_hcd 0000:07:00.3: new USB bus registered, assigned bus number 4
Oct 11 17:22:50 ryzen kernel: xhci_hcd 0000:07:00.3: Host supports USB 3.1 Enhanced SuperSpeed
Oct 11 17:22:50 ryzen kernel: usb usb3: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.05
Oct 11 17:22:50 ryzen kernel: usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Oct 11 17:22:50 ryzen kernel: usb usb3: Product: xHCI Host Controller
Oct 11 17:22:50 ryzen kernel: usb usb3: Manufacturer: Linux 6.5.6-arch2-1 xhci-hcd
Oct 11 17:22:50 ryzen kernel: usb usb3: SerialNumber: 0000:07:00.3
Oct 11 17:22:50 ryzen kernel: hub 3-0:1.0: USB hub found
Oct 11 17:22:50 ryzen kernel: hub 3-0:1.0: 4 ports detected
Oct 11 17:22:50 ryzen kernel: usb usb4: We don't know the algorithms for LPM for this host, disabling LPM.
Oct 11 17:22:50 ryzen kernel: usb usb4: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 6.05
Oct 11 17:22:50 ryzen kernel: usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Oct 11 17:22:50 ryzen kernel: usb usb4: Product: xHCI Host Controller
Oct 11 17:22:50 ryzen kernel: usb usb4: Manufacturer: Linux 6.5.6-arch2-1 xhci-hcd
Oct 11 17:22:50 ryzen kernel: usb usb4: SerialNumber: 0000:07:00.3
Oct 11 17:22:50 ryzen kernel: hub 4-0:1.0: USB hub found
Oct 11 17:22:50 ryzen kernel: hub 4-0:1.0: 4 ports detected
Oct 11 17:22:50 ryzen kernel: input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input2
Oct 11 17:22:50 ryzen kernel: sr 1:0:0:0: [sr0] scsi3-mmc drive: 48x/48x writer dvd-ram cd/rw xa/form2 cdda tray
Oct 11 17:22:50 ryzen kernel: cdrom: Uniform CD-ROM driver Revision: 3.20
Oct 11 17:22:50 ryzen kernel: sr 1:0:0:0: Attached scsi CD-ROM sr0
Oct 11 17:22:50 ryzen kernel: usb 3-2: new full-speed USB device number 2 using xhci_hcd
Oct 11 17:22:50 ryzen kernel: usb 1-2: new high-speed USB device number 2 using xhci_hcd
Oct 11 17:22:50 ryzen kernel: usb 1-2: New USB device found, idVendor=0bda, idProduct=5411, bcdDevice= 1.01
Oct 11 17:22:50 ryzen kernel: usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Oct 11 17:22:50 ryzen kernel: usb 1-2: Product: 4-Port USB 2.1 Hub
Oct 11 17:22:50 ryzen kernel: usb 1-2: Manufacturer: Generic
Oct 11 17:22:50 ryzen kernel: hub 1-2:1.0: USB hub found
Oct 11 17:22:50 ryzen kernel: hub 1-2:1.0: 4 ports detected
Oct 11 17:22:50 ryzen kernel: usb 3-2: New USB device found, idVendor=1852, idProduct=7022, bcdDevice= 0.01
Oct 11 17:22:50 ryzen kernel: usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Oct 11 17:22:50 ryzen kernel: usb 3-2: Product: DigiHug USB Audio
Oct 11 17:22:50 ryzen kernel: usb 3-2: Manufacturer: FiiO
Oct 11 17:22:50 ryzen kernel: usb 2-4: new SuperSpeed USB device number 2 using xhci_hcd
Oct 11 17:22:50 ryzen kernel: input: FiiO DigiHug USB Audio as /devices/pci0000:00/0000:00:08.1/0000:07:00.3/usb3/3-2/3-2:1.0/0003:1852:7022.0001/input/input3
Oct 11 17:22:50 ryzen kernel: usb 2-4: New USB device found, idVendor=11b0, idProduct=3306, bcdDevice= 0.04
Oct 11 17:22:50 ryzen kernel: usb 2-4: New USB device strings: Mfr=3, Product=4, SerialNumber=2
Oct 11 17:22:50 ryzen kernel: usb 2-4: Product: UHS-II SD Reader
Oct 11 17:22:50 ryzen kernel: usb 2-4: Manufacturer: Kingston
Oct 11 17:22:50 ryzen kernel: usb 2-4: SerialNumber: 20210500005123
Oct 11 17:22:50 ryzen kernel: usb-storage 2-4:1.0: USB Mass Storage device detected
Oct 11 17:22:50 ryzen kernel: scsi host6: usb-storage 2-4:1.0
Oct 11 17:22:50 ryzen kernel: usbcore: registered new interface driver usb-storage
Oct 11 17:22:50 ryzen kernel: usbcore: registered new interface driver uas
Oct 11 17:22:50 ryzen kernel: hid-generic 0003:1852:7022.0001: input,hidraw0: USB HID v1.00 Device [FiiO DigiHug USB Audio] on usb-0000:07:00.3-2/input0
Oct 11 17:22:50 ryzen kernel: usbcore: registered new interface driver usbhid
Oct 11 17:22:50 ryzen kernel: usbhid: USB HID core driver
Oct 11 17:22:50 ryzen kernel: BTRFS info (device nvme0n1p2): using crc32c (crc32c-intel) checksum algorithm
Oct 11 17:22:50 ryzen kernel: BTRFS info (device nvme0n1p2): disk space caching is enabled
Oct 11 17:22:50 ryzen kernel: usb 1-5: new low-speed USB device number 3 using xhci_hcd
Oct 11 17:22:50 ryzen kernel: BTRFS info (device nvme0n1p2): enabling ssd optimizations
Oct 11 17:22:50 ryzen kernel: BTRFS info (device nvme0n1p2): auto enabling async discard
Oct 11 17:22:50 ryzen kernel: BTRFS info (device nvme0n1p2): checking UUID tree
Oct 11 17:22:50 ryzen systemd[1]: systemd 254.5-1-arch running in system mode (+PAM +AUDIT -SELINUX -APPARMOR -IMA +SMACK +SECCOMP +GCRYPT +GNUTLS +OPENSSL +ACL +BLKID +CURL +ELFUTILS +FIDO2 +IDN2 -IDN +IPTC +KMOD +LIBCRYPTSETUP +LIBFDISK +PCRE2 -PWQUALITY +P11KIT -QRENCODE +TPM2 +BZIP2 +LZ4 +XZ +ZLIB +ZSTD +BPF_FRAMEWORK +XKBCOMMON +UTMP -SYSVINIT default-hierarchy=unified)
Oct 11 17:22:50 ryzen systemd[1]: Detected architecture x86-64.
Oct 11 17:22:50 ryzen systemd[1]: Hostname set to <ryzen>.
Oct 11 17:22:50 ryzen systemd[1]: bpf-lsm: LSM BPF program attached
Oct 11 17:22:50 ryzen kernel: usb 1-5: New USB device found, idVendor=05f3, idProduct=00ff, bcdDevice= 1.20
Oct 11 17:22:50 ryzen kernel: usb 1-5: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Oct 11 17:22:50 ryzen kernel: usb 1-5: Product: VEC USB Footpedal
Oct 11 17:22:50 ryzen kernel: usb 1-5: Manufacturer: VEC
Oct 11 17:22:50 ryzen kernel: input: VEC VEC USB Footpedal as /devices/pci0000:00/0000:00:01.2/0000:02:00.0/usb1/1-5/1-5:1.0/0003:05F3:00FF.0002/input/input4
Oct 11 17:22:50 ryzen kernel: hid-generic 0003:05F3:00FF.0002: input,hiddev96,hidraw1: USB HID v1.00 Device [VEC VEC USB Footpedal] on usb-0000:02:00.0-5/input0
Oct 11 17:22:50 ryzen kernel: usb 1-2.1: new full-speed USB device number 4 using xhci_hcd
Oct 11 17:22:50 ryzen systemd[1]: Queued start job for default target Graphical Interface.
Oct 11 17:22:50 ryzen systemd[1]: Created slice Virtual Machine and Container Slice.
Oct 11 17:22:50 ryzen systemd[1]: Created slice Slice /system/getty.
Oct 11 17:22:50 ryzen systemd[1]: Created slice Slice /system/modprobe.
Oct 11 17:22:50 ryzen systemd[1]: Created slice Slice /system/serial-getty.
Oct 11 17:22:50 ryzen systemd[1]: Created slice Slice /system/systemd-fsck.
Oct 11 17:22:50 ryzen systemd[1]: Created slice User and Session Slice.
Oct 11 17:22:50 ryzen systemd[1]: Started Dispatch Password Requests to Console Directory Watch.
Oct 11 17:22:50 ryzen systemd[1]: Started Forward Password Requests to Wall Directory Watch.
Oct 11 17:22:50 ryzen systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point.
Oct 11 17:22:50 ryzen systemd[1]: Reached target Local Encrypted Volumes.
Oct 11 17:22:50 ryzen kernel: usb 1-7: new full-speed USB device number 5 using xhci_hcd
Oct 11 17:22:50 ryzen systemd[1]: Reached target Local Integrity Protected Volumes.
Oct 11 17:22:50 ryzen systemd[1]: Reached target Remote File Systems.
Oct 11 17:22:50 ryzen systemd[1]: Reached target Slice Units.
Oct 11 17:22:50 ryzen systemd[1]: Reached target Local Verity Protected Volumes.
Oct 11 17:22:50 ryzen systemd[1]: Listening on Device-mapper event daemon FIFOs.
Oct 11 17:22:50 ryzen systemd[1]: Listening on LVM2 poll daemon socket.
Oct 11 17:22:50 ryzen systemd[1]: Listening on Process Core Dump Socket.
Oct 11 17:22:50 ryzen systemd[1]: Listening on Journal Socket (/dev/log).
Oct 11 17:22:50 ryzen systemd[1]: Listening on Journal Socket.
Oct 11 17:22:50 ryzen kernel: usb 1-2.1: New USB device found, idVendor=0ecb, idProduct=2057, bcdDevice=91.05
Oct 11 17:22:50 ryzen kernel: usb 1-2.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Oct 11 17:22:50 ryzen kernel: usb 1-2.1: Product: AKG Ara USB Microphone
Oct 11 17:22:50 ryzen kernel: usb 1-2.1: Manufacturer: C-Media Electronics Inc.
Oct 11 17:22:50 ryzen systemd[1]: Listening on udev Control Socket.
Oct 11 17:22:50 ryzen systemd[1]: Listening on udev Kernel Socket.
Oct 11 17:22:50 ryzen kernel: input: C-Media Electronics Inc. AKG Ara USB Microphone as /devices/pci0000:00/0000:00:01.2/0000:02:00.0/usb1/1-2/1-2.1/1-2.1:1.3/0003:0ECB:2057.0003/input/input5
Oct 11 17:22:50 ryzen systemd[1]: Mounting Huge Pages File System...
Oct 11 17:22:50 ryzen systemd[1]: Mounting POSIX Message Queue File System...
Oct 11 17:22:50 ryzen kernel: scsi 6:0:0:0: Direct-Access Kingston UHS-II SD Reader 0004 PQ: 0 ANSI: 6
Oct 11 17:22:50 ryzen kernel: sd 6:0:0:0: [sdb] Media removed, stopped polling
Oct 11 17:22:50 ryzen kernel: sd 6:0:0:0: [sdb] Attached SCSI removable disk
Oct 11 17:22:50 ryzen systemd[1]: Mounting Kernel Debug File System...
Oct 11 17:22:50 ryzen kernel: hid-generic 0003:0ECB:2057.0003: input,hidraw2: USB HID v1.11 Device [C-Media Electronics Inc. AKG Ara USB Microphone] on usb-0000:02:00.0-2.1/input3
Oct 11 17:22:50 ryzen systemd[1]: Mounting Kernel Trace File System...
Oct 11 17:22:50 ryzen systemd[1]: Started Early root shell on /dev/tty9 FOR DEBUGGING ONLY.
Oct 11 17:22:50 ryzen kernel: usb 1-7: New USB device found, idVendor=057e, idProduct=0337, bcdDevice= 1.00
Oct 11 17:22:50 ryzen kernel: usb 1-7: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Oct 11 17:22:50 ryzen kernel: usb 1-7: Product: WUP-028
Oct 11 17:22:50 ryzen kernel: usb 1-7: Manufacturer: Nintendo
Oct 11 17:22:50 ryzen kernel: usb 1-7: SerialNumber: 15/07/2014
Oct 11 17:22:50 ryzen systemd[1]: Starting Create List of Static Device Nodes...
Oct 11 17:22:50 ryzen kernel: hid-generic 0003:057E:0337.0004: hiddev97,hidraw3: USB HID v1.10 Device [Nintendo WUP-028] on usb-0000:02:00.0-7/input0
Oct 11 17:22:50 ryzen systemd[1]: Starting Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling...
Oct 11 17:22:50 ryzen systemd[1]: Starting Load Kernel Module configfs...
Oct 11 17:22:50 ryzen systemd[1]: Starting Load Kernel Module dm_mod...
Oct 11 17:22:50 ryzen kernel: usb 1-2.2: new full-speed USB device number 6 using xhci_hcd
Oct 11 17:22:50 ryzen kernel: device-mapper: uevent: version 1.0.3
Oct 11 17:22:50 ryzen kernel: device-mapper: ioctl: 4.48.0-ioctl (2023-03-01) initialised: dm-devel@redhat.com
Oct 11 17:22:50 ryzen systemd[1]: Starting Load Kernel Module drm...
Oct 11 17:22:50 ryzen systemd[1]: Starting Load Kernel Module fuse...
Oct 11 17:22:50 ryzen kernel: fuse: init (API version 7.38)
Oct 11 17:22:50 ryzen systemd[1]: Starting Load Kernel Module loop...
Oct 11 17:22:50 ryzen kernel: loop: module loaded
Oct 11 17:22:50 ryzen systemd[1]: Starting Journal Service...
Oct 11 17:22:50 ryzen systemd[1]: Starting Load Kernel Modules...
Oct 11 17:22:50 ryzen systemd-journald[309]: Collecting audit messages is disabled.
Oct 11 17:22:50 ryzen systemd[1]: TPM2 PCR Machine ID Measurement was skipped because of an unmet condition check (ConditionPathExists=/sys/firmware/efi/efivars/StubPcrKernelImage-4a67b082-0a4c-41cf-b6c7-440b29bb8c4f).
Oct 11 17:22:50 ryzen systemd[1]: Starting Remount Root and Kernel File Systems...
Oct 11 17:22:50 ryzen kernel: sd 0:0:0:0: Attached scsi generic sg0 type 0
Oct 11 17:22:50 ryzen kernel: sr 1:0:0:0: Attached scsi generic sg1 type 5
Oct 11 17:22:50 ryzen kernel: sd 6:0:0:0: Attached scsi generic sg2 type 0
Oct 11 17:22:50 ryzen systemd[1]: Starting Coldplug All udev Devices...
Oct 11 17:22:50 ryzen systemd-journald[309]: Journal started
Oct 11 17:22:50 ryzen systemd-journald[309]: Runtime Journal (/run/log/journal/be541a4ba238441eb205e6279170129b) is 8.0M, max 794.6M, 786.6M free.
Oct 11 17:22:50 ryzen systemd-modules-load[310]: Inserted module 'crypto_user'
Oct 11 17:22:50 ryzen systemd-modules-load[310]: Inserted module 'sg'
Oct 11 17:22:50 ryzen systemd[1]: Started Journal Service.
Oct 11 17:22:50 ryzen systemd[1]: Mounted Huge Pages File System.
Oct 11 17:22:50 ryzen systemd[1]: Mounted POSIX Message Queue File System.
Oct 11 17:22:50 ryzen systemd[1]: Mounted Kernel Debug File System.
Oct 11 17:22:50 ryzen systemd[1]: Mounted Kernel Trace File System.
Oct 11 17:22:50 ryzen systemd-modules-load[310]: Failed to insert module 'it87': No such device
Oct 11 17:22:50 ryzen systemd-modules-load[310]: Inserted module 'dm_multipath'
Oct 11 17:22:50 ryzen systemd-modules-load[310]: Inserted module 'uinput'
Oct 11 17:22:50 ryzen systemd[1]: Finished Create List of Static Device Nodes.
Oct 11 17:22:50 ryzen kernel: usb 1-10: new full-speed USB device number 7 using xhci_hcd
Oct 11 17:22:50 ryzen kernel: usb 1-2.2: New USB device found, idVendor=29ea, idProduct=0102, bcdDevice= 1.00
Oct 11 17:22:50 ryzen kernel: usb 1-2.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Oct 11 17:22:50 ryzen kernel: usb 1-2.2: Product: Freestyle Edge Keyboard
Oct 11 17:22:50 ryzen kernel: usb 1-2.2: Manufacturer: Kinesis
Oct 11 17:22:50 ryzen kernel: usb 1-2.2: SerialNumber: 223606797749
Oct 11 17:22:50 ryzen kernel: input: Kinesis Freestyle Edge Keyboard as /devices/pci0000:00/0000:00:01.2/0000:02:00.0/usb1/1-2/1-2.2/1-2.2:1.0/0003:29EA:0102.0005/input/input6
Oct 11 17:22:50 ryzen kernel: hid-generic 0003:29EA:0102.0005: input,hidraw4: USB HID v1.11 Mouse [Kinesis Freestyle Edge Keyboard] on usb-0000:02:00.0-2.2/input0
Oct 11 17:22:50 ryzen systemd[1]: Finished Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling.
Oct 11 17:22:50 ryzen kernel: input: Kinesis Freestyle Edge Keyboard as /devices/pci0000:00/0000:00:01.2/0000:02:00.0/usb1/1-2/1-2.2/1-2.2:1.1/0003:29EA:0102.0006/input/input7
Oct 11 17:22:50 ryzen systemd[1]: modprobe@configfs.service: Deactivated successfully.
Oct 11 17:22:50 ryzen kernel: hid-generic 0003:29EA:0102.0006: input,hidraw5: USB HID v1.11 Keyboard [Kinesis Freestyle Edge Keyboard] on usb-0000:02:00.0-2.2/input1
Oct 11 17:22:50 ryzen kernel: input: Kinesis Freestyle Edge Keyboard Consumer Control as /devices/pci0000:00/0000:00:01.2/0000:02:00.0/usb1/1-2/1-2.2/1-2.2:1.2/0003:29EA:0102.0007/input/input8
Oct 11 17:22:50 ryzen systemd[1]: Finished Load Kernel Module configfs.
Oct 11 17:22:50 ryzen systemd[1]: modprobe@dm_mod.service: Deactivated successfully.
Oct 11 17:22:50 ryzen kernel: input: Kinesis Freestyle Edge Keyboard System Control as /devices/pci0000:00/0000:00:01.2/0000:02:00.0/usb1/1-2/1-2.2/1-2.2:1.2/0003:29EA:0102.0007/input/input9
Oct 11 17:22:50 ryzen kernel: hid-generic 0003:29EA:0102.0007: input,hidraw6: USB HID v1.11 Device [Kinesis Freestyle Edge Keyboard] on usb-0000:02:00.0-2.2/input2
Oct 11 17:22:51 ryzen systemd[1]: Finished Load Kernel Module dm_mod.
Oct 11 17:22:51 ryzen systemd[1]: modprobe@drm.service: Deactivated successfully.
Oct 11 17:22:51 ryzen kernel: usb 1-2.3: new full-speed USB device number 8 using xhci_hcd
Oct 11 17:22:51 ryzen kernel: usb 1-10: New USB device found, idVendor=048d, idProduct=5702, bcdDevice= 0.01
Oct 11 17:22:51 ryzen kernel: usb 1-10: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Oct 11 17:22:51 ryzen kernel: usb 1-10: Product: ITE Device
Oct 11 17:22:51 ryzen kernel: usb 1-10: Manufacturer: ITE Tech. Inc.
Oct 11 17:22:51 ryzen systemd[1]: Finished Load Kernel Module drm.
Oct 11 17:22:51 ryzen kernel: hid-generic 0003:048D:5702.0008: hiddev98,hidraw7: USB HID v1.12 Device [ITE Tech. Inc. ITE Device] on usb-0000:02:00.0-10/input0
Oct 11 17:22:51 ryzen systemd[1]: modprobe@fuse.service: Deactivated successfully.
Oct 11 17:22:51 ryzen systemd[1]: Finished Load Kernel Module fuse.
Oct 11 17:22:51 ryzen systemd[1]: modprobe@loop.service: Deactivated successfully.
Oct 11 17:22:51 ryzen systemd[1]: Finished Load Kernel Module loop.
Oct 11 17:22:51 ryzen systemd[1]: Finished Load Kernel Modules.
Oct 11 17:22:51 ryzen kernel: usb 1-2.3: New USB device found, idVendor=046d, idProduct=c092, bcdDevice=52.00
Oct 11 17:22:51 ryzen kernel: usb 1-2.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Oct 11 17:22:51 ryzen kernel: usb 1-2.3: Product: G203 LIGHTSYNC Gaming Mouse
Oct 11 17:22:51 ryzen kernel: usb 1-2.3: Manufacturer: Logitech
Oct 11 17:22:51 ryzen kernel: usb 1-2.3: SerialNumber: 204B396D5831
Oct 11 17:22:51 ryzen systemd[1]: Finished Remount Root and Kernel File Systems.
Oct 11 17:22:51 ryzen kernel: input: Logitech G203 LIGHTSYNC Gaming Mouse as /devices/pci0000:00/0000:00:01.2/0000:02:00.0/usb1/1-2/1-2.3/1-2.3:1.0/0003:046D:C092.0009/input/input10
Oct 11 17:22:51 ryzen kernel: hid-generic 0003:046D:C092.0009: input,hidraw8: USB HID v1.11 Mouse [Logitech G203 LIGHTSYNC Gaming Mouse] on usb-0000:02:00.0-2.3/input0
Oct 11 17:22:51 ryzen kernel: input: Logitech G203 LIGHTSYNC Gaming Mouse Keyboard as /devices/pci0000:00/0000:00:01.2/0000:02:00.0/usb1/1-2/1-2.3/1-2.3:1.1/0003:046D:C092.000A/input/input11
Oct 11 17:22:51 ryzen systemd[1]: Finished Coldplug All udev Devices.
Oct 11 17:22:51 ryzen kernel: hid-generic 0003:046D:C092.000A: input,hiddev99,hidraw9: USB HID v1.11 Keyboard [Logitech G203 LIGHTSYNC Gaming Mouse] on usb-0000:02:00.0-2.3/input1
Oct 11 17:22:51 ryzen systemd[1]: Mounting FUSE Control File System...
Oct 11 17:22:51 ryzen systemd[1]: Mounting Kernel Configuration File System...
Oct 11 17:22:51 ryzen systemd[1]: Starting Rebuild Hardware Database...
Oct 11 17:22:51 ryzen systemd[1]: Starting Flush Journal to Persistent Storage...
Oct 11 17:22:51 ryzen systemd-journald[309]: Time spent on flushing to /var/log/journal/be541a4ba238441eb205e6279170129b is 38.770ms for 1062 entries.
Oct 11 17:22:51 ryzen systemd-journald[309]: System Journal (/var/log/journal/be541a4ba238441eb205e6279170129b) is 561.6M, max 4.0G, 3.4G free.
Oct 11 17:22:51 ryzen systemd-journald[309]: Received client request to flush runtime journal.
Oct 11 17:22:51 ryzen kernel: usb 1-2.4: new full-speed USB device number 9 using xhci_hcd
Oct 11 17:22:51 ryzen systemd-journald[309]: /var/log/journal/be541a4ba238441eb205e6279170129b/system.journal: Journal file uses a different sequence number ID, rotating.
Oct 11 17:22:51 ryzen systemd-journald[309]: Rotating system journal.
Oct 11 17:22:51 ryzen systemd[1]: Starting Load/Save OS Random Seed...
Oct 11 17:22:51 ryzen systemd[1]: Repartition Root Disk was skipped because no trigger condition checks were met.
Oct 11 17:22:51 ryzen systemd[1]: Starting Apply Kernel Variables...
Oct 11 17:22:51 ryzen systemd[1]: Starting Create Static Device Nodes in /dev gracefully...
Oct 11 17:22:51 ryzen systemd[1]: Mounted FUSE Control File System.
Oct 11 17:22:51 ryzen systemd[1]: Mounted Kernel Configuration File System.
Oct 11 17:22:51 ryzen systemd[1]: Finished Flush Journal to Persistent Storage.
Oct 11 17:22:51 ryzen systemd[1]: Finished Load/Save OS Random Seed.
Oct 11 17:22:51 ryzen systemd[1]: Finished Rebuild Hardware Database.
Oct 11 17:22:51 ryzen systemd[1]: Finished Apply Kernel Variables.
Oct 11 17:22:51 ryzen kernel: usb 1-2.4: New USB device found, idVendor=1050, idProduct=0120, bcdDevice= 5.24
Oct 11 17:22:51 ryzen kernel: usb 1-2.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Oct 11 17:22:51 ryzen kernel: usb 1-2.4: Product: Security Key by Yubico
Oct 11 17:22:51 ryzen kernel: usb 1-2.4: Manufacturer: Yubico
Oct 11 17:22:52 ryzen kernel: hid-generic 0003:1050:0120.000B: hiddev100,hidraw10: USB HID v1.10 Device [Yubico Security Key by Yubico] on usb-0000:02:00.0-2.4/input0
Oct 11 17:22:52 ryzen systemd[1]: Finished Create Static Device Nodes in /dev gracefully.
Oct 11 17:22:52 ryzen systemd[1]: Starting Create System Users...
Oct 11 17:22:52 ryzen systemd[1]: Finished Create System Users.
Oct 11 17:22:52 ryzen systemd[1]: Starting Create Static Device Nodes in /dev...
Oct 11 17:22:52 ryzen systemd[1]: Finished Create Static Device Nodes in /dev.
Oct 11 17:22:52 ryzen systemd[1]: Reached target Preparation for Local File Systems.
Oct 11 17:22:52 ryzen systemd[1]: Virtual Machine and Container Storage (Compatibility) was skipped because of an unmet condition check (ConditionPathExists=/var/lib/machines.raw).
Oct 11 17:22:52 ryzen systemd[1]: Starting Rule-based Manager for Device Events and Files...
Oct 11 17:22:52 ryzen systemd-udevd[364]: Using default interface naming scheme 'v253'.
Oct 11 17:22:52 ryzen systemd-udevd[364]: /etc/udev/rules.d/30-usbtmc.rules:5 Unknown group 'usbtmc', ignoring.
Oct 11 17:22:52 ryzen systemd-udevd[364]: /etc/udev/rules.d/30-usbtmc.rules:8 Unknown group 'usbtmc', ignoring.
Oct 11 17:22:52 ryzen systemd-udevd[364]: /etc/udev/rules.d/30-usbtmc.rules:11 Unknown group 'usbtmc', ignoring.
Oct 11 17:22:52 ryzen systemd-udevd[364]: /etc/udev/rules.d/30-usbtmc.rules:14 Unknown group 'usbtmc', ignoring.
Oct 11 17:22:52 ryzen systemd-udevd[364]: /etc/udev/rules.d/30-usbtmc.rules:15 Unknown group 'usbtmc', ignoring.
Oct 11 17:22:52 ryzen systemd-udevd[364]: /usr/lib/udev/rules.d/51-footcontroller.rules:10 Invalid value for OPTIONS key, ignoring: 'last_rule'
Oct 11 17:22:52 ryzen systemd[1]: Started Rule-based Manager for Device Events and Files.
Oct 11 17:22:52 ryzen mtp-probe[390]: checking bus 1, device 5: "/sys/devices/pci0000:00/0000:00:01.2/0000:02:00.0/usb1/1-7"
Oct 11 17:22:52 ryzen mtp-probe[390]: bus: 1, device: 5 was not an MTP device
Oct 11 17:22:52 ryzen (udev-worker)[389]: nvme0: /etc/udev/rules.d/99-suspendfix.rules:2 Failed to write ATTR{/sys/devices/pci0000:00/0000:00:01.1/0000:01:00.0/nvme/nvme0/power/wakeup}, ignoring: No such file or directory
Oct 11 17:22:52 ryzen (udev-worker)[389]: nvme0n1: /etc/udev/rules.d/99-suspendfix.rules:2 Failed to write ATTR{/sys/devices/pci0000:00/0000:00:01.1/0000:01:00.0/nvme/nvme0/nvme0n1/power/wakeup}, ignoring: No such file or directory
Oct 11 17:22:52 ryzen (udev-worker)[420]: nvme0n1p3: /etc/udev/rules.d/99-suspendfix.rules:2 Failed to write ATTR{/sys/devices/pci0000:00/0000:00:01.1/0000:01:00.0/nvme/nvme0/nvme0n1/nvme0n1p3/power/wakeup}, ignoring: No such file or directory
Oct 11 17:22:52 ryzen (udev-worker)[389]: nvme0n1p1: /etc/udev/rules.d/99-suspendfix.rules:2 Failed to write ATTR{/sys/devices/pci0000:00/0000:00:01.1/0000:01:00.0/nvme/nvme0/nvme0n1/nvme0n1p1/power/wakeup}, ignoring: No such file or directory
Oct 11 17:22:52 ryzen (udev-worker)[370]: nvme0n1p6: /etc/udev/rules.d/99-suspendfix.rules:2 Failed to write ATTR{/sys/devices/pci0000:00/0000:00:01.1/0000:01:00.0/nvme/nvme0/nvme0n1/nvme0n1p6/power/wakeup}, ignoring: No such file or directory
Oct 11 17:22:52 ryzen (udev-worker)[369]: nvme0n1p5: /etc/udev/rules.d/99-suspendfix.rules:2 Failed to write ATTR{/sys/devices/pci0000:00/0000:00:01.1/0000:01:00.0/nvme/nvme0/nvme0n1/nvme0n1p5/power/wakeup}, ignoring: No such file or directory
Oct 11 17:22:52 ryzen (udev-worker)[385]: nvme0n1p4: /etc/udev/rules.d/99-suspendfix.rules:2 Failed to write ATTR{/sys/devices/pci0000:00/0000:00:01.1/0000:01:00.0/nvme/nvme0/nvme0n1/nvme0n1p4/power/wakeup}, ignoring: No such file or directory
Oct 11 17:22:52 ryzen systemd[1]: Found device /dev/ttyS0.
Oct 11 17:22:52 ryzen (udev-worker)[413]: nvme0n1p2: /etc/udev/rules.d/99-suspendfix.rules:2 Failed to write ATTR{/sys/devices/pci0000:00/0000:00:01.1/0000:01:00.0/nvme/nvme0/nvme0n1/nvme0n1p2/power/wakeup}, ignoring: No such file or directory
Oct 11 17:22:52 ryzen mtp-probe[440]: checking bus 3, device 2: "/sys/devices/pci0000:00/0000:00:08.1/0000:07:00.3/usb3/3-2"
Oct 11 17:22:52 ryzen mtp-probe[440]: bus: 3, device: 2 was not an MTP device
Oct 11 17:22:52 ryzen kernel: mc: Linux media interface: v0.10
Oct 11 17:22:52 ryzen (udev-worker)[415]: 0000:00:01.1:pcie010: /etc/udev/rules.d/99-suspendfix.rules:2 Failed to write ATTR{/sys/devices/pci0000:00/0000:00:01.1/0000:00:01.1:pcie010/power/wakeup}, ignoring: No such file or directory
Oct 11 17:22:52 ryzen (udev-worker)[369]: 0000:00:01.1:pcie001: /etc/udev/rules.d/99-suspendfix.rules:2 Failed to write ATTR{/sys/devices/pci0000:00/0000:00:01.1/0000:00:01.1:pcie001/power/wakeup}, ignoring: No such file or directory
Oct 11 17:22:52 ryzen (udev-worker)[374]: wakeup3: /etc/udev/rules.d/99-suspendfix.rules:2 Failed to write ATTR{/sys/devices/pci0000:00/0000:00:01.1/wakeup/wakeup3/power/wakeup}, ignoring: No such file or directory
Oct 11 17:22:52 ryzen (udev-worker)[370]: 0000:00:01.1:pcie002: /etc/udev/rules.d/99-suspendfix.rules:2 Failed to write ATTR{/sys/devices/pci0000:00/0000:00:01.1/0000:00:01.1:pcie002/power/wakeup}, ignoring: No such file or directory
Oct 11 17:22:52 ryzen (udev-worker)[375]: hwmon1: /etc/udev/rules.d/99-suspendfix.rules:2 Failed to write ATTR{/sys/devices/pci0000:00/0000:00:01.1/0000:01:00.0/nvme/nvme0/hwmon1/power/wakeup}, ignoring: No such file or directory
Oct 11 17:22:52 ryzen (udev-worker)[436]: 0000:01: /etc/udev/rules.d/99-suspendfix.rules:2 Failed to write ATTR{/sys/devices/pci0000:00/0000:00:01.1/pci_bus/0000:01/power/wakeup}, ignoring: No such file or directory
Oct 11 17:22:52 ryzen (udev-worker)[420]: ng0n1: /etc/udev/rules.d/99-suspendfix.rules:2 Failed to write ATTR{/sys/devices/pci0000:00/0000:00:01.1/0000:01:00.0/nvme/nvme0/ng0n1/power/wakeup}, ignoring: No such file or directory
Oct 11 17:22:52 ryzen kernel: ACPI Warning: SystemIO range 0x0000000000000B00-0x0000000000000B08 conflicts with OpRegion 0x0000000000000B00-0x0000000000000B0F (\GSA1.SMBI) (20230331/utaddress-204)
Oct 11 17:22:52 ryzen kernel: ACPI: OSL: Resource conflict; ACPI support missing from driver?
Oct 11 17:22:52 ryzen kernel: ACPI: OSL: Resource conflict: System may be unstable or behave erratically
Oct 11 17:22:52 ryzen kernel: piix4_smbus 0000:00:14.0: SMBus Host Controller at 0xb00, revision 0
Oct 11 17:22:52 ryzen kernel: piix4_smbus 0000:00:14.0: Using register 0x02 for SMBus port selection
Oct 11 17:22:52 ryzen kernel: ACPI Warning: SystemIO range 0x0000000000000B20-0x0000000000000B28 conflicts with OpRegion 0x0000000000000B20-0x0000000000000B3F (\GSA1.SMG0) (20230331/utaddress-204)
Oct 11 17:22:52 ryzen kernel: ACPI: OSL: Resource conflict; ACPI support missing from driver?
Oct 11 17:22:52 ryzen kernel: ACPI: OSL: Resource conflict: System may be unstable or behave erratically
Oct 11 17:22:52 ryzen kernel: piix4_smbus 0000:00:14.0: Auxiliary SMBus Host Controller at 0xb20
Oct 11 17:22:52 ryzen systemd[1]: Found device Samsung SSD 970 EVO Plus 2TB Linux\x20Swap.
Oct 11 17:22:52 ryzen kernel: ccp 0000:07:00.1: enabling device (0000 -> 0002)
Oct 11 17:22:52 ryzen kernel: sp5100_tco: SP5100/SB800 TCO WatchDog Timer Driver
Oct 11 17:22:52 ryzen kernel: sp5100-tco sp5100-tco: Using 0xfeb00000 for watchdog MMIO address
Oct 11 17:22:52 ryzen kernel: input: PC Speaker as /devices/platform/pcspkr/input/input14
Oct 11 17:22:52 ryzen kernel: ccp 0000:07:00.1: ccp: unable to access the device: you might be running a broken BIOS.
Oct 11 17:22:52 ryzen kernel: ccp 0000:07:00.1: psp enabled
Oct 11 17:22:52 ryzen kernel: sp5100-tco sp5100-tco: initialized. heartbeat=60 sec (nowayout=0)
Oct 11 17:22:52 ryzen kernel: RAPL PMU: API unit is 2^-32 Joules, 1 fixed counters, 163840 ms ovfl timer
Oct 11 17:22:52 ryzen kernel: RAPL PMU: hw unit of domain package 2^-16 Joules
Oct 11 17:22:52 ryzen mtp-probe[463]: checking bus 1, device 5: "/sys/devices/pci0000:00/0000:00:01.2/0000:02:00.0/usb1/1-7"
Oct 11 17:22:52 ryzen mtp-probe[463]: bus: 1, device: 5 was not an MTP device
Oct 11 17:22:52 ryzen systemd[1]: Found device Samsung SSD 970 EVO Plus 2TB EFI.
Oct 11 17:22:52 ryzen kernel: cryptd: max_cpu_qlen set to 1000
Oct 11 17:22:52 ryzen kernel: snd_hda_intel 0000:05:00.1: Handle vga_switcheroo audio client
Oct 11 17:22:52 ryzen kernel: snd_hda_intel 0000:05:00.1: Force to non-snoop mode
Oct 11 17:22:52 ryzen kernel: snd_hda_intel 0000:07:00.4: enabling device (0000 -> 0002)
Oct 11 17:22:52 ryzen kernel: AVX2 version of gcm_enc/dec engaged.
Oct 11 17:22:52 ryzen kernel: AES CTR mode by8 optimization enabled
Oct 11 17:22:52 ryzen systemd[1]: Activating swap /dev/disk/by-uuid/52761d05-5222-434a-a2a9-d80fc43e7e05...
Oct 11 17:22:52 ryzen kernel: input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:03.1/0000:05:00.1/sound/card1/input15
Oct 11 17:22:52 ryzen kernel: input: HDA ATI HDMI HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:03.1/0000:05:00.1/sound/card1/input16
Oct 11 17:22:52 ryzen kernel: input: HDA ATI HDMI HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:03.1/0000:05:00.1/sound/card1/input17
Oct 11 17:22:52 ryzen kernel: input: HDA ATI HDMI HDMI/DP,pcm=9 as /devices/pci0000:00/0000:00:03.1/0000:05:00.1/sound/card1/input18
Oct 11 17:22:52 ryzen kernel: input: HDA ATI HDMI HDMI/DP,pcm=10 as /devices/pci0000:00/0000:00:03.1/0000:05:00.1/sound/card1/input19
Oct 11 17:22:52 ryzen kernel: input: HDA ATI HDMI HDMI/DP,pcm=11 as /devices/pci0000:00/0000:00:03.1/0000:05:00.1/sound/card1/input20
Oct 11 17:22:52 ryzen kernel: Adding 16777212k swap on /dev/nvme0n1p6. Priority:-2 extents:1 across:16777212k SSFS
Oct 11 17:22:52 ryzen systemd[1]: Starting File System Check on /dev/disk/by-uuid/2033-9A36...
Oct 11 17:22:52 ryzen systemd[1]: Starting Virtual Console Setup...
Oct 11 17:22:52 ryzen systemd[1]: Activated swap /dev/disk/by-uuid/52761d05-5222-434a-a2a9-d80fc43e7e05.
Oct 11 17:22:52 ryzen systemd[1]: Reached target Swaps.
Oct 11 17:22:52 ryzen kernel: snd_hda_codec_realtek hdaudioC2D0: autoconfig for ALC887-VD: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:line
Oct 11 17:22:52 ryzen kernel: snd_hda_codec_realtek hdaudioC2D0: speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
Oct 11 17:22:52 ryzen kernel: snd_hda_codec_realtek hdaudioC2D0: hp_outs=1 (0x1b/0x0/0x0/0x0/0x0)
Oct 11 17:22:52 ryzen kernel: snd_hda_codec_realtek hdaudioC2D0: mono: mono_out=0x0
Oct 11 17:22:52 ryzen kernel: snd_hda_codec_realtek hdaudioC2D0: inputs:
Oct 11 17:22:52 ryzen kernel: snd_hda_codec_realtek hdaudioC2D0: Front Mic=0x19
Oct 11 17:22:52 ryzen kernel: snd_hda_codec_realtek hdaudioC2D0: Rear Mic=0x18
Oct 11 17:22:52 ryzen kernel: snd_hda_codec_realtek hdaudioC2D0: Line=0x1a
Oct 11 17:22:52 ryzen systemd[1]: Mounting /tmp...
Oct 11 17:22:52 ryzen systemd[1]: Mounted /tmp.
Oct 11 17:22:52 ryzen systemd[1]: Starting Load Kernel Module dm_mod...
Oct 11 17:22:52 ryzen systemd[1]: Starting Load Kernel Module loop...
Oct 11 17:22:52 ryzen systemd[1]: TPM2 PCR Machine ID Measurement was skipped because of an unmet condition check (ConditionPathExists=/sys/firmware/efi/efivars/StubPcrKernelImage-4a67b082-0a4c-41cf-b6c7-440b29bb8c4f).
Oct 11 17:22:52 ryzen systemd[1]: modprobe@dm_mod.service: Deactivated successfully.
Oct 11 17:22:52 ryzen kernel: input: HD-Audio Generic Front Mic as /devices/pci0000:00/0000:00:08.1/0000:07:00.4/sound/card2/input21
Oct 11 17:22:52 ryzen kernel: input: HD-Audio Generic Rear Mic as /devices/pci0000:00/0000:00:08.1/0000:07:00.4/sound/card2/input22
Oct 11 17:22:52 ryzen kernel: input: HD-Audio Generic Line as /devices/pci0000:00/0000:00:08.1/0000:07:00.4/sound/card2/input23
Oct 11 17:22:52 ryzen kernel: input: HD-Audio Generic Line Out as /devices/pci0000:00/0000:00:08.1/0000:07:00.4/sound/card2/input24
Oct 11 17:22:52 ryzen kernel: input: HD-Audio Generic Front Headphone as /devices/pci0000:00/0000:00:08.1/0000:07:00.4/sound/card2/input25
Oct 11 17:22:52 ryzen systemd-vconsole-setup[507]: setfont: ERROR kdfontop.c:183 put_font_kdfontop: Unable to load such font with such kernel version
Oct 11 17:22:52 ryzen systemd-vconsole-setup[497]: /usr/bin/setfont failed with exit status 71.
Oct 11 17:22:52 ryzen systemd-fsck[500]: fsck.fat 4.2 (2021-01-31)
Oct 11 17:22:52 ryzen systemd-fsck[500]: /dev/nvme0n1p1: 528 files, 22912/106444 clusters
Oct 11 17:22:52 ryzen systemd-vconsole-setup[497]: Setting fonts failed with a "system error", ignoring.
Oct 11 17:22:52 ryzen kernel: kvm_amd: SVM disabled (by BIOS) in MSR_VM_CR on CPU 6
Oct 11 17:22:52 ryzen kernel: fbcon: Taking over console
Oct 11 17:22:52 ryzen kernel: Console: switching to colour frame buffer device 240x67
Oct 11 17:22:52 ryzen systemd[1]: Finished Load Kernel Module dm_mod.
Oct 11 17:22:52 ryzen systemd[1]: Finished File System Check on /dev/disk/by-uuid/2033-9A36.
Oct 11 17:22:53 ryzen systemd[1]: Finished Virtual Console Setup.
Oct 11 17:22:53 ryzen systemd[1]: modprobe@loop.service: Deactivated successfully.
Oct 11 17:22:53 ryzen systemd[1]: Finished Load Kernel Module loop.
Oct 11 17:22:53 ryzen systemd[1]: Mounting /boot...
Oct 11 17:22:53 ryzen systemd[1]: Starting Load Kernel Module dm_mod...
Oct 11 17:22:53 ryzen systemd[1]: Starting Load Kernel Module loop...
Oct 11 17:22:53 ryzen systemd[1]: TPM2 PCR Machine ID Measurement was skipped because of an unmet condition check (ConditionPathExists=/sys/firmware/efi/efivars/StubPcrKernelImage-4a67b082-0a4c-41cf-b6c7-440b29bb8c4f).
Oct 11 17:22:53 ryzen systemd[1]: systemd-vconsole-setup.service: Deactivated successfully.
Oct 11 17:22:53 ryzen kernel: usbcore: registered new interface driver snd-usb-audio
Oct 11 17:22:53 ryzen mtp-probe[539]: checking bus 1, device 4: "/sys/devices/pci0000:00/0000:00:01.2/0000:02:00.0/usb1/1-2/1-2.1"
Oct 11 17:22:53 ryzen mtp-probe[539]: bus: 1, device: 4 was not an MTP device
Oct 11 17:22:53 ryzen systemd[1]: Stopped Virtual Console Setup.
Oct 11 17:22:53 ryzen mtp-probe[559]: checking bus 1, device 7: "/sys/devices/pci0000:00/0000:00:01.2/0000:02:00.0/usb1/1-10"
Oct 11 17:22:53 ryzen mtp-probe[560]: checking bus 1, device 5: "/sys/devices/pci0000:00/0000:00:01.2/0000:02:00.0/usb1/1-7"
Oct 11 17:22:53 ryzen mtp-probe[561]: checking bus 1, device 3: "/sys/devices/pci0000:00/0000:00:01.2/0000:02:00.0/usb1/1-5"
Oct 11 17:22:53 ryzen mtp-probe[560]: bus: 1, device: 5 was not an MTP device
Oct 11 17:22:53 ryzen mtp-probe[561]: bus: 1, device: 3 was not an MTP device
Oct 11 17:22:53 ryzen mtp-probe[559]: bus: 1, device: 7 was not an MTP device
Oct 11 17:22:53 ryzen systemd[1]: Stopping Virtual Console Setup...
Oct 11 17:22:53 ryzen kernel: [drm] amdgpu kernel modesetting enabled.
Oct 11 17:22:53 ryzen mtp-probe[589]: checking bus 1, device 4: "/sys/devices/pci0000:00/0000:00:01.2/0000:02:00.0/usb1/1-2/1-2.1"
Oct 11 17:22:53 ryzen mtp-probe[590]: checking bus 1, device 9: "/sys/devices/pci0000:00/0000:00:01.2/0000:02:00.0/usb1/1-2/1-2.4"
Oct 11 17:22:53 ryzen mtp-probe[587]: checking bus 1, device 8: "/sys/devices/pci0000:00/0000:00:01.2/0000:02:00.0/usb1/1-2/1-2.3"
Oct 11 17:22:53 ryzen mtp-probe[588]: checking bus 1, device 6: "/sys/devices/pci0000:00/0000:00:01.2/0000:02:00.0/usb1/1-2/1-2.2"
Oct 11 17:22:53 ryzen mtp-probe[590]: bus: 1, device: 9 was not an MTP device
Oct 11 17:22:53 ryzen mtp-probe[587]: bus: 1, device: 8 was not an MTP device
Oct 11 17:22:53 ryzen mtp-probe[588]: bus: 1, device: 6 was not an MTP device
Oct 11 17:22:53 ryzen kernel: MCE: In-kernel MCE decoding enabled.
Oct 11 17:22:53 ryzen mtp-probe[589]: bus: 1, device: 4 was not an MTP device
Oct 11 17:22:53 ryzen mtp-probe[615]: checking bus 2, device 2: "/sys/devices/pci0000:00/0000:00:01.2/0000:02:00.0/usb2/2-4"
Oct 11 17:22:53 ryzen kernel: amdgpu: CRAT table disabled by module option
Oct 11 17:22:53 ryzen kernel: amdgpu: Virtual CRAT table created for CPU
Oct 11 17:22:53 ryzen kernel: amdgpu: Topology: Add CPU node
Oct 11 17:22:53 ryzen kernel: [drm] initializing kernel modesetting (POLARIS10 0x1002:0x67DF 0x1462:0x3416 0xEF).
Oct 11 17:22:53 ryzen kernel: [drm] register mmio base: 0xFCE00000
Oct 11 17:22:53 ryzen kernel: [drm] register mmio size: 262144
Oct 11 17:22:53 ryzen kernel: [drm] add ip block number 0 <vi_common>
Oct 11 17:22:53 ryzen kernel: [drm] add ip block number 1 <gmc_v8_0>
Oct 11 17:22:53 ryzen kernel: [drm] add ip block number 2 <tonga_ih>
Oct 11 17:22:53 ryzen kernel: [drm] add ip block number 3 <gfx_v8_0>
Oct 11 17:22:53 ryzen kernel: [drm] add ip block number 4 <sdma_v3_0>
Oct 11 17:22:53 ryzen kernel: [drm] add ip block number 5 <powerplay>
Oct 11 17:22:53 ryzen kernel: [drm] add ip block number 6 <dm>
Oct 11 17:22:53 ryzen kernel: [drm] add ip block number 7 <uvd_v6_0>
Oct 11 17:22:53 ryzen kernel: [drm] add ip block number 8 <vce_v3_0>
Oct 11 17:22:53 ryzen kernel: amdgpu 0000:05:00.0: No more image in the PCI ROM
Oct 11 17:22:53 ryzen kernel: amdgpu 0000:05:00.0: amdgpu: Fetched VBIOS from ROM BAR
Oct 11 17:22:53 ryzen kernel: amdgpu: ATOM BIOS: MS-V34113-F4
Oct 11 17:22:53 ryzen kernel: [drm] UVD is enabled in VM mode
Oct 11 17:22:53 ryzen kernel: [drm] UVD ENC is enabled in VM mode
Oct 11 17:22:53 ryzen kernel: [drm] VCE enabled in VM mode
Oct 11 17:22:53 ryzen kernel: Console: switching to colour dummy device 80x25
Oct 11 17:22:53 ryzen kernel: r8169 0000:04:00.0 eth0: RTL8168h/8111h, 18:c0:4d:6e:95:f4, XID 541, IRQ 97
Oct 11 17:22:53 ryzen kernel: r8169 0000:04:00.0 eth0: jumbo features [frames: 9194 bytes, tx checksumming: ko]
Oct 11 17:22:53 ryzen kernel: r8169 0000:04:00.0 enp4s0: renamed from eth0
Oct 11 17:22:53 ryzen mtp-probe[615]: bus: 2, device: 2 was not an MTP device
Oct 11 17:22:53 ryzen systemd[1]: Starting Virtual Console Setup...
Oct 11 17:22:53 ryzen mtp-probe[678]: checking bus 1, device 7: "/sys/devices/pci0000:00/0000:00:01.2/0000:02:00.0/usb1/1-10"
Oct 11 17:22:53 ryzen mtp-probe[678]: bus: 1, device: 7 was not an MTP device
Oct 11 17:22:53 ryzen mtp-probe[682]: checking bus 1, device 9: "/sys/devices/pci0000:00/0000:00:01.2/0000:02:00.0/usb1/1-2/1-2.4"
Oct 11 17:22:53 ryzen mtp-probe[682]: bus: 1, device: 9 was not an MTP device
Oct 11 17:22:53 ryzen systemd-vconsole-setup[700]: setfont: ERROR kdfontop.c:183 put_font_kdfontop: Unable to load such font with such kernel version
Oct 11 17:22:53 ryzen systemd-vconsole-setup[617]: /usr/bin/setfont failed with exit status 71.
Oct 11 17:22:53 ryzen kernel: amdgpu 0000:05:00.0: vgaarb: deactivate vga console
Oct 11 17:22:53 ryzen kernel: amdgpu 0000:05:00.0: amdgpu: Trusted Memory Zone (TMZ) feature not supported
Oct 11 17:22:53 ryzen kernel: [drm] vm size is 64 GB, 2 levels, block size is 10-bit, fragment size is 9-bit
Oct 11 17:22:53 ryzen kernel: amdgpu 0000:05:00.0: amdgpu: VRAM: 4096M 0x000000F400000000 - 0x000000F4FFFFFFFF (4096M used)
Oct 11 17:22:53 ryzen kernel: amdgpu 0000:05:00.0: amdgpu: GART: 256M 0x000000FF00000000 - 0x000000FF0FFFFFFF
Oct 11 17:22:53 ryzen kernel: [drm] Detected VRAM RAM=4096M, BAR=256M
Oct 11 17:22:53 ryzen kernel: [drm] RAM width 256bits GDDR5
Oct 11 17:22:53 ryzen kernel: [drm] amdgpu: 4096M of VRAM memory ready
Oct 11 17:22:53 ryzen kernel: [drm] amdgpu: 7946M of GTT memory ready.
Oct 11 17:22:53 ryzen kernel: [drm] GART: num cpu pages 65536, num gpu pages 65536
Oct 11 17:22:53 ryzen kernel: [drm] PCIE GART of 256M enabled (table at 0x000000F400800000).
Oct 11 17:22:53 ryzen systemd[1]: Mounted /boot.
Oct 11 17:22:53 ryzen systemd-vconsole-setup[617]: Setting fonts failed with a "system error", ignoring.
Oct 11 17:22:53 ryzen kernel: [drm] Chained IB support enabled!
Oct 11 17:22:53 ryzen kernel: amdgpu: hwmgr_sw_init smu backed is polaris10_smu
Oct 11 17:22:53 ryzen kernel: [drm] Found UVD firmware Version: 1.130 Family ID: 16
Oct 11 17:22:53 ryzen kernel: [drm] Found VCE firmware Version: 53.26 Binary ID: 3
Oct 11 17:22:53 ryzen systemd[1]: modprobe@dm_mod.service: Deactivated successfully.
Oct 11 17:22:53 ryzen kernel: mousedev: PS/2 mouse device common for all mice
Oct 11 17:22:53 ryzen kernel: intel_rapl_common: Found RAPL domain package
Oct 11 17:22:53 ryzen kernel: intel_rapl_common: Found RAPL domain core
Oct 11 17:22:53 ryzen systemd[1]: Finished Load Kernel Module dm_mod.
Oct 11 17:22:53 ryzen systemd[1]: modprobe@loop.service: Deactivated successfully.
Oct 11 17:22:54 ryzen systemd[1]: Finished Load Kernel Module loop.
Oct 11 17:22:54 ryzen mtp-probe[735]: checking bus 1, device 8: "/sys/devices/pci0000:00/0000:00:01.2/0000:02:00.0/usb1/1-2/1-2.3"
Oct 11 17:22:54 ryzen mtp-probe[735]: bus: 1, device: 8 was not an MTP device
Oct 11 17:22:54 ryzen mtp-probe[744]: checking bus 1, device 6: "/sys/devices/pci0000:00/0000:00:01.2/0000:02:00.0/usb1/1-2/1-2.2"
Oct 11 17:22:54 ryzen mtp-probe[744]: bus: 1, device: 6 was not an MTP device
Oct 11 17:22:54 ryzen systemd[1]: Finished Virtual Console Setup.
Oct 11 17:22:54 ryzen systemd[1]: Found device WDC_WD20EFRX-68AX9N0 Storage.
Oct 11 17:22:54 ryzen systemd[1]: Reached target Local File Systems.
Oct 11 17:22:54 ryzen systemd[1]: Mounting /mnt/storage...
Oct 11 17:22:54 ryzen systemd[1]: Starting Rebuild Dynamic Linker Cache...
Oct 11 17:22:54 ryzen systemd[1]: Starting Load Kernel Module dm_mod...
Oct 11 17:22:54 ryzen kernel: [drm] Display Core v3.2.241 initialized on DCE 11.2
Oct 11 17:22:54 ryzen systemd[1]: Starting Load Kernel Module loop...
Oct 11 17:22:54 ryzen kernel: snd_hda_intel 0000:05:00.1: bound 0000:05:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu])
Oct 11 17:22:54 ryzen systemd[1]: Starting Set Up Additional Binary Formats...
Oct 11 17:22:54 ryzen systemd[1]: Starting Update Boot Loader Random Seed...
Oct 11 17:22:54 ryzen systemd[1]: TPM2 PCR Machine ID Measurement was skipped because of an unmet condition check (ConditionPathExists=/sys/firmware/efi/efivars/StubPcrKernelImage-4a67b082-0a4c-41cf-b6c7-440b29bb8c4f).
Oct 11 17:22:54 ryzen systemd[1]: Starting Create Volatile Files and Directories...
Oct 11 17:22:54 ryzen bootctl[767]: ! Mount point '/boot' which backs the random seed file is world accessible, which is a security hole! !
Oct 11 17:22:54 ryzen bootctl[767]: ! Random seed file '/boot/loader/random-seed' is world accessible, which is a security hole! !
Oct 11 17:22:54 ryzen bootctl[767]: Random seed file /boot/loader/random-seed successfully refreshed (32 bytes).
Oct 11 17:22:54 ryzen systemd[1]: modprobe@dm_mod.service: Deactivated successfully.
Oct 11 17:22:54 ryzen systemd[1]: Finished Load Kernel Module dm_mod.
Oct 11 17:22:54 ryzen systemd[1]: modprobe@loop.service: Deactivated successfully.
Oct 11 17:22:54 ryzen kernel: [drm] UVD and UVD ENC initialized successfully.
Oct 11 17:22:54 ryzen systemd[1]: Finished Load Kernel Module loop.
Oct 11 17:22:54 ryzen systemd[1]: Finished Update Boot Loader Random Seed.
Oct 11 17:22:54 ryzen ntfs-3g[776]: Version 2022.10.3 external FUSE 29
Oct 11 17:22:54 ryzen ntfs-3g[776]: Mounted /dev/sda1 (Read-Write, label "Storage", NTFS 3.1)
Oct 11 17:22:54 ryzen ntfs-3g[776]: Cmdline options: rw,nosuid,nodev,umask=0
Oct 11 17:22:54 ryzen ntfs-3g[776]: Mount options: nosuid,nodev,allow_other,nonempty,relatime,rw,default_permissions,fsname=/dev/sda1,blkdev,blksize=4096
Oct 11 17:22:54 ryzen ntfs-3g[776]: Global ownership and permissions enforced, configuration type 7
Oct 11 17:22:54 ryzen systemd[1]: Mounted /mnt/storage.
Oct 11 17:22:54 ryzen kernel: [drm] VCE initialized successfully.
Oct 11 17:22:54 ryzen kernel: kfd kfd: amdgpu: Allocated 3969056 bytes on gart
Oct 11 17:22:54 ryzen kernel: kfd kfd: amdgpu: Total number of KFD nodes to be created: 1
Oct 11 17:22:54 ryzen kernel: amdgpu: Virtual CRAT table created for GPU
Oct 11 17:22:54 ryzen kernel: amdgpu: Topology: Add dGPU node [0x67df:0x1002]
Oct 11 17:22:54 ryzen kernel: kfd kfd: amdgpu: added device 1002:67df
Oct 11 17:22:54 ryzen kernel: amdgpu 0000:05:00.0: amdgpu: SE 4, SH per SE 1, CU per SH 9, active_cu_number 32
Oct 11 17:22:54 ryzen systemd[1]: proc-sys-fs-binfmt_misc.automount: Got automount request for /proc/sys/fs/binfmt_misc, triggered by 766 (systemd-binfmt)
Oct 11 17:22:54 ryzen kernel: amdgpu 0000:05:00.0: amdgpu: Using BACO for runtime pm
Oct 11 17:22:54 ryzen kernel: [drm] Initialized amdgpu 3.54.0 20150101 for 0000:05:00.0 on minor 1
Oct 11 17:22:54 ryzen kernel: fbcon: amdgpudrmfb (fb0) is primary device
Oct 11 17:22:54 ryzen systemd[1]: Mounting Arbitrary Executable File Formats File System...
Oct 11 17:22:54 ryzen kernel: Console: switching to colour frame buffer device 240x67
Oct 11 17:22:54 ryzen kernel: amdgpu 0000:05:00.0: [drm] fb0: amdgpudrmfb frame buffer device
Oct 11 17:22:54 ryzen systemd[1]: Repartition Root Disk was skipped because no trigger condition checks were met.
Oct 11 17:22:54 ryzen systemd[1]: Mounted Arbitrary Executable File Formats File System.
Oct 11 17:22:54 ryzen systemd[1]: Finished Set Up Additional Binary Formats.
Oct 11 17:22:54 ryzen systemd[1]: Finished Rebuild Dynamic Linker Cache.
Oct 11 17:22:54 ryzen systemd[1]: Finished Create Volatile Files and Directories.
Oct 11 17:22:54 ryzen systemd[1]: First Boot Wizard was skipped because of an unmet condition check (ConditionFirstBoot=yes).
Oct 11 17:22:54 ryzen systemd[1]: First Boot Complete was skipped because of an unmet condition check (ConditionFirstBoot=yes).
Oct 11 17:22:54 ryzen systemd[1]: Starting Rebuild Journal Catalog...
Oct 11 17:22:54 ryzen systemd[1]: Commit a transient machine-id on disk was skipped because of an unmet condition check (ConditionPathIsMountPoint=/etc/machine-id).
Oct 11 17:22:54 ryzen systemd[1]: Starting Network Time Synchronization...
Oct 11 17:22:54 ryzen systemd[1]: Starting Record System Boot/Shutdown in UTMP...
Oct 11 17:22:54 ryzen systemd[1]: Finished Rebuild Journal Catalog.
Oct 11 17:22:54 ryzen systemd[1]: Starting Update is Completed...
Oct 11 17:22:54 ryzen systemd[1]: Finished Update is Completed.
Oct 11 17:22:54 ryzen systemd[1]: Started Network Time Synchronization.
Oct 11 17:22:54 ryzen systemd[1]: Reached target System Time Set.
Oct 11 17:22:55 ryzen systemd[1]: Finished Record System Boot/Shutdown in UTMP.
Oct 11 17:22:55 ryzen systemd[1]: Reached target System Initialization.
Oct 11 17:22:55 ryzen systemd[1]: Started CUPS Scheduler.
Oct 11 17:22:55 ryzen systemd[1]: Started Virtual console mouse server.
Oct 11 17:22:55 ryzen systemd[1]: Started Refresh existing PGP keys of archlinux-keyring regularly.
Oct 11 17:22:55 ryzen systemd[1]: Started Daily man-db regeneration.
Oct 11 17:22:55 ryzen systemd[1]: Started Daily verification of password and group files.
Oct 11 17:22:55 ryzen systemd[1]: Started Daily Cleanup of Temporary Directories.
Oct 11 17:22:55 ryzen systemd[1]: Reached target Path Units.
Oct 11 17:22:55 ryzen systemd[1]: Reached target Timer Units.
Oct 11 17:22:55 ryzen systemd[1]: Listening on Avahi mDNS/DNS-SD Stack Activation Socket.
Oct 11 17:22:55 ryzen systemd[1]: Listening on CUPS Scheduler.
Oct 11 17:22:55 ryzen systemd[1]: Listening on D-Bus System Message Bus Socket.
Oct 11 17:22:55 ryzen systemd[1]: Listening on Libvirt local socket.
Oct 11 17:22:55 ryzen systemd[1]: Listening on Libvirt admin socket.
Oct 11 17:22:55 ryzen systemd[1]: Listening on Libvirt local read-only socket.
Oct 11 17:22:55 ryzen systemd[1]: Listening on Podman API Socket.
Oct 11 17:22:55 ryzen systemd[1]: Listening on Virtual machine lock manager socket.
Oct 11 17:22:55 ryzen systemd[1]: Listening on Virtual machine log manager socket.
Oct 11 17:22:55 ryzen systemd[1]: Reached target Socket Units.
Oct 11 17:22:55 ryzen systemd[1]: TPM2 PCR Barrier (Initialization) was skipped because of an unmet condition check (ConditionPathExists=/sys/firmware/efi/efivars/StubPcrKernelImage-4a67b082-0a4c-41cf-b6c7-440b29bb8c4f).
Oct 11 17:22:55 ryzen systemd[1]: Reached target Basic System.
Oct 11 17:22:55 ryzen systemd[1]: Starting Save/Restore Sound Card State...
Oct 11 17:22:55 ryzen systemd[1]: Manage Sound Card State (restore and store) was skipped because of an unmet condition check (ConditionPathExists=/etc/alsa/state-daemon.conf).
Oct 11 17:22:55 ryzen systemd[1]: Starting Avahi mDNS/DNS-SD Stack...
Oct 11 17:22:55 ryzen systemd[1]: Starting D-Bus System Message Bus...
Oct 11 17:22:55 ryzen systemd[1]: Starting Virtual console mouse server...
Oct 11 17:22:55 ryzen systemd[1]: Starting Clean up modules from old kernels...
Oct 11 17:22:55 ryzen /usr/bin/gpm[827]: *** info [daemon/startup.c(136)]:
Oct 11 17:22:55 ryzen /usr/bin/gpm[827]: Started gpm successfully. Entered daemon mode.
Oct 11 17:22:55 ryzen systemd[1]: Starting Initialize hardware monitoring sensors...
Oct 11 17:22:55 ryzen bash[826]: + for i in /usr/lib/modules/[0-9]*
Oct 11 17:22:55 ryzen bash[826]: + [[ 6.5.5-arch1-1 = \6\.\5\.\6\-\a\r\c\h\2\-\1 ]]
Oct 11 17:22:55 ryzen bash[826]: + pacman -Qo /usr/lib/modules/6.5.5-arch1-1
Oct 11 17:22:55 ryzen (modprobe)[828]: lm_sensors.service: Referenced but unset environment variable evaluates to an empty string: BUS_MODULES
Oct 11 17:22:55 ryzen systemd[1]: Starting User Login Management...
Oct 11 17:22:55 ryzen systemd[1]: Starting Virtual Machine and Container Registration Service...
Oct 11 17:22:55 ryzen systemd[1]: TPM2 PCR Barrier (User) was skipped because of an unmet condition check (ConditionPathExists=/sys/firmware/efi/efivars/StubPcrKernelImage-4a67b082-0a4c-41cf-b6c7-440b29bb8c4f).
Oct 11 17:22:55 ryzen systemd[1]: Starting Manage swap spaces on zram, files and partitions....
Oct 11 17:22:55 ryzen systemd-logind[830]: New seat seat0.
Oct 11 17:22:55 ryzen systemd-logind[830]: Watching system buttons on /dev/input/event1 (Power Button)
Oct 11 17:22:55 ryzen systemd-logind[830]: Watching system buttons on /dev/input/event0 (Power Button)
Oct 11 17:22:55 ryzen systemd-logind[830]: Watching system buttons on /dev/input/event7 (Kinesis Freestyle Edge Keyboard)
Oct 11 17:22:55 ryzen systemd-logind[830]: Watching system buttons on /dev/input/event9 (Kinesis Freestyle Edge Keyboard System Control)
Oct 11 17:22:55 ryzen systemd-logind[830]: Watching system buttons on /dev/input/event11 (Logitech G203 LIGHTSYNC Gaming Mouse Keyboard)
Oct 11 17:22:55 ryzen systemd-logind[830]: Watching system buttons on /dev/input/event2 (AT Translated Set 2 keyboard)
Oct 11 17:22:55 ryzen systemd[1]: Starting Startup script for rr zen workaround...
Oct 11 17:22:55 ryzen systemd[1]: Started D-Bus System Message Bus.
Oct 11 17:22:55 ryzen kernel: msr: Write to unrecognized MSR 0xc0011020 by python3 (pid: 862).
Oct 11 17:22:55 ryzen kernel: msr: See https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/about for details.
Oct 11 17:22:55 ryzen zen_workaround.py[862]: Zen workaround in place
Oct 11 17:22:55 ryzen systemd[1]: Started User Login Management.
Oct 11 17:22:55 ryzen systemd-swap[833]: INFO: Removing working directory...
Oct 11 17:22:55 ryzen systemd-swap[833]: INFO: Removing files in /var/lib/systemd-swap/swapfc/...
Oct 11 17:22:55 ryzen systemd[1]: Finished Save/Restore Sound Card State.
Oct 11 17:22:55 ryzen systemd[1]: Started Virtual console mouse server.
Oct 11 17:22:55 ryzen systemd-swap[833]: INFO: Zswap: backup current configuration: start
Oct 11 17:22:55 ryzen systemd-swap[833]: INFO: Zswap: backup current configuration: complete
Oct 11 17:22:55 ryzen systemd-swap[833]: INFO: Zswap: set new parameters: start
Oct 11 17:22:55 ryzen systemd-swap[833]: INFO: Zswap: Enable: 1, Comp: zstd, Max pool %: 25, Zpool: z3fold
Oct 11 17:22:55 ryzen systemd-swap[833]: INFO: Zswap: set new parameters: complete
Oct 11 17:22:55 ryzen systemd-swap[833]: INFO: Writing destroy info...
Oct 11 17:22:55 ryzen systemd-swap[833]: INFO: swapD: pick up devices from systemd-gpt-auto-generator
Oct 11 17:22:55 ryzen systemd-swap[833]: INFO: swapD: searching swap devices
Oct 11 17:22:55 ryzen /usr/bin/gpm[827]: *** info [mice.c(1990)]:
Oct 11 17:22:55 ryzen /usr/bin/gpm[827]: imps2: Auto-detected intellimouse PS/2
Oct 11 17:22:55 ryzen systemd[1]: Finished Startup script for rr zen workaround.
Oct 11 17:22:55 ryzen systemd[1]: Started Manage swap spaces on zram, files and partitions..
Oct 11 17:22:55 ryzen systemd[1]: Finished Initialize hardware monitoring sensors.
Oct 11 17:22:55 ryzen systemd[1]: Reached target Sound Card.
Oct 11 17:22:55 ryzen dbus-daemon[824]: [system] Successfully activated service 'org.freedesktop.systemd1'
Oct 11 17:22:55 ryzen systemd[1]: Starting Network Manager...
Oct 11 17:22:55 ryzen NetworkManager[927]: <info> [1697070175.9523] NetworkManager (version 1.44.2-1) is starting... (boot:a5fc0caa-a1a1-45f8-8498-becad4835c3b)
Oct 11 17:22:55 ryzen NetworkManager[927]: <info> [1697070175.9523] Read config: /etc/NetworkManager/NetworkManager.conf (lib: 20-connectivity.conf)
Oct 11 17:22:55 ryzen systemd[1]: Started Verify integrity of password and group files.
Oct 11 17:22:55 ryzen NetworkManager[927]: <info> [1697070175.9555] manager[0x563abcc8abb0]: monitoring kernel firmware directory '/lib/firmware'.
Oct 11 17:22:55 ryzen dbus-daemon[824]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.4' (uid=0 pid=927 comm="/usr/bin/NetworkManager --no-daemon")
Oct 11 17:22:55 ryzen systemd-udevd[364]: /etc/udev/rules.d/30-usbtmc.rules:5 Unknown group 'usbtmc', ignoring.
Oct 11 17:22:55 ryzen systemd[1]: Started Virtual Machine and Container Registration Service.
Oct 11 17:22:55 ryzen systemd[1]: shadow.service: Deactivated successfully.
Oct 11 17:22:56 ryzen avahi-daemon[823]: Found user 'avahi' (UID 975) and group 'avahi' (GID 975).
Oct 11 17:22:56 ryzen systemd-udevd[364]: /etc/udev/rules.d/30-usbtmc.rules:8 Unknown group 'usbtmc', ignoring.
Oct 11 17:22:56 ryzen avahi-daemon[823]: Successfully dropped root privileges.
Oct 11 17:22:56 ryzen avahi-daemon[823]: avahi-daemon 0.8 starting up.
Oct 11 17:22:56 ryzen avahi-daemon[823]: Successfully called chroot().
Oct 11 17:22:56 ryzen avahi-daemon[823]: Successfully dropped remaining capabilities.
Oct 11 17:22:56 ryzen avahi-daemon[823]: No service file found in /etc/avahi/services.
Oct 11 17:22:56 ryzen avahi-daemon[823]: Joining mDNS multicast group on interface lo.IPv6 with address ::1.
Oct 11 17:22:56 ryzen avahi-daemon[823]: New relevant interface lo.IPv6 for mDNS.
Oct 11 17:22:56 ryzen avahi-daemon[823]: Joining mDNS multicast group on interface lo.IPv4 with address 127.0.0.1.
Oct 11 17:22:56 ryzen avahi-daemon[823]: New relevant interface lo.IPv4 for mDNS.
Oct 11 17:22:56 ryzen avahi-daemon[823]: Network interface enumeration completed.
Oct 11 17:22:56 ryzen avahi-daemon[823]: Registering new address record for ::1 on lo.*.
Oct 11 17:22:56 ryzen avahi-daemon[823]: Registering new address record for 127.0.0.1 on lo.IPv4.
Oct 11 17:22:56 ryzen systemd[1]: Started Avahi mDNS/DNS-SD Stack.
Oct 11 17:22:56 ryzen systemd-udevd[364]: /etc/udev/rules.d/30-usbtmc.rules:11 Unknown group 'usbtmc', ignoring.
Oct 11 17:22:56 ryzen systemd[1]: Starting Hostname Service...
Oct 11 17:22:56 ryzen systemd-udevd[364]: /etc/udev/rules.d/30-usbtmc.rules:14 Unknown group 'usbtmc', ignoring.
Oct 11 17:22:56 ryzen systemd-udevd[364]: /etc/udev/rules.d/30-usbtmc.rules:15 Unknown group 'usbtmc', ignoring.
Oct 11 17:22:56 ryzen systemd-udevd[364]: /usr/lib/udev/rules.d/51-footcontroller.rules:10 Invalid value for OPTIONS key, ignoring: 'last_rule'
Oct 11 17:22:56 ryzen dbus-daemon[824]: [system] Successfully activated service 'org.freedesktop.hostname1'
Oct 11 17:22:56 ryzen systemd[1]: Started Hostname Service.
Oct 11 17:22:56 ryzen NetworkManager[927]: <info> [1697070176.1252] hostname: hostname: using hostnamed
Oct 11 17:22:56 ryzen NetworkManager[927]: <info> [1697070176.1252] hostname: static hostname changed from (none) to "ryzen"
Oct 11 17:22:56 ryzen NetworkManager[927]: <info> [1697070176.1254] dns-mgr: init: dns=default,systemd-resolved rc-manager=symlink
Oct 11 17:22:56 ryzen NetworkManager[927]: <info> [1697070176.1300] manager[0x563abcc8abb0]: rfkill: Wi-Fi hardware radio set enabled
Oct 11 17:22:56 ryzen NetworkManager[927]: <info> [1697070176.1300] manager[0x563abcc8abb0]: rfkill: WWAN hardware radio set enabled
Oct 11 17:22:56 ryzen NetworkManager[927]: <info> [1697070176.1311] Loaded device plugin: NMAtmManager (/usr/lib/NetworkManager/1.44.2-1/libnm-device-plugin-adsl.so)
Oct 11 17:22:56 ryzen NetworkManager[927]: <info> [1697070176.1344] Loaded device plugin: NMBluezManager (/usr/lib/NetworkManager/1.44.2-1/libnm-device-plugin-bluetooth.so)
Oct 11 17:22:56 ryzen NetworkManager[927]: <info> [1697070176.1354] Loaded device plugin: NMOvsFactory (/usr/lib/NetworkManager/1.44.2-1/libnm-device-plugin-ovs.so)
Oct 11 17:22:56 ryzen NetworkManager[927]: <info> [1697070176.1489] Loaded device plugin: NMTeamFactory (/usr/lib/NetworkManager/1.44.2-1/libnm-device-plugin-team.so)
Oct 11 17:22:56 ryzen NetworkManager[927]: <info> [1697070176.1498] Loaded device plugin: NMWifiFactory (/usr/lib/NetworkManager/1.44.2-1/libnm-device-plugin-wifi.so)
Oct 11 17:22:56 ryzen NetworkManager[927]: <info> [1697070176.1503] Loaded device plugin: NMWwanFactory (/usr/lib/NetworkManager/1.44.2-1/libnm-device-plugin-wwan.so)
Oct 11 17:22:56 ryzen NetworkManager[927]: <info> [1697070176.1504] manager: rfkill: Wi-Fi enabled by radio killswitch; enabled by state file
Oct 11 17:22:56 ryzen NetworkManager[927]: <info> [1697070176.1505] manager: rfkill: WWAN enabled by radio killswitch; enabled by state file
Oct 11 17:22:56 ryzen NetworkManager[927]: <info> [1697070176.1505] manager: Networking is enabled by state file
Oct 11 17:22:56 ryzen dbus-daemon[824]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.4' (uid=0 pid=927 comm="/usr/bin/NetworkManager --no-daemon")
Oct 11 17:22:56 ryzen NetworkManager[927]: <info> [1697070176.1510] settings: Loaded settings plugin: keyfile (internal)
Oct 11 17:22:56 ryzen systemd[1]: Listening on Load/Save RF Kill Switch Status /dev/rfkill Watch.
Oct 11 17:22:56 ryzen NetworkManager[927]: <info> [1697070176.1528] dhcp: init: Using DHCP client 'internal'
Oct 11 17:22:56 ryzen NetworkManager[927]: <info> [1697070176.1529] manager: (lo): new Loopback device (/org/freedesktop/NetworkManager/Devices/1)
Oct 11 17:22:56 ryzen NetworkManager[927]: <info> [1697070176.1535] device (lo): state change: unmanaged -> unavailable (reason 'connection-assumed', sys-iface-state: 'external')
Oct 11 17:22:56 ryzen NetworkManager[927]: <info> [1697070176.1537] device (lo): state change: unavailable -> disconnected (reason 'connection-assumed', sys-iface-state: 'external')
Oct 11 17:22:56 ryzen NetworkManager[927]: <info> [1697070176.1540] device (lo): Activation: starting connection 'lo' (ae3ef13d-900f-4e37-9135-dfe1a36098f3)
Oct 11 17:22:56 ryzen NetworkManager[927]: <info> [1697070176.1545] manager: (enp4s0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/2)
Oct 11 17:22:56 ryzen NetworkManager[927]: <info> [1697070176.1546] device (enp4s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Oct 11 17:22:56 ryzen systemd[1]: Starting Network Manager Script Dispatcher Service...
Oct 11 17:22:56 ryzen dbus-daemon[824]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Oct 11 17:22:56 ryzen kernel: Generic FE-GE Realtek PHY r8169-0-400:00: attached PHY driver (mii_bus:phy_addr=r8169-0-400:00, irq=MAC)
Oct 11 17:22:56 ryzen systemd[1]: Started Network Manager Script Dispatcher Service.
Oct 11 17:22:56 ryzen bash[829]: error: No package owns /usr/lib/modules/6.5.5-arch1-1
Oct 11 17:22:56 ryzen systemd[1]: Started Network Manager.
Oct 11 17:22:56 ryzen NetworkManager[927]: <info> [1697070176.3735] bus-manager: acquired D-Bus service "org.freedesktop.NetworkManager"
Oct 11 17:22:56 ryzen NetworkManager[927]: <info> [1697070176.3740] ovsdb: disconnected from ovsdb
Oct 11 17:22:56 ryzen NetworkManager[927]: <info> [1697070176.3740] device (lo): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'external')
Oct 11 17:22:56 ryzen NetworkManager[927]: <info> [1697070176.3741] device (lo): state change: prepare -> config (reason 'none', sys-iface-state: 'external')
Oct 11 17:22:56 ryzen NetworkManager[927]: <info> [1697070176.3742] device (lo): state change: config -> ip-config (reason 'none', sys-iface-state: 'external')
Oct 11 17:22:56 ryzen NetworkManager[927]: <info> [1697070176.3745] device (lo): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'external')
Oct 11 17:22:56 ryzen kernel: r8169 0000:04:00.0 enp4s0: Link is Down
Oct 11 17:22:56 ryzen NetworkManager[927]: <info> [1697070176.3760] device (lo): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'external')
Oct 11 17:22:56 ryzen NetworkManager[927]: <info> [1697070176.3761] device (lo): state change: secondaries -> activated (reason 'none', sys-iface-state: 'external')
Oct 11 17:22:56 ryzen NetworkManager[927]: <info> [1697070176.3763] device (lo): Activation: successful, device activated.
Oct 11 17:22:56 ryzen bash[826]: + rsync -AHXal /usr/lib/modules/6.5.5-arch1-1 /usr/lib/modules/.old/
Oct 11 17:22:56 ryzen systemd[1]: Reached target Network.
Oct 11 17:22:56 ryzen systemd[1]: Starting Network Manager Wait Online...
Oct 11 17:22:56 ryzen systemd[1]: Starting CUPS Scheduler...
Oct 11 17:22:56 ryzen systemd[1]: Starting Virtualization daemon...
Oct 11 17:22:56 ryzen systemd[1]: Starting Permit User Sessions...
Oct 11 17:22:56 ryzen systemd[1]: Finished Permit User Sessions.
Oct 11 17:22:56 ryzen NetworkManager[927]: <info> [1697070176.5402] manager: (virbr1): new Bridge device (/org/freedesktop/NetworkManager/Devices/3)
Oct 11 17:22:56 ryzen kernel: bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this.
Oct 11 17:22:56 ryzen systemd[1]: Started Virtualization daemon.
Oct 11 17:22:56 ryzen systemd[1]: Started Simple Desktop Display Manager.
Oct 11 17:22:56 ryzen systemd[1]: Started Serial Getty on ttyS0.
Oct 11 17:22:56 ryzen sddm[995]: Initializing...
Oct 11 17:22:56 ryzen sddm[995]: Starting...
Oct 11 17:22:56 ryzen sddm[995]: Logind interface found
Oct 11 17:22:56 ryzen sddm[995]: Adding new display...
Oct 11 17:22:56 ryzen sddm[995]: Loaded empty theme configuration
Oct 11 17:22:56 ryzen sddm[995]: Xauthority path: "/run/sddm/xauth_VVticx"
Oct 11 17:22:56 ryzen sddm[995]: Using VT 2
Oct 11 17:22:56 ryzen sddm[995]: Display server starting...
Oct 11 17:22:56 ryzen sddm[995]: Writing cookie to "/run/sddm/xauth_VVticx"
Oct 11 17:22:56 ryzen sddm[995]: Running: /usr/bin/X -nolisten tcp -background none -seat seat0 vt2 -auth /run/sddm/xauth_VVticx -noreset -displayfd 16
Oct 11 17:22:56 ryzen systemd[1]: Reached target Login Prompts.
Oct 11 17:22:56 ryzen dbus-daemon[824]: [system] Activating via systemd: service name='org.freedesktop.ColorManager' unit='colord.service' requested by ':1.11' (uid=0 pid=961 comm="/usr/bin/cupsd -l")
Oct 11 17:22:56 ryzen avahi-daemon[823]: Joining mDNS multicast group on interface virbr1.IPv4 with address 192.168.100.1.
Oct 11 17:22:56 ryzen avahi-daemon[823]: New relevant interface virbr1.IPv4 for mDNS.
Oct 11 17:22:56 ryzen avahi-daemon[823]: Registering new address record for 192.168.100.1 on virbr1.IPv4.
Oct 11 17:22:56 ryzen NetworkManager[927]: <info> [1697070176.6941] device (virbr1): state change: unmanaged -> unavailable (reason 'connection-assumed', sys-iface-state: 'external')
Oct 11 17:22:56 ryzen NetworkManager[927]: <info> [1697070176.6944] device (virbr1): state change: unavailable -> disconnected (reason 'connection-assumed', sys-iface-state: 'external')
Oct 11 17:22:56 ryzen NetworkManager[927]: <info> [1697070176.6947] device (virbr1): Activation: starting connection 'virbr1' (f503e6d9-16ae-49a4-9a64-987713f32cc1)
Oct 11 17:22:56 ryzen NetworkManager[927]: <info> [1697070176.6949] device (virbr1): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'external')
Oct 11 17:22:56 ryzen NetworkManager[927]: <info> [1697070176.6951] device (virbr1): state change: prepare -> config (reason 'none', sys-iface-state: 'external')
Oct 11 17:22:56 ryzen NetworkManager[927]: <info> [1697070176.6952] device (virbr1): state change: config -> ip-config (reason 'none', sys-iface-state: 'external')
Oct 11 17:22:56 ryzen NetworkManager[927]: <info> [1697070176.6953] device (virbr1): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'external')
Oct 11 17:22:56 ryzen NetworkManager[927]: <info> [1697070176.6959] device (virbr1): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'external')
Oct 11 17:22:56 ryzen NetworkManager[927]: <info> [1697070176.6959] device (virbr1): state change: secondaries -> activated (reason 'none', sys-iface-state: 'external')
Oct 11 17:22:56 ryzen NetworkManager[927]: <info> [1697070176.6961] manager: NetworkManager state is now CONNECTED_LOCAL
Oct 11 17:22:56 ryzen NetworkManager[927]: <info> [1697070176.6962] device (virbr1): Activation: successful, device activated.
Oct 11 17:22:56 ryzen systemd[1]: Starting Manage, Install and Generate Color Profiles...
Oct 11 17:22:56 ryzen dnsmasq[1056]: started, version 2.89 cachesize 150
Oct 11 17:22:56 ryzen dnsmasq[1056]: compile time options: IPv6 GNU-getopt DBus no-UBus i18n IDN2 DHCP DHCPv6 no-Lua TFTP conntrack ipset nftset auth cryptohash DNSSEC loop-detect inotify dumpfile
Oct 11 17:22:56 ryzen dnsmasq-dhcp[1056]: DHCP, IP range 192.168.100.128 -- 192.168.100.128, lease time 1h
Oct 11 17:22:56 ryzen dnsmasq-dhcp[1056]: DHCP, sockets bound exclusively to interface virbr1
Oct 11 17:22:56 ryzen dnsmasq[1056]: reading /etc/resolv.conf
Oct 11 17:22:56 ryzen dnsmasq[1056]: using nameserver 1.1.1.1#53
Oct 11 17:22:56 ryzen dnsmasq[1056]: using nameserver 8.8.8.8#53
Oct 11 17:22:56 ryzen dnsmasq[1056]: using nameserver fde3:5408:101c::1#53
Oct 11 17:22:56 ryzen NetworkManager[927]: <info> [1697070176.7416] manager: (virbr0): new Bridge device (/org/freedesktop/NetworkManager/Devices/4)
Oct 11 17:22:56 ryzen dbus-daemon[824]: [system] Successfully activated service 'org.freedesktop.ColorManager'
Oct 11 17:22:56 ryzen systemd[1]: Started Manage, Install and Generate Color Profiles.
Oct 11 17:22:56 ryzen avahi-daemon[823]: Joining mDNS multicast group on interface virbr0.IPv4 with address 192.168.122.1.
Oct 11 17:22:56 ryzen avahi-daemon[823]: New relevant interface virbr0.IPv4 for mDNS.
Oct 11 17:22:56 ryzen avahi-daemon[823]: Registering new address record for 192.168.122.1 on virbr0.IPv4.
Oct 11 17:22:56 ryzen NetworkManager[927]: <info> [1697070176.7896] device (virbr0): state change: unmanaged -> unavailable (reason 'connection-assumed', sys-iface-state: 'external')
Oct 11 17:22:56 ryzen NetworkManager[927]: <info> [1697070176.7899] device (virbr0): state change: unavailable -> disconnected (reason 'connection-assumed', sys-iface-state: 'external')
Oct 11 17:22:56 ryzen NetworkManager[927]: <info> [1697070176.7903] device (virbr0): Activation: starting connection 'virbr0' (831f68af-6557-427f-b56a-e0457ff51d83)
Oct 11 17:22:56 ryzen NetworkManager[927]: <info> [1697070176.7905] device (virbr0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'external')
Oct 11 17:22:56 ryzen NetworkManager[927]: <info> [1697070176.7907] device (virbr0): state change: prepare -> config (reason 'none', sys-iface-state: 'external')
Oct 11 17:22:56 ryzen NetworkManager[927]: <info> [1697070176.7908] device (virbr0): state change: config -> ip-config (reason 'none', sys-iface-state: 'external')
Oct 11 17:22:56 ryzen NetworkManager[927]: <info> [1697070176.7908] device (virbr0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'external')
Oct 11 17:22:56 ryzen NetworkManager[927]: <info> [1697070176.7915] device (virbr0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'external')
Oct 11 17:22:56 ryzen NetworkManager[927]: <info> [1697070176.7915] device (virbr0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'external')
Oct 11 17:22:56 ryzen NetworkManager[927]: <info> [1697070176.7918] device (virbr0): Activation: successful, device activated.
Oct 11 17:22:56 ryzen dnsmasq[1089]: started, version 2.89 cachesize 150
Oct 11 17:22:56 ryzen dnsmasq[1089]: compile time options: IPv6 GNU-getopt DBus no-UBus i18n IDN2 DHCP DHCPv6 no-Lua TFTP conntrack ipset nftset auth cryptohash DNSSEC loop-detect inotify dumpfile
Oct 11 17:22:56 ryzen dnsmasq-dhcp[1089]: DHCP, IP range 192.168.122.2 -- 192.168.122.254, lease time 1h
Oct 11 17:22:56 ryzen dnsmasq-dhcp[1089]: DHCP, sockets bound exclusively to interface virbr0
Oct 11 17:22:56 ryzen dnsmasq[1089]: reading /etc/resolv.conf
Oct 11 17:22:56 ryzen dnsmasq[1089]: using nameserver 1.1.1.1#53
Oct 11 17:22:56 ryzen dnsmasq[1089]: using nameserver 8.8.8.8#53
Oct 11 17:22:56 ryzen dnsmasq[1089]: using nameserver fde3:5408:101c::1#53
Oct 11 17:22:56 ryzen systemd[1]: Started CUPS Scheduler.
Oct 11 17:22:57 ryzen libvirtd[962]: libvirt version: 9.7.0
Oct 11 17:22:57 ryzen libvirtd[962]: hostname: ryzen
Oct 11 17:22:57 ryzen libvirtd[962]: Unable to open /dev/kvm: No such file or directory
Oct 11 17:22:57 ryzen kernel: qemu-system-x86[1112]: memfd_create() called without MFD_EXEC or MFD_NOEXEC_SEAL set
Oct 11 17:22:57 ryzen dnsmasq[1056]: read /etc/hosts - 384777 names
Oct 11 17:22:57 ryzen dnsmasq[1056]: read /var/lib/libvirt/dnsmasq/virus.addnhosts - 0 names
Oct 11 17:22:57 ryzen dnsmasq-dhcp[1056]: read /var/lib/libvirt/dnsmasq/virus.hostsfile
Oct 11 17:22:57 ryzen dnsmasq[1089]: read /etc/hosts - 384764 names
Oct 11 17:22:57 ryzen dnsmasq[1089]: read /var/lib/libvirt/dnsmasq/default.addnhosts - 0 names
Oct 11 17:22:57 ryzen dnsmasq-dhcp[1089]: read /var/lib/libvirt/dnsmasq/default.hostsfile
Oct 11 17:22:57 ryzen avahi-daemon[823]: Server startup complete. Host name is ryzen.local. Local service cookie is 2748090400.
Oct 11 17:22:57 ryzen sddm[995]: Setting default cursor
Oct 11 17:22:57 ryzen sddm[995]: Running display setup script "/usr/share/sddm/scripts/Xsetup"
Oct 11 17:22:57 ryzen sddm[995]: Display server started.
Oct 11 17:22:57 ryzen sddm[995]: Socket server starting...
Oct 11 17:22:57 ryzen sddm[995]: Socket server started.
Oct 11 17:22:57 ryzen sddm[995]: Loading theme configuration from "/usr/share/sddm/themes/breeze/theme.conf"
Oct 11 17:22:57 ryzen sddm[995]: Greeter starting...
Oct 11 17:22:57 ryzen sddm-helper[1126]: [PAM] Starting...
Oct 11 17:22:57 ryzen sddm-helper[1126]: [PAM] Authenticating...
Oct 11 17:22:57 ryzen sddm-helper[1126]: [PAM] returning.
Oct 11 17:22:57 ryzen sddm-helper[1126]: pam_unix(sddm-greeter:session): session opened for user sddm(uid=974) by (uid=0)
Oct 11 17:22:57 ryzen systemd[1]: Created slice User Slice of UID 974.
Oct 11 17:22:57 ryzen systemd[1]: Starting User Runtime Directory /run/user/974...
Oct 11 17:22:57 ryzen systemd-logind[830]: New session c1 of user sddm.
Oct 11 17:22:57 ryzen systemd[1]: Finished User Runtime Directory /run/user/974.
Oct 11 17:22:57 ryzen systemd[1]: Starting User Manager for UID 974...
Oct 11 17:22:57 ryzen dbus-daemon[824]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.19' (uid=0 pid=1129 comm="(systemd)")
Oct 11 17:22:57 ryzen dbus-daemon[824]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.
Oct 11 17:22:57 ryzen (systemd)[1129]: pam_warn(systemd-user:setcred): function=[pam_sm_setcred] flags=0x8002 service=[systemd-user] terminal=[] user=[sddm] ruser=[<unknown>] rhost=[<unknown>]
Oct 11 17:22:57 ryzen (systemd)[1129]: pam_unix(systemd-user:session): session opened for user sddm(uid=974) by sddm(uid=0)
Oct 11 17:22:58 ryzen systemd[1129]: Queued start job for default target Main User Target.
Oct 11 17:22:58 ryzen systemd[1129]: Created slice User Application Slice.
Oct 11 17:22:58 ryzen systemd[1129]: Reached target Paths.
Oct 11 17:22:58 ryzen systemd[1129]: Reached target Timers.
Oct 11 17:22:58 ryzen systemd[1129]: Starting D-Bus User Message Bus Socket...
Oct 11 17:22:58 ryzen systemd[1129]: Listening on GnuPG network certificate management daemon.
Oct 11 17:22:58 ryzen systemd[1129]: Listening on GCR ssh-agent wrapper.
Oct 11 17:22:58 ryzen systemd[1129]: Listening on GNOME Keyring daemon.
Oct 11 17:22:58 ryzen systemd[1129]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers).
Oct 11 17:22:58 ryzen systemd[1129]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
Oct 11 17:22:58 ryzen systemd[1129]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
Oct 11 17:22:58 ryzen systemd[1129]: Listening on GnuPG cryptographic agent and passphrase cache.
Oct 11 17:22:58 ryzen systemd[1129]: Listening on p11-kit server.
Oct 11 17:22:58 ryzen systemd[1129]: Listening on PipeWire PulseAudio.
Oct 11 17:22:58 ryzen systemd[1129]: Listening on PipeWire Multimedia System Socket.
Oct 11 17:22:58 ryzen systemd[1129]: Listening on File watching service socket.
Oct 11 17:22:58 ryzen systemd[1129]: Listening on D-Bus User Message Bus Socket.
Oct 11 17:22:58 ryzen systemd[1129]: Reached target Sockets.
Oct 11 17:22:58 ryzen systemd[1129]: Reached target Basic System.
Oct 11 17:22:58 ryzen systemd[1]: Started User Manager for UID 974.
Oct 11 17:22:58 ryzen systemd[1129]: Starting Update XDG user dir configuration...
Oct 11 17:22:58 ryzen systemd[1129]: Finished Update XDG user dir configuration.
Oct 11 17:22:58 ryzen systemd[1129]: Reached target Main User Target.
Oct 11 17:22:58 ryzen systemd[1129]: Startup finished in 175ms.
Oct 11 17:22:58 ryzen systemd[1]: Started Session c1 of User sddm.
Oct 11 17:22:58 ryzen sddm-helper[1126]: Writing cookie to "/tmp/xauth_efvEjq"
Oct 11 17:22:58 ryzen sddm-helper[1126]: Starting X11 session: "" "/usr/bin/sddm-greeter --socket /tmp/sddm-:0-uGkStQ --theme /usr/share/sddm/themes/breeze"
Oct 11 17:22:58 ryzen sddm[995]: Greeter session started successfully
Oct 11 17:22:58 ryzen sddm-greeter[1146]: High-DPI autoscaling Enabled
Oct 11 17:22:58 ryzen sddm-greeter[1146]: Reading from "/usr/local/share/wayland-sessions/gnome-classic-wayland.desktop"
Oct 11 17:22:58 ryzen sddm-greeter[1146]: Reading from "/usr/share/wayland-sessions/gnome-classic-wayland.desktop"
Oct 11 17:22:58 ryzen sddm-greeter[1146]: Reading from "/usr/local/share/wayland-sessions/gnome-classic.desktop"
Oct 11 17:22:58 ryzen sddm-greeter[1146]: Reading from "/usr/share/wayland-sessions/gnome-classic.desktop"
Oct 11 17:22:58 ryzen sddm-greeter[1146]: Reading from "/usr/local/share/wayland-sessions/gnome-wayland.desktop"
Oct 11 17:22:58 ryzen sddm-greeter[1146]: Reading from "/usr/share/wayland-sessions/gnome-wayland.desktop"
Oct 11 17:22:58 ryzen sddm-greeter[1146]: Reading from "/usr/local/share/wayland-sessions/gnome.desktop"
Oct 11 17:22:58 ryzen sddm-greeter[1146]: Reading from "/usr/share/wayland-sessions/gnome.desktop"
Oct 11 17:22:58 ryzen sddm-greeter[1146]: Reading from "/usr/local/share/wayland-sessions/hyprland.desktop"
Oct 11 17:22:58 ryzen sddm-greeter[1146]: Reading from "/usr/share/wayland-sessions/hyprland.desktop"
Oct 11 17:22:58 ryzen sddm-greeter[1146]: Reading from "/usr/local/share/wayland-sessions/plasmawayland.desktop"
Oct 11 17:22:58 ryzen sddm-greeter[1146]: Reading from "/usr/share/wayland-sessions/plasmawayland.desktop"
Oct 11 17:22:58 ryzen sddm-greeter[1146]: Reading from "/usr/local/share/wayland-sessions/river.desktop"
Oct 11 17:22:58 ryzen sddm-greeter[1146]: Reading from "/usr/share/wayland-sessions/river.desktop"
Oct 11 17:22:58 ryzen sddm-greeter[1146]: Reading from "/usr/local/share/wayland-sessions/weston.desktop"
Oct 11 17:22:58 ryzen sddm-greeter[1146]: Reading from "/usr/share/wayland-sessions/weston.desktop"
Oct 11 17:22:58 ryzen sddm-greeter[1146]: Reading from "/usr/local/share/xsessions/fluxbox.desktop"
Oct 11 17:22:58 ryzen sddm-greeter[1146]: Reading from "/usr/share/xsessions/fluxbox.desktop"
Oct 11 17:22:58 ryzen sddm-greeter[1146]: Reading from "/usr/local/share/xsessions/gnome-classic-xorg.desktop"
Oct 11 17:22:58 ryzen sddm-greeter[1146]: Reading from "/usr/share/xsessions/gnome-classic-xorg.desktop"
Oct 11 17:22:58 ryzen sddm-greeter[1146]: Reading from "/usr/local/share/xsessions/gnome-classic.desktop"
Oct 11 17:22:58 ryzen sddm-greeter[1146]: Reading from "/usr/share/xsessions/gnome-classic.desktop"
Oct 11 17:22:58 ryzen sddm-greeter[1146]: Reading from "/usr/local/share/xsessions/gnome-xorg.desktop"
Oct 11 17:22:58 ryzen sddm-greeter[1146]: Reading from "/usr/share/xsessions/gnome-xorg.desktop"
Oct 11 17:22:58 ryzen sddm-greeter[1146]: Reading from "/usr/local/share/xsessions/gnome.desktop"
Oct 11 17:22:58 ryzen sddm-greeter[1146]: Reading from "/usr/share/xsessions/gnome.desktop"
Oct 11 17:22:58 ryzen sddm-greeter[1146]: Reading from "/usr/local/share/xsessions/lxqt.desktop"
Oct 11 17:22:58 ryzen sddm-greeter[1146]: Reading from "/usr/share/xsessions/lxqt.desktop"
Oct 11 17:22:58 ryzen sddm-greeter[1146]: Reading from "/usr/local/share/xsessions/openbox-kde.desktop"
Oct 11 17:22:58 ryzen sddm-greeter[1146]: Reading from "/usr/share/xsessions/openbox-kde.desktop"
Oct 11 17:22:58 ryzen sddm-greeter[1146]: Reading from "/usr/local/share/xsessions/openbox.desktop"
Oct 11 17:22:58 ryzen sddm-greeter[1146]: Reading from "/usr/share/xsessions/openbox.desktop"
Oct 11 17:22:58 ryzen sddm-greeter[1146]: Reading from "/usr/local/share/xsessions/plasma.desktop"
Oct 11 17:22:58 ryzen sddm-greeter[1146]: Reading from "/usr/share/xsessions/plasma.desktop"
Oct 11 17:22:58 ryzen sddm-greeter[1146]: Reading from "/usr/local/share/xsessions/xfce.desktop"
Oct 11 17:22:58 ryzen sddm-greeter[1146]: Reading from "/usr/share/xsessions/xfce.desktop"
Oct 11 17:22:58 ryzen sddm-greeter[1146]: Loading theme configuration from "/usr/share/sddm/themes/breeze/theme.conf"
Oct 11 17:22:58 ryzen systemd[1129]: Created slice User Core Session Slice.
Oct 11 17:22:58 ryzen systemd[1129]: Starting D-Bus User Message Bus...
Oct 11 17:22:58 ryzen systemd[1129]: Started D-Bus User Message Bus.
Oct 11 17:22:58 ryzen sddm-greeter[1146]: Connected to the daemon.
Oct 11 17:22:58 ryzen sddm[995]: Message received from greeter: Connect
Oct 11 17:22:58 ryzen sddm-greeter[1146]: Loading file:///usr/share/sddm/themes/breeze/Main.qml...
Oct 11 17:22:58 ryzen sddm-greeter[1146]: QObject: Cannot create children for a parent that is in a different thread.
(Parent is QGuiApplication(0x7ffe3dc8b730), parent's thread is QThread(0x5577b8b779e0), current thread is QThread(0x5577b8fad4b0)
Oct 11 17:22:58 ryzen sddm-greeter[1146]: QObject: Cannot create children for a parent that is in a different thread.
(Parent is QGuiApplication(0x7ffe3dc8b730), parent's thread is QThread(0x5577b8b779e0), current thread is QThread(0x5577b8fad4b0)
Oct 11 17:22:58 ryzen sddm-greeter[1146]: QObject: Cannot create children for a parent that is in a different thread.
(Parent is QGuiApplication(0x7ffe3dc8b730), parent's thread is QThread(0x5577b8b779e0), current thread is QThread(0x5577b8fad4b0)
Oct 11 17:22:58 ryzen sddm-greeter[1146]: QObject::installEventFilter(): Cannot filter events for objects in a different thread.
Oct 11 17:22:58 ryzen dbus-daemon[824]: [system] Activating via systemd: service name='org.freedesktop.PolicyKit1' unit='polkit.service' requested by ':1.2' (uid=0 pid=830 comm="/usr/lib/systemd/systemd-logind")
Oct 11 17:22:58 ryzen dbus-daemon[824]: [system] Activating via systemd: service name='org.freedesktop.UDisks2' unit='udisks2.service' requested by ':1.21' (uid=974 pid=1146 comm="/usr/bin/sddm-greeter --socket /tmp/sddm-:0-uGkStQ")
Oct 11 17:22:58 ryzen systemd[1]: Starting Authorization Manager...
Oct 11 17:22:58 ryzen systemd[1]: Starting Disk Manager...
Oct 11 17:22:58 ryzen udisksd[1160]: udisks daemon version 2.10.1 starting
Oct 11 17:22:58 ryzen polkitd[1159]: Started polkitd version 123
Oct 11 17:22:58 ryzen polkitd[1159]: Loading rules from directory /etc/polkit-1/rules.d
Oct 11 17:22:58 ryzen polkitd[1159]: Loading rules from directory /usr/share/polkit-1/rules.d
Oct 11 17:22:58 ryzen polkitd[1159]: Finished loading, compiling and executing 12 rules
Oct 11 17:22:58 ryzen dbus-daemon[824]: [system] Successfully activated service 'org.freedesktop.PolicyKit1'
Oct 11 17:22:58 ryzen systemd[1]: Started Authorization Manager.
Oct 11 17:22:58 ryzen polkitd[1159]: Acquired the name org.freedesktop.PolicyKit1 on the system bus
Oct 11 17:22:58 ryzen dbus-daemon[824]: [system] Successfully activated service 'org.freedesktop.UDisks2'
Oct 11 17:22:58 ryzen systemd[1]: Started Disk Manager.
Oct 11 17:22:58 ryzen dbus-daemon[824]: [system] Activating via systemd: service name='org.freedesktop.UPower' unit='upower.service' requested by ':1.21' (uid=974 pid=1146 comm="/usr/bin/sddm-greeter --socket /tmp/sddm-:0-uGkStQ")
Oct 11 17:22:58 ryzen udisksd[1160]: Acquired the name org.freedesktop.UDisks2 on the system message bus
Oct 11 17:22:58 ryzen systemd[1]: Starting Daemon for power management...
Oct 11 17:22:58 ryzen NetworkManager[927]: <info> [1697070178.8904] device (enp4s0): carrier: link connected
Oct 11 17:22:58 ryzen NetworkManager[927]: <info> [1697070178.8906] device (enp4s0): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed')
Oct 11 17:22:58 ryzen NetworkManager[927]: <info> [1697070178.8910] policy: auto-activating connection 'Wired connection 1' (1a78b687-138e-3a66-9ca0-dc365ee4d000)
Oct 11 17:22:58 ryzen NetworkManager[927]: <info> [1697070178.8912] device (enp4s0): Activation: starting connection 'Wired connection 1' (1a78b687-138e-3a66-9ca0-dc365ee4d000)
Oct 11 17:22:58 ryzen NetworkManager[927]: <info> [1697070178.8912] device (enp4s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Oct 11 17:22:58 ryzen NetworkManager[927]: <info> [1697070178.8913] manager: NetworkManager state is now CONNECTING
Oct 11 17:22:58 ryzen NetworkManager[927]: <info> [1697070178.8914] device (enp4s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Oct 11 17:22:58 ryzen NetworkManager[927]: <info> [1697070178.8918] device (enp4s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Oct 11 17:22:58 ryzen NetworkManager[927]: <info> [1697070178.8920] dhcp4 (enp4s0): activation: beginning transaction (timeout in 45 seconds)
Oct 11 17:22:58 ryzen kernel: r8169 0000:04:00.0 enp4s0: Link is Up - 1Gbps/Full - flow control rx/tx
Oct 11 17:22:58 ryzen dbus-daemon[824]: [system] Activating via systemd: service name='org.freedesktop.resolve1' unit='dbus-org.freedesktop.resolve1.service' requested by ':1.4' (uid=0 pid=927 comm="/usr/bin/NetworkManager --no-daemon")
Oct 11 17:22:58 ryzen dbus-daemon[824]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.resolve1.service': Unit dbus-org.freedesktop.resolve1.service not found.
Oct 11 17:22:58 ryzen dnsmasq[1089]: reading /etc/resolv.conf
Oct 11 17:22:58 ryzen dnsmasq[1056]: reading /etc/resolv.conf
Oct 11 17:22:58 ryzen dnsmasq[1089]: using nameserver 1.1.1.1#53
Oct 11 17:22:58 ryzen dnsmasq[1056]: using nameserver 1.1.1.1#53
Oct 11 17:22:58 ryzen NetworkManager[927]: <info> [1697070178.8991] dhcp4 (enp4s0): state changed new lease, address=192.168.0.91
Oct 11 17:22:58 ryzen NetworkManager[927]: <info> [1697070178.8993] policy: set 'Wired connection 1' (enp4s0) as default for IPv4 routing and DNS
Oct 11 17:22:58 ryzen dnsmasq[1089]: reading /etc/resolv.conf
Oct 11 17:22:58 ryzen dnsmasq[1056]: reading /etc/resolv.conf
Oct 11 17:22:58 ryzen dnsmasq[1056]: using nameserver 1.1.1.1#53
Oct 11 17:22:58 ryzen dnsmasq[1089]: using nameserver 1.1.1.1#53
Oct 11 17:22:58 ryzen dnsmasq[1056]: using nameserver 8.8.8.8#53
Oct 11 17:22:58 ryzen dnsmasq[1089]: using nameserver 8.8.8.8#53
Oct 11 17:22:58 ryzen avahi-daemon[823]: Joining mDNS multicast group on interface enp4s0.IPv4 with address 192.168.0.91.
Oct 11 17:22:58 ryzen avahi-daemon[823]: New relevant interface enp4s0.IPv4 for mDNS.
Oct 11 17:22:58 ryzen avahi-daemon[823]: Registering new address record for 192.168.0.91 on enp4s0.IPv4.
Oct 11 17:22:58 ryzen avahi-daemon[823]: Joining mDNS multicast group on interface enp4s0.IPv6 with address fe80::1b36:1dd4:a5cf:3b8f.
Oct 11 17:22:58 ryzen avahi-daemon[823]: New relevant interface enp4s0.IPv6 for mDNS.
Oct 11 17:22:58 ryzen avahi-daemon[823]: Registering new address record for fe80::1b36:1dd4:a5cf:3b8f on enp4s0.*.
Oct 11 17:22:58 ryzen NetworkManager[927]: <info> [1697070178.9119] device (enp4s0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Oct 11 17:22:58 ryzen NetworkManager[927]: <info> [1697070178.9126] device (enp4s0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Oct 11 17:22:58 ryzen NetworkManager[927]: <info> [1697070178.9126] device (enp4s0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Oct 11 17:22:58 ryzen NetworkManager[927]: <info> [1697070178.9128] manager: NetworkManager state is now CONNECTED_SITE
Oct 11 17:22:58 ryzen NetworkManager[927]: <info> [1697070178.9129] device (enp4s0): Activation: successful, device activated.
Oct 11 17:22:58 ryzen NetworkManager[927]: <info> [1697070178.9132] manager: startup complete
Oct 11 17:22:58 ryzen dbus-daemon[824]: [system] Successfully activated service 'org.freedesktop.UPower'
Oct 11 17:22:58 ryzen systemd[1]: Finished Network Manager Wait Online.
Oct 11 17:22:58 ryzen systemd[1]: Started Daemon for power management.
Oct 11 17:22:58 ryzen systemd[1]: Reached target Network is Online.
Oct 11 17:22:59 ryzen sddm-greeter[1146]: Failed to find a Kirigami platform plugin
Oct 11 17:22:59 ryzen systemd[1]: Starting Samba SMB Daemon...
Oct 11 17:22:59 ryzen sddm-greeter[1146]: file:///usr/share/sddm/themes/breeze/components/VirtualKeyboard.qml:8:1: module "QtQuick.VirtualKeyboard" is not installed
Oct 11 17:22:59 ryzen smbd[1200]: [2023/10/11 17:22:59.116809, 0] ../../source3/smbd/server.c:1746(main)
Oct 11 17:22:59 ryzen smbd[1200]: smbd version 4.19.0 started.
Oct 11 17:22:59 ryzen smbd[1200]: Copyright Andrew Tridgell and the Samba Team 1992-2023
Oct 11 17:22:59 ryzen systemd[1]: Started Samba SMB Daemon.
Oct 11 17:22:59 ryzen systemd[1]: Reached target Multi-User System.
Oct 11 17:22:59 ryzen systemd[1]: Reached target Graphical Interface.
Oct 11 17:22:59 ryzen sddm-greeter[1146]: Adding view for "DP-1" QRect(0,0 2560x1440)
Oct 11 17:22:59 ryzen sddm-greeter[1146]: Loading file:///usr/share/sddm/themes/breeze/Main.qml...
Oct 11 17:22:59 ryzen sddm-greeter[1146]: QQmlEngine::setContextForObject(): Object already has a QQmlContext
Oct 11 17:22:59 ryzen sddm-greeter[1146]: QQmlEngine::setContextForObject(): Object already has a QQmlContext
Oct 11 17:22:59 ryzen sddm-greeter[1146]: Failed to find a Kirigami platform plugin
Oct 11 17:22:59 ryzen sddm-greeter[1146]: file:///usr/share/sddm/themes/breeze/components/VirtualKeyboard.qml:8:1: module "QtQuick.VirtualKeyboard" is not installed
Oct 11 17:22:59 ryzen NetworkManager[927]: <info> [1697070179.2942] manager: NetworkManager state is now CONNECTED_GLOBAL
Oct 11 17:22:59 ryzen sddm-greeter[1146]: Adding view for "DVI-D-1" QRect(2560,0 1920x1080)
Oct 11 17:22:59 ryzen sddm-greeter[1146]: QDBusConnection: name 'org.freedesktop.UDisks2' had owner '' but we thought it was ':1.22'
Oct 11 17:22:59 ryzen sddm-greeter[1146]: QDBusConnection: name 'org.freedesktop.UPower' had owner '' but we thought it was ':1.24'
Oct 11 17:22:59 ryzen sddm-greeter[1146]: Message received from daemon: Capabilities
Oct 11 17:22:59 ryzen sddm-greeter[1146]: Message received from daemon: HostName
Oct 11 17:23:01 ryzen NetworkManager[927]: <info> [1697070181.0456] dhcp6 (enp4s0): activation: beginning transaction (timeout in 45 seconds)
Oct 11 17:23:01 ryzen dnsmasq[1056]: reading /etc/resolv.conf
Oct 11 17:23:01 ryzen dnsmasq[1089]: reading /etc/resolv.conf
Oct 11 17:23:01 ryzen dnsmasq[1056]: using nameserver 1.1.1.1#53
Oct 11 17:23:01 ryzen dnsmasq[1056]: using nameserver 8.8.8.8#53
Oct 11 17:23:01 ryzen dnsmasq[1089]: using nameserver 1.1.1.1#53
Oct 11 17:23:01 ryzen dnsmasq[1056]: using nameserver fde3:5408:101c::1#53
Oct 11 17:23:01 ryzen dnsmasq[1089]: using nameserver 8.8.8.8#53
Oct 11 17:23:01 ryzen dnsmasq[1089]: using nameserver fde3:5408:101c::1#53
Oct 11 17:23:01 ryzen avahi-daemon[823]: Leaving mDNS multicast group on interface enp4s0.IPv6 with address fe80::1b36:1dd4:a5cf:3b8f.
Oct 11 17:23:01 ryzen avahi-daemon[823]: Joining mDNS multicast group on interface enp4s0.IPv6 with address fde3:5408:101c:0:7441:9d56:d3c1:1a95.
Oct 11 17:23:01 ryzen NetworkManager[927]: <info> [1697070181.0526] dhcp6 (enp4s0): state changed new lease, address=fde3:5408:101c::566
Oct 11 17:23:01 ryzen avahi-daemon[823]: Registering new address record for fde3:5408:101c:0:7441:9d56:d3c1:1a95 on enp4s0.*.
Oct 11 17:23:01 ryzen avahi-daemon[823]: Withdrawing address record for fe80::1b36:1dd4:a5cf:3b8f on enp4s0.
Oct 11 17:23:01 ryzen avahi-daemon[823]: Registering new address record for fde3:5408:101c::566 on enp4s0.*.
Oct 11 17:23:01 ryzen bash[826]: + rm -rf /usr/lib/modules/6.5.5-arch1-1
Oct 11 17:23:02 ryzen bash[826]: + for i in /usr/lib/modules/[0-9]*
Oct 11 17:23:02 ryzen bash[826]: + [[ 6.5.6-arch2-1 = \6\.\5\.\6\-\a\r\c\h\2\-\1 ]]
Oct 11 17:23:02 ryzen bash[826]: + continue
Oct 11 17:23:02 ryzen bash[826]: + for i in /usr/lib/modules/[0-9]*
Oct 11 17:23:02 ryzen bash[826]: + [[ 6.5.6-zen2-1-zen = \6\.\5\.\6\-\a\r\c\h\2\-\1 ]]
Oct 11 17:23:02 ryzen bash[826]: + pacman -Qo /usr/lib/modules/6.5.6-zen2-1-zen
Oct 11 17:23:02 ryzen bash[1221]: /usr/lib/modules/6.5.6-zen2-1-zen/ is owned by linux-zen-docs 6.5.6.zen2-1
Oct 11 17:23:02 ryzen bash[1221]: /usr/lib/modules/6.5.6-zen2-1-zen/ is owned by linux-zen-headers 6.5.6.zen2-1
Oct 11 17:23:02 ryzen bash[826]: + continue
Oct 11 17:23:02 ryzen systemd[1]: linux-modules-cleanup.service: Deactivated successfully.
Oct 11 17:23:02 ryzen systemd[1]: Finished Clean up modules from old kernels.
Oct 11 17:23:02 ryzen systemd[1]: Startup finished in 12.324s (firmware) + 6.442s (loader) + 6.537s (kernel) + 12.726s (userspace) = 38.030s.
Oct 11 17:23:02 ryzen systemd[1]: linux-modules-cleanup.service: Consumed 5.747s CPU time.
Oct 11 17:23:06 ryzen systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
Oct 11 17:23:25 ryzen systemd-timesyncd[815]: Contacted time server 18.119.130.247:123 (2.arch.pool.ntp.org).
Oct 11 17:23:25 ryzen systemd-timesyncd[815]: Initial clock synchronization to Wed 2023-10-11 17:23:25.519136 PDT.
Oct 11 17:23:26 ryzen systemd[1]: systemd-hostnamed.service: Deactivated successfully.
Oct 11 17:24:56 ryzen systemd[1]: libvirtd.service: Deactivated successfully.
Oct 11 17:24:56 ryzen systemd[1]: libvirtd.service: Unit process 1056 (dnsmasq) remains running after unit stopped.
Oct 11 17:24:56 ryzen systemd[1]: libvirtd.service: Unit process 1057 (dnsmasq) remains running after unit stopped.
Oct 11 17:24:56 ryzen systemd[1]: libvirtd.service: Unit process 1089 (dnsmasq) remains running after unit stopped.
Oct 11 17:24:56 ryzen systemd[1]: libvirtd.service: Unit process 1090 (dnsmasq) remains running after unit stopped.
Oct 11 17:24:56 ryzen systemd[1]: libvirtd.service: Consumed 1.885s CPU time.
Oct 11 17:25:15 ryzen systemd-timesyncd[815]: Timed out waiting for reply from 18.119.130.247:123 (2.arch.pool.ntp.org).
Oct 11 17:25:15 ryzen systemd-timesyncd[815]: Contacted time server 162.248.241.94:123 (2.arch.pool.ntp.org).
Oct 11 17:25:41 ryzen sddm-greeter[1146]: Reading from "/usr/share/wayland-sessions/plasmawayland.desktop"
Oct 11 17:25:41 ryzen sddm[995]: Message received from greeter: Login
Oct 11 17:25:41 ryzen sddm[995]: Reading from "/usr/share/wayland-sessions/plasmawayland.desktop"
Oct 11 17:25:41 ryzen sddm[995]: Session "/usr/share/wayland-sessions/plasmawayland.desktop" selected, command: "/usr/lib/plasma-dbus-run-session-if-needed /usr/bin/startplasma-wayland" for VT 1
Oct 11 17:25:41 ryzen sddm-helper[1232]: [PAM] Starting...
Oct 11 17:25:41 ryzen sddm-helper[1232]: [PAM] Authenticating...
Oct 11 17:25:41 ryzen dbus-daemon[824]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.26' (uid=0 pid=1232 comm="/usr/lib/sddm/sddm-helper --socket /tmp/sddm-auth-")
Oct 11 17:25:41 ryzen dbus-daemon[824]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.
Oct 11 17:25:41 ryzen sddm-helper[1232]: [PAM] Preparing to converse...
Oct 11 17:25:41 ryzen sddm-helper[1232]: [PAM] Conversation with 1 messages
Oct 11 17:25:41 ryzen sddm-helper[1232]: gkr-pam: unable to locate daemon control file
Oct 11 17:25:41 ryzen sddm-helper[1232]: gkr-pam: stashed password to try later in open session
Oct 11 17:25:41 ryzen sddm-helper[1232]: [PAM] returning.
Oct 11 17:25:41 ryzen sddm-helper[1232]: pam_kwallet5(sddm:auth): pam_kwallet5: pam_sm_authenticate
Oct 11 17:25:41 ryzen sddm[995]: Authentication for user "nyanpasu64" successful
Oct 11 17:25:41 ryzen sddm-helper[1232]: pam_kwallet5(sddm:setcred): pam_kwallet5: pam_sm_setcred
Oct 11 17:25:41 ryzen sddm-helper[1232]: pam_unix(sddm:session): session opened for user nyanpasu64(uid=1001) by nyanpasu64(uid=0)
Oct 11 17:25:41 ryzen systemd[1]: Created slice User Slice of UID 1001.
Oct 11 17:25:41 ryzen sddm-greeter[1146]: Message received from daemon: LoginSucceeded
Oct 11 17:25:41 ryzen systemd[1]: Starting User Runtime Directory /run/user/1001...
Oct 11 17:25:41 ryzen systemd-logind[830]: New session 2 of user nyanpasu64.
Oct 11 17:25:41 ryzen systemd[1]: Finished User Runtime Directory /run/user/1001.
Oct 11 17:25:41 ryzen systemd[1]: Starting User Manager for UID 1001...
Oct 11 17:25:41 ryzen dbus-daemon[824]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.29' (uid=0 pid=1235 comm="(systemd)")
Oct 11 17:25:41 ryzen dbus-daemon[824]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.
Oct 11 17:25:41 ryzen (systemd)[1235]: pam_warn(systemd-user:setcred): function=[pam_sm_setcred] flags=0x8002 service=[systemd-user] terminal=[] user=[nyanpasu64] ruser=[<unknown>] rhost=[<unknown>]
Oct 11 17:25:41 ryzen (systemd)[1235]: pam_unix(systemd-user:session): session opened for user nyanpasu64(uid=1001) by nyanpasu64(uid=0)
Oct 11 17:25:41 ryzen sddm-helper[1126]: [PAM] Closing session
Oct 11 17:25:41 ryzen sddm-helper[1126]: pam_unix(sddm-greeter:session): session closed for user sddm
Oct 11 17:25:41 ryzen sddm-helper[1126]: [PAM] Ended.
Oct 11 17:25:41 ryzen sddm[995]: Auth: sddm-helper exited successfully
Oct 11 17:25:41 ryzen systemd[1]: session-c1.scope: Deactivated successfully.
Oct 11 17:25:41 ryzen sddm[995]: Greeter stopped. SDDM::Auth::HELPER_SUCCESS
Oct 11 17:25:41 ryzen systemd[1]: session-c1.scope: Consumed 1.241s CPU time.
Oct 11 17:25:41 ryzen systemd-logind[830]: Session c1 logged out. Waiting for processes to exit.
Oct 11 17:25:41 ryzen systemd-logind[830]: Removed session c1.
Oct 11 17:25:41 ryzen systemd-journald[309]: /var/log/journal/be541a4ba238441eb205e6279170129b/user-1001.journal: Journal file uses a different sequence number ID, rotating.
Oct 11 17:25:41 ryzen sddm-helper[1232]: gkr-pam: unlocked login keyring
Oct 11 17:25:41 ryzen sddm-helper[1232]: pam_kwallet5(sddm:session): pam_kwallet5: pam_sm_open_session
Oct 11 17:25:41 ryzen systemd[1]: Started User Manager for UID 1001.
Oct 11 17:25:41 ryzen systemd[1]: Started Session 2 of User nyanpasu64.
Oct 11 17:25:41 ryzen sddm-helper[1232]: Starting Wayland user session: "/usr/share/sddm/scripts/wayland-session" "/usr/lib/plasma-dbus-run-session-if-needed /usr/bin/startplasma-wayland"
Oct 11 17:25:41 ryzen sddm-helper[1281]: Jumping to VT 1
Oct 11 17:25:41 ryzen sddm-helper[1281]: VT mode didn't need to be fixed
Oct 11 17:25:41 ryzen sddm[995]: Session started true
Oct 11 17:25:42 ryzen dbus-daemon[824]: [system] Activating via systemd: service name='org.freedesktop.locale1' unit='dbus-org.freedesktop.locale1.service' requested by ':1.33' (uid=1001 pid=1281 comm="/usr/bin/startplasma-wayland")
Oct 11 17:25:42 ryzen systemd[1]: Starting Locale Service...
Oct 11 17:25:42 ryzen dbus-daemon[824]: [system] Successfully activated service 'org.freedesktop.locale1'
Oct 11 17:25:42 ryzen systemd[1]: Started Locale Service.
Oct 11 17:25:42 ryzen systemd-udevd[364]: /etc/udev/rules.d/30-usbtmc.rules:5 Unknown group 'usbtmc', ignoring.
Oct 11 17:25:42 ryzen systemd-udevd[364]: /etc/udev/rules.d/30-usbtmc.rules:8 Unknown group 'usbtmc', ignoring.
Oct 11 17:25:42 ryzen systemd-udevd[364]: /etc/udev/rules.d/30-usbtmc.rules:11 Unknown group 'usbtmc', ignoring.
Oct 11 17:25:42 ryzen systemd-udevd[364]: /etc/udev/rules.d/30-usbtmc.rules:14 Unknown group 'usbtmc', ignoring.
Oct 11 17:25:42 ryzen systemd-udevd[364]: /etc/udev/rules.d/30-usbtmc.rules:15 Unknown group 'usbtmc', ignoring.
Oct 11 17:25:42 ryzen systemd-udevd[364]: /usr/lib/udev/rules.d/51-footcontroller.rules:10 Invalid value for OPTIONS key, ignoring: 'last_rule'
Oct 11 17:25:42 ryzen dbus-daemon[824]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.36' (uid=1001 pid=1340 comm="/usr/lib/xdg-desktop-portal")
Oct 11 17:25:42 ryzen systemd[1]: Starting RealtimeKit Scheduling Policy Service...
Oct 11 17:25:42 ryzen dbus-daemon[824]: [system] Successfully activated service 'org.freedesktop.RealtimeKit1'
Oct 11 17:25:42 ryzen systemd[1]: Started RealtimeKit Scheduling Policy Service.
Oct 11 17:25:42 ryzen rtkit-daemon[1365]: Successfully called chroot.
Oct 11 17:25:42 ryzen rtkit-daemon[1365]: Successfully dropped privileges.
Oct 11 17:25:42 ryzen rtkit-daemon[1365]: Successfully limited resources.
Oct 11 17:25:42 ryzen rtkit-daemon[1365]: Canary thread running.
Oct 11 17:25:42 ryzen rtkit-daemon[1365]: Running.
Oct 11 17:25:42 ryzen rtkit-daemon[1365]: Watchdog thread running.
Oct 11 17:25:42 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 17:25:42 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 17:25:42 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 17:25:43 ryzen dbus-daemon[824]: [system] Activating service name='org.kde.powerdevil.discretegpuhelper' requested by ':1.40' (uid=1001 pid=1520 comm="/usr/lib/org_kde_powerdevil") (using servicehelper)
Oct 11 17:25:43 ryzen dbus-daemon[824]: [system] Successfully activated service 'org.kde.powerdevil.discretegpuhelper'
Oct 11 17:25:43 ryzen dbus-daemon[824]: [system] Activating service name='org.kde.powerdevil.chargethresholdhelper' requested by ':1.40' (uid=1001 pid=1520 comm="/usr/lib/org_kde_powerdevil") (using servicehelper)
Oct 11 17:25:43 ryzen dbus-daemon[824]: [system] Successfully activated service 'org.kde.powerdevil.chargethresholdhelper'
Oct 11 17:25:43 ryzen dbus-daemon[824]: [system] Activating service name='org.kde.powerdevil.backlighthelper' requested by ':1.40' (uid=1001 pid=1520 comm="/usr/lib/org_kde_powerdevil") (using servicehelper)
Oct 11 17:25:43 ryzen backlighthelper[1575]: org.kde.powerdevil: no kernel backlight interface found
Oct 11 17:25:43 ryzen dbus-daemon[824]: [system] Successfully activated service 'org.kde.powerdevil.backlighthelper'
Oct 11 17:25:44 ryzen polkitd[1159]: Registered Authentication Agent for unix-session:2 (system bus name :1.52 [/usr/lib/polkit-kde-authentication-agent-1], object path /org/kde/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8)
Oct 11 17:25:44 ryzen dbus-daemon[824]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.54' (uid=1001 pid=1566 comm="/usr/bin/ksystemstats")
Oct 11 17:25:44 ryzen systemd[1]: Starting Hostname Service...
Oct 11 17:25:44 ryzen NetworkManager[927]: <info> [1697070344.0945] audit: op="statistics" interface="enp4s0" ifindex=2 args="500" pid=1566 uid=1001 result="success"
Oct 11 17:25:44 ryzen dbus-daemon[824]: [system] Successfully activated service 'org.freedesktop.hostname1'
Oct 11 17:25:44 ryzen systemd[1]: Started Hostname Service.
Oct 11 17:25:44 ryzen dbus-daemon[824]: [system] Activating via systemd: service name='net.hadess.PowerProfiles' unit='power-profiles-daemon.service' requested by ':1.40' (uid=1001 pid=1520 comm="/usr/lib/org_kde_powerdevil")
Oct 11 17:25:44 ryzen systemd[1]: Starting Power Profiles daemon...
Oct 11 17:25:44 ryzen NetworkManager[927]: <info> [1697070344.3508] agent-manager: agent[06269b39b97af5a2,:1.39/org.kde.plasma.networkmanagement/1001]: agent registered
Oct 11 17:25:44 ryzen dbus-daemon[824]: [system] Successfully activated service 'net.hadess.PowerProfiles'
Oct 11 17:25:44 ryzen systemd[1]: Started Power Profiles daemon.
Oct 11 17:25:44 ryzen dbus-daemon[824]: [system] Activating via systemd: service name='org.freedesktop.ModemManager1' unit='dbus-org.freedesktop.ModemManager1.service' requested by ':1.39' (uid=1001 pid=1448 comm="/usr/bin/kded5")
Oct 11 17:25:44 ryzen dbus-daemon[824]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.ModemManager1.service': Unit dbus-org.freedesktop.ModemManager1.service not found.
Oct 11 17:25:44 ryzen dbus-daemon[824]: [system] Activating via systemd: service name='org.freedesktop.ModemManager1' unit='dbus-org.freedesktop.ModemManager1.service' requested by ':1.39' (uid=1001 pid=1448 comm="/usr/bin/kded5")
Oct 11 17:25:44 ryzen dbus-daemon[824]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.ModemManager1.service': Unit dbus-org.freedesktop.ModemManager1.service not found.
Oct 11 17:25:44 ryzen dbus-daemon[824]: [system] Activating service name='org.kde.kded.smart' requested by ':1.39' (uid=1001 pid=1448 comm="/usr/bin/kded5") (using servicehelper)
Oct 11 17:25:44 ryzen dbus-daemon[824]: [system] Successfully activated service 'org.kde.kded.smart'
Oct 11 17:25:44 ryzen dbus-daemon[824]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.39' (uid=1001 pid=1448 comm="/usr/bin/kded5")
Oct 11 17:25:44 ryzen systemd[1]: Bluetooth service was skipped because of an unmet condition check (ConditionPathIsDirectory=/sys/class/bluetooth).
Oct 11 17:25:44 ryzen dbus-daemon[824]: [system] Activating via systemd: service name='org.freedesktop.PackageKit' unit='packagekit.service' requested by ':1.67' (uid=1001 pid=1804 comm="/usr/lib/DiscoverNotifier")
Oct 11 17:25:44 ryzen systemd[1]: Starting PackageKit Daemon...
Oct 11 17:25:44 ryzen PackageKit[1897]: daemon start
Oct 11 17:25:44 ryzen dbus-daemon[824]: [system] Successfully activated service 'org.freedesktop.PackageKit'
Oct 11 17:25:44 ryzen systemd[1]: Started PackageKit Daemon.
Oct 11 17:25:44 ryzen dbus-daemon[824]: [system] Activating via systemd: service name='org.freedesktop.ModemManager1' unit='dbus-org.freedesktop.ModemManager1.service' requested by ':1.65' (uid=1001 pid=1769 comm="/usr/lib/kdeconnectd")
Oct 11 17:25:44 ryzen dbus-daemon[824]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.ModemManager1.service': Unit dbus-org.freedesktop.ModemManager1.service not found.
Oct 11 17:25:44 ryzen dbus-daemon[824]: [system] Activating via systemd: service name='org.freedesktop.ModemManager1' unit='dbus-org.freedesktop.ModemManager1.service' requested by ':1.65' (uid=1001 pid=1769 comm="/usr/lib/kdeconnectd")
Oct 11 17:25:44 ryzen dbus-daemon[824]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.ModemManager1.service': Unit dbus-org.freedesktop.ModemManager1.service not found.
Oct 11 17:25:45 ryzen PackageKit[1897]: get-updates transaction /1_cecdebcb from uid 1001 finished with success after 104ms
Oct 11 17:25:45 ryzen PackageKit[1897]: get-updates transaction /2_ecccdbda from uid 1001 finished with success after 2ms
Oct 11 17:25:47 ryzen dbus-daemon[824]: [system] Activating via systemd: service name='org.freedesktop.Accounts' unit='accounts-daemon.service' requested by ':1.78' (uid=1001 pid=1804 comm="/usr/lib/DiscoverNotifier")
Oct 11 17:25:47 ryzen systemd[1]: Reached target User and Group Name Lookups.
Oct 11 17:25:47 ryzen systemd[1]: Starting Accounts Service...
Oct 11 17:25:47 ryzen accounts-daemon[2405]: started daemon version 23.13.0
Oct 11 17:25:47 ryzen dbus-daemon[824]: [system] Successfully activated service 'org.freedesktop.Accounts'
Oct 11 17:25:47 ryzen systemd[1]: Started Accounts Service.
Oct 11 17:25:47 ryzen dbus-daemon[824]: [system] Activating via systemd: service name='org.freedesktop.Flatpak.SystemHelper' unit='flatpak-system-helper.service' requested by ':1.78' (uid=1001 pid=1804 comm="/usr/lib/DiscoverNotifier")
Oct 11 17:25:47 ryzen systemd[1]: Starting flatpak system helper...
Oct 11 17:25:47 ryzen dbus-daemon[824]: [system] Successfully activated service 'org.freedesktop.Flatpak.SystemHelper'
Oct 11 17:25:47 ryzen systemd[1]: Started flatpak system helper.
Oct 11 17:25:51 ryzen systemd[1]: Stopping User Manager for UID 974...
Oct 11 17:25:51 ryzen systemd[1129]: Activating special unit Exit the Session...
Oct 11 17:25:51 ryzen systemd[1129]: Stopped target Main User Target.
Oct 11 17:25:51 ryzen systemd[1129]: Stopping D-Bus User Message Bus...
Oct 11 17:25:51 ryzen systemd[1129]: Stopped D-Bus User Message Bus.
Oct 11 17:25:51 ryzen systemd[1129]: Removed slice User Core Session Slice.
Oct 11 17:25:51 ryzen systemd[1129]: Stopped target Basic System.
Oct 11 17:25:51 ryzen systemd[1129]: Stopped target Paths.
Oct 11 17:25:51 ryzen systemd[1129]: Stopped target Sockets.
Oct 11 17:25:51 ryzen systemd[1129]: Stopped target Timers.
Oct 11 17:25:51 ryzen systemd[1129]: Closed D-Bus User Message Bus Socket.
Oct 11 17:25:51 ryzen systemd[1129]: Closed GnuPG network certificate management daemon.
Oct 11 17:25:51 ryzen systemd[1129]: Closed GCR ssh-agent wrapper.
Oct 11 17:25:51 ryzen systemd[1129]: Closed GNOME Keyring daemon.
Oct 11 17:25:51 ryzen systemd[1129]: Closed GnuPG cryptographic agent and passphrase cache (access for web browsers).
Oct 11 17:25:51 ryzen systemd[1129]: Closed GnuPG cryptographic agent and passphrase cache (restricted).
Oct 11 17:25:51 ryzen systemd[1129]: Closed GnuPG cryptographic agent (ssh-agent emulation).
Oct 11 17:25:51 ryzen systemd[1129]: Closed GnuPG cryptographic agent and passphrase cache.
Oct 11 17:25:51 ryzen systemd[1129]: Closed p11-kit server.
Oct 11 17:25:51 ryzen systemd[1129]: Closed PipeWire PulseAudio.
Oct 11 17:25:51 ryzen systemd[1129]: Closed PipeWire Multimedia System Socket.
Oct 11 17:25:51 ryzen systemd[1129]: Closed File watching service socket.
Oct 11 17:25:51 ryzen systemd[1129]: Removed slice User Application Slice.
Oct 11 17:25:51 ryzen systemd[1129]: Reached target Shutdown.
Oct 11 17:25:51 ryzen systemd[1129]: Finished Exit the Session.
Oct 11 17:25:51 ryzen systemd[1129]: Reached target Exit the Session.
Oct 11 17:25:51 ryzen (sd-pam)[1130]: pam_warn(systemd-user:setcred): function=[pam_sm_setcred] flags=0x8004 service=[systemd-user] terminal=[] user=[sddm] ruser=[<unknown>] rhost=[<unknown>]
Oct 11 17:25:51 ryzen systemd[1]: user@974.service: Deactivated successfully.
Oct 11 17:25:51 ryzen systemd[1]: Stopped User Manager for UID 974.
Oct 11 17:25:51 ryzen systemd[1]: Stopping User Runtime Directory /run/user/974...
Oct 11 17:25:51 ryzen systemd[1]: run-user-974.mount: Deactivated successfully.
Oct 11 17:25:51 ryzen systemd[1]: user-runtime-dir@974.service: Deactivated successfully.
Oct 11 17:25:51 ryzen systemd[1]: Stopped User Runtime Directory /run/user/974.
Oct 11 17:25:51 ryzen systemd[1]: Removed slice User Slice of UID 974.
Oct 11 17:25:51 ryzen systemd[1]: user-974.slice: Consumed 1.394s CPU time.
Oct 11 17:26:04 ryzen dbus-daemon[824]: [system] Activating via systemd: service name='org.freedesktop.timedate1' unit='dbus-org.freedesktop.timedate1.service' requested by ':1.82' (uid=1001 pid=2544 comm="/usr/lib/firefox/firefox")
Oct 11 17:26:04 ryzen systemd[1]: Starting Time & Date Service...
Oct 11 17:26:04 ryzen dbus-daemon[824]: [system] Successfully activated service 'org.freedesktop.timedate1'
Oct 11 17:26:04 ryzen systemd[1]: Started Time & Date Service.
Oct 11 17:26:04 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 17:26:04 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 17:26:04 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 17:26:04 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 17:26:04 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 17:26:04 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 17:26:04 ryzen rtkit-daemon[1365]: Successfully made thread 2699 of process 2544 owned by '1001' RT at priority 10.
Oct 11 17:26:04 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 17:26:05 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 17:26:05 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 17:26:05 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 17:26:05 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 17:26:05 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 17:26:05 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 17:26:05 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 17:26:05 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 17:26:06 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 17:26:06 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 17:26:06 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 17:26:06 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 17:26:06 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 17:26:06 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 17:26:09 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 17:26:09 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 17:26:09 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 17:26:09 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 17:26:09 ryzen dbus-daemon[824]: [system] Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms)
Oct 11 17:26:12 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 17:26:12 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 17:26:14 ryzen systemd[1]: systemd-hostnamed.service: Deactivated successfully.
Oct 11 17:26:17 ryzen systemd[1]: systemd-localed.service: Deactivated successfully.
Oct 11 17:26:34 ryzen systemd[1]: systemd-timedated.service: Deactivated successfully.
Oct 11 17:26:38 ryzen dbus-daemon[824]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.99' (uid=1001 pid=3534 comm="/opt/visual-studio-code/code --unity-launch")
Oct 11 17:26:38 ryzen systemd[1]: Bluetooth service was skipped because of an unmet condition check (ConditionPathIsDirectory=/sys/class/bluetooth).
Oct 11 17:26:43 ryzen systemd-udevd[364]: /etc/udev/rules.d/30-usbtmc.rules:5 Unknown group 'usbtmc', ignoring.
Oct 11 17:26:43 ryzen systemd-udevd[364]: /etc/udev/rules.d/30-usbtmc.rules:8 Unknown group 'usbtmc', ignoring.
Oct 11 17:26:43 ryzen systemd-udevd[364]: /etc/udev/rules.d/30-usbtmc.rules:11 Unknown group 'usbtmc', ignoring.
Oct 11 17:26:43 ryzen systemd-udevd[364]: /etc/udev/rules.d/30-usbtmc.rules:14 Unknown group 'usbtmc', ignoring.
Oct 11 17:26:43 ryzen systemd-udevd[364]: /etc/udev/rules.d/30-usbtmc.rules:15 Unknown group 'usbtmc', ignoring.
Oct 11 17:26:43 ryzen systemd-udevd[364]: /usr/lib/udev/rules.d/51-footcontroller.rules:10 Invalid value for OPTIONS key, ignoring: 'last_rule'
Oct 11 17:26:44 ryzen systemd[1]: tmp-.mount_kotato5wvEAm.mount: Deactivated successfully.
Oct 11 17:27:03 ryzen dbus-daemon[824]: [system] Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms)
Oct 11 17:27:33 ryzen kernel: usb 1-7: input irq status -75 received
Oct 11 17:27:33 ryzen kernel: usb 1-7: input irq status -75 received
Oct 11 17:27:35 ryzen dbus-daemon[824]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.104' (uid=0 pid=4267 comm="sudo sh -c unswap-perl & pid=$! ; swapoff -a ; swa")
Oct 11 17:27:35 ryzen dbus-daemon[824]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.
Oct 11 17:27:39 ryzen systemd[1]: dev-disk-by\x2dpath-pci\x2d0000:01:00.0\x2dnvme\x2d1\x2dpart6.swap: Deactivated successfully.
Oct 11 17:27:39 ryzen kernel: Adding 16777212k swap on /dev/nvme0n1p6. Priority:-2 extents:1 across:16777212k SSFS
Oct 11 17:27:39 ryzen systemd[1]: dev-disk-by\x2did-nvme\x2deui.0025385631900958\x2dpart6.swap: Deactivated successfully.
Oct 11 17:27:39 ryzen systemd[1]: dev-disk-by\x2dpartlabel-Linux\x5cx20Swap.swap: Deactivated successfully.
Oct 11 17:27:39 ryzen systemd[1]: dev-disk-by\x2ddiskseq-3\x2dpart6.swap: Deactivated successfully.
Oct 11 17:27:39 ryzen systemd[1]: dev-disk-by\x2dpartuuid-95091b40\x2d9763\x2ddf42\x2db099\x2d2f9f1584bc28.swap: Deactivated successfully.
Oct 11 17:27:39 ryzen systemd[1]: dev-disk-by\x2did-nvme\x2dSamsung_SSD_970_EVO_Plus_2TB_S59CNM0W601482A\x2dpart6.swap: Deactivated successfully.
Oct 11 17:27:39 ryzen systemd[1]: dev-disk-by\x2did-nvme\x2dSamsung_SSD_970_EVO_Plus_2TB_S59CNM0W601482A_1\x2dpart6.swap: Deactivated successfully.
Oct 11 17:27:39 ryzen systemd[1]: dev-nvme0n1p6.swap: Deactivated successfully.
Oct 11 17:27:39 ryzen systemd[1]: dev-disk-by\x2duuid-52761d05\x2d5222\x2d434a\x2da2a9\x2dd80fc43e7e05.swap: Deactivated successfully.
Oct 11 17:27:40 ryzen systemd-udevd[364]: /etc/udev/rules.d/30-usbtmc.rules:5 Unknown group 'usbtmc', ignoring.
Oct 11 17:27:40 ryzen systemd-udevd[364]: /etc/udev/rules.d/30-usbtmc.rules:8 Unknown group 'usbtmc', ignoring.
Oct 11 17:27:40 ryzen systemd-udevd[364]: /etc/udev/rules.d/30-usbtmc.rules:11 Unknown group 'usbtmc', ignoring.
Oct 11 17:27:40 ryzen systemd-udevd[364]: /etc/udev/rules.d/30-usbtmc.rules:14 Unknown group 'usbtmc', ignoring.
Oct 11 17:27:40 ryzen systemd-udevd[364]: /etc/udev/rules.d/30-usbtmc.rules:15 Unknown group 'usbtmc', ignoring.
Oct 11 17:27:40 ryzen systemd-udevd[364]: /usr/lib/udev/rules.d/51-footcontroller.rules:10 Invalid value for OPTIONS key, ignoring: 'last_rule'
Oct 11 17:27:42 ryzen dbus-daemon[824]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.105' (uid=0 pid=4286 comm="sudo sh -c unswap-perl & pid=$! ; swapoff -a ; swa")
Oct 11 17:27:42 ryzen dbus-daemon[824]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.
Oct 11 17:27:42 ryzen systemd[1]: dev-disk-by\x2did-nvme\x2deui.0025385631900958\x2dpart6.swap: Deactivated successfully.
Oct 11 17:27:42 ryzen kernel: Adding 16777212k swap on /dev/nvme0n1p6. Priority:-2 extents:1 across:16777212k SSFS
Oct 11 17:27:42 ryzen systemd[1]: dev-disk-by\x2dpartuuid-95091b40\x2d9763\x2ddf42\x2db099\x2d2f9f1584bc28.swap: Deactivated successfully.
Oct 11 17:27:42 ryzen systemd[1]: dev-disk-by\x2dpartlabel-Linux\x5cx20Swap.swap: Deactivated successfully.
Oct 11 17:27:43 ryzen systemd[1]: dev-disk-by\x2dpath-pci\x2d0000:01:00.0\x2dnvme\x2d1\x2dpart6.swap: Deactivated successfully.
Oct 11 17:27:43 ryzen systemd[1]: dev-disk-by\x2did-nvme\x2dSamsung_SSD_970_EVO_Plus_2TB_S59CNM0W601482A_1\x2dpart6.swap: Deactivated successfully.
Oct 11 17:27:43 ryzen systemd[1]: dev-disk-by\x2ddiskseq-3\x2dpart6.swap: Deactivated successfully.
Oct 11 17:27:43 ryzen systemd[1]: dev-disk-by\x2did-nvme\x2dSamsung_SSD_970_EVO_Plus_2TB_S59CNM0W601482A\x2dpart6.swap: Deactivated successfully.
Oct 11 17:27:43 ryzen systemd[1]: dev-nvme0n1p6.swap: Deactivated successfully.
Oct 11 17:27:43 ryzen systemd[1]: dev-disk-by\x2duuid-52761d05\x2d5222\x2d434a\x2da2a9\x2dd80fc43e7e05.swap: Deactivated successfully.
Oct 11 17:27:43 ryzen systemd-udevd[364]: /etc/udev/rules.d/30-usbtmc.rules:5 Unknown group 'usbtmc', ignoring.
Oct 11 17:27:43 ryzen systemd-udevd[364]: /etc/udev/rules.d/30-usbtmc.rules:8 Unknown group 'usbtmc', ignoring.
Oct 11 17:27:43 ryzen systemd-udevd[364]: /etc/udev/rules.d/30-usbtmc.rules:11 Unknown group 'usbtmc', ignoring.
Oct 11 17:27:43 ryzen systemd-udevd[364]: /etc/udev/rules.d/30-usbtmc.rules:14 Unknown group 'usbtmc', ignoring.
Oct 11 17:27:43 ryzen systemd-udevd[364]: /etc/udev/rules.d/30-usbtmc.rules:15 Unknown group 'usbtmc', ignoring.
Oct 11 17:27:43 ryzen systemd-udevd[364]: /usr/lib/udev/rules.d/51-footcontroller.rules:10 Invalid value for OPTIONS key, ignoring: 'last_rule'
Oct 11 17:30:44 ryzen PackageKit[1897]: uid 1001 is trying to obtain org.freedesktop.packagekit.system-sources-refresh auth (only_trusted:0)
Oct 11 17:30:44 ryzen PackageKit[1897]: uid 1001 obtained auth for org.freedesktop.packagekit.system-sources-refresh
Oct 11 17:30:44 ryzen PackageKit[1897]: refresh-cache transaction /3_cddeceab from uid 1001 finished with success after 1ms
Oct 11 17:30:45 ryzen PackageKit[1897]: get-updates transaction /4_babecccd from uid 1001 finished with success after 19ms
Oct 11 17:30:54 ryzen dbus-daemon[824]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.107' (uid=0 pid=1025 comm="/bin/login -p -- ")
Oct 11 17:30:54 ryzen dbus-daemon[824]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.
Oct 11 17:30:55 ryzen login[1025]: pam_unix(login:session): session opened for user nyanpasu64(uid=1001) by nyanpasu64(uid=0)
Oct 11 17:30:55 ryzen systemd-logind[830]: New session 4 of user nyanpasu64.
Oct 11 17:30:55 ryzen systemd[1]: Started Session 4 of User nyanpasu64.
Oct 11 17:30:55 ryzen login[1025]: DIALUP AT ttyS0 BY nyanpasu64
Oct 11 17:30:55 ryzen login[1025]: LOGIN ON ttyS0 BY nyanpasu64
Oct 11 17:31:00 ryzen kernel: usb 1-7: input irq status -75 received
Oct 11 17:31:00 ryzen kernel: usb 1-7: input irq status -75 received
Oct 11 17:31:00 ryzen kernel: usb 1-7: input irq status -75 received
Oct 11 17:31:04 ryzen dbus-daemon[824]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.109' (uid=0 pid=4419 comm="sudo sh -c echo 1 > /sys/power/pm_print_times && e")
Oct 11 17:31:04 ryzen dbus-daemon[824]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.
Oct 11 17:31:09 ryzen systemd-logind[830]: The system will suspend now!
Oct 11 17:31:09 ryzen NetworkManager[927]: <info> [1697070669.0635] manager: sleep: sleep requested (sleeping: no enabled: yes)
Oct 11 17:31:09 ryzen NetworkManager[927]: <info> [1697070669.0639] manager: NetworkManager state is now ASLEEP
Oct 11 17:31:09 ryzen NetworkManager[927]: <info> [1697070669.0641] device (enp4s0): state change: activated -> deactivating (reason 'sleeping', sys-iface-state: 'managed')
Oct 11 17:31:09 ryzen dbus-daemon[824]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.4' (uid=0 pid=927 comm="/usr/bin/NetworkManager --no-daemon")
Oct 11 17:31:09 ryzen systemd[1]: Starting Network Manager Script Dispatcher Service...
Oct 11 17:31:09 ryzen dbus-daemon[824]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Oct 11 17:31:09 ryzen systemd[1]: Started Network Manager Script Dispatcher Service.
Oct 11 17:31:09 ryzen NetworkManager[927]: <info> [1697070669.1172] device (enp4s0): state change: deactivating -> disconnected (reason 'sleeping', sys-iface-state: 'managed')
Oct 11 17:31:09 ryzen avahi-daemon[823]: Withdrawing address record for fde3:5408:101c::566 on enp4s0.
Oct 11 17:31:09 ryzen avahi-daemon[823]: Withdrawing address record for fde3:5408:101c:0:7441:9d56:d3c1:1a95 on enp4s0.
Oct 11 17:31:09 ryzen NetworkManager[927]: <info> [1697070669.1186] dhcp4 (enp4s0): canceled DHCP transaction
Oct 11 17:31:09 ryzen avahi-daemon[823]: Leaving mDNS multicast group on interface enp4s0.IPv6 with address fde3:5408:101c:0:7441:9d56:d3c1:1a95.
Oct 11 17:31:09 ryzen NetworkManager[927]: <info> [1697070669.1186] dhcp4 (enp4s0): activation: beginning transaction (timeout in 45 seconds)
Oct 11 17:31:09 ryzen avahi-daemon[823]: Joining mDNS multicast group on interface enp4s0.IPv6 with address fe80::1b36:1dd4:a5cf:3b8f.
Oct 11 17:31:09 ryzen NetworkManager[927]: <info> [1697070669.1186] dhcp4 (enp4s0): state changed no lease
Oct 11 17:31:09 ryzen avahi-daemon[823]: Registering new address record for fe80::1b36:1dd4:a5cf:3b8f on enp4s0.*.
Oct 11 17:31:09 ryzen NetworkManager[927]: <info> [1697070669.1188] dhcp6 (enp4s0): canceled DHCP transaction
Oct 11 17:31:09 ryzen avahi-daemon[823]: Withdrawing address record for fe80::1b36:1dd4:a5cf:3b8f on enp4s0.
Oct 11 17:31:09 ryzen NetworkManager[927]: <info> [1697070669.1188] dhcp6 (enp4s0): activation: beginning transaction (timeout in 45 seconds)
Oct 11 17:31:09 ryzen avahi-daemon[823]: Leaving mDNS multicast group on interface enp4s0.IPv6 with address fe80::1b36:1dd4:a5cf:3b8f.
Oct 11 17:31:09 ryzen NetworkManager[927]: <info> [1697070669.1188] dhcp6 (enp4s0): state changed no lease
Oct 11 17:31:09 ryzen avahi-daemon[823]: Interface enp4s0.IPv6 no longer relevant for mDNS.
Oct 11 17:31:09 ryzen dnsmasq[1089]: no servers found in /etc/resolv.conf, will retry
Oct 11 17:31:09 ryzen dnsmasq[1056]: no servers found in /etc/resolv.conf, will retry
Oct 11 17:31:09 ryzen avahi-daemon[823]: Withdrawing address record for 192.168.0.91 on enp4s0.
Oct 11 17:31:09 ryzen avahi-daemon[823]: Leaving mDNS multicast group on interface enp4s0.IPv4 with address 192.168.0.91.
Oct 11 17:31:09 ryzen avahi-daemon[823]: Interface enp4s0.IPv4 no longer relevant for mDNS.
Oct 11 17:31:09 ryzen NetworkManager[927]: <info> [1697070669.2690] device (enp4s0): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Oct 11 17:31:09 ryzen kernel: r8169 0000:04:00.0 enp4s0: Link is Down
Oct 11 17:31:09 ryzen PackageKit[1897]: get-updates transaction /5_cbbedabb from uid 1001 finished with success after 5ms
Oct 11 17:31:09 ryzen systemd[1]: Reached target Sleep.
Oct 11 17:31:09 ryzen systemd[1]: Starting System Suspend...
Oct 11 17:31:09 ryzen systemd-sleep[4494]: Entering sleep state 'suspend'...
Oct 11 17:31:09 ryzen kernel: PM: suspend entry (deep)
Oct 11 17:31:09 ryzen kernel: Filesystems sync: 0.077 seconds
Oct 11 17:31:09 ryzen systemd-udevd[364]: /etc/udev/rules.d/30-usbtmc.rules:5 Unknown group 'usbtmc', ignoring.
Oct 11 17:31:09 ryzen systemd-udevd[364]: /etc/udev/rules.d/30-usbtmc.rules:8 Unknown group 'usbtmc', ignoring.
Oct 11 17:31:09 ryzen systemd-udevd[364]: /etc/udev/rules.d/30-usbtmc.rules:11 Unknown group 'usbtmc', ignoring.
Oct 11 17:31:09 ryzen systemd-udevd[364]: /etc/udev/rules.d/30-usbtmc.rules:14 Unknown group 'usbtmc', ignoring.
Oct 11 17:31:09 ryzen systemd-udevd[364]: /etc/udev/rules.d/30-usbtmc.rules:15 Unknown group 'usbtmc', ignoring.
Oct 11 17:31:09 ryzen systemd-udevd[364]: /usr/lib/udev/rules.d/51-footcontroller.rules:10 Invalid value for OPTIONS key, ignoring: 'last_rule'
Oct 11 17:31:27 ryzen kernel: Freezing user space processes
Oct 11 17:31:27 ryzen kernel: Freezing user space processes completed (elapsed 0.008 seconds)
Oct 11 17:31:27 ryzen kernel: OOM killer disabled.
Oct 11 17:31:27 ryzen kernel: Freezing remaining freezable tasks
Oct 11 17:31:27 ryzen kernel: Freezing remaining freezable tasks completed (elapsed 0.003 seconds)
Oct 11 17:31:27 ryzen kernel: intel_rapl_msr intel_rapl_msr.0: PM: calling platform_pm_suspend+0x0/0x50 @ 4494, parent: platform
Oct 11 17:31:27 ryzen kernel: intel_rapl_msr intel_rapl_msr.0: PM: platform_pm_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: Generic FE-GE Realtek PHY r8169-0-400:00: PM: calling mdio_bus_phy_suspend+0x0/0x120 [libphy] @ 4494, parent: r8169-0-400
Oct 11 17:31:27 ryzen kernel: Generic FE-GE Realtek PHY r8169-0-400:00: PM: mdio_bus_phy_suspend+0x0/0x120 [libphy] returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: sound pcmC3D0c: PM: calling do_pcm_suspend+0x0/0x30 [snd_pcm] @ 4494, parent: card3
Oct 11 17:31:27 ryzen kernel: sound pcmC3D0c: PM: do_pcm_suspend+0x0/0x30 [snd_pcm] returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: sound pcmC3D0p: PM: calling do_pcm_suspend+0x0/0x30 [snd_pcm] @ 4494, parent: card3
Oct 11 17:31:27 ryzen kernel: sound pcmC3D0p: PM: do_pcm_suspend+0x0/0x30 [snd_pcm] returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: sound pcmC0D1p: PM: calling do_pcm_suspend+0x0/0x30 [snd_pcm] @ 4494, parent: card0
Oct 11 17:31:27 ryzen kernel: sound pcmC0D1p: PM: do_pcm_suspend+0x0/0x30 [snd_pcm] returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: sound pcmC0D0c: PM: calling do_pcm_suspend+0x0/0x30 [snd_pcm] @ 4494, parent: card0
Oct 11 17:31:27 ryzen kernel: sound pcmC0D0c: PM: do_pcm_suspend+0x0/0x30 [snd_pcm] returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: sound pcmC0D0p: PM: calling do_pcm_suspend+0x0/0x30 [snd_pcm] @ 4494, parent: card0
Oct 11 17:31:27 ryzen kernel: sound pcmC0D0p: PM: do_pcm_suspend+0x0/0x30 [snd_pcm] returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: input input25: PM: calling input_dev_suspend+0x0/0x70 @ 4494, parent: card2
Oct 11 17:31:27 ryzen kernel: input input25: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: input input24: PM: calling input_dev_suspend+0x0/0x70 @ 4494, parent: card2
Oct 11 17:31:27 ryzen kernel: input input24: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: input input23: PM: calling input_dev_suspend+0x0/0x70 @ 4494, parent: card2
Oct 11 17:31:27 ryzen kernel: input input23: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: input input22: PM: calling input_dev_suspend+0x0/0x70 @ 4494, parent: card2
Oct 11 17:31:27 ryzen kernel: input input22: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: input input21: PM: calling input_dev_suspend+0x0/0x70 @ 4494, parent: card2
Oct 11 17:31:27 ryzen kernel: input input21: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: sound pcmC2D2c: PM: calling do_pcm_suspend+0x0/0x30 [snd_pcm] @ 4494, parent: card2
Oct 11 17:31:27 ryzen kernel: sound pcmC2D2c: PM: do_pcm_suspend+0x0/0x30 [snd_pcm] returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: sound pcmC2D0c: PM: calling do_pcm_suspend+0x0/0x30 [snd_pcm] @ 4494, parent: card2
Oct 11 17:31:27 ryzen kernel: sound pcmC2D0c: PM: do_pcm_suspend+0x0/0x30 [snd_pcm] returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: sound pcmC2D0p: PM: calling do_pcm_suspend+0x0/0x30 [snd_pcm] @ 4494, parent: card2
Oct 11 17:31:27 ryzen kernel: sound pcmC2D0p: PM: do_pcm_suspend+0x0/0x30 [snd_pcm] returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: input input20: PM: calling input_dev_suspend+0x0/0x70 @ 4494, parent: card1
Oct 11 17:31:27 ryzen kernel: input input20: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: input input19: PM: calling input_dev_suspend+0x0/0x70 @ 4494, parent: card1
Oct 11 17:31:27 ryzen kernel: input input19: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: input input18: PM: calling input_dev_suspend+0x0/0x70 @ 4494, parent: card1
Oct 11 17:31:27 ryzen kernel: input input18: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: input input17: PM: calling input_dev_suspend+0x0/0x70 @ 4494, parent: card1
Oct 11 17:31:27 ryzen kernel: snd_hda_codec_realtek hdaudioC2D0: PM: calling hda_codec_pm_suspend+0x0/0x20 [snd_hda_codec] @ 148, parent: 0000:07:00.4
Oct 11 17:31:27 ryzen kernel: input input17: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: input input16: PM: calling input_dev_suspend+0x0/0x70 @ 4494, parent: card1
Oct 11 17:31:27 ryzen kernel: input input16: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: input input15: PM: calling input_dev_suspend+0x0/0x70 @ 4494, parent: card1
Oct 11 17:31:27 ryzen kernel: input input15: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: sound pcmC1D11p: PM: calling do_pcm_suspend+0x0/0x30 [snd_pcm] @ 4494, parent: card1
Oct 11 17:31:27 ryzen kernel: sound pcmC1D11p: PM: do_pcm_suspend+0x0/0x30 [snd_pcm] returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: sound pcmC1D10p: PM: calling do_pcm_suspend+0x0/0x30 [snd_pcm] @ 4494, parent: card1
Oct 11 17:31:27 ryzen kernel: sound pcmC1D10p: PM: do_pcm_suspend+0x0/0x30 [snd_pcm] returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: sound pcmC1D9p: PM: calling do_pcm_suspend+0x0/0x30 [snd_pcm] @ 4494, parent: card1
Oct 11 17:31:27 ryzen kernel: sound pcmC1D9p: PM: do_pcm_suspend+0x0/0x30 [snd_pcm] returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: sound pcmC1D8p: PM: calling do_pcm_suspend+0x0/0x30 [snd_pcm] @ 4494, parent: card1
Oct 11 17:31:27 ryzen kernel: sound pcmC1D8p: PM: do_pcm_suspend+0x0/0x30 [snd_pcm] returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: sound pcmC1D7p: PM: calling do_pcm_suspend+0x0/0x30 [snd_pcm] @ 4494, parent: card1
Oct 11 17:31:27 ryzen kernel: sound pcmC1D7p: PM: do_pcm_suspend+0x0/0x30 [snd_pcm] returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: sound pcmC1D3p: PM: calling do_pcm_suspend+0x0/0x30 [snd_pcm] @ 4494, parent: card1
Oct 11 17:31:27 ryzen kernel: sound pcmC1D3p: PM: do_pcm_suspend+0x0/0x30 [snd_pcm] returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: input input14: PM: calling input_dev_suspend+0x0/0x70 @ 4494, parent: pcspkr
Oct 11 17:31:27 ryzen kernel: input input14: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: sp5100-tco sp5100-tco: PM: calling platform_pm_suspend+0x0/0x50 @ 4494, parent: platform
Oct 11 17:31:27 ryzen kernel: sp5100-tco sp5100-tco: PM: platform_pm_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: input input11: PM: calling input_dev_suspend+0x0/0x70 @ 4494, parent: 0003:046D:C092.000A
Oct 11 17:31:27 ryzen kernel: input input11: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: usb 1-2.4: PM: calling usb_dev_suspend+0x0/0x20 @ 12, parent: 1-2
Oct 11 17:31:27 ryzen kernel: input input10: PM: calling input_dev_suspend+0x0/0x70 @ 4494, parent: 0003:046D:C092.0009
Oct 11 17:31:27 ryzen kernel: input input10: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: usb 1-2.4: PM: usb_dev_suspend+0x0/0x20 returned 0 after 4 usecs
Oct 11 17:31:27 ryzen kernel: input input9: PM: calling input_dev_suspend+0x0/0x70 @ 4494, parent: 0003:29EA:0102.0007
Oct 11 17:31:27 ryzen kernel: input input9: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: usb 1-10: PM: calling usb_dev_suspend+0x0/0x20 @ 3812, parent: usb1
Oct 11 17:31:27 ryzen kernel: usb 1-2.3: PM: calling usb_dev_suspend+0x0/0x20 @ 12, parent: 1-2
Oct 11 17:31:27 ryzen kernel: input input8: PM: calling input_dev_suspend+0x0/0x70 @ 4494, parent: 0003:29EA:0102.0007
Oct 11 17:31:27 ryzen kernel: input input8: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: usb 1-10: PM: usb_dev_suspend+0x0/0x20 returned 0 after 5 usecs
Oct 11 17:31:27 ryzen kernel: leds input7::kana: PM: calling led_suspend+0x0/0x50 @ 4494, parent: input7
Oct 11 17:31:27 ryzen kernel: leds input7::kana: PM: led_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: leds input7::compose: PM: calling led_suspend+0x0/0x50 @ 4494, parent: input7
Oct 11 17:31:27 ryzen kernel: leds input7::compose: PM: led_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: leds input7::scrolllock: PM: calling led_suspend+0x0/0x50 @ 4494, parent: input7
Oct 11 17:31:27 ryzen kernel: leds input7::scrolllock: PM: led_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: leds input7::capslock: PM: calling led_suspend+0x0/0x50 @ 4494, parent: input7
Oct 11 17:31:27 ryzen kernel: leds input7::capslock: PM: led_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: leds input7::numlock: PM: calling led_suspend+0x0/0x50 @ 4494, parent: input7
Oct 11 17:31:27 ryzen kernel: leds input7::numlock: PM: led_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: input input7: PM: calling input_dev_suspend+0x0/0x70 @ 4494, parent: 0003:29EA:0102.0006
Oct 11 17:31:27 ryzen kernel: input input7: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: input input6: PM: calling input_dev_suspend+0x0/0x70 @ 4494, parent: 0003:29EA:0102.0005
Oct 11 17:31:27 ryzen kernel: input input6: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: usb 1-2.2: PM: calling usb_dev_suspend+0x0/0x20 @ 10, parent: 1-2
Oct 11 17:31:27 ryzen kernel: usb 1-7: PM: calling usb_dev_suspend+0x0/0x20 @ 321, parent: usb1
Oct 11 17:31:27 ryzen kernel: input input5: PM: calling input_dev_suspend+0x0/0x70 @ 4494, parent: 0003:0ECB:2057.0003
Oct 11 17:31:27 ryzen kernel: input input5: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: usb 1-7: PM: usb_dev_suspend+0x0/0x20 returned 0 after 3 usecs
Oct 11 17:31:27 ryzen kernel: sd 6:0:0:0: PM: calling scsi_bus_suspend+0x0/0xc0 @ 144, parent: target6:0:0
Oct 11 17:31:27 ryzen kernel: input input4: PM: calling input_dev_suspend+0x0/0x70 @ 4494, parent: 0003:05F3:00FF.0002
Oct 11 17:31:27 ryzen kernel: usb 1-2.1: PM: calling usb_dev_suspend+0x0/0x20 @ 321, parent: 1-2
Oct 11 17:31:27 ryzen kernel: input input4: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: input input3: PM: calling input_dev_suspend+0x0/0x70 @ 4494, parent: 0003:1852:7022.0001
Oct 11 17:31:27 ryzen kernel: input input3: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: usb 1-5: PM: calling usb_dev_suspend+0x0/0x20 @ 1219, parent: usb1
Oct 11 17:31:27 ryzen kernel: leds input2::scrolllock: PM: calling led_suspend+0x0/0x50 @ 4494, parent: input2
Oct 11 17:31:27 ryzen kernel: leds input2::scrolllock: PM: led_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: leds input2::capslock: PM: calling led_suspend+0x0/0x50 @ 4494, parent: input2
Oct 11 17:31:27 ryzen kernel: leds input2::capslock: PM: led_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: usb 3-2: PM: calling usb_dev_suspend+0x0/0x20 @ 145, parent: usb3
Oct 11 17:31:27 ryzen kernel: leds input2::numlock: PM: calling led_suspend+0x0/0x50 @ 4494, parent: input2
Oct 11 17:31:27 ryzen kernel: leds input2::numlock: PM: led_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: input input2: PM: calling input_dev_suspend+0x0/0x70 @ 4494, parent: serio0
Oct 11 17:31:27 ryzen kernel: input input2: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: usb usb4: PM: calling usb_dev_suspend+0x0/0x20 @ 3684, parent: 0000:07:00.3
Oct 11 17:31:27 ryzen kernel: atkbd serio0: PM: calling serio_suspend+0x0/0x50 [serio] @ 4494, parent: i8042
Oct 11 17:31:27 ryzen kernel: usb 3-2: PM: usb_dev_suspend+0x0/0x20 returned 0 after 102 usecs
Oct 11 17:31:27 ryzen kernel: usb usb3: PM: calling usb_dev_suspend+0x0/0x20 @ 96, parent: 0000:07:00.3
Oct 11 17:31:27 ryzen kernel: usb 1-5: PM: usb_dev_suspend+0x0/0x20 returned 0 after 1154 usecs
Oct 11 17:31:27 ryzen kernel: usb 1-2.3: PM: usb_dev_suspend+0x0/0x20 returned 0 after 1908 usecs
Oct 11 17:31:27 ryzen kernel: usb 1-2.1: PM: usb_dev_suspend+0x0/0x20 returned 0 after 2119 usecs
Oct 11 17:31:27 ryzen kernel: atkbd serio0: PM: serio_suspend+0x0/0x50 [serio] returned 0 after 2799 usecs
Oct 11 17:31:27 ryzen kernel: i8042 i8042: PM: calling platform_pm_suspend+0x0/0x50 @ 4494, parent: platform
Oct 11 17:31:27 ryzen kernel: i8042 i8042: PM: platform_pm_suspend+0x0/0x50 returned 0 after 127 usecs
Oct 11 17:31:27 ryzen kernel: platform microcode: PM: calling platform_pm_suspend+0x0/0x50 @ 4494, parent: platform
Oct 11 17:31:27 ryzen kernel: sr 1:0:0:0: PM: calling scsi_bus_suspend+0x0/0xc0 @ 321, parent: target1:0:0
Oct 11 17:31:27 ryzen kernel: platform microcode: PM: platform_pm_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: alarmtimer alarmtimer.0.auto: PM: calling platform_pm_suspend+0x0/0x50 @ 4494, parent: rtc0
Oct 11 17:31:27 ryzen kernel: alarmtimer alarmtimer.0.auto: PM: platform_pm_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: rtc rtc0: PM: calling rtc_suspend+0x0/0x1f0 @ 4494, parent: 00:02
Oct 11 17:31:27 ryzen kernel: sd 0:0:0:0: PM: calling scsi_bus_suspend+0x0/0xc0 @ 1219, parent: target0:0:0
Oct 11 17:31:27 ryzen kernel: rtc rtc0: PM: rtc_suspend+0x0/0x1f0 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: scsi host5: PM: calling scsi_bus_suspend+0x0/0xc0 @ 146, parent: ata6
Oct 11 17:31:27 ryzen kernel: scsi host4: PM: calling scsi_bus_suspend+0x0/0xc0 @ 147, parent: ata5
Oct 11 17:31:27 ryzen kernel: scsi host5: PM: scsi_bus_suspend+0x0/0xc0 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: scsi host4: PM: scsi_bus_suspend+0x0/0xc0 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: scsi host3: PM: calling scsi_bus_suspend+0x0/0xc0 @ 146, parent: ata4
Oct 11 17:31:27 ryzen kernel: scsi host2: PM: calling scsi_bus_suspend+0x0/0xc0 @ 147, parent: ata3
Oct 11 17:31:27 ryzen kernel: scsi host3: PM: scsi_bus_suspend+0x0/0xc0 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: scsi host2: PM: scsi_bus_suspend+0x0/0xc0 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: port serial8250:0.31: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 4494, parent: serial8250:0
Oct 11 17:31:27 ryzen kernel: port serial8250:0.31: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: port serial8250:0.30: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 4494, parent: serial8250:0
Oct 11 17:31:27 ryzen kernel: port serial8250:0.30: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: port serial8250:0.29: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 4494, parent: serial8250:0
Oct 11 17:31:27 ryzen kernel: port serial8250:0.29: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: ata6: PM: calling ata_port_pm_suspend+0x0/0x50 @ 3813, parent: 0000:02:00.1
Oct 11 17:31:27 ryzen kernel: port serial8250:0.28: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 4494, parent: serial8250:0
Oct 11 17:31:27 ryzen kernel: port serial8250:0.28: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: port serial8250:0.27: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 4494, parent: serial8250:0
Oct 11 17:31:27 ryzen kernel: port serial8250:0.27: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: port serial8250:0.26: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 4494, parent: serial8250:0
Oct 11 17:31:27 ryzen kernel: ata6: PM: ata_port_pm_suspend+0x0/0x50 returned 0 after 23 usecs
Oct 11 17:31:27 ryzen kernel: ata5: PM: calling ata_port_pm_suspend+0x0/0x50 @ 4522, parent: 0000:02:00.1
Oct 11 17:31:27 ryzen kernel: port serial8250:0.26: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: ata4: PM: calling ata_port_pm_suspend+0x0/0x50 @ 3813, parent: 0000:02:00.1
Oct 11 17:31:27 ryzen kernel: port serial8250:0.25: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 4494, parent: serial8250:0
Oct 11 17:31:27 ryzen kernel: port serial8250:0.25: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: port serial8250:0.24: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 4494, parent: serial8250:0
Oct 11 17:31:27 ryzen kernel: port serial8250:0.24: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: ata5: PM: ata_port_pm_suspend+0x0/0x50 returned 0 after 24 usecs
Oct 11 17:31:27 ryzen kernel: port serial8250:0.23: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 4494, parent: serial8250:0
Oct 11 17:31:27 ryzen kernel: ata3: PM: calling ata_port_pm_suspend+0x0/0x50 @ 4523, parent: 0000:02:00.1
Oct 11 17:31:27 ryzen kernel: port serial8250:0.23: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: ata4: PM: ata_port_pm_suspend+0x0/0x50 returned 0 after 31 usecs
Oct 11 17:31:27 ryzen kernel: port serial8250:0.22: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 4494, parent: serial8250:0
Oct 11 17:31:27 ryzen kernel: port serial8250:0.22: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: port serial8250:0.21: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 4494, parent: serial8250:0
Oct 11 17:31:27 ryzen kernel: port serial8250:0.21: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: ata3: PM: ata_port_pm_suspend+0x0/0x50 returned 0 after 22 usecs
Oct 11 17:31:27 ryzen kernel: port serial8250:0.20: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 4494, parent: serial8250:0
Oct 11 17:31:27 ryzen kernel: port serial8250:0.20: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: port serial8250:0.19: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 4494, parent: serial8250:0
Oct 11 17:31:27 ryzen kernel: port serial8250:0.19: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: port serial8250:0.18: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 4494, parent: serial8250:0
Oct 11 17:31:27 ryzen kernel: port serial8250:0.18: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: port serial8250:0.17: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 4494, parent: serial8250:0
Oct 11 17:31:27 ryzen kernel: port serial8250:0.17: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: port serial8250:0.16: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 4494, parent: serial8250:0
Oct 11 17:31:27 ryzen kernel: port serial8250:0.16: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: port serial8250:0.15: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 4494, parent: serial8250:0
Oct 11 17:31:27 ryzen kernel: port serial8250:0.15: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: port serial8250:0.14: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 4494, parent: serial8250:0
Oct 11 17:31:27 ryzen kernel: port serial8250:0.14: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: port serial8250:0.13: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 4494, parent: serial8250:0
Oct 11 17:31:27 ryzen kernel: port serial8250:0.13: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: port serial8250:0.12: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 4494, parent: serial8250:0
Oct 11 17:31:27 ryzen kernel: port serial8250:0.12: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: port serial8250:0.11: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 4494, parent: serial8250:0
Oct 11 17:31:27 ryzen kernel: port serial8250:0.11: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: port serial8250:0.10: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 4494, parent: serial8250:0
Oct 11 17:31:27 ryzen kernel: port serial8250:0.10: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: port serial8250:0.9: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 4494, parent: serial8250:0
Oct 11 17:31:27 ryzen kernel: port serial8250:0.9: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: port serial8250:0.8: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 4494, parent: serial8250:0
Oct 11 17:31:27 ryzen kernel: port serial8250:0.8: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: port serial8250:0.7: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 4494, parent: serial8250:0
Oct 11 17:31:27 ryzen kernel: port serial8250:0.7: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: port serial8250:0.6: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 4494, parent: serial8250:0
Oct 11 17:31:27 ryzen kernel: port serial8250:0.6: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: port serial8250:0.5: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 4494, parent: serial8250:0
Oct 11 17:31:27 ryzen kernel: port serial8250:0.5: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: port serial8250:0.4: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 4494, parent: serial8250:0
Oct 11 17:31:27 ryzen kernel: port serial8250:0.4: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: port serial8250:0.3: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 4494, parent: serial8250:0
Oct 11 17:31:27 ryzen kernel: port serial8250:0.3: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: port serial8250:0.2: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 4494, parent: serial8250:0
Oct 11 17:31:27 ryzen kernel: port serial8250:0.2: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: port serial8250:0.1: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 4494, parent: serial8250:0
Oct 11 17:31:27 ryzen kernel: port serial8250:0.1: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: serial8250 serial8250: PM: calling platform_pm_suspend+0x0/0x50 @ 4494, parent: platform
Oct 11 17:31:27 ryzen kernel: serial8250 serial8250: PM: platform_pm_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: port 00:05:0.0: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 4494, parent: 00:05:0
Oct 11 17:31:27 ryzen kernel: port 00:05:0.0: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: input input1: PM: calling input_dev_suspend+0x0/0x70 @ 4494, parent: LNXPWRBN:00
Oct 11 17:31:27 ryzen kernel: input input1: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: input input0: PM: calling input_dev_suspend+0x0/0x70 @ 4494, parent: PNP0C0C:00
Oct 11 17:31:27 ryzen kernel: input input0: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: pcspkr pcspkr: PM: calling platform_pm_suspend+0x0/0x50 @ 4494, parent: platform
Oct 11 17:31:27 ryzen kernel: pcspkr pcspkr: PM: platform_pm_suspend+0x0/0x50 returned 0 after 5 usecs
Oct 11 17:31:27 ryzen kernel: snd_hda_intel 0000:05:00.1: PM: calling pci_pm_suspend+0x0/0x170 @ 4526, parent: 0000:00:03.1
Oct 11 17:31:27 ryzen kernel: system 00:06: PM: calling pnp_bus_suspend+0x0/0x20 @ 4494, parent: pnp0
Oct 11 17:31:27 ryzen kernel: system 00:06: PM: pnp_bus_suspend+0x0/0x20 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: serial 00:05: PM: calling pnp_bus_suspend+0x0/0x20 @ 4494, parent: pnp0
Oct 11 17:31:27 ryzen kernel: serial 00:05: PM: pnp_bus_suspend+0x0/0x20 returned 0 after 4 usecs
Oct 11 17:31:27 ryzen kernel: i8042 kbd 00:04: PM: calling pnp_bus_suspend+0x0/0x20 @ 4494, parent: pnp0
Oct 11 17:31:27 ryzen kernel: i8042 kbd 00:04: PM: pnp_bus_suspend+0x0/0x20 returned 0 after 59 usecs
Oct 11 17:31:27 ryzen kernel: system 00:03: PM: calling pnp_bus_suspend+0x0/0x20 @ 4494, parent: pnp0
Oct 11 17:31:27 ryzen kernel: system 00:03: PM: pnp_bus_suspend+0x0/0x20 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: rtc_cmos 00:02: PM: calling pnp_bus_suspend+0x0/0x20 @ 4494, parent: pnp0
Oct 11 17:31:27 ryzen kernel: rtc_cmos 00:02: PM: pnp_bus_suspend+0x0/0x20 returned 0 after 23 usecs
Oct 11 17:31:27 ryzen kernel: system 00:01: PM: calling pnp_bus_suspend+0x0/0x20 @ 4494, parent: pnp0
Oct 11 17:31:27 ryzen kernel: system 00:01: PM: pnp_bus_suspend+0x0/0x20 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: system 00:00: PM: calling pnp_bus_suspend+0x0/0x20 @ 4494, parent: pnp0
Oct 11 17:31:27 ryzen kernel: system 00:00: PM: pnp_bus_suspend+0x0/0x20 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: platform efivars.0: PM: calling platform_pm_suspend+0x0/0x50 @ 4494, parent: platform
Oct 11 17:31:27 ryzen kernel: platform efivars.0: PM: platform_pm_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: platform rtc-efi.0: PM: calling platform_pm_suspend+0x0/0x50 @ 4494, parent: platform
Oct 11 17:31:27 ryzen kernel: platform rtc-efi.0: PM: platform_pm_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: button LNXPWRBN:00: PM: calling acpi_button_suspend+0x0/0x20 @ 4494, parent: LNXSYSTM:00
Oct 11 17:31:27 ryzen kernel: button LNXPWRBN:00: PM: acpi_button_suspend+0x0/0x20 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: acpi-wmi PNP0C14:01: PM: calling acpi_subsys_suspend+0x0/0x60 @ 4494, parent: platform
Oct 11 17:31:27 ryzen kernel: acpi-wmi PNP0C14:01: PM: acpi_subsys_suspend+0x0/0x60 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: acpi-wmi PNP0C14:00: PM: calling acpi_subsys_suspend+0x0/0x60 @ 4494, parent: platform
Oct 11 17:31:27 ryzen kernel: acpi-wmi PNP0C14:00: PM: acpi_subsys_suspend+0x0/0x60 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: platform PNP0103:00: PM: calling platform_pm_suspend+0x0/0x50 @ 4494, parent: platform
Oct 11 17:31:27 ryzen kernel: platform PNP0103:00: PM: platform_pm_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: pt-gpio AMDIF030:00: PM: calling acpi_subsys_suspend+0x0/0x60 @ 4494, parent: platform
Oct 11 17:31:27 ryzen kernel: pt-gpio AMDIF030:00: PM: acpi_subsys_suspend+0x0/0x60 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: acpi-cpufreq acpi-cpufreq: PM: calling platform_pm_suspend+0x0/0x50 @ 4494, parent: platform
Oct 11 17:31:27 ryzen kernel: acpi-cpufreq acpi-cpufreq: PM: platform_pm_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: platform MSFT0101:00: PM: calling platform_pm_suspend+0x0/0x50 @ 4494, parent: platform
Oct 11 17:31:27 ryzen kernel: platform MSFT0101:00: PM: platform_pm_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: amd_gpio AMDI0030:00: PM: calling acpi_subsys_suspend+0x0/0x60 @ 4494, parent: platform
Oct 11 17:31:27 ryzen kernel: amd_gpio AMDI0030:00: PM: acpi_subsys_suspend+0x0/0x60 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: platform PNP0C0C:00: PM: calling platform_pm_suspend+0x0/0x50 @ 4494, parent: platform
Oct 11 17:31:27 ryzen kernel: platform PNP0C0C:00: PM: platform_pm_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: platform PNP0800:00: PM: calling platform_pm_suspend+0x0/0x50 @ 4494, parent: 0000:00:14.3
Oct 11 17:31:27 ryzen kernel: platform PNP0800:00: PM: platform_pm_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: thermal LNXTHERM:01: PM: calling acpi_thermal_suspend+0x0/0x20 @ 4494, parent: LNXSYBUS:01
Oct 11 17:31:27 ryzen kernel: thermal LNXTHERM:01: PM: acpi_thermal_suspend+0x0/0x20 returned 0 after 2 usecs
Oct 11 17:31:27 ryzen kernel: thermal LNXTHERM:00: PM: calling acpi_thermal_suspend+0x0/0x20 @ 4494, parent: LNXSYBUS:01
Oct 11 17:31:27 ryzen kernel: ccp 0000:07:00.1: PM: calling pci_pm_suspend+0x0/0x170 @ 4525, parent: 0000:00:08.1
Oct 11 17:31:27 ryzen kernel: thermal LNXTHERM:00: PM: acpi_thermal_suspend+0x0/0x20 returned 0 after 1 usecs
Oct 11 17:31:27 ryzen kernel: ccp 0000:07:00.1: PM: pci_pm_suspend+0x0/0x170 returned 0 after 1 usecs
Oct 11 17:31:27 ryzen kernel: pci 0000:07:00.0: PM: calling pci_pm_suspend+0x0/0x170 @ 4525, parent: 0000:00:08.1
Oct 11 17:31:27 ryzen kernel: pci 0000:07:00.0: PM: pci_pm_suspend+0x0/0x170 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: pci 0000:06:00.0: PM: calling pci_pm_suspend+0x0/0x170 @ 4525, parent: 0000:00:07.1
Oct 11 17:31:27 ryzen kernel: pci 0000:06:00.0: PM: pci_pm_suspend+0x0/0x170 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: r8169 0000:04:00.0: PM: calling pci_pm_suspend+0x0/0x170 @ 4527, parent: 0000:03:09.0
Oct 11 17:31:27 ryzen kernel: tpm_crb MSFT0101:00: PM: calling tpm_pm_suspend+0x0/0xd0 @ 4494, parent: LNXSYBUS:00
Oct 11 17:31:27 ryzen kernel: r8169 0000:04:00.0: PM: pci_pm_suspend+0x0/0x170 returned 0 after 1 usecs
Oct 11 17:31:27 ryzen kernel: pcieport 0000:03:09.0: PM: calling pci_pm_suspend+0x0/0x170 @ 4527, parent: 0000:02:00.2
Oct 11 17:31:27 ryzen kernel: pcieport 0000:03:09.0: PM: pci_pm_suspend+0x0/0x170 returned 0 after 1 usecs
Oct 11 17:31:27 ryzen kernel: pcieport 0000:02:00.2: PM: calling pci_pm_suspend+0x0/0x170 @ 4527, parent: 0000:00:01.2
Oct 11 17:31:27 ryzen kernel: pcieport 0000:02:00.2: PM: pci_pm_suspend+0x0/0x170 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: nvme 0000:01:00.0: PM: calling pci_pm_suspend+0x0/0x170 @ 4529, parent: 0000:00:01.1
Oct 11 17:31:27 ryzen kernel: pci 0000:00:18.7: PM: calling pci_pm_suspend+0x0/0x170 @ 4530, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pci 0000:00:18.7: PM: pci_pm_suspend+0x0/0x170 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: pci 0000:00:18.6: PM: calling pci_pm_suspend+0x0/0x170 @ 4530, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pci 0000:00:18.6: PM: pci_pm_suspend+0x0/0x170 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: pci 0000:00:18.5: PM: calling pci_pm_suspend+0x0/0x170 @ 4530, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pci 0000:00:18.5: PM: pci_pm_suspend+0x0/0x170 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: pci 0000:00:18.4: PM: calling pci_pm_suspend+0x0/0x170 @ 4530, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pci 0000:00:18.4: PM: pci_pm_suspend+0x0/0x170 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: k10temp 0000:00:18.3: PM: calling pci_pm_suspend+0x0/0x170 @ 4530, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pci 0000:00:18.2: PM: calling pci_pm_suspend+0x0/0x170 @ 4531, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: k10temp 0000:00:18.3: PM: pci_pm_suspend+0x0/0x170 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: pci 0000:00:18.2: PM: pci_pm_suspend+0x0/0x170 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: pci 0000:00:18.1: PM: calling pci_pm_suspend+0x0/0x170 @ 4530, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pci 0000:00:18.1: PM: pci_pm_suspend+0x0/0x170 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: pci 0000:00:18.0: PM: calling pci_pm_suspend+0x0/0x170 @ 4531, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pci 0000:00:18.0: PM: pci_pm_suspend+0x0/0x170 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: pci 0000:00:14.3: PM: calling pci_pm_suspend+0x0/0x170 @ 4530, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pci 0000:00:14.3: PM: pci_pm_suspend+0x0/0x170 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: piix4_smbus 0000:00:14.0: PM: calling pci_pm_suspend+0x0/0x170 @ 4531, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: piix4_smbus 0000:00:14.0: PM: pci_pm_suspend+0x0/0x170 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: pci 0000:00:08.0: PM: calling pci_pm_suspend+0x0/0x170 @ 4531, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pci 0000:00:08.0: PM: pci_pm_suspend+0x0/0x170 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: pcieport 0000:00:07.1: PM: calling pci_pm_suspend+0x0/0x170 @ 4532, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pci 0000:00:07.0: PM: calling pci_pm_suspend+0x0/0x170 @ 4531, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pci 0000:00:07.0: PM: pci_pm_suspend+0x0/0x170 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: pcieport 0000:00:07.1: PM: pci_pm_suspend+0x0/0x170 returned 0 after 3 usecs
Oct 11 17:31:27 ryzen kernel: pci 0000:00:05.0: PM: calling pci_pm_suspend+0x0/0x170 @ 4531, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pci 0000:00:05.0: PM: pci_pm_suspend+0x0/0x170 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: pci 0000:00:04.0: PM: calling pci_pm_suspend+0x0/0x170 @ 4532, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pci 0000:00:04.0: PM: pci_pm_suspend+0x0/0x170 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: pci 0000:00:03.0: PM: calling pci_pm_suspend+0x0/0x170 @ 4533, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pci 0000:00:03.0: PM: pci_pm_suspend+0x0/0x170 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: pci 0000:00:02.0: PM: calling pci_pm_suspend+0x0/0x170 @ 4532, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pci 0000:00:02.0: PM: pci_pm_suspend+0x0/0x170 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: pci 0000:00:01.0: PM: calling pci_pm_suspend+0x0/0x170 @ 4534, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pci 0000:00:01.0: PM: pci_pm_suspend+0x0/0x170 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: pci 0000:00:00.2: PM: calling pci_pm_suspend+0x0/0x170 @ 4534, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pci 0000:00:00.2: PM: pci_pm_suspend+0x0/0x170 returned 0 after 1 usecs
Oct 11 17:31:27 ryzen kernel: pci 0000:00:00.0: PM: calling pci_pm_suspend+0x0/0x170 @ 4534, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pci 0000:00:00.0: PM: pci_pm_suspend+0x0/0x170 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: usb usb3: PM: usb_dev_suspend+0x0/0x20 returned 0 after 8173 usecs
Oct 11 17:31:27 ryzen kernel: sd 6:0:0:0: PM: scsi_bus_suspend+0x0/0xc0 returned 0 after 15061 usecs
Oct 11 17:31:27 ryzen kernel: scsi target6:0:0: PM: calling scsi_bus_suspend+0x0/0xc0 @ 3812, parent: host6
Oct 11 17:31:27 ryzen kernel: scsi target6:0:0: PM: scsi_bus_suspend+0x0/0xc0 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: scsi host6: PM: calling scsi_bus_suspend+0x0/0xc0 @ 314, parent: 2-4:1.0
Oct 11 17:31:27 ryzen kernel: scsi host6: PM: scsi_bus_suspend+0x0/0xc0 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: usb 2-4: PM: calling usb_dev_suspend+0x0/0x20 @ 316, parent: usb2
Oct 11 17:31:27 ryzen kernel: snd_hda_codec_realtek hdaudioC2D0: PM: hda_codec_pm_suspend+0x0/0x20 [snd_hda_codec] returned 0 after 16348 usecs
Oct 11 17:31:27 ryzen kernel: snd_hda_intel 0000:07:00.4: PM: calling pci_pm_suspend+0x0/0x170 @ 4524, parent: 0000:00:08.1
Oct 11 17:31:27 ryzen kernel: snd_hda_intel 0000:07:00.4: PM: pci_pm_suspend+0x0/0x170 returned 0 after 1072 usecs
Oct 11 17:31:27 ryzen kernel: snd_hda_intel 0000:05:00.1: PM: pci_pm_suspend+0x0/0x170 returned 0 after 13770 usecs
Oct 11 17:31:27 ryzen kernel: amdgpu 0000:05:00.0: PM: calling pci_pm_suspend+0x0/0x170 @ 4525, parent: 0000:00:03.1
Oct 11 17:31:27 ryzen kernel: usb 1-2.2: PM: usb_dev_suspend+0x0/0x20 returned 0 after 25014 usecs
Oct 11 17:31:27 ryzen kernel: usb 1-2: PM: calling usb_dev_suspend+0x0/0x20 @ 315, parent: usb1
Oct 11 17:31:27 ryzen kernel: usb usb4: PM: usb_dev_suspend+0x0/0x20 returned 0 after 24977 usecs
Oct 11 17:31:27 ryzen kernel: xhci_hcd 0000:07:00.3: PM: calling pci_pm_suspend+0x0/0x170 @ 4523, parent: 0000:00:08.1
Oct 11 17:31:27 ryzen kernel: xhci_hcd 0000:07:00.3: PM: pci_pm_suspend+0x0/0x170 returned 0 after 162 usecs
Oct 11 17:31:27 ryzen kernel: pcieport 0000:00:08.1: PM: calling pci_pm_suspend+0x0/0x170 @ 4530, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pcieport 0000:00:08.1: PM: pci_pm_suspend+0x0/0x170 returned 0 after 2 usecs
Oct 11 17:31:27 ryzen kernel: sr 1:0:0:0: PM: scsi_bus_suspend+0x0/0xc0 returned 0 after 25307 usecs
Oct 11 17:31:27 ryzen kernel: scsi target1:0:0: PM: calling scsi_bus_suspend+0x0/0xc0 @ 12, parent: host1
Oct 11 17:31:27 ryzen kernel: scsi target1:0:0: PM: scsi_bus_suspend+0x0/0xc0 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: scsi host1: PM: calling scsi_bus_suspend+0x0/0xc0 @ 147, parent: ata2
Oct 11 17:31:27 ryzen kernel: scsi host1: PM: scsi_bus_suspend+0x0/0xc0 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: ata2: PM: calling ata_port_pm_suspend+0x0/0x50 @ 4522, parent: 0000:02:00.1
Oct 11 17:31:27 ryzen kernel: ata2: PM: ata_port_pm_suspend+0x0/0x50 returned 0 after 24 usecs
Oct 11 17:31:27 ryzen kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Oct 11 17:31:27 ryzen kernel: sd 0:0:0:0: [sda] Stopping disk
Oct 11 17:31:27 ryzen kernel: usb 2-4: PM: usb_dev_suspend+0x0/0x20 returned 0 after 26555 usecs
Oct 11 17:31:27 ryzen kernel: usb usb2: PM: calling usb_dev_suspend+0x0/0x20 @ 317, parent: 0000:02:00.0
Oct 11 17:31:27 ryzen kernel: usb usb2: PM: usb_dev_suspend+0x0/0x20 returned 0 after 15 usecs
Oct 11 17:31:27 ryzen kernel: tpm_crb MSFT0101:00: PM: tpm_pm_suspend+0x0/0xd0 returned 0 after 47832 usecs
Oct 11 17:31:27 ryzen kernel: button PNP0C0C:00: PM: calling acpi_button_suspend+0x0/0x20 @ 4494, parent: LNXSYBUS:00
Oct 11 17:31:27 ryzen kernel: button PNP0C0C:00: PM: acpi_button_suspend+0x0/0x20 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: PCCT PCCT: PM: calling platform_pm_suspend+0x0/0x50 @ 4494, parent: platform
Oct 11 17:31:27 ryzen kernel: PCCT PCCT: PM: platform_pm_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: regulator regulator.0: PM: calling regulator_suspend+0x0/0x120 @ 4494, parent: reg-dummy
Oct 11 17:31:27 ryzen kernel: regulator regulator.0: PM: regulator_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: reg-dummy reg-dummy: PM: calling platform_pm_suspend+0x0/0x50 @ 4494, parent: platform
Oct 11 17:31:27 ryzen kernel: reg-dummy reg-dummy: PM: platform_pm_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: usb 1-2: PM: usb_dev_suspend+0x0/0x20 returned 0 after 36653 usecs
Oct 11 17:31:27 ryzen kernel: usb usb1: PM: calling usb_dev_suspend+0x0/0x20 @ 3814, parent: 0000:02:00.0
Oct 11 17:31:27 ryzen kernel: usb usb1: PM: usb_dev_suspend+0x0/0x20 returned 0 after 10791 usecs
Oct 11 17:31:27 ryzen kernel: xhci_hcd 0000:02:00.0: PM: calling pci_pm_suspend+0x0/0x170 @ 4528, parent: 0000:00:01.2
Oct 11 17:31:27 ryzen kernel: xhci_hcd 0000:02:00.0: PM: pci_pm_suspend+0x0/0x170 returned 0 after 1114 usecs
Oct 11 17:31:27 ryzen kernel: amdgpu 0000:05:00.0: PM: pci_pm_suspend+0x0/0x170 returned 0 after 141282 usecs
Oct 11 17:31:27 ryzen kernel: pcieport 0000:00:03.1: PM: calling pci_pm_suspend+0x0/0x170 @ 4531, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pcieport 0000:00:03.1: PM: pci_pm_suspend+0x0/0x170 returned 0 after 2 usecs
Oct 11 17:31:27 ryzen kernel: sd 0:0:0:0: PM: scsi_bus_suspend+0x0/0xc0 returned 0 after 434702 usecs
Oct 11 17:31:27 ryzen kernel: scsi target0:0:0: PM: calling scsi_bus_suspend+0x0/0xc0 @ 145, parent: host0
Oct 11 17:31:27 ryzen kernel: scsi target0:0:0: PM: scsi_bus_suspend+0x0/0xc0 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: scsi host0: PM: calling scsi_bus_suspend+0x0/0xc0 @ 146, parent: ata1
Oct 11 17:31:27 ryzen kernel: scsi host0: PM: scsi_bus_suspend+0x0/0xc0 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: ata1: PM: calling ata_port_pm_suspend+0x0/0x50 @ 3813, parent: 0000:02:00.1
Oct 11 17:31:27 ryzen kernel: ata1: PM: ata_port_pm_suspend+0x0/0x50 returned 0 after 26 usecs
Oct 11 17:31:27 ryzen kernel: ahci 0000:02:00.1: PM: calling pci_pm_suspend+0x0/0x170 @ 4527, parent: 0000:00:01.2
Oct 11 17:31:27 ryzen kernel: ahci 0000:02:00.1: PM: pci_pm_suspend+0x0/0x170 returned 0 after 3 usecs
Oct 11 17:31:27 ryzen kernel: pcieport 0000:00:01.2: PM: calling pci_pm_suspend+0x0/0x170 @ 4533, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pcieport 0000:00:01.2: PM: pci_pm_suspend+0x0/0x170 returned 0 after 2 usecs
Oct 11 17:31:27 ryzen kernel: nvme 0000:01:00.0: PM: pci_pm_suspend+0x0/0x170 returned 0 after 807100 usecs
Oct 11 17:31:27 ryzen kernel: pcieport 0000:00:01.1: PM: calling pci_pm_suspend+0x0/0x170 @ 4532, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pcieport 0000:00:01.1: PM: pci_pm_suspend+0x0/0x170 returned 0 after 5 usecs
Oct 11 17:31:27 ryzen kernel: PM: suspend of devices complete after 811.971 msecs
Oct 11 17:31:27 ryzen kernel: PM: start suspend of devices complete after 3119.951 msecs
Oct 11 17:31:27 ryzen kernel: snd_hda_intel 0000:05:00.1: PM: calling pci_pm_suspend_late+0x0/0x40 @ 4532, parent: 0000:00:03.1
Oct 11 17:31:27 ryzen kernel: snd_hda_intel 0000:05:00.1: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: acpi-wmi PNP0C14:01: PM: calling acpi_subsys_suspend_late+0x0/0x50 @ 4494, parent: platform
Oct 11 17:31:27 ryzen kernel: acpi-wmi PNP0C14:01: PM: acpi_subsys_suspend_late+0x0/0x50 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: acpi-wmi PNP0C14:00: PM: calling acpi_subsys_suspend_late+0x0/0x50 @ 4494, parent: platform
Oct 11 17:31:27 ryzen kernel: acpi-wmi PNP0C14:00: PM: acpi_subsys_suspend_late+0x0/0x50 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: pt-gpio AMDIF030:00: PM: calling acpi_subsys_suspend_late+0x0/0x50 @ 4494, parent: platform
Oct 11 17:31:27 ryzen kernel: pt-gpio AMDIF030:00: PM: acpi_subsys_suspend_late+0x0/0x50 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: amd_gpio AMDI0030:00: PM: calling acpi_subsys_suspend_late+0x0/0x50 @ 4494, parent: platform
Oct 11 17:31:27 ryzen kernel: amd_gpio AMDI0030:00: PM: acpi_subsys_suspend_late+0x0/0x50 returned 0 after 8 usecs
Oct 11 17:31:27 ryzen kernel: snd_hda_intel 0000:07:00.4: PM: calling pci_pm_suspend_late+0x0/0x40 @ 4532, parent: 0000:00:08.1
Oct 11 17:31:27 ryzen kernel: xhci_hcd 0000:07:00.3: PM: calling pci_pm_suspend_late+0x0/0x40 @ 4534, parent: 0000:00:08.1
Oct 11 17:31:27 ryzen kernel: ccp 0000:07:00.1: PM: calling pci_pm_suspend_late+0x0/0x40 @ 4529, parent: 0000:00:08.1
Oct 11 17:31:27 ryzen kernel: snd_hda_intel 0000:07:00.4: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: xhci_hcd 0000:07:00.3: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: ccp 0000:07:00.1: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: pci 0000:07:00.0: PM: calling pci_pm_suspend_late+0x0/0x40 @ 4533, parent: 0000:00:08.1
Oct 11 17:31:27 ryzen kernel: pci 0000:06:00.0: PM: calling pci_pm_suspend_late+0x0/0x40 @ 4532, parent: 0000:00:07.1
Oct 11 17:31:27 ryzen kernel: r8169 0000:04:00.0: PM: calling pci_pm_suspend_late+0x0/0x40 @ 4529, parent: 0000:03:09.0
Oct 11 17:31:27 ryzen kernel: amdgpu 0000:05:00.0: PM: calling pci_pm_suspend_late+0x0/0x40 @ 4534, parent: 0000:00:03.1
Oct 11 17:31:27 ryzen kernel: pci 0000:07:00.0: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: pci 0000:06:00.0: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: r8169 0000:04:00.0: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: ahci 0000:02:00.1: PM: calling pci_pm_suspend_late+0x0/0x40 @ 4533, parent: 0000:00:01.2
Oct 11 17:31:27 ryzen kernel: xhci_hcd 0000:02:00.0: PM: calling pci_pm_suspend_late+0x0/0x40 @ 4529, parent: 0000:00:01.2
Oct 11 17:31:27 ryzen kernel: amdgpu 0000:05:00.0: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: nvme 0000:01:00.0: PM: calling pci_pm_suspend_late+0x0/0x40 @ 3813, parent: 0000:00:01.1
Oct 11 17:31:27 ryzen kernel: xhci_hcd 0000:02:00.0: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: ahci 0000:02:00.1: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: pci 0000:00:18.6: PM: calling pci_pm_suspend_late+0x0/0x40 @ 4529, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pcieport 0000:03:09.0: PM: calling pci_pm_suspend_late+0x0/0x40 @ 4527, parent: 0000:02:00.2
Oct 11 17:31:27 ryzen kernel: nvme 0000:01:00.0: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: pci 0000:00:18.5: PM: calling pci_pm_suspend_late+0x0/0x40 @ 4534, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pci 0000:00:18.7: PM: calling pci_pm_suspend_late+0x0/0x40 @ 146, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pci 0000:00:18.4: PM: calling pci_pm_suspend_late+0x0/0x40 @ 4533, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pci 0000:00:18.6: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: pci 0000:00:18.4: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: pci 0000:00:18.5: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: pci 0000:00:18.2: PM: calling pci_pm_suspend_late+0x0/0x40 @ 4529, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pci 0000:00:18.7: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: k10temp 0000:00:18.3: PM: calling pci_pm_suspend_late+0x0/0x40 @ 3813, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pcieport 0000:03:09.0: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: k10temp 0000:00:18.3: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: pci 0000:00:18.0: PM: calling pci_pm_suspend_late+0x0/0x40 @ 4533, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pci 0000:00:18.2: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: pci 0000:00:14.3: PM: calling pci_pm_suspend_late+0x0/0x40 @ 4534, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pci 0000:00:18.1: PM: calling pci_pm_suspend_late+0x0/0x40 @ 145, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: piix4_smbus 0000:00:14.0: PM: calling pci_pm_suspend_late+0x0/0x40 @ 146, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pci 0000:00:14.3: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: pci 0000:00:18.0: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: pci 0000:00:08.0: PM: calling pci_pm_suspend_late+0x0/0x40 @ 3813, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pcieport 0000:00:08.1: PM: calling pci_pm_suspend_late+0x0/0x40 @ 1219, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pci 0000:00:07.0: PM: calling pci_pm_suspend_late+0x0/0x40 @ 4529, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pcieport 0000:00:07.1: PM: calling pci_pm_suspend_late+0x0/0x40 @ 4527, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: piix4_smbus 0000:00:14.0: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: pci 0000:00:08.0: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: pcieport 0000:00:08.1: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: pci 0000:00:18.1: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: pcieport 0000:00:07.1: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: pci 0000:00:04.0: PM: calling pci_pm_suspend_late+0x0/0x40 @ 4534, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pci 0000:00:05.0: PM: calling pci_pm_suspend_late+0x0/0x40 @ 4531, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pci 0000:00:07.0: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: pci 0000:00:03.0: PM: calling pci_pm_suspend_late+0x0/0x40 @ 146, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pcieport 0000:00:03.1: PM: calling pci_pm_suspend_late+0x0/0x40 @ 4533, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pci 0000:00:02.0: PM: calling pci_pm_suspend_late+0x0/0x40 @ 3813, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pci 0000:00:04.0: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: pci 0000:00:05.0: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: pcieport 0000:00:01.1: PM: calling pci_pm_suspend_late+0x0/0x40 @ 1219, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pci 0000:00:01.0: PM: calling pci_pm_suspend_late+0x0/0x40 @ 4529, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pci 0000:00:03.0: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: pcieport 0000:00:03.1: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: pci 0000:00:02.0: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: pcieport 0000:00:01.1: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: pci 0000:00:00.2: PM: calling pci_pm_suspend_late+0x0/0x40 @ 4525, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pci 0000:00:01.0: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: pci 0000:00:00.0: PM: calling pci_pm_suspend_late+0x0/0x40 @ 4527, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pci 0000:00:00.2: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: pci 0000:00:00.0: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: pcieport 0000:02:00.2: PM: calling pci_pm_suspend_late+0x0/0x40 @ 4532, parent: 0000:00:01.2
Oct 11 17:31:27 ryzen kernel: pcieport 0000:02:00.2: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: pcieport 0000:00:01.2: PM: calling pci_pm_suspend_late+0x0/0x40 @ 145, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pcieport 0000:00:01.2: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: PM: late suspend of devices complete after 0.586 msecs
Oct 11 17:31:27 ryzen kernel: snd_hda_intel 0000:05:00.1: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 4532, parent: 0000:00:03.1
Oct 11 17:31:27 ryzen kernel: acpi-wmi PNP0C14:01: PM: calling acpi_subsys_suspend_noirq+0x0/0x50 @ 4494, parent: platform
Oct 11 17:31:27 ryzen kernel: acpi-wmi PNP0C14:01: PM: acpi_subsys_suspend_noirq+0x0/0x50 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: acpi-wmi PNP0C14:00: PM: calling acpi_subsys_suspend_noirq+0x0/0x50 @ 4494, parent: platform
Oct 11 17:31:27 ryzen kernel: acpi-wmi PNP0C14:00: PM: acpi_subsys_suspend_noirq+0x0/0x50 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: pt-gpio AMDIF030:00: PM: calling acpi_subsys_suspend_noirq+0x0/0x50 @ 4494, parent: platform
Oct 11 17:31:27 ryzen kernel: pt-gpio AMDIF030:00: PM: acpi_subsys_suspend_noirq+0x0/0x50 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: amd_gpio AMDI0030:00: PM: calling acpi_subsys_suspend_noirq+0x0/0x50 @ 4494, parent: platform
Oct 11 17:31:27 ryzen kernel: amd_gpio AMDI0030:00: PM: acpi_subsys_suspend_noirq+0x0/0x50 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: snd_hda_intel 0000:07:00.4: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 145, parent: 0000:00:08.1
Oct 11 17:31:27 ryzen kernel: xhci_hcd 0000:07:00.3: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 4531, parent: 0000:00:08.1
Oct 11 17:31:27 ryzen kernel: ccp 0000:07:00.1: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 4527, parent: 0000:00:08.1
Oct 11 17:31:27 ryzen kernel: pci 0000:07:00.0: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 4525, parent: 0000:00:08.1
Oct 11 17:31:27 ryzen kernel: pci 0000:06:00.0: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 4534, parent: 0000:00:07.1
Oct 11 17:31:27 ryzen kernel: r8169 0000:04:00.0: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 4529, parent: 0000:03:09.0
Oct 11 17:31:27 ryzen kernel: ahci 0000:02:00.1: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 4533, parent: 0000:00:01.2
Oct 11 17:31:27 ryzen kernel: xhci_hcd 0000:02:00.0: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 146, parent: 0000:00:01.2
Oct 11 17:31:27 ryzen kernel: nvme 0000:01:00.0: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 3814, parent: 0000:00:01.1
Oct 11 17:31:27 ryzen kernel: pci 0000:00:18.7: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 315, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pci 0000:00:18.6: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 317, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pci 0000:00:18.5: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 316, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pci 0000:00:18.7: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 170 usecs
Oct 11 17:31:27 ryzen kernel: pci 0000:00:18.6: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 170 usecs
Oct 11 17:31:27 ryzen kernel: pci 0000:00:18.4: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 315, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: k10temp 0000:00:18.3: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 317, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pci 0000:07:00.0: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 280 usecs
Oct 11 17:31:27 ryzen kernel: pci 0000:00:18.1: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 4525, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pci 0000:00:18.2: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 4522, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pci 0000:00:18.0: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 147, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pci 0000:00:18.5: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 189 usecs
Oct 11 17:31:27 ryzen kernel: pci 0000:00:14.3: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 316, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pci 0000:06:00.0: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 289 usecs
Oct 11 17:31:27 ryzen kernel: piix4_smbus 0000:00:14.0: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 4534, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pci 0000:00:08.0: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 321, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pci 0000:00:18.4: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 199 usecs
Oct 11 17:31:27 ryzen kernel: k10temp 0000:00:18.3: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 199 usecs
Oct 11 17:31:27 ryzen kernel: pci 0000:00:07.0: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 317, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pcieport 0000:00:07.1: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 315, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pci 0000:00:05.0: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 4530, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pci 0000:00:04.0: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 4523, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pci 0000:00:03.0: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 10, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pci 0000:00:02.0: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 4526, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pci 0000:00:18.2: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 156 usecs
Oct 11 17:31:27 ryzen kernel: pci 0000:00:18.0: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 155 usecs
Oct 11 17:31:27 ryzen kernel: pci 0000:00:01.0: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 4522, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pci 0000:00:14.3: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 154 usecs
Oct 11 17:31:27 ryzen kernel: pci 0000:00:00.2: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 147, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: piix4_smbus 0000:00:14.0: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 154 usecs
Oct 11 17:31:27 ryzen kernel: pci 0000:00:08.0: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 148 usecs
Oct 11 17:31:27 ryzen kernel: pci 0000:00:00.0: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 3803, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pci 0000:00:07.0: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 88 usecs
Oct 11 17:31:27 ryzen kernel: pci 0000:00:05.0: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 90 usecs
Oct 11 17:31:27 ryzen kernel: pci 0000:00:04.0: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 91 usecs
Oct 11 17:31:27 ryzen kernel: pci 0000:00:03.0: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 87 usecs
Oct 11 17:31:27 ryzen kernel: pci 0000:00:02.0: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 86 usecs
Oct 11 17:31:27 ryzen kernel: pci 0000:00:18.1: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 246 usecs
Oct 11 17:31:27 ryzen kernel: pci 0000:00:01.0: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 80 usecs
Oct 11 17:31:27 ryzen kernel: pci 0000:00:00.0: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 79 usecs
Oct 11 17:31:27 ryzen kernel: pci 0000:00:00.2: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 86 usecs
Oct 11 17:31:27 ryzen kernel: snd_hda_intel 0000:05:00.1: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 12063 usecs
Oct 11 17:31:27 ryzen kernel: pcieport 0000:00:07.1: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 11590 usecs
Oct 11 17:31:27 ryzen kernel: amdgpu 0000:05:00.0: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 4528, parent: 0000:00:03.1
Oct 11 17:31:27 ryzen kernel: snd_hda_intel 0000:07:00.4: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 12244 usecs
Oct 11 17:31:27 ryzen kernel: amdgpu 0000:05:00.0: amdgpu: PCI CONFIG reset
Oct 11 17:31:27 ryzen kernel: xhci_hcd 0000:07:00.3: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 12289 usecs
Oct 11 17:31:27 ryzen kernel: ccp 0000:07:00.1: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 12311 usecs
Oct 11 17:31:27 ryzen kernel: pcieport 0000:00:08.1: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 12, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: ahci 0000:02:00.1: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 12333 usecs
Oct 11 17:31:27 ryzen kernel: r8169 0000:04:00.0: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 12473 usecs
Oct 11 17:31:27 ryzen kernel: xhci_hcd 0000:02:00.0: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 12459 usecs
Oct 11 17:31:27 ryzen kernel: pcieport 0000:03:09.0: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 1219, parent: 0000:02:00.2
Oct 11 17:31:27 ryzen kernel: nvme 0000:01:00.0: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 12603 usecs
Oct 11 17:31:27 ryzen kernel: pcieport 0000:00:01.1: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 148, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pcieport 0000:00:08.1: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 12079 usecs
Oct 11 17:31:27 ryzen kernel: amdgpu 0000:05:00.0: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 12487 usecs
Oct 11 17:31:27 ryzen kernel: pcieport 0000:00:03.1: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 3684, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pcieport 0000:03:09.0: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 12253 usecs
Oct 11 17:31:27 ryzen kernel: pcieport 0000:00:01.1: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 12114 usecs
Oct 11 17:31:27 ryzen kernel: pcieport 0000:02:00.2: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 3813, parent: 0000:00:01.2
Oct 11 17:31:27 ryzen kernel: pcieport 0000:00:03.1: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 12306 usecs
Oct 11 17:31:27 ryzen kernel: pcieport 0000:02:00.2: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 12259 usecs
Oct 11 17:31:27 ryzen kernel: pcieport 0000:00:01.2: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 4524, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pcieport 0000:00:01.2: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 12331 usecs
Oct 11 17:31:27 ryzen kernel: PM: noirq suspend of devices complete after 49.961 msecs
Oct 11 17:31:27 ryzen kernel: ACPI: PM: Preparing to enter system sleep state S3
Oct 11 17:31:27 ryzen kernel: ACPI: PM: Saving platform NVS memory
Oct 11 17:31:27 ryzen kernel: Disabling non-boot CPUs ...
Oct 11 17:31:27 ryzen kernel: smpboot: CPU 1 is now offline
Oct 11 17:31:27 ryzen kernel: smpboot: CPU 2 is now offline
Oct 11 17:31:27 ryzen kernel: smpboot: CPU 3 is now offline
Oct 11 17:31:27 ryzen kernel: smpboot: CPU 4 is now offline
Oct 11 17:31:27 ryzen kernel: smpboot: CPU 5 is now offline
Oct 11 17:31:27 ryzen kernel: smpboot: CPU 6 is now offline
Oct 11 17:31:27 ryzen kernel: Spectre V2 : Update user space SMT mitigation: STIBP off
Oct 11 17:31:27 ryzen kernel: smpboot: CPU 7 is now offline
Oct 11 17:31:27 ryzen kernel: smpboot: CPU 8 is now offline
Oct 11 17:31:27 ryzen kernel: smpboot: CPU 9 is now offline
Oct 11 17:31:27 ryzen kernel: smpboot: CPU 10 is now offline
Oct 11 17:31:27 ryzen kernel: smpboot: CPU 11 is now offline
Oct 11 17:31:27 ryzen kernel: Checking wakeup interrupts
Oct 11 17:31:27 ryzen kernel: Calling mce_syscore_suspend+0x0/0x20
Oct 11 17:31:27 ryzen kernel: Calling ledtrig_cpu_syscore_suspend+0x0/0x20
Oct 11 17:31:27 ryzen kernel: Calling timekeeping_suspend+0x0/0x2f0
Oct 11 17:31:27 ryzen kernel: Calling irq_gc_suspend+0x0/0x80
Oct 11 17:31:27 ryzen kernel: Calling save_ioapic_entries+0x0/0xd0
Oct 11 17:31:27 ryzen kernel: Calling i8259A_suspend+0x0/0x30
Oct 11 17:31:27 ryzen kernel: Calling perf_ibs_suspend+0x0/0x40
Oct 11 17:31:27 ryzen kernel: Calling amd_iommu_suspend+0x0/0x50
Oct 11 17:31:27 ryzen kernel: Calling fw_suspend+0x0/0x20
Oct 11 17:31:27 ryzen kernel: Calling acpi_save_bm_rld+0x0/0x30
Oct 11 17:31:27 ryzen kernel: Calling lapic_suspend+0x0/0x210
Oct 11 17:31:27 ryzen kernel: ACPI: PM: Low-level resume complete
Oct 11 17:31:27 ryzen kernel: ACPI: PM: Restoring platform NVS memory
Oct 11 17:31:27 ryzen kernel: Calling lapic_resume+0x0/0x2e0
Oct 11 17:31:27 ryzen kernel: Calling acpi_restore_bm_rld+0x0/0x70
Oct 11 17:31:27 ryzen kernel: Calling irqrouter_resume+0x0/0x50
Oct 11 17:31:27 ryzen kernel: Calling amd_iommu_resume+0x0/0x50
Oct 11 17:31:27 ryzen kernel: Calling perf_ibs_resume+0x0/0x30
Oct 11 17:31:27 ryzen kernel: LVT offset 0 assigned for vector 0x400
Oct 11 17:31:27 ryzen kernel: Calling i8259A_resume+0x0/0x40
Oct 11 17:31:27 ryzen kernel: Calling i8237A_resume+0x0/0xb0
Oct 11 17:31:27 ryzen kernel: Calling ioapic_resume+0x0/0xc0
Oct 11 17:31:27 ryzen kernel: Calling irq_gc_resume+0x0/0x70
Oct 11 17:31:27 ryzen kernel: Calling irq_pm_syscore_resume+0x0/0x20
Oct 11 17:31:27 ryzen kernel: Calling timekeeping_resume+0x0/0x1e0
Oct 11 17:31:27 ryzen kernel: Timekeeping suspended for 4.986 seconds
Oct 11 17:31:27 ryzen kernel: Calling init_counter_refs+0x0/0x40
Oct 11 17:31:27 ryzen kernel: Calling ledtrig_cpu_syscore_resume+0x0/0x20
Oct 11 17:31:27 ryzen kernel: Calling mce_syscore_resume+0x0/0x30
Oct 11 17:31:27 ryzen kernel: Calling microcode_bsp_resume+0x0/0x40
Oct 11 17:31:27 ryzen kernel: Enabling non-boot CPUs ...
Oct 11 17:31:27 ryzen kernel: smpboot: Booting Node 0 Processor 1 APIC 0x2
Oct 11 17:31:27 ryzen kernel: ACPI: \_SB_.PLTF.C002: Found 2 idle states
Oct 11 17:31:27 ryzen kernel: CPU1 is up
Oct 11 17:31:27 ryzen kernel: smpboot: Booting Node 0 Processor 2 APIC 0x4
Oct 11 17:31:27 ryzen kernel: ACPI: \_SB_.PLTF.C004: Found 2 idle states
Oct 11 17:31:27 ryzen kernel: CPU2 is up
Oct 11 17:31:27 ryzen kernel: smpboot: Booting Node 0 Processor 3 APIC 0x6
Oct 11 17:31:27 ryzen kernel: ACPI: \_SB_.PLTF.C006: Found 2 idle states
Oct 11 17:31:27 ryzen kernel: CPU3 is up
Oct 11 17:31:27 ryzen kernel: smpboot: Booting Node 0 Processor 4 APIC 0x8
Oct 11 17:31:27 ryzen kernel: ACPI: \_SB_.PLTF.C008: Found 2 idle states
Oct 11 17:31:27 ryzen kernel: CPU4 is up
Oct 11 17:31:27 ryzen kernel: smpboot: Booting Node 0 Processor 5 APIC 0xa
Oct 11 17:31:27 ryzen kernel: ACPI: \_SB_.PLTF.C00A: Found 2 idle states
Oct 11 17:31:27 ryzen kernel: CPU5 is up
Oct 11 17:31:27 ryzen kernel: smpboot: Booting Node 0 Processor 6 APIC 0x1
Oct 11 17:31:27 ryzen kernel: ACPI: \_SB_.PLTF.C001: Found 2 idle states
Oct 11 17:31:27 ryzen kernel: Spectre V2 : Update user space SMT mitigation: STIBP always-on
Oct 11 17:31:27 ryzen kernel: CPU6 is up
Oct 11 17:31:27 ryzen kernel: smpboot: Booting Node 0 Processor 7 APIC 0x3
Oct 11 17:31:27 ryzen kernel: ACPI: \_SB_.PLTF.C003: Found 2 idle states
Oct 11 17:31:27 ryzen kernel: CPU7 is up
Oct 11 17:31:27 ryzen kernel: smpboot: Booting Node 0 Processor 8 APIC 0x5
Oct 11 17:31:27 ryzen kernel: ACPI: \_SB_.PLTF.C005: Found 2 idle states
Oct 11 17:31:27 ryzen kernel: CPU8 is up
Oct 11 17:31:27 ryzen kernel: smpboot: Booting Node 0 Processor 9 APIC 0x7
Oct 11 17:31:27 ryzen kernel: ACPI: \_SB_.PLTF.C007: Found 2 idle states
Oct 11 17:31:27 ryzen kernel: CPU9 is up
Oct 11 17:31:27 ryzen kernel: smpboot: Booting Node 0 Processor 10 APIC 0x9
Oct 11 17:31:27 ryzen kernel: ACPI: \_SB_.PLTF.C009: Found 2 idle states
Oct 11 17:31:27 ryzen kernel: CPU10 is up
Oct 11 17:31:27 ryzen kernel: smpboot: Booting Node 0 Processor 11 APIC 0xb
Oct 11 17:31:27 ryzen kernel: ACPI: \_SB_.PLTF.C00B: Found 2 idle states
Oct 11 17:31:27 ryzen kernel: CPU11 is up
Oct 11 17:31:27 ryzen kernel: ACPI: PM: Waking up from system sleep state S3
Oct 11 17:31:27 ryzen kernel: pcieport 0000:00:01.2: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 1219, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pci 0000:00:01.0: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 3813, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pci 0000:00:00.2: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 316, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pci 0000:00:02.0: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 4524, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pcieport 0000:00:01.1: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 148, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pci 0000:00:00.0: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 3684, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pci 0000:00:03.0: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 4528, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pcieport 0000:00:03.1: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 12, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pci 0000:00:04.0: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 3814, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pci 0000:00:05.0: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 146, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pci 0000:00:07.0: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 4529, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pcieport 0000:00:07.1: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 4533, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pci 0000:00:03.0: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 233 usecs
Oct 11 17:31:27 ryzen kernel: pci 0000:00:08.0: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 4528, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pci 0000:00:02.0: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 238 usecs
Oct 11 17:31:27 ryzen kernel: pcieport 0000:00:08.1: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 4524, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pci 0000:00:01.0: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 243 usecs
Oct 11 17:31:27 ryzen kernel: piix4_smbus 0000:00:14.0: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 3813, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pci 0000:00:04.0: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 247 usecs
Oct 11 17:31:27 ryzen kernel: pci 0000:00:14.3: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 3814, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pci 0000:00:05.0: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 255 usecs
Oct 11 17:31:27 ryzen kernel: pci 0000:00:18.0: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 146, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pci 0000:00:07.0: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 249 usecs
Oct 11 17:31:27 ryzen kernel: pci 0000:00:00.0: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 282 usecs
Oct 11 17:31:27 ryzen kernel: pci 0000:00:18.1: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 3684, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pci 0000:00:18.2: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 4529, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pci 0000:00:08.0: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 183 usecs
Oct 11 17:31:27 ryzen kernel: pci 0000:00:00.2: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 429 usecs
Oct 11 17:31:27 ryzen kernel: k10temp 0000:00:18.3: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 4528, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pci 0000:00:18.4: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 316, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: piix4_smbus 0000:00:14.0: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 182 usecs
Oct 11 17:31:27 ryzen kernel: pci 0000:00:18.5: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 3813, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pci 0000:00:14.3: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 176 usecs
Oct 11 17:31:27 ryzen kernel: pci 0000:00:18.0: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 169 usecs
Oct 11 17:31:27 ryzen kernel: pci 0000:00:18.6: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 3814, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pci 0000:00:18.1: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 166 usecs
Oct 11 17:31:27 ryzen kernel: pci 0000:00:18.2: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 167 usecs
Oct 11 17:31:27 ryzen kernel: pci 0000:00:18.7: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 146, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: k10temp 0000:00:18.3: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 99 usecs
Oct 11 17:31:27 ryzen kernel: pci 0000:00:18.4: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 96 usecs
Oct 11 17:31:27 ryzen kernel: pci 0000:00:18.5: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 95 usecs
Oct 11 17:31:27 ryzen kernel: amd_gpio AMDI0030:00: PM: calling acpi_subsys_resume_noirq+0x0/0x30 @ 4494, parent: platform
Oct 11 17:31:27 ryzen kernel: pci 0000:00:18.6: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 94 usecs
Oct 11 17:31:27 ryzen kernel: amd_gpio AMDI0030:00: PM: acpi_subsys_resume_noirq+0x0/0x30 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: pci 0000:00:18.7: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 94 usecs
Oct 11 17:31:27 ryzen kernel: pt-gpio AMDIF030:00: PM: calling acpi_subsys_resume_noirq+0x0/0x30 @ 4494, parent: platform
Oct 11 17:31:27 ryzen kernel: pt-gpio AMDIF030:00: PM: acpi_subsys_resume_noirq+0x0/0x30 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: pcieport 0000:00:01.2: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 566 usecs
Oct 11 17:31:27 ryzen kernel: acpi-wmi PNP0C14:00: PM: calling acpi_subsys_resume_noirq+0x0/0x30 @ 4494, parent: platform
Oct 11 17:31:27 ryzen kernel: acpi-wmi PNP0C14:00: PM: acpi_subsys_resume_noirq+0x0/0x30 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: pcieport 0000:00:01.1: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 572 usecs
Oct 11 17:31:27 ryzen kernel: xhci_hcd 0000:02:00.0: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 4529, parent: 0000:00:01.2
Oct 11 17:31:27 ryzen kernel: ahci 0000:02:00.1: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 4528, parent: 0000:00:01.2
Oct 11 17:31:27 ryzen kernel: acpi-wmi PNP0C14:01: PM: calling acpi_subsys_resume_noirq+0x0/0x30 @ 4494, parent: platform
Oct 11 17:31:27 ryzen kernel: pcieport 0000:02:00.2: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 316, parent: 0000:00:01.2
Oct 11 17:31:27 ryzen kernel: nvme 0000:01:00.0: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 3684, parent: 0000:00:01.1
Oct 11 17:31:27 ryzen kernel: pcieport 0000:00:07.1: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 539 usecs
Oct 11 17:31:27 ryzen kernel: acpi-wmi PNP0C14:01: PM: acpi_subsys_resume_noirq+0x0/0x30 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: pcieport 0000:00:03.1: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 574 usecs
Oct 11 17:31:27 ryzen kernel: pci 0000:06:00.0: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 3814, parent: 0000:00:07.1
Oct 11 17:31:27 ryzen kernel: amdgpu 0000:05:00.0: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 4531, parent: 0000:00:03.1
Oct 11 17:31:27 ryzen kernel: i8042 i8042: PM: calling i8042_pm_resume_noirq+0x0/0x30 [i8042] @ 4494, parent: platform
Oct 11 17:31:27 ryzen kernel: i8042 i8042: PM: i8042_pm_resume_noirq+0x0/0x30 [i8042] returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: pcieport 0000:00:08.1: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 505 usecs
Oct 11 17:31:27 ryzen kernel: snd_hda_intel 0000:07:00.4: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 4532, parent: 0000:00:08.1
Oct 11 17:31:27 ryzen kernel: xhci_hcd 0000:07:00.3: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 315, parent: 0000:00:08.1
Oct 11 17:31:27 ryzen kernel: ccp 0000:07:00.1: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 145, parent: 0000:00:08.1
Oct 11 17:31:27 ryzen kernel: pci 0000:07:00.0: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 146, parent: 0000:00:08.1
Oct 11 17:31:27 ryzen kernel: pci 0000:06:00.0: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 627 usecs
Oct 11 17:31:27 ryzen kernel: nvme 0000:01:00.0: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 653 usecs
Oct 11 17:31:27 ryzen kernel: pcieport 0000:02:00.2: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 683 usecs
Oct 11 17:31:27 ryzen kernel: pcieport 0000:03:09.0: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 3813, parent: 0000:02:00.2
Oct 11 17:31:27 ryzen kernel: ahci 0000:02:00.1: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 708 usecs
Oct 11 17:31:27 ryzen kernel: pci 0000:07:00.0: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 543 usecs
Oct 11 17:31:27 ryzen kernel: xhci_hcd 0000:02:00.0: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 736 usecs
Oct 11 17:31:27 ryzen kernel: snd_hda_intel 0000:07:00.4: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 590 usecs
Oct 11 17:31:27 ryzen kernel: ccp 0000:07:00.1: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 623 usecs
Oct 11 17:31:27 ryzen kernel: amdgpu 0000:05:00.0: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 812 usecs
Oct 11 17:31:27 ryzen kernel: xhci_hcd 0000:07:00.3: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 647 usecs
Oct 11 17:31:27 ryzen kernel: snd_hda_intel 0000:05:00.1: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 1219, parent: 0000:00:03.1
Oct 11 17:31:27 ryzen kernel: pcieport 0000:03:09.0: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 231 usecs
Oct 11 17:31:27 ryzen kernel: r8169 0000:04:00.0: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 4527, parent: 0000:03:09.0
Oct 11 17:31:27 ryzen kernel: snd_hda_intel 0000:05:00.1: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 166 usecs
Oct 11 17:31:27 ryzen kernel: r8169 0000:04:00.0: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 244 usecs
Oct 11 17:31:27 ryzen kernel: PM: noirq resume of devices complete after 1.923 msecs
Oct 11 17:31:27 ryzen kernel: pcieport 0000:00:01.2: PM: calling pci_pm_resume_early+0x0/0x30 @ 4574, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pci 0000:00:00.2: PM: calling pci_pm_resume_early+0x0/0x30 @ 3813, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pci 0000:00:03.0: PM: calling pci_pm_resume_early+0x0/0x30 @ 4571, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pci 0000:00:05.0: PM: calling pci_pm_resume_early+0x0/0x30 @ 4527, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pci 0000:00:02.0: PM: calling pci_pm_resume_early+0x0/0x30 @ 4573, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pcieport 0000:00:03.1: PM: calling pci_pm_resume_early+0x0/0x30 @ 4572, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pcieport 0000:00:01.1: PM: calling pci_pm_resume_early+0x0/0x30 @ 316, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pci 0000:00:01.0: PM: calling pci_pm_resume_early+0x0/0x30 @ 4581, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pci 0000:00:04.0: PM: calling pci_pm_resume_early+0x0/0x30 @ 4580, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pci 0000:00:00.0: PM: calling pci_pm_resume_early+0x0/0x30 @ 1219, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pci 0000:00:03.0: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: pci 0000:00:00.2: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: pci 0000:00:02.0: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: pci 0000:00:05.0: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: pcieport 0000:00:03.1: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: pci 0000:00:04.0: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: pci 0000:00:01.0: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: pcieport 0000:00:01.1: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: pci 0000:00:00.0: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: pcieport 0000:00:01.2: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: pci 0000:00:07.0: PM: calling pci_pm_resume_early+0x0/0x30 @ 3813, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pcieport 0000:00:07.1: PM: calling pci_pm_resume_early+0x0/0x30 @ 4527, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pci 0000:00:08.0: PM: calling pci_pm_resume_early+0x0/0x30 @ 4573, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pcieport 0000:00:08.1: PM: calling pci_pm_resume_early+0x0/0x30 @ 4572, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: piix4_smbus 0000:00:14.0: PM: calling pci_pm_resume_early+0x0/0x30 @ 4571, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pci 0000:00:14.3: PM: calling pci_pm_resume_early+0x0/0x30 @ 1219, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pcieport 0000:00:07.1: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: pci 0000:00:18.0: PM: calling pci_pm_resume_early+0x0/0x30 @ 4581, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pci 0000:00:18.1: PM: calling pci_pm_resume_early+0x0/0x30 @ 316, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pci 0000:00:08.0: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: pci 0000:00:18.2: PM: calling pci_pm_resume_early+0x0/0x30 @ 4574, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pci 0000:00:07.0: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: pcieport 0000:00:08.1: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: piix4_smbus 0000:00:14.0: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: pci 0000:00:14.3: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: k10temp 0000:00:18.3: PM: calling pci_pm_resume_early+0x0/0x30 @ 4580, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pci 0000:00:18.2: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: pci 0000:00:18.1: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: pci 0000:00:18.4: PM: calling pci_pm_resume_early+0x0/0x30 @ 4527, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pci 0000:00:18.5: PM: calling pci_pm_resume_early+0x0/0x30 @ 3813, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pci 0000:00:18.6: PM: calling pci_pm_resume_early+0x0/0x30 @ 4573, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pci 0000:00:18.7: PM: calling pci_pm_resume_early+0x0/0x30 @ 4572, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: nvme 0000:01:00.0: PM: calling pci_pm_resume_early+0x0/0x30 @ 4571, parent: 0000:00:01.1
Oct 11 17:31:27 ryzen kernel: pci 0000:00:18.0: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: xhci_hcd 0000:02:00.0: PM: calling pci_pm_resume_early+0x0/0x30 @ 1219, parent: 0000:00:01.2
Oct 11 17:31:27 ryzen kernel: ahci 0000:02:00.1: PM: calling pci_pm_resume_early+0x0/0x30 @ 4574, parent: 0000:00:01.2
Oct 11 17:31:27 ryzen kernel: pci 0000:00:18.5: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: pci 0000:00:18.4: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: pcieport 0000:02:00.2: PM: calling pci_pm_resume_early+0x0/0x30 @ 316, parent: 0000:00:01.2
Oct 11 17:31:27 ryzen kernel: pci 0000:00:18.6: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: pci 0000:00:18.7: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: nvme 0000:01:00.0: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: k10temp 0000:00:18.3: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: xhci_hcd 0000:02:00.0: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: pcieport 0000:02:00.2: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: pci 0000:06:00.0: PM: calling pci_pm_resume_early+0x0/0x30 @ 4573, parent: 0000:00:07.1
Oct 11 17:31:27 ryzen kernel: amdgpu 0000:05:00.0: PM: calling pci_pm_resume_early+0x0/0x30 @ 3813, parent: 0000:00:03.1
Oct 11 17:31:27 ryzen kernel: pci 0000:07:00.0: PM: calling pci_pm_resume_early+0x0/0x30 @ 4572, parent: 0000:00:08.1
Oct 11 17:31:27 ryzen kernel: ccp 0000:07:00.1: PM: calling pci_pm_resume_early+0x0/0x30 @ 4571, parent: 0000:00:08.1
Oct 11 17:31:27 ryzen kernel: ahci 0000:02:00.1: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: xhci_hcd 0000:07:00.3: PM: calling pci_pm_resume_early+0x0/0x30 @ 4580, parent: 0000:00:08.1
Oct 11 17:31:27 ryzen kernel: amdgpu 0000:05:00.0: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: snd_hda_intel 0000:07:00.4: PM: calling pci_pm_resume_early+0x0/0x30 @ 316, parent: 0000:00:08.1
Oct 11 17:31:27 ryzen kernel: pci 0000:07:00.0: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: ccp 0000:07:00.1: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: xhci_hcd 0000:07:00.3: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: pcieport 0000:03:09.0: PM: calling pci_pm_resume_early+0x0/0x30 @ 4581, parent: 0000:02:00.2
Oct 11 17:31:27 ryzen kernel: pci 0000:06:00.0: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: snd_hda_intel 0000:07:00.4: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: pcieport 0000:03:09.0: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: snd_hda_intel 0000:05:00.1: PM: calling pci_pm_resume_early+0x0/0x30 @ 1219, parent: 0000:00:03.1
Oct 11 17:31:27 ryzen kernel: snd_hda_intel 0000:05:00.1: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: r8169 0000:04:00.0: PM: calling pci_pm_resume_early+0x0/0x30 @ 4527, parent: 0000:03:09.0
Oct 11 17:31:27 ryzen kernel: r8169 0000:04:00.0: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: amd_gpio AMDI0030:00: PM: calling acpi_subsys_resume_early+0x0/0x80 @ 4494, parent: platform
Oct 11 17:31:27 ryzen kernel: amd_gpio AMDI0030:00: PM: acpi_subsys_resume_early+0x0/0x80 returned 0 after 12 usecs
Oct 11 17:31:27 ryzen kernel: pt-gpio AMDIF030:00: PM: calling acpi_subsys_resume_early+0x0/0x80 @ 4494, parent: platform
Oct 11 17:31:27 ryzen kernel: pt-gpio AMDIF030:00: PM: acpi_subsys_resume_early+0x0/0x80 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: acpi-wmi PNP0C14:00: PM: calling acpi_subsys_resume_early+0x0/0x80 @ 4494, parent: platform
Oct 11 17:31:27 ryzen kernel: acpi-wmi PNP0C14:00: PM: acpi_subsys_resume_early+0x0/0x80 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: acpi-wmi PNP0C14:01: PM: calling acpi_subsys_resume_early+0x0/0x80 @ 4494, parent: platform
Oct 11 17:31:27 ryzen kernel: acpi-wmi PNP0C14:01: PM: acpi_subsys_resume_early+0x0/0x80 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: PM: early resume of devices complete after 0.211 msecs
Oct 11 17:31:27 ryzen kernel: pci 0000:00:00.2: PM: calling pci_pm_resume+0x0/0xf0 @ 4572, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pci 0000:00:00.0: PM: calling pci_pm_resume+0x0/0xf0 @ 4573, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pci 0000:00:01.0: PM: calling pci_pm_resume+0x0/0xf0 @ 4574, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pcieport 0000:00:03.1: PM: calling pci_pm_resume+0x0/0xf0 @ 4570, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pcieport 0000:00:01.1: PM: calling pci_pm_resume+0x0/0xf0 @ 4580, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pci 0000:00:03.0: PM: calling pci_pm_resume+0x0/0xf0 @ 316, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pci 0000:00:02.0: PM: calling pci_pm_resume+0x0/0xf0 @ 4581, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pcieport 0000:00:01.2: PM: calling pci_pm_resume+0x0/0xf0 @ 4527, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pci 0000:00:07.0: PM: calling pci_pm_resume+0x0/0xf0 @ 1219, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pcieport 0000:00:07.1: PM: calling pci_pm_resume+0x0/0xf0 @ 4579, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pci 0000:00:04.0: PM: calling pci_pm_resume+0x0/0xf0 @ 4566, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pci 0000:00:02.0: PM: pci_pm_resume+0x0/0xf0 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: pci 0000:00:03.0: PM: pci_pm_resume+0x0/0xf0 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: pci 0000:00:01.0: PM: pci_pm_resume+0x0/0xf0 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: pci 0000:00:07.0: PM: pci_pm_resume+0x0/0xf0 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: pci 0000:00:00.0: PM: pci_pm_resume+0x0/0xf0 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: pci 0000:00:04.0: PM: pci_pm_resume+0x0/0xf0 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: pcieport 0000:00:01.2: PM: pci_pm_resume+0x0/0xf0 returned 0 after 1 usecs
Oct 11 17:31:27 ryzen kernel: pci 0000:00:08.0: PM: calling pci_pm_resume+0x0/0xf0 @ 316, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pcieport 0000:00:08.1: PM: calling pci_pm_resume+0x0/0xf0 @ 4574, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: piix4_smbus 0000:00:14.0: PM: calling pci_pm_resume+0x0/0xf0 @ 1219, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pci 0000:00:14.3: PM: calling pci_pm_resume+0x0/0xf0 @ 4573, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pci 0000:00:18.0: PM: calling pci_pm_resume+0x0/0xf0 @ 4566, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pci 0000:00:18.1: PM: calling pci_pm_resume+0x0/0xf0 @ 4527, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pci 0000:00:18.2: PM: calling pci_pm_resume+0x0/0xf0 @ 4581, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pci 0000:00:00.2: PM: pci_pm_resume+0x0/0xf0 returned 0 after 3 usecs
Oct 11 17:31:27 ryzen kernel: piix4_smbus 0000:00:14.0: PM: pci_pm_resume+0x0/0xf0 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: pci 0000:00:14.3: PM: pci_pm_resume+0x0/0xf0 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: pci 0000:00:18.1: PM: pci_pm_resume+0x0/0xf0 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: pci 0000:00:18.0: PM: pci_pm_resume+0x0/0xf0 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: pci 0000:00:18.2: PM: pci_pm_resume+0x0/0xf0 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: pcieport 0000:00:01.1: PM: pci_pm_resume+0x0/0xf0 returned 0 after 8 usecs
Oct 11 17:31:27 ryzen kernel: pci 0000:00:08.0: PM: pci_pm_resume+0x0/0xf0 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: k10temp 0000:00:18.3: PM: calling pci_pm_resume+0x0/0xf0 @ 4573, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pci 0000:00:18.4: PM: calling pci_pm_resume+0x0/0xf0 @ 1219, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pci 0000:00:18.5: PM: calling pci_pm_resume+0x0/0xf0 @ 4527, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pci 0000:00:18.6: PM: calling pci_pm_resume+0x0/0xf0 @ 4566, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pci 0000:00:18.7: PM: calling pci_pm_resume+0x0/0xf0 @ 4581, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: k10temp 0000:00:18.3: PM: pci_pm_resume+0x0/0xf0 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: xhci_hcd 0000:02:00.0: PM: calling pci_pm_resume+0x0/0xf0 @ 316, parent: 0000:00:01.2
Oct 11 17:31:27 ryzen kernel: pci 0000:00:18.4: PM: pci_pm_resume+0x0/0xf0 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: pci 0000:00:18.5: PM: pci_pm_resume+0x0/0xf0 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: pci 0000:00:18.7: PM: pci_pm_resume+0x0/0xf0 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: pci 0000:00:18.6: PM: pci_pm_resume+0x0/0xf0 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: ahci 0000:02:00.1: PM: calling pci_pm_resume+0x0/0xf0 @ 4573, parent: 0000:00:01.2
Oct 11 17:31:27 ryzen kernel: pcieport 0000:02:00.2: PM: calling pci_pm_resume+0x0/0xf0 @ 4527, parent: 0000:00:01.2
Oct 11 17:31:27 ryzen kernel: pci 0000:00:05.0: PM: calling pci_pm_resume+0x0/0xf0 @ 4568, parent: pci0000:00
Oct 11 17:31:27 ryzen kernel: pcieport 0000:00:03.1: PM: pci_pm_resume+0x0/0xf0 returned 0 after 14 usecs
Oct 11 17:31:27 ryzen kernel: reg-dummy reg-dummy: PM: calling platform_pm_resume+0x0/0x50 @ 4494, parent: platform
Oct 11 17:31:27 ryzen kernel: pci 0000:00:05.0: PM: pci_pm_resume+0x0/0xf0 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: pcieport 0000:02:00.2: PM: pci_pm_resume+0x0/0xf0 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: nvme 0000:01:00.0: PM: calling pci_pm_resume+0x0/0xf0 @ 4572, parent: 0000:00:01.1
Oct 11 17:31:27 ryzen kernel: reg-dummy reg-dummy: PM: platform_pm_resume+0x0/0x50 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: amdgpu 0000:05:00.0: PM: calling pci_pm_resume+0x0/0xf0 @ 1219, parent: 0000:00:03.1
Oct 11 17:31:27 ryzen kernel: pcieport 0000:00:07.1: PM: pci_pm_resume+0x0/0xf0 returned 0 after 20 usecs
Oct 11 17:31:27 ryzen kernel: nvme 0000:01:00.0: PM: pci_pm_resume+0x0/0xf0 returned 0 after 1 usecs
Oct 11 17:31:27 ryzen kernel: pcieport 0000:03:09.0: PM: calling pci_pm_resume+0x0/0xf0 @ 4581, parent: 0000:02:00.2
Oct 11 17:31:27 ryzen kernel: regulator regulator.0: PM: calling regulator_resume+0x0/0x190 @ 4494, parent: reg-dummy
Oct 11 17:31:27 ryzen kernel: pcieport 0000:00:08.1: PM: pci_pm_resume+0x0/0xf0 returned 0 after 19 usecs
Oct 11 17:31:27 ryzen kernel: regulator regulator.0: PM: regulator_resume+0x0/0x190 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: pci 0000:06:00.0: PM: calling pci_pm_resume+0x0/0xf0 @ 4580, parent: 0000:00:07.1
Oct 11 17:31:27 ryzen kernel: pci 0000:06:00.0: PM: pci_pm_resume+0x0/0xf0 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: PCCT PCCT: PM: calling platform_pm_resume+0x0/0x50 @ 4494, parent: platform
Oct 11 17:31:27 ryzen kernel: pci 0000:07:00.0: PM: calling pci_pm_resume+0x0/0xf0 @ 4570, parent: 0000:00:08.1
Oct 11 17:31:27 ryzen kernel: ccp 0000:07:00.1: PM: calling pci_pm_resume+0x0/0xf0 @ 4527, parent: 0000:00:08.1
Oct 11 17:31:27 ryzen kernel: PCCT PCCT: PM: platform_pm_resume+0x0/0x50 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: xhci_hcd 0000:07:00.3: PM: calling pci_pm_resume+0x0/0xf0 @ 4568, parent: 0000:00:08.1
Oct 11 17:31:27 ryzen kernel: snd_hda_intel 0000:07:00.4: PM: calling pci_pm_resume+0x0/0xf0 @ 4572, parent: 0000:00:08.1
Oct 11 17:31:27 ryzen kernel: pci 0000:07:00.0: PM: pci_pm_resume+0x0/0xf0 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: ccp 0000:07:00.1: PM: pci_pm_resume+0x0/0xf0 returned 0 after 1 usecs
Oct 11 17:31:27 ryzen kernel: pcieport 0000:03:09.0: PM: pci_pm_resume+0x0/0xf0 returned 0 after 26 usecs
Oct 11 17:31:27 ryzen kernel: button PNP0C0C:00: PM: calling acpi_button_resume+0x0/0x110 @ 4494, parent: LNXSYBUS:00
Oct 11 17:31:27 ryzen kernel: button PNP0C0C:00: PM: acpi_button_resume+0x0/0x110 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: r8169 0000:04:00.0: PM: calling pci_pm_resume+0x0/0xf0 @ 4566, parent: 0000:03:09.0
Oct 11 17:31:27 ryzen kernel: tpm_crb MSFT0101:00: PM: calling tpm_pm_resume+0x0/0x30 @ 4494, parent: LNXSYBUS:00
Oct 11 17:31:27 ryzen kernel: tpm_crb MSFT0101:00: PM: tpm_pm_resume+0x0/0x30 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: xhci_hcd 0000:02:00.0: xHC error in resume, USBSTS 0x401, Reinit
Oct 11 17:31:27 ryzen kernel: thermal LNXTHERM:00: PM: calling acpi_thermal_resume+0x0/0xf0 @ 4494, parent: LNXSYBUS:01
Oct 11 17:31:27 ryzen kernel: usb usb1: root hub lost power or was reset
Oct 11 17:31:27 ryzen kernel: usb usb2: root hub lost power or was reset
Oct 11 17:31:27 ryzen kernel: thermal LNXTHERM:00: PM: acpi_thermal_resume+0x0/0xf0 returned 0 after 2 usecs
Oct 11 17:31:27 ryzen kernel: thermal LNXTHERM:01: PM: calling acpi_thermal_resume+0x0/0xf0 @ 4494, parent: LNXSYBUS:01
Oct 11 17:31:27 ryzen kernel: thermal LNXTHERM:01: PM: acpi_thermal_resume+0x0/0xf0 returned 0 after 1 usecs
Oct 11 17:31:27 ryzen kernel: ahci 0000:02:00.1: PM: pci_pm_resume+0x0/0xf0 returned 0 after 86 usecs
Oct 11 17:31:27 ryzen kernel: platform PNP0800:00: PM: calling platform_pm_resume+0x0/0x50 @ 4494, parent: 0000:00:14.3
Oct 11 17:31:27 ryzen kernel: platform PNP0800:00: PM: platform_pm_resume+0x0/0x50 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: platform PNP0C0C:00: PM: calling platform_pm_resume+0x0/0x50 @ 4494, parent: platform
Oct 11 17:31:27 ryzen kernel: ata1: PM: calling ata_port_pm_resume+0x0/0x60 @ 4574, parent: 0000:02:00.1
Oct 11 17:31:27 ryzen kernel: ata2: PM: calling ata_port_pm_resume+0x0/0x60 @ 4571, parent: 0000:02:00.1
Oct 11 17:31:27 ryzen kernel: ata4: PM: calling ata_port_pm_resume+0x0/0x60 @ 4567, parent: 0000:02:00.1
Oct 11 17:31:27 ryzen kernel: ata6: PM: calling ata_port_pm_resume+0x0/0x60 @ 4565, parent: 0000:02:00.1
Oct 11 17:31:27 ryzen kernel: ata5: PM: calling ata_port_pm_resume+0x0/0x60 @ 4579, parent: 0000:02:00.1
Oct 11 17:31:27 ryzen kernel: ata3: PM: calling ata_port_pm_resume+0x0/0x60 @ 4580, parent: 0000:02:00.1
Oct 11 17:31:27 ryzen kernel: platform PNP0C0C:00: PM: platform_pm_resume+0x0/0x50 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: amd_gpio AMDI0030:00: PM: calling acpi_subsys_resume+0x0/0x80 @ 4494, parent: platform
Oct 11 17:31:27 ryzen kernel: ata2: PM: ata_port_pm_resume+0x0/0x60 returned 0 after 3 usecs
Oct 11 17:31:27 ryzen kernel: amd_gpio AMDI0030:00: PM: acpi_subsys_resume+0x0/0x80 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: ata4: PM: ata_port_pm_resume+0x0/0x60 returned 0 after 6 usecs
Oct 11 17:31:27 ryzen kernel: platform MSFT0101:00: PM: calling platform_pm_resume+0x0/0x50 @ 4494, parent: platform
Oct 11 17:31:27 ryzen kernel: platform MSFT0101:00: PM: platform_pm_resume+0x0/0x50 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: ata6: PM: ata_port_pm_resume+0x0/0x60 returned 0 after 11 usecs
Oct 11 17:31:27 ryzen kernel: acpi-cpufreq acpi-cpufreq: PM: calling platform_pm_resume+0x0/0x50 @ 4494, parent: platform
Oct 11 17:31:27 ryzen kernel: scsi host1: PM: calling scsi_bus_resume+0x0/0x90 @ 4527, parent: ata2
Oct 11 17:31:27 ryzen kernel: scsi host3: PM: calling scsi_bus_resume+0x0/0x90 @ 4569, parent: ata4
Oct 11 17:31:27 ryzen kernel: acpi-cpufreq acpi-cpufreq: PM: platform_pm_resume+0x0/0x50 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: ata3: PM: ata_port_pm_resume+0x0/0x60 returned 0 after 13 usecs
Oct 11 17:31:27 ryzen kernel: scsi host1: PM: scsi_bus_resume+0x0/0x90 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: scsi host3: PM: scsi_bus_resume+0x0/0x90 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: ata1: PM: ata_port_pm_resume+0x0/0x60 returned 0 after 15 usecs
Oct 11 17:31:27 ryzen kernel: pt-gpio AMDIF030:00: PM: calling acpi_subsys_resume+0x0/0x80 @ 4494, parent: platform
Oct 11 17:31:27 ryzen kernel: scsi target1:0:0: PM: calling scsi_bus_resume+0x0/0x90 @ 4581, parent: host1
Oct 11 17:31:27 ryzen kernel: pt-gpio AMDIF030:00: PM: acpi_subsys_resume+0x0/0x80 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: scsi target1:0:0: PM: scsi_bus_resume+0x0/0x90 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: scsi host0: PM: calling scsi_bus_resume+0x0/0x90 @ 4570, parent: ata1
Oct 11 17:31:27 ryzen kernel: scsi host2: PM: calling scsi_bus_resume+0x0/0x90 @ 4564, parent: ata3
Oct 11 17:31:27 ryzen kernel: platform PNP0103:00: PM: calling platform_pm_resume+0x0/0x50 @ 4494, parent: platform
Oct 11 17:31:27 ryzen kernel: scsi host0: PM: scsi_bus_resume+0x0/0x90 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: scsi host2: PM: scsi_bus_resume+0x0/0x90 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: platform PNP0103:00: PM: platform_pm_resume+0x0/0x50 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: scsi host5: PM: calling scsi_bus_resume+0x0/0x90 @ 315, parent: ata6
Oct 11 17:31:27 ryzen kernel: sr 1:0:0:0: PM: calling scsi_bus_resume+0x0/0x90 @ 4522, parent: target1:0:0
Oct 11 17:31:27 ryzen kernel: scsi target0:0:0: PM: calling scsi_bus_resume+0x0/0x90 @ 4531, parent: host0
Oct 11 17:31:27 ryzen kernel: acpi-wmi PNP0C14:00: PM: calling acpi_subsys_resume+0x0/0x80 @ 4494, parent: platform
Oct 11 17:31:27 ryzen kernel: scsi host5: PM: scsi_bus_resume+0x0/0x90 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: ata5: PM: ata_port_pm_resume+0x0/0x60 returned 0 after 33 usecs
Oct 11 17:31:27 ryzen kernel: acpi-wmi PNP0C14:00: PM: acpi_subsys_resume+0x0/0x80 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: sr 1:0:0:0: PM: scsi_bus_resume+0x0/0x90 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: scsi target0:0:0: PM: scsi_bus_resume+0x0/0x90 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: acpi-wmi PNP0C14:01: PM: calling acpi_subsys_resume+0x0/0x80 @ 4494, parent: platform
Oct 11 17:31:27 ryzen kernel: sd 0:0:0:0: PM: calling scsi_bus_resume+0x0/0x90 @ 145, parent: target0:0:0
Oct 11 17:31:27 ryzen kernel: acpi-wmi PNP0C14:01: PM: acpi_subsys_resume+0x0/0x80 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: button LNXPWRBN:00: PM: calling acpi_button_resume+0x0/0x110 @ 4494, parent: LNXSYSTM:00
Oct 11 17:31:27 ryzen kernel: sd 0:0:0:0: PM: scsi_bus_resume+0x0/0x90 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: button LNXPWRBN:00: PM: acpi_button_resume+0x0/0x110 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: platform rtc-efi.0: PM: calling platform_pm_resume+0x0/0x50 @ 4494, parent: platform
Oct 11 17:31:27 ryzen kernel: platform rtc-efi.0: PM: platform_pm_resume+0x0/0x50 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: platform efivars.0: PM: calling platform_pm_resume+0x0/0x50 @ 4494, parent: platform
Oct 11 17:31:27 ryzen kernel: platform efivars.0: PM: platform_pm_resume+0x0/0x50 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: system 00:00: PM: calling pnp_bus_resume+0x0/0xa0 @ 4494, parent: pnp0
Oct 11 17:31:27 ryzen kernel: system 00:00: PM: pnp_bus_resume+0x0/0xa0 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: system 00:01: PM: calling pnp_bus_resume+0x0/0xa0 @ 4494, parent: pnp0
Oct 11 17:31:27 ryzen kernel: system 00:01: PM: pnp_bus_resume+0x0/0xa0 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: rtc_cmos 00:02: PM: calling pnp_bus_resume+0x0/0xa0 @ 4494, parent: pnp0
Oct 11 17:31:27 ryzen kernel: rtc_cmos 00:02: PM: pnp_bus_resume+0x0/0xa0 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: system 00:03: PM: calling pnp_bus_resume+0x0/0xa0 @ 4494, parent: pnp0
Oct 11 17:31:27 ryzen kernel: system 00:03: PM: pnp_bus_resume+0x0/0xa0 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: i8042 kbd 00:04: PM: calling pnp_bus_resume+0x0/0xa0 @ 4494, parent: pnp0
Oct 11 17:31:27 ryzen kernel: xhci_hcd 0000:07:00.3: PM: pci_pm_resume+0x0/0xf0 returned 0 after 173 usecs
Oct 11 17:31:27 ryzen kernel: scsi host4: PM: calling scsi_bus_resume+0x0/0x90 @ 4563, parent: ata5
Oct 11 17:31:27 ryzen kernel: usb usb3: PM: calling usb_dev_resume+0x0/0x20 @ 4552, parent: 0000:07:00.3
Oct 11 17:31:27 ryzen kernel: usb usb4: PM: calling usb_dev_resume+0x0/0x20 @ 4522, parent: 0000:07:00.3
Oct 11 17:31:27 ryzen kernel: scsi host4: PM: scsi_bus_resume+0x0/0x90 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: i8042 kbd 00:04: PM: pnp_bus_resume+0x0/0xa0 returned 0 after 43 usecs
Oct 11 17:31:27 ryzen kernel: serial 00:05: PM: calling pnp_bus_resume+0x0/0xa0 @ 4494, parent: pnp0
Oct 11 17:31:27 ryzen kernel: r8169 0000:04:00.0: PM: pci_pm_resume+0x0/0xf0 returned 0 after 198 usecs
Oct 11 17:31:27 ryzen kernel: serial 00:05: activated
Oct 11 17:31:27 ryzen kernel: serial 00:05: PM: pnp_bus_resume+0x0/0xa0 returned 0 after 895 usecs
Oct 11 17:31:27 ryzen kernel: system 00:06: PM: calling pnp_bus_resume+0x0/0xa0 @ 4494, parent: pnp0
Oct 11 17:31:27 ryzen kernel: system 00:06: PM: pnp_bus_resume+0x0/0xa0 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: pcspkr pcspkr: PM: calling platform_pm_resume+0x0/0x50 @ 4494, parent: platform
Oct 11 17:31:27 ryzen kernel: pcspkr pcspkr: PM: platform_pm_resume+0x0/0x50 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: input input0: PM: calling input_dev_resume+0x0/0x40 @ 4494, parent: PNP0C0C:00
Oct 11 17:31:27 ryzen kernel: input input0: PM: input_dev_resume+0x0/0x40 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: input input1: PM: calling input_dev_resume+0x0/0x40 @ 4494, parent: LNXPWRBN:00
Oct 11 17:31:27 ryzen kernel: input input1: PM: input_dev_resume+0x0/0x40 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: port 00:05:0.0: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 4494, parent: 00:05:0
Oct 11 17:31:27 ryzen kernel: port 00:05:0.0: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: serial8250 serial8250: PM: calling platform_pm_resume+0x0/0x50 @ 4494, parent: platform
Oct 11 17:31:27 ryzen kernel: serial8250 serial8250: PM: platform_pm_resume+0x0/0x50 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: port serial8250:0.1: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 4494, parent: serial8250:0
Oct 11 17:31:27 ryzen kernel: port serial8250:0.1: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: port serial8250:0.2: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 4494, parent: serial8250:0
Oct 11 17:31:27 ryzen kernel: port serial8250:0.2: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: port serial8250:0.3: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 4494, parent: serial8250:0
Oct 11 17:31:27 ryzen kernel: port serial8250:0.3: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: port serial8250:0.4: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 4494, parent: serial8250:0
Oct 11 17:31:27 ryzen kernel: port serial8250:0.4: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: port serial8250:0.5: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 4494, parent: serial8250:0
Oct 11 17:31:27 ryzen kernel: port serial8250:0.5: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: port serial8250:0.6: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 4494, parent: serial8250:0
Oct 11 17:31:27 ryzen kernel: port serial8250:0.6: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: port serial8250:0.7: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 4494, parent: serial8250:0
Oct 11 17:31:27 ryzen kernel: port serial8250:0.7: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: port serial8250:0.8: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 4494, parent: serial8250:0
Oct 11 17:31:27 ryzen kernel: port serial8250:0.8: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: port serial8250:0.9: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 4494, parent: serial8250:0
Oct 11 17:31:27 ryzen kernel: port serial8250:0.9: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: port serial8250:0.10: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 4494, parent: serial8250:0
Oct 11 17:31:27 ryzen kernel: port serial8250:0.10: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: port serial8250:0.11: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 4494, parent: serial8250:0
Oct 11 17:31:27 ryzen kernel: port serial8250:0.11: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: port serial8250:0.12: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 4494, parent: serial8250:0
Oct 11 17:31:27 ryzen kernel: port serial8250:0.12: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: port serial8250:0.13: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 4494, parent: serial8250:0
Oct 11 17:31:27 ryzen kernel: port serial8250:0.13: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: port serial8250:0.14: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 4494, parent: serial8250:0
Oct 11 17:31:27 ryzen kernel: port serial8250:0.14: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: port serial8250:0.15: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 4494, parent: serial8250:0
Oct 11 17:31:27 ryzen kernel: port serial8250:0.15: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: port serial8250:0.16: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 4494, parent: serial8250:0
Oct 11 17:31:27 ryzen kernel: port serial8250:0.16: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: port serial8250:0.17: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 4494, parent: serial8250:0
Oct 11 17:31:27 ryzen kernel: port serial8250:0.17: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: port serial8250:0.18: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 4494, parent: serial8250:0
Oct 11 17:31:27 ryzen kernel: port serial8250:0.18: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: port serial8250:0.19: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 4494, parent: serial8250:0
Oct 11 17:31:27 ryzen kernel: port serial8250:0.19: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: port serial8250:0.20: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 4494, parent: serial8250:0
Oct 11 17:31:27 ryzen kernel: port serial8250:0.20: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: port serial8250:0.21: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 4494, parent: serial8250:0
Oct 11 17:31:27 ryzen kernel: port serial8250:0.21: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: port serial8250:0.22: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 4494, parent: serial8250:0
Oct 11 17:31:27 ryzen kernel: port serial8250:0.22: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: port serial8250:0.23: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 4494, parent: serial8250:0
Oct 11 17:31:27 ryzen kernel: port serial8250:0.23: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: port serial8250:0.24: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 4494, parent: serial8250:0
Oct 11 17:31:27 ryzen kernel: port serial8250:0.24: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: port serial8250:0.25: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 4494, parent: serial8250:0
Oct 11 17:31:27 ryzen kernel: port serial8250:0.25: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: port serial8250:0.26: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 4494, parent: serial8250:0
Oct 11 17:31:27 ryzen kernel: port serial8250:0.26: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: port serial8250:0.27: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 4494, parent: serial8250:0
Oct 11 17:31:27 ryzen kernel: port serial8250:0.27: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: port serial8250:0.28: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 4494, parent: serial8250:0
Oct 11 17:31:27 ryzen kernel: port serial8250:0.28: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: port serial8250:0.29: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 4494, parent: serial8250:0
Oct 11 17:31:27 ryzen kernel: port serial8250:0.29: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: port serial8250:0.30: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 4494, parent: serial8250:0
Oct 11 17:31:27 ryzen kernel: port serial8250:0.30: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: port serial8250:0.31: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 4494, parent: serial8250:0
Oct 11 17:31:27 ryzen kernel: port serial8250:0.31: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: rtc rtc0: PM: calling rtc_resume+0x0/0x240 @ 4494, parent: 00:02
Oct 11 17:31:27 ryzen kernel: rtc rtc0: PM: rtc_resume+0x0/0x240 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: alarmtimer alarmtimer.0.auto: PM: calling platform_pm_resume+0x0/0x50 @ 4494, parent: rtc0
Oct 11 17:31:27 ryzen kernel: alarmtimer alarmtimer.0.auto: PM: platform_pm_resume+0x0/0x50 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: platform microcode: PM: calling platform_pm_resume+0x0/0x50 @ 4494, parent: platform
Oct 11 17:31:27 ryzen kernel: platform microcode: PM: platform_pm_resume+0x0/0x50 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: i8042 i8042: PM: calling platform_pm_resume+0x0/0x50 @ 4494, parent: platform
Oct 11 17:31:27 ryzen kernel: i8042 i8042: PM: platform_pm_resume+0x0/0x50 returned 0 after 58 usecs
Oct 11 17:31:27 ryzen kernel: atkbd serio0: PM: calling serio_resume+0x0/0xa0 [serio] @ 4494, parent: i8042
Oct 11 17:31:27 ryzen kernel: atkbd serio0: PM: serio_resume+0x0/0xa0 [serio] returned 0 after 2 usecs
Oct 11 17:31:27 ryzen kernel: input input2: PM: calling input_dev_resume+0x0/0x40 @ 4494, parent: serio0
Oct 11 17:31:27 ryzen kernel: input input2: PM: input_dev_resume+0x0/0x40 returned 0 after 1 usecs
Oct 11 17:31:27 ryzen kernel: leds input2::numlock: PM: calling led_resume+0x0/0x50 @ 4494, parent: input2
Oct 11 17:31:27 ryzen kernel: leds input2::numlock: PM: led_resume+0x0/0x50 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: leds input2::capslock: PM: calling led_resume+0x0/0x50 @ 4494, parent: input2
Oct 11 17:31:27 ryzen kernel: leds input2::capslock: PM: led_resume+0x0/0x50 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: leds input2::scrolllock: PM: calling led_resume+0x0/0x50 @ 4494, parent: input2
Oct 11 17:31:27 ryzen kernel: leds input2::scrolllock: PM: led_resume+0x0/0x50 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: snd_hda_intel 0000:07:00.4: PM: pci_pm_resume+0x0/0xf0 returned 0 after 4364 usecs
Oct 11 17:31:27 ryzen kernel: snd_hda_codec_realtek hdaudioC2D0: PM: calling hda_codec_pm_resume+0x0/0x20 [snd_hda_codec] @ 4587, parent: 0000:07:00.4
Oct 11 17:31:27 ryzen kernel: usb usb4: PM: usb_dev_resume+0x0/0x20 returned 0 after 26570 usecs
Oct 11 17:31:27 ryzen kernel: xhci_hcd 0000:02:00.0: PM: pci_pm_resume+0x0/0xf0 returned 0 after 56346 usecs
Oct 11 17:31:27 ryzen kernel: usb usb2: PM: calling usb_dev_resume+0x0/0x20 @ 4571, parent: 0000:02:00.0
Oct 11 17:31:27 ryzen kernel: usb usb1: PM: calling usb_dev_resume+0x0/0x20 @ 4532, parent: 0000:02:00.0
Oct 11 17:31:27 ryzen kernel: usb usb3: PM: usb_dev_resume+0x0/0x20 returned 0 after 57607 usecs
Oct 11 17:31:27 ryzen kernel: usb 3-2: PM: calling usb_dev_resume+0x0/0x20 @ 4555, parent: usb3
Oct 11 17:31:27 ryzen kernel: nvme nvme0: Shutdown timeout set to 8 seconds
Oct 11 17:31:27 ryzen kernel: usb 3-2: PM: usb_dev_resume+0x0/0x20 returned 0 after 26763 usecs
Oct 11 17:31:27 ryzen kernel: input input3: PM: calling input_dev_resume+0x0/0x40 @ 4494, parent: 0003:1852:7022.0001
Oct 11 17:31:27 ryzen kernel: input input3: PM: input_dev_resume+0x0/0x40 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: nvme nvme0: 32/0/0 default/read/poll queues
Oct 11 17:31:27 ryzen kernel: snd_hda_codec_realtek hdaudioC2D0: PM: hda_codec_pm_resume+0x0/0x20 [snd_hda_codec] returned 0 after 161743 usecs
Oct 11 17:31:27 ryzen kernel: usb usb1: PM: usb_dev_resume+0x0/0x20 returned 0 after 143718 usecs
Oct 11 17:31:27 ryzen kernel: usb 1-5: PM: calling usb_dev_resume+0x0/0x20 @ 147, parent: usb1
Oct 11 17:31:27 ryzen kernel: usb 1-7: PM: calling usb_dev_resume+0x0/0x20 @ 4563, parent: usb1
Oct 11 17:31:27 ryzen kernel: usb 1-10: PM: calling usb_dev_resume+0x0/0x20 @ 4526, parent: usb1
Oct 11 17:31:27 ryzen kernel: usb 1-2: PM: calling usb_dev_resume+0x0/0x20 @ 4578, parent: usb1
Oct 11 17:31:27 ryzen kernel: usb usb2: PM: usb_dev_resume+0x0/0x20 returned 0 after 210381 usecs
Oct 11 17:31:27 ryzen kernel: usb 2-4: PM: calling usb_dev_resume+0x0/0x20 @ 4529, parent: usb2
Oct 11 17:31:27 ryzen kernel: ata4: SATA link down (SStatus 0 SControl 330)
Oct 11 17:31:27 ryzen kernel: ata3: SATA link down (SStatus 0 SControl 330)
Oct 11 17:31:27 ryzen kernel: usb 1-2: reset high-speed USB device number 2 using xhci_hcd
Oct 11 17:31:27 ryzen kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
Oct 11 17:31:27 ryzen kernel: ata2.00: configured for UDMA/100
Oct 11 17:31:27 ryzen kernel: [drm] PCIE GART of 256M enabled (table at 0x000000F400800000).
Oct 11 17:31:27 ryzen kernel: usb 1-7: reset full-speed USB device number 5 using xhci_hcd
Oct 11 17:31:27 ryzen kernel: usb 1-2: PM: usb_dev_resume+0x0/0x20 returned 0 after 539889 usecs
Oct 11 17:31:27 ryzen kernel: usb 1-2.2: PM: calling usb_dev_resume+0x0/0x20 @ 10, parent: 1-2
Oct 11 17:31:27 ryzen kernel: usb 1-2.1: PM: calling usb_dev_resume+0x0/0x20 @ 317, parent: 1-2
Oct 11 17:31:27 ryzen kernel: usb 1-2.3: PM: calling usb_dev_resume+0x0/0x20 @ 4566, parent: 1-2
Oct 11 17:31:27 ryzen kernel: usb 1-2.4: PM: calling usb_dev_resume+0x0/0x20 @ 4586, parent: 1-2
Oct 11 17:31:27 ryzen kernel: usb 1-7: PM: usb_dev_resume+0x0/0x20 returned 0 after 651379 usecs
Oct 11 17:31:27 ryzen kernel: usb 1-10: reset full-speed USB device number 7 using xhci_hcd
Oct 11 17:31:27 ryzen kernel: ata6: failed to resume link (SControl 0)
Oct 11 17:31:27 ryzen kernel: ata6: SATA link down (SStatus 0 SControl 0)
Oct 11 17:31:27 ryzen kernel: ata5: failed to resume link (SControl 0)
Oct 11 17:31:27 ryzen kernel: ata5: SATA link down (SStatus 0 SControl 0)
Oct 11 17:31:27 ryzen kernel: usb 1-10: PM: usb_dev_resume+0x0/0x20 returned 0 after 999091 usecs
Oct 11 17:31:27 ryzen kernel: [drm] Fence fallback timer expired on ring sdma0
Oct 11 17:31:27 ryzen kernel: usb 1-5: reset low-speed USB device number 3 using xhci_hcd
Oct 11 17:31:27 ryzen kernel: [drm] Fence fallback timer expired on ring sdma0
Oct 11 17:31:27 ryzen kernel: usb 1-5: PM: usb_dev_resume+0x0/0x20 returned 0 after 1637402 usecs
Oct 11 17:31:27 ryzen kernel: input input4: PM: calling input_dev_resume+0x0/0x40 @ 4494, parent: 0003:05F3:00FF.0002
Oct 11 17:31:27 ryzen kernel: input input4: PM: input_dev_resume+0x0/0x40 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: usb 2-4: reset SuperSpeed USB device number 2 using xhci_hcd
Oct 11 17:31:27 ryzen kernel: usb 2-4: PM: usb_dev_resume+0x0/0x20 returned 0 after 1692938 usecs
Oct 11 17:31:27 ryzen kernel: scsi host6: PM: calling scsi_bus_resume+0x0/0x90 @ 4557, parent: 2-4:1.0
Oct 11 17:31:27 ryzen kernel: scsi host6: PM: scsi_bus_resume+0x0/0x90 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: scsi target6:0:0: PM: calling scsi_bus_resume+0x0/0x90 @ 4551, parent: host6
Oct 11 17:31:27 ryzen kernel: scsi target6:0:0: PM: scsi_bus_resume+0x0/0x90 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: sd 6:0:0:0: PM: calling scsi_bus_resume+0x0/0x90 @ 4535, parent: target6:0:0
Oct 11 17:31:27 ryzen kernel: sd 6:0:0:0: PM: scsi_bus_resume+0x0/0x90 returned 0 after 1 usecs
Oct 11 17:31:27 ryzen kernel: usb 1-2.2: reset full-speed USB device number 6 using xhci_hcd
Oct 11 17:31:27 ryzen kernel: [drm] Fence fallback timer expired on ring sdma0
Oct 11 17:31:27 ryzen kernel: usb 1-2.2: PM: usb_dev_resume+0x0/0x20 returned 0 after 1569871 usecs
Oct 11 17:31:27 ryzen kernel: usb 1-2.1: reset full-speed USB device number 4 using xhci_hcd
Oct 11 17:31:27 ryzen kernel: [drm] Fence fallback timer expired on ring sdma0
Oct 11 17:31:27 ryzen kernel: [drm] Fence fallback timer expired on ring sdma0
Oct 11 17:31:27 ryzen kernel: [drm] Fence fallback timer expired on ring sdma0
Oct 11 17:31:27 ryzen kernel: [drm] Fence fallback timer expired on ring sdma0
Oct 11 17:31:27 ryzen kernel: [drm] Fence fallback timer expired on ring sdma0
Oct 11 17:31:27 ryzen kernel: [drm] UVD and UVD ENC initialized successfully.
Oct 11 17:31:27 ryzen kernel: [drm] VCE initialized successfully.
Oct 11 17:31:27 ryzen kernel: amdgpu 0000:05:00.0: PM: pci_pm_resume+0x0/0xf0 returned 0 after 5018211 usecs
Oct 11 17:31:27 ryzen kernel: snd_hda_intel 0000:05:00.1: PM: calling pci_pm_resume+0x0/0xf0 @ 3813, parent: 0000:00:03.1
Oct 11 17:31:27 ryzen kernel: snd_hda_intel 0000:05:00.1: PM: pci_pm_resume+0x0/0xf0 returned 0 after 2314 usecs
Oct 11 17:31:27 ryzen kernel: ata1: link is slow to respond, please be patient (ready=0)
Oct 11 17:31:27 ryzen kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Oct 11 17:31:27 ryzen kernel: ata1.00: configured for UDMA/133
Oct 11 17:31:27 ryzen kernel: usb 1-2.1: PM: usb_dev_resume+0x0/0x20 returned 0 after 7148603 usecs
Oct 11 17:31:27 ryzen kernel: input input5: PM: calling input_dev_resume+0x0/0x40 @ 4494, parent: 0003:0ECB:2057.0003
Oct 11 17:31:27 ryzen kernel: input input5: PM: input_dev_resume+0x0/0x40 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: input input6: PM: calling input_dev_resume+0x0/0x40 @ 4494, parent: 0003:29EA:0102.0005
Oct 11 17:31:27 ryzen kernel: input input6: PM: input_dev_resume+0x0/0x40 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: input input7: PM: calling input_dev_resume+0x0/0x40 @ 4494, parent: 0003:29EA:0102.0006
Oct 11 17:31:27 ryzen kernel: input input7: PM: input_dev_resume+0x0/0x40 returned 0 after 8 usecs
Oct 11 17:31:27 ryzen kernel: leds input7::numlock: PM: calling led_resume+0x0/0x50 @ 4494, parent: input7
Oct 11 17:31:27 ryzen kernel: leds input7::numlock: PM: led_resume+0x0/0x50 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: leds input7::capslock: PM: calling led_resume+0x0/0x50 @ 4494, parent: input7
Oct 11 17:31:27 ryzen kernel: leds input7::capslock: PM: led_resume+0x0/0x50 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: leds input7::scrolllock: PM: calling led_resume+0x0/0x50 @ 4494, parent: input7
Oct 11 17:31:27 ryzen kernel: leds input7::scrolllock: PM: led_resume+0x0/0x50 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: leds input7::compose: PM: calling led_resume+0x0/0x50 @ 4494, parent: input7
Oct 11 17:31:27 ryzen kernel: leds input7::compose: PM: led_resume+0x0/0x50 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: leds input7::kana: PM: calling led_resume+0x0/0x50 @ 4494, parent: input7
Oct 11 17:31:27 ryzen kernel: leds input7::kana: PM: led_resume+0x0/0x50 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: input input8: PM: calling input_dev_resume+0x0/0x40 @ 4494, parent: 0003:29EA:0102.0007
Oct 11 17:31:27 ryzen kernel: input input8: PM: input_dev_resume+0x0/0x40 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: input input9: PM: calling input_dev_resume+0x0/0x40 @ 4494, parent: 0003:29EA:0102.0007
Oct 11 17:31:27 ryzen kernel: input input9: PM: input_dev_resume+0x0/0x40 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: usb 1-2.3: reset full-speed USB device number 8 using xhci_hcd
Oct 11 17:31:27 ryzen kernel: usb 1-2.3: PM: usb_dev_resume+0x0/0x20 returned 0 after 7454189 usecs
Oct 11 17:31:27 ryzen kernel: input input10: PM: calling input_dev_resume+0x0/0x40 @ 4494, parent: 0003:046D:C092.0009
Oct 11 17:31:27 ryzen kernel: input input10: PM: input_dev_resume+0x0/0x40 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: input input11: PM: calling input_dev_resume+0x0/0x40 @ 4494, parent: 0003:046D:C092.000A
Oct 11 17:31:27 ryzen kernel: input input11: PM: input_dev_resume+0x0/0x40 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: sp5100-tco sp5100-tco: PM: calling platform_pm_resume+0x0/0x50 @ 4494, parent: platform
Oct 11 17:31:27 ryzen kernel: sp5100-tco sp5100-tco: PM: platform_pm_resume+0x0/0x50 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: input input14: PM: calling input_dev_resume+0x0/0x40 @ 4494, parent: pcspkr
Oct 11 17:31:27 ryzen kernel: input input14: PM: input_dev_resume+0x0/0x40 returned 0 after 12 usecs
Oct 11 17:31:27 ryzen kernel: input input15: PM: calling input_dev_resume+0x0/0x40 @ 4494, parent: card1
Oct 11 17:31:27 ryzen kernel: input input15: PM: input_dev_resume+0x0/0x40 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: input input16: PM: calling input_dev_resume+0x0/0x40 @ 4494, parent: card1
Oct 11 17:31:27 ryzen kernel: input input16: PM: input_dev_resume+0x0/0x40 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: input input17: PM: calling input_dev_resume+0x0/0x40 @ 4494, parent: card1
Oct 11 17:31:27 ryzen kernel: input input17: PM: input_dev_resume+0x0/0x40 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: input input18: PM: calling input_dev_resume+0x0/0x40 @ 4494, parent: card1
Oct 11 17:31:27 ryzen kernel: input input18: PM: input_dev_resume+0x0/0x40 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: input input19: PM: calling input_dev_resume+0x0/0x40 @ 4494, parent: card1
Oct 11 17:31:27 ryzen kernel: input input19: PM: input_dev_resume+0x0/0x40 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: input input20: PM: calling input_dev_resume+0x0/0x40 @ 4494, parent: card1
Oct 11 17:31:27 ryzen kernel: input input20: PM: input_dev_resume+0x0/0x40 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: input input21: PM: calling input_dev_resume+0x0/0x40 @ 4494, parent: card2
Oct 11 17:31:27 ryzen kernel: input input21: PM: input_dev_resume+0x0/0x40 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: input input22: PM: calling input_dev_resume+0x0/0x40 @ 4494, parent: card2
Oct 11 17:31:27 ryzen kernel: input input22: PM: input_dev_resume+0x0/0x40 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: input input23: PM: calling input_dev_resume+0x0/0x40 @ 4494, parent: card2
Oct 11 17:31:27 ryzen kernel: input input23: PM: input_dev_resume+0x0/0x40 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: input input24: PM: calling input_dev_resume+0x0/0x40 @ 4494, parent: card2
Oct 11 17:31:27 ryzen kernel: input input24: PM: input_dev_resume+0x0/0x40 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: input input25: PM: calling input_dev_resume+0x0/0x40 @ 4494, parent: card2
Oct 11 17:31:27 ryzen kernel: input input25: PM: input_dev_resume+0x0/0x40 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: Generic FE-GE Realtek PHY r8169-0-400:00: PM: calling mdio_bus_phy_resume+0x0/0x130 [libphy] @ 4494, parent: r8169-0-400
Oct 11 17:31:27 ryzen kernel: Generic FE-GE Realtek PHY r8169-0-400:00: PM: mdio_bus_phy_resume+0x0/0x130 [libphy] returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: intel_rapl_msr intel_rapl_msr.0: PM: calling platform_pm_resume+0x0/0x50 @ 4494, parent: platform
Oct 11 17:31:27 ryzen kernel: intel_rapl_msr intel_rapl_msr.0: PM: platform_pm_resume+0x0/0x50 returned 0 after 0 usecs
Oct 11 17:31:27 ryzen kernel: usb 1-2.4: reset full-speed USB device number 9 using xhci_hcd
Oct 11 17:31:27 ryzen kernel: usb 1-2.4: PM: usb_dev_resume+0x0/0x20 returned 0 after 7728490 usecs
Oct 11 17:31:27 ryzen kernel: PM: resume of devices complete after 8468.793 msecs
Oct 11 17:31:27 ryzen kernel: OOM killer enabled.
Oct 11 17:31:27 ryzen kernel: Restarting tasks ... done.
Oct 11 17:31:27 ryzen kernel: random: crng reseeded on system resumption
Oct 11 17:31:27 ryzen kernel: PM: suspend exit
Oct 11 17:31:27 ryzen rtkit-daemon[1365]: The canary thread is apparently starving. Taking action.
Oct 11 17:31:27 ryzen systemd-udevd[364]: /etc/udev/rules.d/30-usbtmc.rules:5 Unknown group 'usbtmc', ignoring.
Oct 11 17:31:27 ryzen rtkit-daemon[1365]: Demoting known real-time threads.
Oct 11 17:31:27 ryzen systemd-udevd[364]: /etc/udev/rules.d/30-usbtmc.rules:8 Unknown group 'usbtmc', ignoring.
Oct 11 17:31:27 ryzen rtkit-daemon[1365]: Successfully demoted thread 2699 of process 2544.
Oct 11 17:31:27 ryzen systemd-sleep[4494]: System returned from sleep state.
Oct 11 17:31:27 ryzen rtkit-daemon[1365]: Demoted 1 threads.
Oct 11 17:31:27 ryzen systemd-udevd[364]: /etc/udev/rules.d/30-usbtmc.rules:11 Unknown group 'usbtmc', ignoring.
Oct 11 17:31:27 ryzen /usr/bin/gpm[827]: *** info [mice.c(1990)]:
Oct 11 17:31:27 ryzen systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
Oct 11 17:31:27 ryzen /usr/bin/gpm[827]: imps2: Auto-detected intellimouse PS/2
Oct 11 17:31:27 ryzen systemd[1]: systemd-suspend.service: Deactivated successfully.
Oct 11 17:31:27 ryzen systemd[1]: Finished System Suspend.
Oct 11 17:31:27 ryzen systemd[1]: systemd-suspend.service: Consumed 2.446s CPU time.
Oct 11 17:31:27 ryzen systemd-udevd[364]: /etc/udev/rules.d/30-usbtmc.rules:14 Unknown group 'usbtmc', ignoring.
Oct 11 17:31:27 ryzen systemd-udevd[364]: /etc/udev/rules.d/30-usbtmc.rules:15 Unknown group 'usbtmc', ignoring.
Oct 11 17:31:27 ryzen systemd[1]: Stopped target Sleep.
Oct 11 17:31:27 ryzen systemd[1]: Reached target Suspend.
Oct 11 17:31:27 ryzen systemd[1]: Stopped target Suspend.
Oct 11 17:31:27 ryzen systemd-logind[830]: Operation 'sleep' finished.
Oct 11 17:31:27 ryzen NetworkManager[927]: <info> [1697070687.8847] manager: sleep: wake requested (sleeping: yes enabled: yes)
Oct 11 17:31:27 ryzen NetworkManager[927]: <info> [1697070687.8848] device (enp4s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Oct 11 17:31:27 ryzen systemd-udevd[364]: /usr/lib/udev/rules.d/51-footcontroller.rules:10 Invalid value for OPTIONS key, ignoring: 'last_rule'
Oct 11 17:31:27 ryzen kernel: Generic FE-GE Realtek PHY r8169-0-400:00: attached PHY driver (mii_bus:phy_addr=r8169-0-400:00, irq=MAC)
Oct 11 17:31:28 ryzen NetworkManager[927]: <info> [1697070688.1057] manager: NetworkManager state is now CONNECTED_LOCAL
Oct 11 17:31:28 ryzen kernel: r8169 0000:04:00.0 enp4s0: Link is Down
Oct 11 17:31:30 ryzen NetworkManager[927]: <info> [1697070690.7932] device (enp4s0): carrier: link connected
Oct 11 17:31:30 ryzen NetworkManager[927]: <info> [1697070690.7934] device (enp4s0): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed')
Oct 11 17:31:30 ryzen NetworkManager[927]: <info> [1697070690.7939] policy: auto-activating connection 'Wired connection 1' (1a78b687-138e-3a66-9ca0-dc365ee4d000)
Oct 11 17:31:30 ryzen NetworkManager[927]: <info> [1697070690.7941] device (enp4s0): Activation: starting connection 'Wired connection 1' (1a78b687-138e-3a66-9ca0-dc365ee4d000)
Oct 11 17:31:30 ryzen NetworkManager[927]: <info> [1697070690.7942] device (enp4s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Oct 11 17:31:30 ryzen NetworkManager[927]: <info> [1697070690.7942] manager: NetworkManager state is now CONNECTING
Oct 11 17:31:30 ryzen NetworkManager[927]: <info> [1697070690.7943] device (enp4s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Oct 11 17:31:30 ryzen NetworkManager[927]: <info> [1697070690.7946] device (enp4s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Oct 11 17:31:30 ryzen NetworkManager[927]: <info> [1697070690.7950] dhcp4 (enp4s0): activation: beginning transaction (timeout in 45 seconds)
Oct 11 17:31:30 ryzen kernel: r8169 0000:04:00.0 enp4s0: Link is Up - 1Gbps/Full - flow control rx/tx
Oct 11 17:31:30 ryzen dnsmasq[1089]: reading /etc/resolv.conf
Oct 11 17:31:30 ryzen dnsmasq[1056]: reading /etc/resolv.conf
Oct 11 17:31:30 ryzen dnsmasq[1089]: using nameserver 1.1.1.1#53
Oct 11 17:31:30 ryzen dnsmasq[1056]: using nameserver 1.1.1.1#53
Oct 11 17:31:30 ryzen NetworkManager[927]: <info> [1697070690.8005] dhcp4 (enp4s0): state changed new lease, address=192.168.0.91
Oct 11 17:31:30 ryzen NetworkManager[927]: <info> [1697070690.8007] policy: set 'Wired connection 1' (enp4s0) as default for IPv4 routing and DNS
Oct 11 17:31:30 ryzen dnsmasq[1089]: reading /etc/resolv.conf
Oct 11 17:31:30 ryzen dnsmasq[1056]: reading /etc/resolv.conf
Oct 11 17:31:30 ryzen dnsmasq[1089]: using nameserver 1.1.1.1#53
Oct 11 17:31:30 ryzen dnsmasq[1089]: using nameserver 8.8.8.8#53
Oct 11 17:31:30 ryzen dnsmasq[1056]: using nameserver 1.1.1.1#53
Oct 11 17:31:30 ryzen dnsmasq[1056]: using nameserver 8.8.8.8#53
Oct 11 17:31:30 ryzen avahi-daemon[823]: Joining mDNS multicast group on interface enp4s0.IPv4 with address 192.168.0.91.
Oct 11 17:31:30 ryzen avahi-daemon[823]: New relevant interface enp4s0.IPv4 for mDNS.
Oct 11 17:31:30 ryzen avahi-daemon[823]: Registering new address record for 192.168.0.91 on enp4s0.IPv4.
Oct 11 17:31:30 ryzen avahi-daemon[823]: Joining mDNS multicast group on interface enp4s0.IPv6 with address fe80::1b36:1dd4:a5cf:3b8f.
Oct 11 17:31:30 ryzen avahi-daemon[823]: New relevant interface enp4s0.IPv6 for mDNS.
Oct 11 17:31:30 ryzen avahi-daemon[823]: Registering new address record for fe80::1b36:1dd4:a5cf:3b8f on enp4s0.*.
Oct 11 17:31:30 ryzen dbus-daemon[824]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.4' (uid=0 pid=927 comm="/usr/bin/NetworkManager --no-daemon")
Oct 11 17:31:30 ryzen NetworkManager[927]: <info> [1697070690.8112] device (enp4s0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Oct 11 17:31:30 ryzen systemd[1]: Starting Network Manager Script Dispatcher Service...
Oct 11 17:31:30 ryzen dbus-daemon[824]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Oct 11 17:31:30 ryzen systemd[1]: Started Network Manager Script Dispatcher Service.
Oct 11 17:31:30 ryzen NetworkManager[927]: <info> [1697070690.8443] device (enp4s0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Oct 11 17:31:30 ryzen NetworkManager[927]: <info> [1697070690.8444] device (enp4s0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Oct 11 17:31:30 ryzen NetworkManager[927]: <info> [1697070690.8445] manager: NetworkManager state is now CONNECTED_SITE
Oct 11 17:31:30 ryzen NetworkManager[927]: <info> [1697070690.8447] device (enp4s0): Activation: successful, device activated.
Oct 11 17:31:31 ryzen NetworkManager[927]: <info> [1697070691.2429] manager: NetworkManager state is now CONNECTED_GLOBAL
Oct 11 17:31:31 ryzen PackageKit[1897]: get-updates transaction /6_eddaaeac from uid 1001 finished with success after 2ms
Oct 11 17:31:32 ryzen NetworkManager[927]: <info> [1697070692.3519] dhcp6 (enp4s0): activation: beginning transaction (timeout in 45 seconds)
Oct 11 17:31:32 ryzen dnsmasq[1089]: reading /etc/resolv.conf
Oct 11 17:31:32 ryzen dnsmasq[1056]: reading /etc/resolv.conf
Oct 11 17:31:32 ryzen dnsmasq[1089]: using nameserver 1.1.1.1#53
Oct 11 17:31:32 ryzen dnsmasq[1056]: using nameserver 1.1.1.1#53
Oct 11 17:31:32 ryzen dnsmasq[1089]: using nameserver 8.8.8.8#53
Oct 11 17:31:32 ryzen dnsmasq[1056]: using nameserver 8.8.8.8#53
Oct 11 17:31:32 ryzen dnsmasq[1089]: using nameserver fde3:5408:101c::1#53
Oct 11 17:31:32 ryzen dnsmasq[1056]: using nameserver fde3:5408:101c::1#53
Oct 11 17:31:32 ryzen avahi-daemon[823]: Leaving mDNS multicast group on interface enp4s0.IPv6 with address fe80::1b36:1dd4:a5cf:3b8f.
Oct 11 17:31:32 ryzen avahi-daemon[823]: Joining mDNS multicast group on interface enp4s0.IPv6 with address fde3:5408:101c:0:7441:9d56:d3c1:1a95.
Oct 11 17:31:32 ryzen NetworkManager[927]: <info> [1697070692.3578] dhcp6 (enp4s0): state changed new lease, address=fde3:5408:101c::566
Oct 11 17:31:32 ryzen avahi-daemon[823]: Registering new address record for fde3:5408:101c:0:7441:9d56:d3c1:1a95 on enp4s0.*.
Oct 11 17:31:32 ryzen avahi-daemon[823]: Withdrawing address record for fe80::1b36:1dd4:a5cf:3b8f on enp4s0.
Oct 11 17:31:32 ryzen avahi-daemon[823]: Registering new address record for fde3:5408:101c::566 on enp4s0.*.
Oct 11 17:31:33 ryzen dbus-daemon[824]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.114' (uid=1001 pid=4439 comm="/usr/lib/kscreenlocker_greet --immediateLock --gra")
Oct 11 17:31:33 ryzen dbus-daemon[824]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.
Oct 11 17:31:34 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 17:31:34 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 17:31:40 ryzen systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
Oct 11 17:32:04 ryzen dbus-daemon[824]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.116' (uid=0 pid=4867 comm="sudo sh -c unswap-perl & pid=$! ; swapoff -a ; swa")
Oct 11 17:32:04 ryzen dbus-daemon[824]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.
Oct 11 17:32:10 ryzen systemd[1]: dev-disk-by\x2dpath-pci\x2d0000:01:00.0\x2dnvme\x2d1\x2dpart6.swap: Deactivated successfully.
Oct 11 17:32:10 ryzen kernel: Adding 16777212k swap on /dev/nvme0n1p6. Priority:-2 extents:1 across:16777212k SSFS
Oct 11 17:32:10 ryzen systemd[1]: dev-disk-by\x2dpartuuid-95091b40\x2d9763\x2ddf42\x2db099\x2d2f9f1584bc28.swap: Deactivated successfully.
Oct 11 17:32:10 ryzen systemd[1]: dev-disk-by\x2dpartlabel-Linux\x5cx20Swap.swap: Deactivated successfully.
Oct 11 17:32:10 ryzen systemd[1]: dev-disk-by\x2did-nvme\x2dSamsung_SSD_970_EVO_Plus_2TB_S59CNM0W601482A_1\x2dpart6.swap: Deactivated successfully.
Oct 11 17:32:10 ryzen systemd[1]: dev-disk-by\x2did-nvme\x2deui.0025385631900958\x2dpart6.swap: Deactivated successfully.
Oct 11 17:32:10 ryzen systemd[1]: dev-disk-by\x2did-nvme\x2dSamsung_SSD_970_EVO_Plus_2TB_S59CNM0W601482A\x2dpart6.swap: Deactivated successfully.
Oct 11 17:32:10 ryzen systemd[1]: dev-disk-by\x2ddiskseq-3\x2dpart6.swap: Deactivated successfully.
Oct 11 17:32:10 ryzen systemd[1]: dev-nvme0n1p6.swap: Deactivated successfully.
Oct 11 17:32:10 ryzen systemd[1]: dev-disk-by\x2duuid-52761d05\x2d5222\x2d434a\x2da2a9\x2dd80fc43e7e05.swap: Deactivated successfully.
Oct 11 17:32:10 ryzen systemd-udevd[364]: /etc/udev/rules.d/30-usbtmc.rules:5 Unknown group 'usbtmc', ignoring.
Oct 11 17:32:10 ryzen systemd-udevd[364]: /etc/udev/rules.d/30-usbtmc.rules:8 Unknown group 'usbtmc', ignoring.
Oct 11 17:32:10 ryzen systemd-udevd[364]: /etc/udev/rules.d/30-usbtmc.rules:11 Unknown group 'usbtmc', ignoring.
Oct 11 17:32:10 ryzen systemd-udevd[364]: /etc/udev/rules.d/30-usbtmc.rules:14 Unknown group 'usbtmc', ignoring.
Oct 11 17:32:10 ryzen systemd-udevd[364]: /etc/udev/rules.d/30-usbtmc.rules:15 Unknown group 'usbtmc', ignoring.
Oct 11 17:32:10 ryzen systemd-udevd[364]: /usr/lib/udev/rules.d/51-footcontroller.rules:10 Invalid value for OPTIONS key, ignoring: 'last_rule'
Oct 11 17:32:14 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 17:32:14 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 17:32:51 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 17:32:51 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 17:32:51 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 17:32:51 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 17:32:51 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 17:32:51 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 17:33:55 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 17:33:55 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 17:33:59 ryzen systemd-logind[830]: The system will suspend now!
Oct 11 17:33:59 ryzen NetworkManager[927]: <info> [1697070839.8168] manager: sleep: sleep requested (sleeping: no enabled: yes)
Oct 11 17:33:59 ryzen NetworkManager[927]: <info> [1697070839.8169] manager: NetworkManager state is now ASLEEP
Oct 11 17:33:59 ryzen NetworkManager[927]: <info> [1697070839.8170] device (enp4s0): state change: activated -> deactivating (reason 'sleeping', sys-iface-state: 'managed')
Oct 11 17:33:59 ryzen dbus-daemon[824]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.4' (uid=0 pid=927 comm="/usr/bin/NetworkManager --no-daemon")
Oct 11 17:33:59 ryzen systemd[1]: Starting Network Manager Script Dispatcher Service...
Oct 11 17:33:59 ryzen dbus-daemon[824]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Oct 11 17:33:59 ryzen systemd[1]: Started Network Manager Script Dispatcher Service.
Oct 11 17:33:59 ryzen NetworkManager[927]: <info> [1697070839.8694] device (enp4s0): state change: deactivating -> disconnected (reason 'sleeping', sys-iface-state: 'managed')
Oct 11 17:33:59 ryzen avahi-daemon[823]: Withdrawing address record for fde3:5408:101c::566 on enp4s0.
Oct 11 17:33:59 ryzen avahi-daemon[823]: Withdrawing address record for fde3:5408:101c:0:7441:9d56:d3c1:1a95 on enp4s0.
Oct 11 17:33:59 ryzen avahi-daemon[823]: Leaving mDNS multicast group on interface enp4s0.IPv6 with address fde3:5408:101c:0:7441:9d56:d3c1:1a95.
Oct 11 17:33:59 ryzen avahi-daemon[823]: Joining mDNS multicast group on interface enp4s0.IPv6 with address fe80::1b36:1dd4:a5cf:3b8f.
Oct 11 17:33:59 ryzen NetworkManager[927]: <info> [1697070839.8709] dhcp4 (enp4s0): canceled DHCP transaction
Oct 11 17:33:59 ryzen avahi-daemon[823]: Registering new address record for fe80::1b36:1dd4:a5cf:3b8f on enp4s0.*.
Oct 11 17:33:59 ryzen NetworkManager[927]: <info> [1697070839.8709] dhcp4 (enp4s0): activation: beginning transaction (timeout in 45 seconds)
Oct 11 17:33:59 ryzen avahi-daemon[823]: Withdrawing address record for fe80::1b36:1dd4:a5cf:3b8f on enp4s0.
Oct 11 17:33:59 ryzen NetworkManager[927]: <info> [1697070839.8709] dhcp4 (enp4s0): state changed no lease
Oct 11 17:33:59 ryzen avahi-daemon[823]: Leaving mDNS multicast group on interface enp4s0.IPv6 with address fe80::1b36:1dd4:a5cf:3b8f.
Oct 11 17:33:59 ryzen NetworkManager[927]: <info> [1697070839.8710] dhcp6 (enp4s0): canceled DHCP transaction
Oct 11 17:33:59 ryzen avahi-daemon[823]: Interface enp4s0.IPv6 no longer relevant for mDNS.
Oct 11 17:33:59 ryzen NetworkManager[927]: <info> [1697070839.8711] dhcp6 (enp4s0): activation: beginning transaction (timeout in 45 seconds)
Oct 11 17:33:59 ryzen NetworkManager[927]: <info> [1697070839.8711] dhcp6 (enp4s0): state changed no lease
Oct 11 17:33:59 ryzen dnsmasq[1056]: no servers found in /etc/resolv.conf, will retry
Oct 11 17:33:59 ryzen dnsmasq[1089]: no servers found in /etc/resolv.conf, will retry
Oct 11 17:33:59 ryzen avahi-daemon[823]: Withdrawing address record for 192.168.0.91 on enp4s0.
Oct 11 17:33:59 ryzen avahi-daemon[823]: Leaving mDNS multicast group on interface enp4s0.IPv4 with address 192.168.0.91.
Oct 11 17:33:59 ryzen avahi-daemon[823]: Interface enp4s0.IPv4 no longer relevant for mDNS.
Oct 11 17:33:59 ryzen NetworkManager[927]: <info> [1697070839.9195] device (enp4s0): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Oct 11 17:33:59 ryzen kernel: r8169 0000:04:00.0 enp4s0: Link is Down
Oct 11 17:34:00 ryzen PackageKit[1897]: get-updates transaction /7_ecacccac from uid 1001 finished with success after 13ms
Oct 11 17:34:00 ryzen systemd[1]: Reached target Sleep.
Oct 11 17:34:00 ryzen systemd[1]: Starting System Suspend...
Oct 11 17:34:00 ryzen systemd-sleep[5277]: Entering sleep state 'suspend'...
Oct 11 17:34:00 ryzen kernel: PM: suspend entry (deep)
Oct 11 17:34:00 ryzen kernel: Filesystems sync: 0.091 seconds
Oct 11 17:34:22 ryzen kernel: Freezing user space processes
Oct 11 17:34:22 ryzen kernel: Freezing user space processes completed (elapsed 0.002 seconds)
Oct 11 17:34:22 ryzen kernel: OOM killer disabled.
Oct 11 17:34:22 ryzen kernel: Freezing remaining freezable tasks
Oct 11 17:34:22 ryzen kernel: Freezing remaining freezable tasks completed (elapsed 0.001 seconds)
Oct 11 17:34:22 ryzen kernel: intel_rapl_msr intel_rapl_msr.0: PM: calling platform_pm_suspend+0x0/0x50 @ 5277, parent: platform
Oct 11 17:34:22 ryzen kernel: intel_rapl_msr intel_rapl_msr.0: PM: platform_pm_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: Generic FE-GE Realtek PHY r8169-0-400:00: PM: calling mdio_bus_phy_suspend+0x0/0x120 [libphy] @ 5277, parent: r8169-0-400
Oct 11 17:34:22 ryzen kernel: Generic FE-GE Realtek PHY r8169-0-400:00: PM: mdio_bus_phy_suspend+0x0/0x120 [libphy] returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: sound pcmC3D0c: PM: calling do_pcm_suspend+0x0/0x30 [snd_pcm] @ 5277, parent: card3
Oct 11 17:34:22 ryzen kernel: sound pcmC3D0c: PM: do_pcm_suspend+0x0/0x30 [snd_pcm] returned 0 after 1 usecs
Oct 11 17:34:22 ryzen kernel: sound pcmC3D0p: PM: calling do_pcm_suspend+0x0/0x30 [snd_pcm] @ 5277, parent: card3
Oct 11 17:34:22 ryzen kernel: sound pcmC3D0p: PM: do_pcm_suspend+0x0/0x30 [snd_pcm] returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: sound pcmC0D1p: PM: calling do_pcm_suspend+0x0/0x30 [snd_pcm] @ 5277, parent: card0
Oct 11 17:34:22 ryzen kernel: sound pcmC0D1p: PM: do_pcm_suspend+0x0/0x30 [snd_pcm] returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: sound pcmC0D0c: PM: calling do_pcm_suspend+0x0/0x30 [snd_pcm] @ 5277, parent: card0
Oct 11 17:34:22 ryzen kernel: sound pcmC0D0c: PM: do_pcm_suspend+0x0/0x30 [snd_pcm] returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: sound pcmC0D0p: PM: calling do_pcm_suspend+0x0/0x30 [snd_pcm] @ 5277, parent: card0
Oct 11 17:34:22 ryzen kernel: sound pcmC0D0p: PM: do_pcm_suspend+0x0/0x30 [snd_pcm] returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: input input25: PM: calling input_dev_suspend+0x0/0x70 @ 5277, parent: card2
Oct 11 17:34:22 ryzen kernel: input input25: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: input input24: PM: calling input_dev_suspend+0x0/0x70 @ 5277, parent: card2
Oct 11 17:34:22 ryzen kernel: input input24: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: input input23: PM: calling input_dev_suspend+0x0/0x70 @ 5277, parent: card2
Oct 11 17:34:22 ryzen kernel: input input23: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: input input22: PM: calling input_dev_suspend+0x0/0x70 @ 5277, parent: card2
Oct 11 17:34:22 ryzen kernel: input input22: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: input input21: PM: calling input_dev_suspend+0x0/0x70 @ 5277, parent: card2
Oct 11 17:34:22 ryzen kernel: input input21: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: sound pcmC2D2c: PM: calling do_pcm_suspend+0x0/0x30 [snd_pcm] @ 5277, parent: card2
Oct 11 17:34:22 ryzen kernel: sound pcmC2D2c: PM: do_pcm_suspend+0x0/0x30 [snd_pcm] returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: sound pcmC2D0c: PM: calling do_pcm_suspend+0x0/0x30 [snd_pcm] @ 5277, parent: card2
Oct 11 17:34:22 ryzen kernel: sound pcmC2D0c: PM: do_pcm_suspend+0x0/0x30 [snd_pcm] returned 0 after 31 usecs
Oct 11 17:34:22 ryzen kernel: sound pcmC2D0p: PM: calling do_pcm_suspend+0x0/0x30 [snd_pcm] @ 5277, parent: card2
Oct 11 17:34:22 ryzen kernel: sound pcmC2D0p: PM: do_pcm_suspend+0x0/0x30 [snd_pcm] returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: input input20: PM: calling input_dev_suspend+0x0/0x70 @ 5277, parent: card1
Oct 11 17:34:22 ryzen kernel: input input20: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: input input19: PM: calling input_dev_suspend+0x0/0x70 @ 5277, parent: card1
Oct 11 17:34:22 ryzen kernel: input input19: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: input input18: PM: calling input_dev_suspend+0x0/0x70 @ 5277, parent: card1
Oct 11 17:34:22 ryzen kernel: input input18: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: input input17: PM: calling input_dev_suspend+0x0/0x70 @ 5277, parent: card1
Oct 11 17:34:22 ryzen kernel: input input17: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: input input16: PM: calling input_dev_suspend+0x0/0x70 @ 5277, parent: card1
Oct 11 17:34:22 ryzen kernel: snd_hda_codec_realtek hdaudioC2D0: PM: calling hda_codec_pm_suspend+0x0/0x20 [snd_hda_codec] @ 3803, parent: 0000:07:00.4
Oct 11 17:34:22 ryzen kernel: input input16: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: input input15: PM: calling input_dev_suspend+0x0/0x70 @ 5277, parent: card1
Oct 11 17:34:22 ryzen kernel: input input15: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: sound pcmC1D11p: PM: calling do_pcm_suspend+0x0/0x30 [snd_pcm] @ 5277, parent: card1
Oct 11 17:34:22 ryzen kernel: sound pcmC1D11p: PM: do_pcm_suspend+0x0/0x30 [snd_pcm] returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: sound pcmC1D10p: PM: calling do_pcm_suspend+0x0/0x30 [snd_pcm] @ 5277, parent: card1
Oct 11 17:34:22 ryzen kernel: sound pcmC1D10p: PM: do_pcm_suspend+0x0/0x30 [snd_pcm] returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: sound pcmC1D9p: PM: calling do_pcm_suspend+0x0/0x30 [snd_pcm] @ 5277, parent: card1
Oct 11 17:34:22 ryzen kernel: sound pcmC1D9p: PM: do_pcm_suspend+0x0/0x30 [snd_pcm] returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: sound pcmC1D8p: PM: calling do_pcm_suspend+0x0/0x30 [snd_pcm] @ 5277, parent: card1
Oct 11 17:34:22 ryzen kernel: sound pcmC1D8p: PM: do_pcm_suspend+0x0/0x30 [snd_pcm] returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: sound pcmC1D7p: PM: calling do_pcm_suspend+0x0/0x30 [snd_pcm] @ 5277, parent: card1
Oct 11 17:34:22 ryzen kernel: sound pcmC1D7p: PM: do_pcm_suspend+0x0/0x30 [snd_pcm] returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: sound pcmC1D3p: PM: calling do_pcm_suspend+0x0/0x30 [snd_pcm] @ 5277, parent: card1
Oct 11 17:34:22 ryzen kernel: sound pcmC1D3p: PM: do_pcm_suspend+0x0/0x30 [snd_pcm] returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: input input14: PM: calling input_dev_suspend+0x0/0x70 @ 5277, parent: pcspkr
Oct 11 17:34:22 ryzen kernel: input input14: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: sp5100-tco sp5100-tco: PM: calling platform_pm_suspend+0x0/0x50 @ 5277, parent: platform
Oct 11 17:34:22 ryzen kernel: sp5100-tco sp5100-tco: PM: platform_pm_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: input input11: PM: calling input_dev_suspend+0x0/0x70 @ 5277, parent: 0003:046D:C092.000A
Oct 11 17:34:22 ryzen kernel: input input11: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: input input10: PM: calling input_dev_suspend+0x0/0x70 @ 5277, parent: 0003:046D:C092.0009
Oct 11 17:34:22 ryzen kernel: input input10: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: usb 1-2.4: PM: calling usb_dev_suspend+0x0/0x20 @ 4566, parent: 1-2
Oct 11 17:34:22 ryzen kernel: input input9: PM: calling input_dev_suspend+0x0/0x70 @ 5277, parent: 0003:29EA:0102.0007
Oct 11 17:34:22 ryzen kernel: input input9: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: input input8: PM: calling input_dev_suspend+0x0/0x70 @ 5277, parent: 0003:29EA:0102.0007
Oct 11 17:34:22 ryzen kernel: usb 1-2.3: PM: calling usb_dev_suspend+0x0/0x20 @ 1219, parent: 1-2
Oct 11 17:34:22 ryzen kernel: input input8: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: leds input7::kana: PM: calling led_suspend+0x0/0x50 @ 5277, parent: input7
Oct 11 17:34:22 ryzen kernel: usb 1-2.4: PM: usb_dev_suspend+0x0/0x20 returned 0 after 5 usecs
Oct 11 17:34:22 ryzen kernel: leds input7::kana: PM: led_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: usb 1-10: PM: calling usb_dev_suspend+0x0/0x20 @ 3813, parent: usb1
Oct 11 17:34:22 ryzen kernel: leds input7::compose: PM: calling led_suspend+0x0/0x50 @ 5277, parent: input7
Oct 11 17:34:22 ryzen kernel: leds input7::compose: PM: led_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: leds input7::scrolllock: PM: calling led_suspend+0x0/0x50 @ 5277, parent: input7
Oct 11 17:34:22 ryzen kernel: leds input7::scrolllock: PM: led_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: usb 1-10: PM: usb_dev_suspend+0x0/0x20 returned 0 after 3 usecs
Oct 11 17:34:22 ryzen kernel: leds input7::capslock: PM: calling led_suspend+0x0/0x50 @ 5277, parent: input7
Oct 11 17:34:22 ryzen kernel: leds input7::capslock: PM: led_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: leds input7::numlock: PM: calling led_suspend+0x0/0x50 @ 5277, parent: input7
Oct 11 17:34:22 ryzen kernel: leds input7::numlock: PM: led_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: input input7: PM: calling input_dev_suspend+0x0/0x70 @ 5277, parent: 0003:29EA:0102.0006
Oct 11 17:34:22 ryzen kernel: input input7: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: input input6: PM: calling input_dev_suspend+0x0/0x70 @ 5277, parent: 0003:29EA:0102.0005
Oct 11 17:34:22 ryzen kernel: input input6: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: usb 1-2.2: PM: calling usb_dev_suspend+0x0/0x20 @ 3813, parent: 1-2
Oct 11 17:34:22 ryzen kernel: input input5: PM: calling input_dev_suspend+0x0/0x70 @ 5277, parent: 0003:0ECB:2057.0003
Oct 11 17:34:22 ryzen kernel: input input5: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: sd 6:0:0:0: PM: calling scsi_bus_suspend+0x0/0xc0 @ 321, parent: target6:0:0
Oct 11 17:34:22 ryzen kernel: usb 1-7: PM: calling usb_dev_suspend+0x0/0x20 @ 4554, parent: usb1
Oct 11 17:34:22 ryzen kernel: input input4: PM: calling input_dev_suspend+0x0/0x70 @ 5277, parent: 0003:05F3:00FF.0002
Oct 11 17:34:22 ryzen kernel: input input4: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: usb 1-7: PM: usb_dev_suspend+0x0/0x20 returned 0 after 4 usecs
Oct 11 17:34:22 ryzen kernel: input input3: PM: calling input_dev_suspend+0x0/0x70 @ 5277, parent: 0003:1852:7022.0001
Oct 11 17:34:22 ryzen kernel: input input3: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: usb 1-2.1: PM: calling usb_dev_suspend+0x0/0x20 @ 4554, parent: 1-2
Oct 11 17:34:22 ryzen kernel: leds input2::scrolllock: PM: calling led_suspend+0x0/0x50 @ 5277, parent: input2
Oct 11 17:34:22 ryzen kernel: leds input2::scrolllock: PM: led_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: leds input2::capslock: PM: calling led_suspend+0x0/0x50 @ 5277, parent: input2
Oct 11 17:34:22 ryzen kernel: leds input2::capslock: PM: led_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: leds input2::numlock: PM: calling led_suspend+0x0/0x50 @ 5277, parent: input2
Oct 11 17:34:22 ryzen kernel: leds input2::numlock: PM: led_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: input input2: PM: calling input_dev_suspend+0x0/0x70 @ 5277, parent: serio0
Oct 11 17:34:22 ryzen kernel: input input2: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: atkbd serio0: PM: calling serio_suspend+0x0/0x50 [serio] @ 5277, parent: i8042
Oct 11 17:34:22 ryzen kernel: usb 1-5: PM: calling usb_dev_suspend+0x0/0x20 @ 3812, parent: usb1
Oct 11 17:34:22 ryzen kernel: usb 3-2: PM: calling usb_dev_suspend+0x0/0x20 @ 4568, parent: usb3
Oct 11 17:34:22 ryzen kernel: usb usb4: PM: calling usb_dev_suspend+0x0/0x20 @ 4586, parent: 0000:07:00.3
Oct 11 17:34:22 ryzen kernel: usb 3-2: PM: usb_dev_suspend+0x0/0x20 returned 0 after 82 usecs
Oct 11 17:34:22 ryzen kernel: usb usb3: PM: calling usb_dev_suspend+0x0/0x20 @ 4530, parent: 0000:07:00.3
Oct 11 17:34:22 ryzen kernel: usb 1-5: PM: usb_dev_suspend+0x0/0x20 returned 0 after 1240 usecs
Oct 11 17:34:22 ryzen kernel: usb 1-2.3: PM: usb_dev_suspend+0x0/0x20 returned 0 after 1908 usecs
Oct 11 17:34:22 ryzen kernel: usb 1-2.1: PM: usb_dev_suspend+0x0/0x20 returned 0 after 2140 usecs
Oct 11 17:34:22 ryzen kernel: atkbd serio0: PM: serio_suspend+0x0/0x50 [serio] returned 0 after 2786 usecs
Oct 11 17:34:22 ryzen kernel: i8042 i8042: PM: calling platform_pm_suspend+0x0/0x50 @ 5277, parent: platform
Oct 11 17:34:22 ryzen kernel: i8042 i8042: PM: platform_pm_suspend+0x0/0x50 returned 0 after 127 usecs
Oct 11 17:34:22 ryzen kernel: platform microcode: PM: calling platform_pm_suspend+0x0/0x50 @ 5277, parent: platform
Oct 11 17:34:22 ryzen kernel: sr 1:0:0:0: PM: calling scsi_bus_suspend+0x0/0xc0 @ 4554, parent: target1:0:0
Oct 11 17:34:22 ryzen kernel: platform microcode: PM: platform_pm_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: alarmtimer alarmtimer.0.auto: PM: calling platform_pm_suspend+0x0/0x50 @ 5277, parent: rtc0
Oct 11 17:34:22 ryzen kernel: alarmtimer alarmtimer.0.auto: PM: platform_pm_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: rtc rtc0: PM: calling rtc_suspend+0x0/0x1f0 @ 5277, parent: 00:02
Oct 11 17:34:22 ryzen kernel: rtc rtc0: PM: rtc_suspend+0x0/0x1f0 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: sd 0:0:0:0: PM: calling scsi_bus_suspend+0x0/0xc0 @ 3812, parent: target0:0:0
Oct 11 17:34:22 ryzen kernel: scsi host5: PM: calling scsi_bus_suspend+0x0/0xc0 @ 4582, parent: ata6
Oct 11 17:34:22 ryzen kernel: scsi host5: PM: scsi_bus_suspend+0x0/0xc0 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: scsi host4: PM: calling scsi_bus_suspend+0x0/0xc0 @ 10, parent: ata5
Oct 11 17:34:22 ryzen kernel: scsi host4: PM: scsi_bus_suspend+0x0/0xc0 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: scsi host3: PM: calling scsi_bus_suspend+0x0/0xc0 @ 4582, parent: ata4
Oct 11 17:34:22 ryzen kernel: scsi host3: PM: scsi_bus_suspend+0x0/0xc0 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: scsi host2: PM: calling scsi_bus_suspend+0x0/0xc0 @ 4551, parent: ata3
Oct 11 17:34:22 ryzen kernel: scsi host2: PM: scsi_bus_suspend+0x0/0xc0 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: ata5: PM: calling ata_port_pm_suspend+0x0/0x50 @ 4582, parent: 0000:02:00.1
Oct 11 17:34:22 ryzen kernel: ata6: PM: calling ata_port_pm_suspend+0x0/0x50 @ 4535, parent: 0000:02:00.1
Oct 11 17:34:22 ryzen kernel: ata4: PM: calling ata_port_pm_suspend+0x0/0x50 @ 4557, parent: 0000:02:00.1
Oct 11 17:34:22 ryzen kernel: ata3: PM: calling ata_port_pm_suspend+0x0/0x50 @ 4551, parent: 0000:02:00.1
Oct 11 17:34:22 ryzen kernel: port serial8250:0.31: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 5277, parent: serial8250:0
Oct 11 17:34:22 ryzen kernel: port serial8250:0.31: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: port serial8250:0.30: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 5277, parent: serial8250:0
Oct 11 17:34:22 ryzen kernel: port serial8250:0.30: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: port serial8250:0.29: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 5277, parent: serial8250:0
Oct 11 17:34:22 ryzen kernel: port serial8250:0.29: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: port serial8250:0.28: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 5277, parent: serial8250:0
Oct 11 17:34:22 ryzen kernel: port serial8250:0.28: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: ata5: PM: ata_port_pm_suspend+0x0/0x50 returned 0 after 29 usecs
Oct 11 17:34:22 ryzen kernel: port serial8250:0.27: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 5277, parent: serial8250:0
Oct 11 17:34:22 ryzen kernel: port serial8250:0.27: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: port serial8250:0.26: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 5277, parent: serial8250:0
Oct 11 17:34:22 ryzen kernel: port serial8250:0.26: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: ata4: PM: ata_port_pm_suspend+0x0/0x50 returned 0 after 41 usecs
Oct 11 17:34:22 ryzen kernel: port serial8250:0.25: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 5277, parent: serial8250:0
Oct 11 17:34:22 ryzen kernel: port serial8250:0.25: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: port serial8250:0.24: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 5277, parent: serial8250:0
Oct 11 17:34:22 ryzen kernel: port serial8250:0.24: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: ata3: PM: ata_port_pm_suspend+0x0/0x50 returned 0 after 50 usecs
Oct 11 17:34:22 ryzen kernel: port serial8250:0.23: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 5277, parent: serial8250:0
Oct 11 17:34:22 ryzen kernel: port serial8250:0.23: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: port serial8250:0.22: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 5277, parent: serial8250:0
Oct 11 17:34:22 ryzen kernel: port serial8250:0.22: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: ata6: PM: ata_port_pm_suspend+0x0/0x50 returned 0 after 74 usecs
Oct 11 17:34:22 ryzen kernel: port serial8250:0.21: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 5277, parent: serial8250:0
Oct 11 17:34:22 ryzen kernel: port serial8250:0.21: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: port serial8250:0.20: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 5277, parent: serial8250:0
Oct 11 17:34:22 ryzen kernel: port serial8250:0.20: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: port serial8250:0.19: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 5277, parent: serial8250:0
Oct 11 17:34:22 ryzen kernel: port serial8250:0.19: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: port serial8250:0.18: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 5277, parent: serial8250:0
Oct 11 17:34:22 ryzen kernel: port serial8250:0.18: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: port serial8250:0.17: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 5277, parent: serial8250:0
Oct 11 17:34:22 ryzen kernel: port serial8250:0.17: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: port serial8250:0.16: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 5277, parent: serial8250:0
Oct 11 17:34:22 ryzen kernel: port serial8250:0.16: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: port serial8250:0.15: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 5277, parent: serial8250:0
Oct 11 17:34:22 ryzen kernel: port serial8250:0.15: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: port serial8250:0.14: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 5277, parent: serial8250:0
Oct 11 17:34:22 ryzen kernel: port serial8250:0.14: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: port serial8250:0.13: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 5277, parent: serial8250:0
Oct 11 17:34:22 ryzen kernel: port serial8250:0.13: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: port serial8250:0.12: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 5277, parent: serial8250:0
Oct 11 17:34:22 ryzen kernel: port serial8250:0.12: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: port serial8250:0.11: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 5277, parent: serial8250:0
Oct 11 17:34:22 ryzen kernel: port serial8250:0.11: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: port serial8250:0.10: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 5277, parent: serial8250:0
Oct 11 17:34:22 ryzen kernel: port serial8250:0.10: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: port serial8250:0.9: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 5277, parent: serial8250:0
Oct 11 17:34:22 ryzen kernel: port serial8250:0.9: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: port serial8250:0.8: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 5277, parent: serial8250:0
Oct 11 17:34:22 ryzen kernel: port serial8250:0.8: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: port serial8250:0.7: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 5277, parent: serial8250:0
Oct 11 17:34:22 ryzen kernel: port serial8250:0.7: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: port serial8250:0.6: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 5277, parent: serial8250:0
Oct 11 17:34:22 ryzen kernel: port serial8250:0.6: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: port serial8250:0.5: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 5277, parent: serial8250:0
Oct 11 17:34:22 ryzen kernel: port serial8250:0.5: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: port serial8250:0.4: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 5277, parent: serial8250:0
Oct 11 17:34:22 ryzen kernel: port serial8250:0.4: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: port serial8250:0.3: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 5277, parent: serial8250:0
Oct 11 17:34:22 ryzen kernel: port serial8250:0.3: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: port serial8250:0.2: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 5277, parent: serial8250:0
Oct 11 17:34:22 ryzen kernel: port serial8250:0.2: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: port serial8250:0.1: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 5277, parent: serial8250:0
Oct 11 17:34:22 ryzen kernel: port serial8250:0.1: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: serial8250 serial8250: PM: calling platform_pm_suspend+0x0/0x50 @ 5277, parent: platform
Oct 11 17:34:22 ryzen kernel: serial8250 serial8250: PM: platform_pm_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: port 00:05:0.0: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 5277, parent: 00:05:0
Oct 11 17:34:22 ryzen kernel: port 00:05:0.0: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: input input1: PM: calling input_dev_suspend+0x0/0x70 @ 5277, parent: LNXPWRBN:00
Oct 11 17:34:22 ryzen kernel: input input1: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: input input0: PM: calling input_dev_suspend+0x0/0x70 @ 5277, parent: PNP0C0C:00
Oct 11 17:34:22 ryzen kernel: input input0: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: pcspkr pcspkr: PM: calling platform_pm_suspend+0x0/0x50 @ 5277, parent: platform
Oct 11 17:34:22 ryzen kernel: pcspkr pcspkr: PM: platform_pm_suspend+0x0/0x50 returned 0 after 4 usecs
Oct 11 17:34:22 ryzen kernel: snd_hda_intel 0000:05:00.1: PM: calling pci_pm_suspend+0x0/0x170 @ 4535, parent: 0000:00:03.1
Oct 11 17:34:22 ryzen kernel: system 00:06: PM: calling pnp_bus_suspend+0x0/0x20 @ 5277, parent: pnp0
Oct 11 17:34:22 ryzen kernel: system 00:06: PM: pnp_bus_suspend+0x0/0x20 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: serial 00:05: PM: calling pnp_bus_suspend+0x0/0x20 @ 5277, parent: pnp0
Oct 11 17:34:22 ryzen kernel: serial 00:05: PM: pnp_bus_suspend+0x0/0x20 returned 0 after 5 usecs
Oct 11 17:34:22 ryzen kernel: i8042 kbd 00:04: PM: calling pnp_bus_suspend+0x0/0x20 @ 5277, parent: pnp0
Oct 11 17:34:22 ryzen kernel: i8042 kbd 00:04: PM: pnp_bus_suspend+0x0/0x20 returned 0 after 51 usecs
Oct 11 17:34:22 ryzen kernel: system 00:03: PM: calling pnp_bus_suspend+0x0/0x20 @ 5277, parent: pnp0
Oct 11 17:34:22 ryzen kernel: system 00:03: PM: pnp_bus_suspend+0x0/0x20 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: rtc_cmos 00:02: PM: calling pnp_bus_suspend+0x0/0x20 @ 5277, parent: pnp0
Oct 11 17:34:22 ryzen kernel: rtc_cmos 00:02: PM: pnp_bus_suspend+0x0/0x20 returned 0 after 23 usecs
Oct 11 17:34:22 ryzen kernel: system 00:01: PM: calling pnp_bus_suspend+0x0/0x20 @ 5277, parent: pnp0
Oct 11 17:34:22 ryzen kernel: system 00:01: PM: pnp_bus_suspend+0x0/0x20 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: system 00:00: PM: calling pnp_bus_suspend+0x0/0x20 @ 5277, parent: pnp0
Oct 11 17:34:22 ryzen kernel: system 00:00: PM: pnp_bus_suspend+0x0/0x20 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: platform efivars.0: PM: calling platform_pm_suspend+0x0/0x50 @ 5277, parent: platform
Oct 11 17:34:22 ryzen kernel: platform efivars.0: PM: platform_pm_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: platform rtc-efi.0: PM: calling platform_pm_suspend+0x0/0x50 @ 5277, parent: platform
Oct 11 17:34:22 ryzen kernel: platform rtc-efi.0: PM: platform_pm_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: button LNXPWRBN:00: PM: calling acpi_button_suspend+0x0/0x20 @ 5277, parent: LNXSYSTM:00
Oct 11 17:34:22 ryzen kernel: button LNXPWRBN:00: PM: acpi_button_suspend+0x0/0x20 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: acpi-wmi PNP0C14:01: PM: calling acpi_subsys_suspend+0x0/0x60 @ 5277, parent: platform
Oct 11 17:34:22 ryzen kernel: acpi-wmi PNP0C14:01: PM: acpi_subsys_suspend+0x0/0x60 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: acpi-wmi PNP0C14:00: PM: calling acpi_subsys_suspend+0x0/0x60 @ 5277, parent: platform
Oct 11 17:34:22 ryzen kernel: acpi-wmi PNP0C14:00: PM: acpi_subsys_suspend+0x0/0x60 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: platform PNP0103:00: PM: calling platform_pm_suspend+0x0/0x50 @ 5277, parent: platform
Oct 11 17:34:22 ryzen kernel: platform PNP0103:00: PM: platform_pm_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: pt-gpio AMDIF030:00: PM: calling acpi_subsys_suspend+0x0/0x60 @ 5277, parent: platform
Oct 11 17:34:22 ryzen kernel: pt-gpio AMDIF030:00: PM: acpi_subsys_suspend+0x0/0x60 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: acpi-cpufreq acpi-cpufreq: PM: calling platform_pm_suspend+0x0/0x50 @ 5277, parent: platform
Oct 11 17:34:22 ryzen kernel: acpi-cpufreq acpi-cpufreq: PM: platform_pm_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: platform MSFT0101:00: PM: calling platform_pm_suspend+0x0/0x50 @ 5277, parent: platform
Oct 11 17:34:22 ryzen kernel: platform MSFT0101:00: PM: platform_pm_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: amd_gpio AMDI0030:00: PM: calling acpi_subsys_suspend+0x0/0x60 @ 5277, parent: platform
Oct 11 17:34:22 ryzen kernel: amd_gpio AMDI0030:00: PM: acpi_subsys_suspend+0x0/0x60 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: platform PNP0C0C:00: PM: calling platform_pm_suspend+0x0/0x50 @ 5277, parent: platform
Oct 11 17:34:22 ryzen kernel: platform PNP0C0C:00: PM: platform_pm_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: platform PNP0800:00: PM: calling platform_pm_suspend+0x0/0x50 @ 5277, parent: 0000:00:14.3
Oct 11 17:34:22 ryzen kernel: platform PNP0800:00: PM: platform_pm_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: ccp 0000:07:00.1: PM: calling pci_pm_suspend+0x0/0x170 @ 4551, parent: 0000:00:08.1
Oct 11 17:34:22 ryzen kernel: ccp 0000:07:00.1: PM: pci_pm_suspend+0x0/0x170 returned 0 after 1 usecs
Oct 11 17:34:22 ryzen kernel: pci 0000:07:00.0: PM: calling pci_pm_suspend+0x0/0x170 @ 144, parent: 0000:00:08.1
Oct 11 17:34:22 ryzen kernel: pci 0000:07:00.0: PM: pci_pm_suspend+0x0/0x170 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: pci 0000:06:00.0: PM: calling pci_pm_suspend+0x0/0x170 @ 12, parent: 0000:00:07.1
Oct 11 17:34:22 ryzen kernel: thermal LNXTHERM:01: PM: calling acpi_thermal_suspend+0x0/0x20 @ 5277, parent: LNXSYBUS:01
Oct 11 17:34:22 ryzen kernel: pci 0000:06:00.0: PM: pci_pm_suspend+0x0/0x170 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: r8169 0000:04:00.0: PM: calling pci_pm_suspend+0x0/0x170 @ 147, parent: 0000:03:09.0
Oct 11 17:34:22 ryzen kernel: thermal LNXTHERM:01: PM: acpi_thermal_suspend+0x0/0x20 returned 0 after 2 usecs
Oct 11 17:34:22 ryzen kernel: r8169 0000:04:00.0: PM: pci_pm_suspend+0x0/0x170 returned 0 after 1 usecs
Oct 11 17:34:22 ryzen kernel: thermal LNXTHERM:00: PM: calling acpi_thermal_suspend+0x0/0x20 @ 5277, parent: LNXSYBUS:01
Oct 11 17:34:22 ryzen kernel: nvme 0000:01:00.0: PM: calling pci_pm_suspend+0x0/0x170 @ 147, parent: 0000:00:01.1
Oct 11 17:34:22 ryzen kernel: pcieport 0000:03:09.0: PM: calling pci_pm_suspend+0x0/0x170 @ 144, parent: 0000:02:00.2
Oct 11 17:34:22 ryzen kernel: thermal LNXTHERM:00: PM: acpi_thermal_suspend+0x0/0x20 returned 0 after 1 usecs
Oct 11 17:34:22 ryzen kernel: pcieport 0000:03:09.0: PM: pci_pm_suspend+0x0/0x170 returned 0 after 1 usecs
Oct 11 17:34:22 ryzen kernel: pci 0000:00:18.7: PM: calling pci_pm_suspend+0x0/0x170 @ 144, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pcieport 0000:02:00.2: PM: calling pci_pm_suspend+0x0/0x170 @ 4523, parent: 0000:00:01.2
Oct 11 17:34:22 ryzen kernel: pci 0000:00:18.7: PM: pci_pm_suspend+0x0/0x170 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: pci 0000:00:18.6: PM: calling pci_pm_suspend+0x0/0x170 @ 4563, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pcieport 0000:02:00.2: PM: pci_pm_suspend+0x0/0x170 returned 0 after 1 usecs
Oct 11 17:34:22 ryzen kernel: pci 0000:00:18.5: PM: calling pci_pm_suspend+0x0/0x170 @ 3814, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pci 0000:00:18.4: PM: calling pci_pm_suspend+0x0/0x170 @ 144, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pci 0000:00:18.5: PM: pci_pm_suspend+0x0/0x170 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: pci 0000:00:18.4: PM: pci_pm_suspend+0x0/0x170 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: pci 0000:00:18.6: PM: pci_pm_suspend+0x0/0x170 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: pci 0000:00:18.2: PM: calling pci_pm_suspend+0x0/0x170 @ 4523, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: k10temp 0000:00:18.3: PM: calling pci_pm_suspend+0x0/0x170 @ 4576, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pci 0000:00:18.1: PM: calling pci_pm_suspend+0x0/0x170 @ 3814, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: tpm_crb MSFT0101:00: PM: calling tpm_pm_suspend+0x0/0xd0 @ 5277, parent: LNXSYBUS:00
Oct 11 17:34:22 ryzen kernel: pci 0000:00:18.2: PM: pci_pm_suspend+0x0/0x170 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: pci 0000:00:18.1: PM: pci_pm_suspend+0x0/0x170 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: k10temp 0000:00:18.3: PM: pci_pm_suspend+0x0/0x170 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: pci 0000:00:14.3: PM: calling pci_pm_suspend+0x0/0x170 @ 4563, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: piix4_smbus 0000:00:14.0: PM: calling pci_pm_suspend+0x0/0x170 @ 144, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pci 0000:00:18.0: PM: calling pci_pm_suspend+0x0/0x170 @ 4558, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pci 0000:00:08.0: PM: calling pci_pm_suspend+0x0/0x170 @ 4576, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: piix4_smbus 0000:00:14.0: PM: pci_pm_suspend+0x0/0x170 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: pci 0000:00:08.0: PM: pci_pm_suspend+0x0/0x170 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: pci 0000:00:14.3: PM: pci_pm_suspend+0x0/0x170 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: pci 0000:00:07.0: PM: calling pci_pm_suspend+0x0/0x170 @ 4523, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pci 0000:00:18.0: PM: pci_pm_suspend+0x0/0x170 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: pcieport 0000:00:07.1: PM: calling pci_pm_suspend+0x0/0x170 @ 4536, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pci 0000:00:07.0: PM: pci_pm_suspend+0x0/0x170 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: pci 0000:00:04.0: PM: calling pci_pm_suspend+0x0/0x170 @ 144, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pci 0000:00:05.0: PM: calling pci_pm_suspend+0x0/0x170 @ 4578, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pci 0000:00:03.0: PM: calling pci_pm_suspend+0x0/0x170 @ 4576, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pci 0000:00:02.0: PM: calling pci_pm_suspend+0x0/0x170 @ 4523, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pci 0000:00:03.0: PM: pci_pm_suspend+0x0/0x170 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: pci 0000:00:05.0: PM: pci_pm_suspend+0x0/0x170 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: pci 0000:00:02.0: PM: pci_pm_suspend+0x0/0x170 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: pcieport 0000:00:07.1: PM: pci_pm_suspend+0x0/0x170 returned 0 after 3 usecs
Oct 11 17:34:22 ryzen kernel: pci 0000:00:04.0: PM: pci_pm_suspend+0x0/0x170 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: pci 0000:00:01.0: PM: calling pci_pm_suspend+0x0/0x170 @ 4523, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pci 0000:00:00.2: PM: calling pci_pm_suspend+0x0/0x170 @ 4576, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pci 0000:00:00.0: PM: calling pci_pm_suspend+0x0/0x170 @ 4536, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pci 0000:00:01.0: PM: pci_pm_suspend+0x0/0x170 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: pci 0000:00:00.2: PM: pci_pm_suspend+0x0/0x170 returned 0 after 1 usecs
Oct 11 17:34:22 ryzen kernel: pci 0000:00:00.0: PM: pci_pm_suspend+0x0/0x170 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: usb usb3: PM: usb_dev_suspend+0x0/0x20 returned 0 after 8538 usecs
Oct 11 17:34:22 ryzen kernel: tpm_crb MSFT0101:00: PM: tpm_pm_suspend+0x0/0xd0 returned 0 after 8517 usecs
Oct 11 17:34:22 ryzen kernel: button PNP0C0C:00: PM: calling acpi_button_suspend+0x0/0x20 @ 5277, parent: LNXSYBUS:00
Oct 11 17:34:22 ryzen kernel: button PNP0C0C:00: PM: acpi_button_suspend+0x0/0x20 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: PCCT PCCT: PM: calling platform_pm_suspend+0x0/0x50 @ 5277, parent: platform
Oct 11 17:34:22 ryzen kernel: PCCT PCCT: PM: platform_pm_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: regulator regulator.0: PM: calling regulator_suspend+0x0/0x120 @ 5277, parent: reg-dummy
Oct 11 17:34:22 ryzen kernel: regulator regulator.0: PM: regulator_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: reg-dummy reg-dummy: PM: calling platform_pm_suspend+0x0/0x50 @ 5277, parent: platform
Oct 11 17:34:22 ryzen kernel: reg-dummy reg-dummy: PM: platform_pm_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: snd_hda_codec_realtek hdaudioC2D0: PM: hda_codec_pm_suspend+0x0/0x20 [snd_hda_codec] returned 0 after 16766 usecs
Oct 11 17:34:22 ryzen kernel: snd_hda_intel 0000:07:00.4: PM: calling pci_pm_suspend+0x0/0x170 @ 4557, parent: 0000:00:08.1
Oct 11 17:34:22 ryzen kernel: snd_hda_intel 0000:07:00.4: PM: pci_pm_suspend+0x0/0x170 returned 0 after 1077 usecs
Oct 11 17:34:22 ryzen kernel: snd_hda_intel 0000:05:00.1: PM: pci_pm_suspend+0x0/0x170 returned 0 after 14330 usecs
Oct 11 17:34:22 ryzen kernel: amdgpu 0000:05:00.0: PM: calling pci_pm_suspend+0x0/0x170 @ 4551, parent: 0000:00:03.1
Oct 11 17:34:22 ryzen kernel: sd 6:0:0:0: PM: scsi_bus_suspend+0x0/0xc0 returned 0 after 18871 usecs
Oct 11 17:34:22 ryzen kernel: scsi target6:0:0: PM: calling scsi_bus_suspend+0x0/0xc0 @ 4566, parent: host6
Oct 11 17:34:22 ryzen kernel: scsi target6:0:0: PM: scsi_bus_suspend+0x0/0xc0 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: scsi host6: PM: calling scsi_bus_suspend+0x0/0xc0 @ 317, parent: 2-4:1.0
Oct 11 17:34:22 ryzen kernel: scsi host6: PM: scsi_bus_suspend+0x0/0xc0 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: usb 2-4: PM: calling usb_dev_suspend+0x0/0x20 @ 4583, parent: usb2
Oct 11 17:34:22 ryzen kernel: usb usb4: PM: usb_dev_suspend+0x0/0x20 returned 0 after 25332 usecs
Oct 11 17:34:22 ryzen kernel: xhci_hcd 0000:07:00.3: PM: calling pci_pm_suspend+0x0/0x170 @ 4582, parent: 0000:00:08.1
Oct 11 17:34:22 ryzen kernel: xhci_hcd 0000:07:00.3: PM: pci_pm_suspend+0x0/0x170 returned 0 after 155 usecs
Oct 11 17:34:22 ryzen kernel: pcieport 0000:00:08.1: PM: calling pci_pm_suspend+0x0/0x170 @ 3814, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pcieport 0000:00:08.1: PM: pci_pm_suspend+0x0/0x170 returned 0 after 1 usecs
Oct 11 17:34:22 ryzen kernel: usb 1-2.2: PM: usb_dev_suspend+0x0/0x20 returned 0 after 28809 usecs
Oct 11 17:34:22 ryzen kernel: usb 1-2: PM: calling usb_dev_suspend+0x0/0x20 @ 148, parent: usb1
Oct 11 17:34:22 ryzen kernel: sr 1:0:0:0: PM: scsi_bus_suspend+0x0/0xc0 returned 0 after 29141 usecs
Oct 11 17:34:22 ryzen kernel: scsi target1:0:0: PM: calling scsi_bus_suspend+0x0/0xc0 @ 1219, parent: host1
Oct 11 17:34:22 ryzen kernel: scsi target1:0:0: PM: scsi_bus_suspend+0x0/0xc0 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Oct 11 17:34:22 ryzen kernel: scsi host1: PM: calling scsi_bus_suspend+0x0/0xc0 @ 10, parent: ata2
Oct 11 17:34:22 ryzen kernel: scsi host1: PM: scsi_bus_suspend+0x0/0xc0 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: ata2: PM: calling ata_port_pm_suspend+0x0/0x50 @ 4533, parent: 0000:02:00.1
Oct 11 17:34:22 ryzen kernel: ata2: PM: ata_port_pm_suspend+0x0/0x50 returned 0 after 24 usecs
Oct 11 17:34:22 ryzen kernel: sd 0:0:0:0: [sda] Stopping disk
Oct 11 17:34:22 ryzen kernel: usb 2-4: PM: usb_dev_suspend+0x0/0x20 returned 0 after 23213 usecs
Oct 11 17:34:22 ryzen kernel: usb usb2: PM: calling usb_dev_suspend+0x0/0x20 @ 4584, parent: 0000:02:00.0
Oct 11 17:34:22 ryzen kernel: usb usb2: PM: usb_dev_suspend+0x0/0x20 returned 0 after 13 usecs
Oct 11 17:34:22 ryzen kernel: usb 1-2: PM: usb_dev_suspend+0x0/0x20 returned 0 after 33319 usecs
Oct 11 17:34:22 ryzen kernel: usb usb1: PM: calling usb_dev_suspend+0x0/0x20 @ 146, parent: 0000:02:00.0
Oct 11 17:34:22 ryzen kernel: usb usb1: PM: usb_dev_suspend+0x0/0x20 returned 0 after 11069 usecs
Oct 11 17:34:22 ryzen kernel: xhci_hcd 0000:02:00.0: PM: calling pci_pm_suspend+0x0/0x170 @ 4526, parent: 0000:00:01.2
Oct 11 17:34:22 ryzen kernel: xhci_hcd 0000:02:00.0: PM: pci_pm_suspend+0x0/0x170 returned 0 after 1113 usecs
Oct 11 17:34:22 ryzen kernel: amdgpu 0000:05:00.0: PM: pci_pm_suspend+0x0/0x170 returned 0 after 153812 usecs
Oct 11 17:34:22 ryzen kernel: pcieport 0000:00:03.1: PM: calling pci_pm_suspend+0x0/0x170 @ 4563, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pcieport 0000:00:03.1: PM: pci_pm_suspend+0x0/0x170 returned 0 after 2 usecs
Oct 11 17:34:22 ryzen kernel: sd 0:0:0:0: PM: scsi_bus_suspend+0x0/0xc0 returned 0 after 438971 usecs
Oct 11 17:34:22 ryzen kernel: scsi target0:0:0: PM: calling scsi_bus_suspend+0x0/0xc0 @ 4568, parent: host0
Oct 11 17:34:22 ryzen kernel: scsi target0:0:0: PM: scsi_bus_suspend+0x0/0xc0 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: scsi host0: PM: calling scsi_bus_suspend+0x0/0xc0 @ 96, parent: ata1
Oct 11 17:34:22 ryzen kernel: scsi host0: PM: scsi_bus_suspend+0x0/0xc0 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: ata1: PM: calling ata_port_pm_suspend+0x0/0x50 @ 4529, parent: 0000:02:00.1
Oct 11 17:34:22 ryzen kernel: ata1: PM: ata_port_pm_suspend+0x0/0x50 returned 0 after 27 usecs
Oct 11 17:34:22 ryzen kernel: ahci 0000:02:00.1: PM: calling pci_pm_suspend+0x0/0x170 @ 12, parent: 0000:00:01.2
Oct 11 17:34:22 ryzen kernel: ahci 0000:02:00.1: PM: pci_pm_suspend+0x0/0x170 returned 0 after 2 usecs
Oct 11 17:34:22 ryzen kernel: pcieport 0000:00:01.2: PM: calling pci_pm_suspend+0x0/0x170 @ 4558, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pcieport 0000:00:01.2: PM: pci_pm_suspend+0x0/0x170 returned 0 after 2 usecs
Oct 11 17:34:22 ryzen kernel: nvme 0000:01:00.0: PM: pci_pm_suspend+0x0/0x170 returned 0 after 524532 usecs
Oct 11 17:34:22 ryzen kernel: pcieport 0000:00:01.1: PM: calling pci_pm_suspend+0x0/0x170 @ 4580, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pcieport 0000:00:01.1: PM: pci_pm_suspend+0x0/0x170 returned 0 after 5 usecs
Oct 11 17:34:22 ryzen kernel: PM: suspend of devices complete after 528.807 msecs
Oct 11 17:34:22 ryzen kernel: PM: start suspend of devices complete after 4465.276 msecs
Oct 11 17:34:22 ryzen kernel: snd_hda_intel 0000:05:00.1: PM: calling pci_pm_suspend_late+0x0/0x40 @ 4578, parent: 0000:00:03.1
Oct 11 17:34:22 ryzen kernel: snd_hda_intel 0000:05:00.1: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: acpi-wmi PNP0C14:01: PM: calling acpi_subsys_suspend_late+0x0/0x50 @ 5277, parent: platform
Oct 11 17:34:22 ryzen kernel: acpi-wmi PNP0C14:01: PM: acpi_subsys_suspend_late+0x0/0x50 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: acpi-wmi PNP0C14:00: PM: calling acpi_subsys_suspend_late+0x0/0x50 @ 5277, parent: platform
Oct 11 17:34:22 ryzen kernel: acpi-wmi PNP0C14:00: PM: acpi_subsys_suspend_late+0x0/0x50 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: pt-gpio AMDIF030:00: PM: calling acpi_subsys_suspend_late+0x0/0x50 @ 5277, parent: platform
Oct 11 17:34:22 ryzen kernel: pt-gpio AMDIF030:00: PM: acpi_subsys_suspend_late+0x0/0x50 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: amd_gpio AMDI0030:00: PM: calling acpi_subsys_suspend_late+0x0/0x50 @ 5277, parent: platform
Oct 11 17:34:22 ryzen kernel: amd_gpio AMDI0030:00: PM: acpi_subsys_suspend_late+0x0/0x50 returned 0 after 8 usecs
Oct 11 17:34:22 ryzen kernel: snd_hda_intel 0000:07:00.4: PM: calling pci_pm_suspend_late+0x0/0x40 @ 4578, parent: 0000:00:08.1
Oct 11 17:34:22 ryzen kernel: xhci_hcd 0000:07:00.3: PM: calling pci_pm_suspend_late+0x0/0x40 @ 4580, parent: 0000:00:08.1
Oct 11 17:34:22 ryzen kernel: snd_hda_intel 0000:07:00.4: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: xhci_hcd 0000:07:00.3: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: ccp 0000:07:00.1: PM: calling pci_pm_suspend_late+0x0/0x40 @ 4578, parent: 0000:00:08.1
Oct 11 17:34:22 ryzen kernel: pci 0000:07:00.0: PM: calling pci_pm_suspend_late+0x0/0x40 @ 4580, parent: 0000:00:08.1
Oct 11 17:34:22 ryzen kernel: ccp 0000:07:00.1: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: pci 0000:07:00.0: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: pci 0000:06:00.0: PM: calling pci_pm_suspend_late+0x0/0x40 @ 4578, parent: 0000:00:07.1
Oct 11 17:34:22 ryzen kernel: amdgpu 0000:05:00.0: PM: calling pci_pm_suspend_late+0x0/0x40 @ 4580, parent: 0000:00:03.1
Oct 11 17:34:22 ryzen kernel: pci 0000:06:00.0: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: amdgpu 0000:05:00.0: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: r8169 0000:04:00.0: PM: calling pci_pm_suspend_late+0x0/0x40 @ 4558, parent: 0000:03:09.0
Oct 11 17:34:22 ryzen kernel: ahci 0000:02:00.1: PM: calling pci_pm_suspend_late+0x0/0x40 @ 4580, parent: 0000:00:01.2
Oct 11 17:34:22 ryzen kernel: ahci 0000:02:00.1: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: r8169 0000:04:00.0: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: nvme 0000:01:00.0: PM: calling pci_pm_suspend_late+0x0/0x40 @ 4580, parent: 0000:00:01.1
Oct 11 17:34:22 ryzen kernel: xhci_hcd 0000:02:00.0: PM: calling pci_pm_suspend_late+0x0/0x40 @ 12, parent: 0000:00:01.2
Oct 11 17:34:22 ryzen kernel: nvme 0000:01:00.0: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: pci 0000:00:18.7: PM: calling pci_pm_suspend_late+0x0/0x40 @ 4558, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pcieport 0000:03:09.0: PM: calling pci_pm_suspend_late+0x0/0x40 @ 147, parent: 0000:02:00.2
Oct 11 17:34:22 ryzen kernel: pci 0000:00:18.6: PM: calling pci_pm_suspend_late+0x0/0x40 @ 4580, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: xhci_hcd 0000:02:00.0: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: pci 0000:00:18.7: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: pcieport 0000:03:09.0: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: pci 0000:00:18.6: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: pci 0000:00:18.5: PM: calling pci_pm_suspend_late+0x0/0x40 @ 4558, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pci 0000:00:18.4: PM: calling pci_pm_suspend_late+0x0/0x40 @ 12, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pci 0000:00:18.2: PM: calling pci_pm_suspend_late+0x0/0x40 @ 4580, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: k10temp 0000:00:18.3: PM: calling pci_pm_suspend_late+0x0/0x40 @ 147, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pcieport 0000:02:00.2: PM: calling pci_pm_suspend_late+0x0/0x40 @ 4578, parent: 0000:00:01.2
Oct 11 17:34:22 ryzen kernel: pci 0000:00:18.5: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: pci 0000:00:18.4: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: pci 0000:00:18.2: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: pcieport 0000:02:00.2: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: k10temp 0000:00:18.3: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: pci 0000:00:18.0: PM: calling pci_pm_suspend_late+0x0/0x40 @ 4558, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pci 0000:00:18.1: PM: calling pci_pm_suspend_late+0x0/0x40 @ 4529, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pci 0000:00:14.3: PM: calling pci_pm_suspend_late+0x0/0x40 @ 4580, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: piix4_smbus 0000:00:14.0: PM: calling pci_pm_suspend_late+0x0/0x40 @ 4578, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pci 0000:00:08.0: PM: calling pci_pm_suspend_late+0x0/0x40 @ 147, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pcieport 0000:00:08.1: PM: calling pci_pm_suspend_late+0x0/0x40 @ 12, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pci 0000:00:14.3: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: piix4_smbus 0000:00:14.0: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: pci 0000:00:18.1: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: pci 0000:00:08.0: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: pcieport 0000:00:08.1: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: pcieport 0000:00:07.1: PM: calling pci_pm_suspend_late+0x0/0x40 @ 96, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pci 0000:00:07.0: PM: calling pci_pm_suspend_late+0x0/0x40 @ 4580, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pci 0000:00:05.0: PM: calling pci_pm_suspend_late+0x0/0x40 @ 4578, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pcieport 0000:00:07.1: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: pci 0000:00:04.0: PM: calling pci_pm_suspend_late+0x0/0x40 @ 4529, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pci 0000:00:07.0: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: pci 0000:00:03.0: PM: calling pci_pm_suspend_late+0x0/0x40 @ 12, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pcieport 0000:00:03.1: PM: calling pci_pm_suspend_late+0x0/0x40 @ 147, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pci 0000:00:05.0: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: pci 0000:00:18.0: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: pci 0000:00:03.0: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: pci 0000:00:02.0: PM: calling pci_pm_suspend_late+0x0/0x40 @ 4568, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pcieport 0000:00:03.1: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: pci 0000:00:01.0: PM: calling pci_pm_suspend_late+0x0/0x40 @ 4578, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pcieport 0000:00:01.1: PM: calling pci_pm_suspend_late+0x0/0x40 @ 4580, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pcieport 0000:00:01.2: PM: calling pci_pm_suspend_late+0x0/0x40 @ 96, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pci 0000:00:04.0: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: pci 0000:00:00.2: PM: calling pci_pm_suspend_late+0x0/0x40 @ 12, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pci 0000:00:02.0: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: pcieport 0000:00:01.1: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: pcieport 0000:00:01.2: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: pci 0000:00:00.0: PM: calling pci_pm_suspend_late+0x0/0x40 @ 3812, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pci 0000:00:00.2: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: pci 0000:00:01.0: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: pci 0000:00:00.0: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: PM: late suspend of devices complete after 0.498 msecs
Oct 11 17:34:22 ryzen kernel: snd_hda_intel 0000:05:00.1: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 4578, parent: 0000:00:03.1
Oct 11 17:34:22 ryzen kernel: acpi-wmi PNP0C14:01: PM: calling acpi_subsys_suspend_noirq+0x0/0x50 @ 5277, parent: platform
Oct 11 17:34:22 ryzen kernel: acpi-wmi PNP0C14:01: PM: acpi_subsys_suspend_noirq+0x0/0x50 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: acpi-wmi PNP0C14:00: PM: calling acpi_subsys_suspend_noirq+0x0/0x50 @ 5277, parent: platform
Oct 11 17:34:22 ryzen kernel: acpi-wmi PNP0C14:00: PM: acpi_subsys_suspend_noirq+0x0/0x50 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: pt-gpio AMDIF030:00: PM: calling acpi_subsys_suspend_noirq+0x0/0x50 @ 5277, parent: platform
Oct 11 17:34:22 ryzen kernel: pt-gpio AMDIF030:00: PM: acpi_subsys_suspend_noirq+0x0/0x50 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: amd_gpio AMDI0030:00: PM: calling acpi_subsys_suspend_noirq+0x0/0x50 @ 5277, parent: platform
Oct 11 17:34:22 ryzen kernel: amd_gpio AMDI0030:00: PM: acpi_subsys_suspend_noirq+0x0/0x50 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: snd_hda_intel 0000:07:00.4: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 96, parent: 0000:00:08.1
Oct 11 17:34:22 ryzen kernel: xhci_hcd 0000:07:00.3: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 3812, parent: 0000:00:08.1
Oct 11 17:34:22 ryzen kernel: ccp 0000:07:00.1: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 12, parent: 0000:00:08.1
Oct 11 17:34:22 ryzen kernel: pci 0000:07:00.0: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 147, parent: 0000:00:08.1
Oct 11 17:34:22 ryzen kernel: pci 0000:06:00.0: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 4551, parent: 0000:00:07.1
Oct 11 17:34:22 ryzen kernel: r8169 0000:04:00.0: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 4568, parent: 0000:03:09.0
Oct 11 17:34:22 ryzen kernel: ahci 0000:02:00.1: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 4563, parent: 0000:00:01.2
Oct 11 17:34:22 ryzen kernel: xhci_hcd 0000:02:00.0: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 4526, parent: 0000:00:01.2
Oct 11 17:34:22 ryzen kernel: nvme 0000:01:00.0: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 146, parent: 0000:00:01.1
Oct 11 17:34:22 ryzen kernel: pci 0000:00:18.7: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 148, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pci 0000:00:18.6: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 4584, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pci 0000:00:18.5: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 4583, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pci 0000:00:18.7: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 188 usecs
Oct 11 17:34:22 ryzen kernel: pci 0000:00:18.4: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 4533, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: k10temp 0000:00:18.3: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 148, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pci 0000:00:18.6: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 193 usecs
Oct 11 17:34:22 ryzen kernel: pci 0000:00:18.2: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 4584, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pci 0000:07:00.0: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 285 usecs
Oct 11 17:34:22 ryzen kernel: pci 0000:00:18.1: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 147, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pci 0000:00:18.5: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 206 usecs
Oct 11 17:34:22 ryzen kernel: pci 0000:06:00.0: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 305 usecs
Oct 11 17:34:22 ryzen kernel: pci 0000:00:18.0: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 4583, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pci 0000:00:14.3: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 4551, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: piix4_smbus 0000:00:14.0: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 10, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pci 0000:00:08.0: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 4554, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: k10temp 0000:00:18.3: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 154 usecs
Oct 11 17:34:22 ryzen kernel: pci 0000:00:18.4: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 154 usecs
Oct 11 17:34:22 ryzen kernel: pci 0000:00:07.0: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 148, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pcieport 0000:00:07.1: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 4533, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pci 0000:00:18.2: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 152 usecs
Oct 11 17:34:22 ryzen kernel: pci 0000:00:05.0: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 4584, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pci 0000:00:18.1: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 138 usecs
Oct 11 17:34:22 ryzen kernel: pci 0000:00:04.0: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 3813, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pci 0000:00:03.0: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 147, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pci 0000:00:18.0: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 125 usecs
Oct 11 17:34:22 ryzen kernel: pci 0000:00:02.0: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 4582, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pci 0000:00:14.3: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 126 usecs
Oct 11 17:34:22 ryzen kernel: pci 0000:00:01.0: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 4585, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pci 0000:00:00.2: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 4551, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pci 0000:00:00.0: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 317, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: piix4_smbus 0000:00:14.0: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 105 usecs
Oct 11 17:34:22 ryzen kernel: pci 0000:00:08.0: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 106 usecs
Oct 11 17:34:22 ryzen kernel: pci 0000:00:07.0: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 99 usecs
Oct 11 17:34:22 ryzen kernel: pci 0000:00:05.0: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 98 usecs
Oct 11 17:34:22 ryzen kernel: pci 0000:00:04.0: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 96 usecs
Oct 11 17:34:22 ryzen kernel: pci 0000:00:03.0: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 95 usecs
Oct 11 17:34:22 ryzen kernel: pci 0000:00:02.0: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 93 usecs
Oct 11 17:34:22 ryzen kernel: pci 0000:00:01.0: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 90 usecs
Oct 11 17:34:22 ryzen kernel: pci 0000:00:00.0: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 90 usecs
Oct 11 17:34:22 ryzen kernel: pci 0000:00:00.2: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 96 usecs
Oct 11 17:34:22 ryzen kernel: snd_hda_intel 0000:05:00.1: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 12060 usecs
Oct 11 17:34:22 ryzen kernel: amdgpu 0000:05:00.0: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 4580, parent: 0000:00:03.1
Oct 11 17:34:22 ryzen kernel: amdgpu 0000:05:00.0: amdgpu: PCI CONFIG reset
Oct 11 17:34:22 ryzen kernel: nvme 0000:01:00.0: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 12086 usecs
Oct 11 17:34:22 ryzen kernel: pcieport 0000:00:01.1: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 4586, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: snd_hda_intel 0000:07:00.4: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 12263 usecs
Oct 11 17:34:22 ryzen kernel: pcieport 0000:00:07.1: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 11840 usecs
Oct 11 17:34:22 ryzen kernel: xhci_hcd 0000:07:00.3: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 12309 usecs
Oct 11 17:34:22 ryzen kernel: ccp 0000:07:00.1: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 12309 usecs
Oct 11 17:34:22 ryzen kernel: pcieport 0000:00:08.1: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 1219, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: r8169 0000:04:00.0: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 12474 usecs
Oct 11 17:34:22 ryzen kernel: xhci_hcd 0000:02:00.0: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 12449 usecs
Oct 11 17:34:22 ryzen kernel: ahci 0000:02:00.1: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 12445 usecs
Oct 11 17:34:22 ryzen kernel: pcieport 0000:03:09.0: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 4529, parent: 0000:02:00.2
Oct 11 17:34:22 ryzen kernel: pcieport 0000:00:01.1: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 12070 usecs
Oct 11 17:34:22 ryzen kernel: amdgpu 0000:05:00.0: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 12332 usecs
Oct 11 17:34:22 ryzen kernel: pcieport 0000:00:08.1: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 12062 usecs
Oct 11 17:34:22 ryzen kernel: pcieport 0000:00:03.1: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 3814, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pcieport 0000:03:09.0: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 12084 usecs
Oct 11 17:34:22 ryzen kernel: pcieport 0000:02:00.2: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 4558, parent: 0000:00:01.2
Oct 11 17:34:22 ryzen kernel: pcieport 0000:00:03.1: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 12318 usecs
Oct 11 17:34:22 ryzen kernel: pcieport 0000:02:00.2: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 12336 usecs
Oct 11 17:34:22 ryzen kernel: pcieport 0000:00:01.2: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 4583, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pcieport 0000:00:01.2: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 12404 usecs
Oct 11 17:34:22 ryzen kernel: PM: noirq suspend of devices complete after 49.768 msecs
Oct 11 17:34:22 ryzen kernel: ACPI: PM: Preparing to enter system sleep state S3
Oct 11 17:34:22 ryzen kernel: ACPI: PM: Saving platform NVS memory
Oct 11 17:34:22 ryzen kernel: Disabling non-boot CPUs ...
Oct 11 17:34:22 ryzen kernel: smpboot: CPU 1 is now offline
Oct 11 17:34:22 ryzen kernel: smpboot: CPU 2 is now offline
Oct 11 17:34:22 ryzen kernel: smpboot: CPU 3 is now offline
Oct 11 17:34:22 ryzen kernel: smpboot: CPU 4 is now offline
Oct 11 17:34:22 ryzen kernel: smpboot: CPU 5 is now offline
Oct 11 17:34:22 ryzen kernel: smpboot: CPU 6 is now offline
Oct 11 17:34:22 ryzen kernel: Spectre V2 : Update user space SMT mitigation: STIBP off
Oct 11 17:34:22 ryzen kernel: smpboot: CPU 7 is now offline
Oct 11 17:34:22 ryzen kernel: smpboot: CPU 8 is now offline
Oct 11 17:34:22 ryzen kernel: smpboot: CPU 9 is now offline
Oct 11 17:34:22 ryzen kernel: smpboot: CPU 10 is now offline
Oct 11 17:34:22 ryzen kernel: smpboot: CPU 11 is now offline
Oct 11 17:34:22 ryzen kernel: Checking wakeup interrupts
Oct 11 17:34:22 ryzen kernel: Calling mce_syscore_suspend+0x0/0x20
Oct 11 17:34:22 ryzen kernel: Calling ledtrig_cpu_syscore_suspend+0x0/0x20
Oct 11 17:34:22 ryzen kernel: Calling timekeeping_suspend+0x0/0x2f0
Oct 11 17:34:22 ryzen kernel: Calling irq_gc_suspend+0x0/0x80
Oct 11 17:34:22 ryzen kernel: Calling save_ioapic_entries+0x0/0xd0
Oct 11 17:34:22 ryzen kernel: Calling i8259A_suspend+0x0/0x30
Oct 11 17:34:22 ryzen kernel: Calling perf_ibs_suspend+0x0/0x40
Oct 11 17:34:22 ryzen kernel: Calling amd_iommu_suspend+0x0/0x50
Oct 11 17:34:22 ryzen kernel: Calling fw_suspend+0x0/0x20
Oct 11 17:34:22 ryzen kernel: Calling acpi_save_bm_rld+0x0/0x30
Oct 11 17:34:22 ryzen kernel: Calling lapic_suspend+0x0/0x210
Oct 11 17:34:22 ryzen kernel: ACPI: PM: Low-level resume complete
Oct 11 17:34:22 ryzen kernel: ACPI: PM: Restoring platform NVS memory
Oct 11 17:34:22 ryzen kernel: Calling lapic_resume+0x0/0x2e0
Oct 11 17:34:22 ryzen kernel: Calling acpi_restore_bm_rld+0x0/0x70
Oct 11 17:34:22 ryzen kernel: Calling irqrouter_resume+0x0/0x50
Oct 11 17:34:22 ryzen kernel: Calling amd_iommu_resume+0x0/0x50
Oct 11 17:34:22 ryzen kernel: Calling perf_ibs_resume+0x0/0x30
Oct 11 17:34:22 ryzen kernel: LVT offset 0 assigned for vector 0x400
Oct 11 17:34:22 ryzen kernel: Calling i8259A_resume+0x0/0x40
Oct 11 17:34:22 ryzen kernel: Calling i8237A_resume+0x0/0xb0
Oct 11 17:34:22 ryzen kernel: Calling ioapic_resume+0x0/0xc0
Oct 11 17:34:22 ryzen kernel: Calling irq_gc_resume+0x0/0x70
Oct 11 17:34:22 ryzen kernel: Calling irq_pm_syscore_resume+0x0/0x20
Oct 11 17:34:22 ryzen kernel: Calling timekeeping_resume+0x0/0x1e0
Oct 11 17:34:22 ryzen kernel: Timekeeping suspended for 7.800 seconds
Oct 11 17:34:22 ryzen kernel: Calling init_counter_refs+0x0/0x40
Oct 11 17:34:22 ryzen kernel: Calling ledtrig_cpu_syscore_resume+0x0/0x20
Oct 11 17:34:22 ryzen kernel: Calling mce_syscore_resume+0x0/0x30
Oct 11 17:34:22 ryzen kernel: Calling microcode_bsp_resume+0x0/0x40
Oct 11 17:34:22 ryzen kernel: Enabling non-boot CPUs ...
Oct 11 17:34:22 ryzen kernel: smpboot: Booting Node 0 Processor 1 APIC 0x2
Oct 11 17:34:22 ryzen kernel: ACPI: \_SB_.PLTF.C002: Found 2 idle states
Oct 11 17:34:22 ryzen kernel: CPU1 is up
Oct 11 17:34:22 ryzen kernel: smpboot: Booting Node 0 Processor 2 APIC 0x4
Oct 11 17:34:22 ryzen kernel: ACPI: \_SB_.PLTF.C004: Found 2 idle states
Oct 11 17:34:22 ryzen kernel: CPU2 is up
Oct 11 17:34:22 ryzen kernel: smpboot: Booting Node 0 Processor 3 APIC 0x6
Oct 11 17:34:22 ryzen kernel: ACPI: \_SB_.PLTF.C006: Found 2 idle states
Oct 11 17:34:22 ryzen kernel: CPU3 is up
Oct 11 17:34:22 ryzen kernel: smpboot: Booting Node 0 Processor 4 APIC 0x8
Oct 11 17:34:22 ryzen kernel: ACPI: \_SB_.PLTF.C008: Found 2 idle states
Oct 11 17:34:22 ryzen kernel: CPU4 is up
Oct 11 17:34:22 ryzen kernel: smpboot: Booting Node 0 Processor 5 APIC 0xa
Oct 11 17:34:22 ryzen kernel: ACPI: \_SB_.PLTF.C00A: Found 2 idle states
Oct 11 17:34:22 ryzen kernel: CPU5 is up
Oct 11 17:34:22 ryzen kernel: smpboot: Booting Node 0 Processor 6 APIC 0x1
Oct 11 17:34:22 ryzen kernel: ACPI: \_SB_.PLTF.C001: Found 2 idle states
Oct 11 17:34:22 ryzen kernel: Spectre V2 : Update user space SMT mitigation: STIBP always-on
Oct 11 17:34:22 ryzen kernel: CPU6 is up
Oct 11 17:34:22 ryzen kernel: smpboot: Booting Node 0 Processor 7 APIC 0x3
Oct 11 17:34:22 ryzen kernel: ACPI: \_SB_.PLTF.C003: Found 2 idle states
Oct 11 17:34:22 ryzen kernel: CPU7 is up
Oct 11 17:34:22 ryzen kernel: smpboot: Booting Node 0 Processor 8 APIC 0x5
Oct 11 17:34:22 ryzen kernel: ACPI: \_SB_.PLTF.C005: Found 2 idle states
Oct 11 17:34:22 ryzen kernel: CPU8 is up
Oct 11 17:34:22 ryzen kernel: smpboot: Booting Node 0 Processor 9 APIC 0x7
Oct 11 17:34:22 ryzen kernel: ACPI: \_SB_.PLTF.C007: Found 2 idle states
Oct 11 17:34:22 ryzen kernel: CPU9 is up
Oct 11 17:34:22 ryzen kernel: smpboot: Booting Node 0 Processor 10 APIC 0x9
Oct 11 17:34:22 ryzen kernel: ACPI: \_SB_.PLTF.C009: Found 2 idle states
Oct 11 17:34:22 ryzen kernel: CPU10 is up
Oct 11 17:34:22 ryzen kernel: smpboot: Booting Node 0 Processor 11 APIC 0xb
Oct 11 17:34:22 ryzen kernel: ACPI: \_SB_.PLTF.C00B: Found 2 idle states
Oct 11 17:34:22 ryzen kernel: CPU11 is up
Oct 11 17:34:22 ryzen kernel: ACPI: PM: Waking up from system sleep state S3
Oct 11 17:34:22 ryzen kernel: pcieport 0000:00:01.2: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 1219, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pci 0000:00:00.2: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 4558, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pci 0000:00:02.0: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 4583, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pcieport 0000:00:01.1: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 4529, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pci 0000:00:00.0: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 4566, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pci 0000:00:01.0: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 3814, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pci 0000:00:03.0: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 4580, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pcieport 0000:00:03.1: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 4586, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pci 0000:00:04.0: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 4563, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pci 0000:00:05.0: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 4526, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pci 0000:00:07.0: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 4568, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pcieport 0000:00:07.1: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 12, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pci 0000:00:01.0: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 235 usecs
Oct 11 17:34:22 ryzen kernel: pci 0000:00:02.0: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 238 usecs
Oct 11 17:34:22 ryzen kernel: pci 0000:00:08.0: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 3814, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pcieport 0000:00:08.1: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 4583, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pci 0000:00:03.0: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 247 usecs
Oct 11 17:34:22 ryzen kernel: piix4_smbus 0000:00:14.0: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 4580, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pci 0000:00:04.0: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 249 usecs
Oct 11 17:34:22 ryzen kernel: pci 0000:00:00.0: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 273 usecs
Oct 11 17:34:22 ryzen kernel: pci 0000:00:14.3: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 4563, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pci 0000:00:18.0: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 4566, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pci 0000:00:05.0: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 250 usecs
Oct 11 17:34:22 ryzen kernel: pci 0000:00:18.1: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 4526, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pci 0000:00:07.0: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 243 usecs
Oct 11 17:34:22 ryzen kernel: pci 0000:00:18.2: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 4568, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pci 0000:00:08.0: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 181 usecs
Oct 11 17:34:22 ryzen kernel: k10temp 0000:00:18.3: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 3814, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pci 0000:00:00.2: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 436 usecs
Oct 11 17:34:22 ryzen kernel: piix4_smbus 0000:00:14.0: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 179 usecs
Oct 11 17:34:22 ryzen kernel: pci 0000:00:18.4: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 4580, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pci 0000:00:18.5: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 4558, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pci 0000:00:18.0: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 171 usecs
Oct 11 17:34:22 ryzen kernel: pci 0000:00:14.3: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 174 usecs
Oct 11 17:34:22 ryzen kernel: pci 0000:00:18.6: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 4566, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pci 0000:00:18.1: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 170 usecs
Oct 11 17:34:22 ryzen kernel: pci 0000:00:18.7: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 4563, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pci 0000:00:18.2: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 165 usecs
Oct 11 17:34:22 ryzen kernel: k10temp 0000:00:18.3: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 104 usecs
Oct 11 17:34:22 ryzen kernel: amd_gpio AMDI0030:00: PM: calling acpi_subsys_resume_noirq+0x0/0x30 @ 5277, parent: platform
Oct 11 17:34:22 ryzen kernel: pci 0000:00:18.4: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 98 usecs
Oct 11 17:34:22 ryzen kernel: amd_gpio AMDI0030:00: PM: acpi_subsys_resume_noirq+0x0/0x30 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: pci 0000:00:18.5: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 99 usecs
Oct 11 17:34:22 ryzen kernel: pt-gpio AMDIF030:00: PM: calling acpi_subsys_resume_noirq+0x0/0x30 @ 5277, parent: platform
Oct 11 17:34:22 ryzen kernel: pt-gpio AMDIF030:00: PM: acpi_subsys_resume_noirq+0x0/0x30 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: pci 0000:00:18.6: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 96 usecs
Oct 11 17:34:22 ryzen kernel: acpi-wmi PNP0C14:00: PM: calling acpi_subsys_resume_noirq+0x0/0x30 @ 5277, parent: platform
Oct 11 17:34:22 ryzen kernel: acpi-wmi PNP0C14:00: PM: acpi_subsys_resume_noirq+0x0/0x30 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: pci 0000:00:18.7: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 95 usecs
Oct 11 17:34:22 ryzen kernel: acpi-wmi PNP0C14:01: PM: calling acpi_subsys_resume_noirq+0x0/0x30 @ 5277, parent: platform
Oct 11 17:34:22 ryzen kernel: acpi-wmi PNP0C14:01: PM: acpi_subsys_resume_noirq+0x0/0x30 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: pcieport 0000:00:01.1: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 565 usecs
Oct 11 17:34:22 ryzen kernel: nvme 0000:01:00.0: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 4526, parent: 0000:00:01.1
Oct 11 17:34:22 ryzen kernel: pcieport 0000:00:01.2: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 575 usecs
Oct 11 17:34:22 ryzen kernel: ahci 0000:02:00.1: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 3812, parent: 0000:00:01.2
Oct 11 17:34:22 ryzen kernel: xhci_hcd 0000:02:00.0: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 4568, parent: 0000:00:01.2
Oct 11 17:34:22 ryzen kernel: pcieport 0000:02:00.2: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 4533, parent: 0000:00:01.2
Oct 11 17:34:22 ryzen kernel: pcieport 0000:00:07.1: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 537 usecs
Oct 11 17:34:22 ryzen kernel: pcieport 0000:00:03.1: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 578 usecs
Oct 11 17:34:22 ryzen kernel: pci 0000:06:00.0: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 4551, parent: 0000:00:07.1
Oct 11 17:34:22 ryzen kernel: amdgpu 0000:05:00.0: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 4578, parent: 0000:00:03.1
Oct 11 17:34:22 ryzen kernel: i8042 i8042: PM: calling i8042_pm_resume_noirq+0x0/0x30 [i8042] @ 5277, parent: platform
Oct 11 17:34:22 ryzen kernel: i8042 i8042: PM: i8042_pm_resume_noirq+0x0/0x30 [i8042] returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: pcieport 0000:00:08.1: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 518 usecs
Oct 11 17:34:22 ryzen kernel: ccp 0000:07:00.1: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 4585, parent: 0000:00:08.1
Oct 11 17:34:22 ryzen kernel: xhci_hcd 0000:07:00.3: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 4582, parent: 0000:00:08.1
Oct 11 17:34:22 ryzen kernel: pci 0000:07:00.0: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 317, parent: 0000:00:08.1
Oct 11 17:34:22 ryzen kernel: snd_hda_intel 0000:07:00.4: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 147, parent: 0000:00:08.1
Oct 11 17:34:22 ryzen kernel: pci 0000:06:00.0: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 618 usecs
Oct 11 17:34:22 ryzen kernel: nvme 0000:01:00.0: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 641 usecs
Oct 11 17:34:22 ryzen kernel: pcieport 0000:02:00.2: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 676 usecs
Oct 11 17:34:22 ryzen kernel: pcieport 0000:03:09.0: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 96, parent: 0000:02:00.2
Oct 11 17:34:22 ryzen kernel: ahci 0000:02:00.1: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 706 usecs
Oct 11 17:34:22 ryzen kernel: pci 0000:07:00.0: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 524 usecs
Oct 11 17:34:22 ryzen kernel: xhci_hcd 0000:02:00.0: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 737 usecs
Oct 11 17:34:22 ryzen kernel: snd_hda_intel 0000:07:00.4: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 568 usecs
Oct 11 17:34:22 ryzen kernel: ccp 0000:07:00.1: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 609 usecs
Oct 11 17:34:22 ryzen kernel: amdgpu 0000:05:00.0: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 804 usecs
Oct 11 17:34:22 ryzen kernel: snd_hda_intel 0000:05:00.1: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 3813, parent: 0000:00:03.1
Oct 11 17:34:22 ryzen kernel: xhci_hcd 0000:07:00.3: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 627 usecs
Oct 11 17:34:22 ryzen kernel: pcieport 0000:03:09.0: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 230 usecs
Oct 11 17:34:22 ryzen kernel: r8169 0000:04:00.0: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 146, parent: 0000:03:09.0
Oct 11 17:34:22 ryzen kernel: snd_hda_intel 0000:05:00.1: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 166 usecs
Oct 11 17:34:22 ryzen kernel: r8169 0000:04:00.0: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 241 usecs
Oct 11 17:34:22 ryzen kernel: PM: noirq resume of devices complete after 1.916 msecs
Oct 11 17:34:22 ryzen kernel: pcieport 0000:00:01.2: PM: calling pci_pm_resume_early+0x0/0x30 @ 4560, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pci 0000:00:03.0: PM: calling pci_pm_resume_early+0x0/0x30 @ 4587, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pcieport 0000:00:01.1: PM: calling pci_pm_resume_early+0x0/0x30 @ 4570, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pci 0000:00:00.2: PM: calling pci_pm_resume_early+0x0/0x30 @ 96, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pci 0000:00:04.0: PM: calling pci_pm_resume_early+0x0/0x30 @ 4524, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pci 0000:00:05.0: PM: calling pci_pm_resume_early+0x0/0x30 @ 146, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pcieport 0000:00:03.1: PM: calling pci_pm_resume_early+0x0/0x30 @ 4528, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pci 0000:00:01.0: PM: calling pci_pm_resume_early+0x0/0x30 @ 4579, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pci 0000:00:02.0: PM: calling pci_pm_resume_early+0x0/0x30 @ 4555, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pci 0000:00:00.0: PM: calling pci_pm_resume_early+0x0/0x30 @ 3813, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pci 0000:00:00.2: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: pci 0000:00:05.0: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: pci 0000:00:02.0: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: pci 0000:00:04.0: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: pcieport 0000:00:01.2: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: pci 0000:00:01.0: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: pcieport 0000:00:01.1: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: pcieport 0000:00:03.1: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: pci 0000:00:00.0: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: pci 0000:00:03.0: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: pci 0000:00:07.0: PM: calling pci_pm_resume_early+0x0/0x30 @ 146, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pcieport 0000:00:07.1: PM: calling pci_pm_resume_early+0x0/0x30 @ 4555, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pci 0000:00:08.0: PM: calling pci_pm_resume_early+0x0/0x30 @ 4524, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pcieport 0000:00:08.1: PM: calling pci_pm_resume_early+0x0/0x30 @ 4560, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: piix4_smbus 0000:00:14.0: PM: calling pci_pm_resume_early+0x0/0x30 @ 4579, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pci 0000:00:14.3: PM: calling pci_pm_resume_early+0x0/0x30 @ 4570, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pci 0000:00:18.0: PM: calling pci_pm_resume_early+0x0/0x30 @ 3813, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pci 0000:00:18.1: PM: calling pci_pm_resume_early+0x0/0x30 @ 4528, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pci 0000:00:18.2: PM: calling pci_pm_resume_early+0x0/0x30 @ 96, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: k10temp 0000:00:18.3: PM: calling pci_pm_resume_early+0x0/0x30 @ 4587, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pci 0000:00:07.0: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: pci 0000:00:08.0: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: pcieport 0000:00:08.1: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: pci 0000:00:14.3: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: piix4_smbus 0000:00:14.0: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: pci 0000:00:18.0: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: pci 0000:00:18.1: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: pcieport 0000:00:07.1: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: k10temp 0000:00:18.3: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: pci 0000:00:18.4: PM: calling pci_pm_resume_early+0x0/0x30 @ 146, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pci 0000:00:18.5: PM: calling pci_pm_resume_early+0x0/0x30 @ 4524, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pci 0000:00:18.6: PM: calling pci_pm_resume_early+0x0/0x30 @ 4560, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pci 0000:00:18.7: PM: calling pci_pm_resume_early+0x0/0x30 @ 4570, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: nvme 0000:01:00.0: PM: calling pci_pm_resume_early+0x0/0x30 @ 4579, parent: 0000:00:01.1
Oct 11 17:34:22 ryzen kernel: xhci_hcd 0000:02:00.0: PM: calling pci_pm_resume_early+0x0/0x30 @ 3813, parent: 0000:00:01.2
Oct 11 17:34:22 ryzen kernel: ahci 0000:02:00.1: PM: calling pci_pm_resume_early+0x0/0x30 @ 4528, parent: 0000:00:01.2
Oct 11 17:34:22 ryzen kernel: pcieport 0000:02:00.2: PM: calling pci_pm_resume_early+0x0/0x30 @ 4555, parent: 0000:00:01.2
Oct 11 17:34:22 ryzen kernel: pci 0000:00:18.4: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: pci 0000:00:18.5: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: pci 0000:00:18.6: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: pci 0000:00:18.2: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: nvme 0000:01:00.0: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: xhci_hcd 0000:02:00.0: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: ahci 0000:02:00.1: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: pcieport 0000:02:00.2: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: pci 0000:00:18.7: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: amdgpu 0000:05:00.0: PM: calling pci_pm_resume_early+0x0/0x30 @ 146, parent: 0000:00:03.1
Oct 11 17:34:22 ryzen kernel: pci 0000:06:00.0: PM: calling pci_pm_resume_early+0x0/0x30 @ 4524, parent: 0000:00:07.1
Oct 11 17:34:22 ryzen kernel: pci 0000:07:00.0: PM: calling pci_pm_resume_early+0x0/0x30 @ 4560, parent: 0000:00:08.1
Oct 11 17:34:22 ryzen kernel: ccp 0000:07:00.1: PM: calling pci_pm_resume_early+0x0/0x30 @ 96, parent: 0000:00:08.1
Oct 11 17:34:22 ryzen kernel: xhci_hcd 0000:07:00.3: PM: calling pci_pm_resume_early+0x0/0x30 @ 4579, parent: 0000:00:08.1
Oct 11 17:34:22 ryzen kernel: snd_hda_intel 0000:07:00.4: PM: calling pci_pm_resume_early+0x0/0x30 @ 4528, parent: 0000:00:08.1
Oct 11 17:34:22 ryzen kernel: pci 0000:07:00.0: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: ccp 0000:07:00.1: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: amdgpu 0000:05:00.0: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: xhci_hcd 0000:07:00.3: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: snd_hda_intel 0000:07:00.4: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: pci 0000:06:00.0: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: pcieport 0000:03:09.0: PM: calling pci_pm_resume_early+0x0/0x30 @ 4587, parent: 0000:02:00.2
Oct 11 17:34:22 ryzen kernel: amd_gpio AMDI0030:00: PM: calling acpi_subsys_resume_early+0x0/0x80 @ 5277, parent: platform
Oct 11 17:34:22 ryzen kernel: pcieport 0000:03:09.0: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: amd_gpio AMDI0030:00: PM: acpi_subsys_resume_early+0x0/0x80 returned 0 after 11 usecs
Oct 11 17:34:22 ryzen kernel: pt-gpio AMDIF030:00: PM: calling acpi_subsys_resume_early+0x0/0x80 @ 5277, parent: platform
Oct 11 17:34:22 ryzen kernel: r8169 0000:04:00.0: PM: calling pci_pm_resume_early+0x0/0x30 @ 4534, parent: 0000:03:09.0
Oct 11 17:34:22 ryzen kernel: pt-gpio AMDIF030:00: PM: acpi_subsys_resume_early+0x0/0x80 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: snd_hda_intel 0000:05:00.1: PM: calling pci_pm_resume_early+0x0/0x30 @ 4556, parent: 0000:00:03.1
Oct 11 17:34:22 ryzen kernel: r8169 0000:04:00.0: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: acpi-wmi PNP0C14:00: PM: calling acpi_subsys_resume_early+0x0/0x80 @ 5277, parent: platform
Oct 11 17:34:22 ryzen kernel: snd_hda_intel 0000:05:00.1: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: acpi-wmi PNP0C14:00: PM: acpi_subsys_resume_early+0x0/0x80 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: acpi-wmi PNP0C14:01: PM: calling acpi_subsys_resume_early+0x0/0x80 @ 5277, parent: platform
Oct 11 17:34:22 ryzen kernel: acpi-wmi PNP0C14:01: PM: acpi_subsys_resume_early+0x0/0x80 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: PM: early resume of devices complete after 0.213 msecs
Oct 11 17:34:22 ryzen kernel: pci 0000:00:00.0: PM: calling pci_pm_resume+0x0/0xf0 @ 4534, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pcieport 0000:00:01.1: PM: calling pci_pm_resume+0x0/0xf0 @ 146, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pci 0000:00:01.0: PM: calling pci_pm_resume+0x0/0xf0 @ 3813, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pci 0000:00:00.2: PM: calling pci_pm_resume+0x0/0xf0 @ 314, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pci 0000:00:03.0: PM: calling pci_pm_resume+0x0/0xf0 @ 4532, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pcieport 0000:00:03.1: PM: calling pci_pm_resume+0x0/0xf0 @ 4560, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pci 0000:00:02.0: PM: calling pci_pm_resume+0x0/0xf0 @ 4579, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pcieport 0000:00:01.2: PM: calling pci_pm_resume+0x0/0xf0 @ 4528, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pci 0000:00:04.0: PM: calling pci_pm_resume+0x0/0xf0 @ 96, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pci 0000:00:05.0: PM: calling pci_pm_resume+0x0/0xf0 @ 4570, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pci 0000:00:07.0: PM: calling pci_pm_resume+0x0/0xf0 @ 4556, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pci 0000:00:01.0: PM: pci_pm_resume+0x0/0xf0 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: pci 0000:00:04.0: PM: pci_pm_resume+0x0/0xf0 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: pci 0000:00:03.0: PM: pci_pm_resume+0x0/0xf0 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: pci 0000:00:02.0: PM: pci_pm_resume+0x0/0xf0 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: pci 0000:00:07.0: PM: pci_pm_resume+0x0/0xf0 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: pci 0000:00:05.0: PM: pci_pm_resume+0x0/0xf0 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: pci 0000:00:00.2: PM: pci_pm_resume+0x0/0xf0 returned 0 after 1 usecs
Oct 11 17:34:22 ryzen kernel: pcieport 0000:00:01.2: PM: pci_pm_resume+0x0/0xf0 returned 0 after 1 usecs
Oct 11 17:34:22 ryzen kernel: pcieport 0000:00:07.1: PM: calling pci_pm_resume+0x0/0xf0 @ 3813, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pci 0000:00:08.0: PM: calling pci_pm_resume+0x0/0xf0 @ 96, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pcieport 0000:00:08.1: PM: calling pci_pm_resume+0x0/0xf0 @ 4532, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: piix4_smbus 0000:00:14.0: PM: calling pci_pm_resume+0x0/0xf0 @ 4556, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pci 0000:00:14.3: PM: calling pci_pm_resume+0x0/0xf0 @ 4579, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pci 0000:00:18.0: PM: calling pci_pm_resume+0x0/0xf0 @ 4570, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pci 0000:00:18.1: PM: calling pci_pm_resume+0x0/0xf0 @ 314, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pci 0000:00:00.0: PM: pci_pm_resume+0x0/0xf0 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: pci 0000:00:18.2: PM: calling pci_pm_resume+0x0/0xf0 @ 4528, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pci 0000:00:08.0: PM: pci_pm_resume+0x0/0xf0 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: piix4_smbus 0000:00:14.0: PM: pci_pm_resume+0x0/0xf0 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: pci 0000:00:14.3: PM: pci_pm_resume+0x0/0xf0 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: pci 0000:00:18.0: PM: pci_pm_resume+0x0/0xf0 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: pci 0000:00:18.1: PM: pci_pm_resume+0x0/0xf0 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: pcieport 0000:00:01.1: PM: pci_pm_resume+0x0/0xf0 returned 0 after 8 usecs
Oct 11 17:34:22 ryzen kernel: k10temp 0000:00:18.3: PM: calling pci_pm_resume+0x0/0xf0 @ 4534, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pci 0000:00:18.2: PM: pci_pm_resume+0x0/0xf0 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: pci 0000:00:18.4: PM: calling pci_pm_resume+0x0/0xf0 @ 96, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pci 0000:00:18.5: PM: calling pci_pm_resume+0x0/0xf0 @ 4579, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: k10temp 0000:00:18.3: PM: pci_pm_resume+0x0/0xf0 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: pci 0000:00:18.6: PM: calling pci_pm_resume+0x0/0xf0 @ 4570, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: pci 0000:00:18.7: PM: calling pci_pm_resume+0x0/0xf0 @ 314, parent: pci0000:00
Oct 11 17:34:22 ryzen kernel: nvme 0000:01:00.0: PM: calling pci_pm_resume+0x0/0xf0 @ 146, parent: 0000:00:01.1
Oct 11 17:34:22 ryzen kernel: xhci_hcd 0000:02:00.0: PM: calling pci_pm_resume+0x0/0xf0 @ 4528, parent: 0000:00:01.2
Oct 11 17:34:22 ryzen kernel: pci 0000:00:18.4: PM: pci_pm_resume+0x0/0xf0 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: ahci 0000:02:00.1: PM: calling pci_pm_resume+0x0/0xf0 @ 4556, parent: 0000:00:01.2
Oct 11 17:34:22 ryzen kernel: pci 0000:00:18.5: PM: pci_pm_resume+0x0/0xf0 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: pci 0000:00:18.7: PM: pci_pm_resume+0x0/0xf0 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: pcieport 0000:02:00.2: PM: calling pci_pm_resume+0x0/0xf0 @ 4534, parent: 0000:00:01.2
Oct 11 17:34:22 ryzen kernel: pcieport 0000:00:03.1: PM: pci_pm_resume+0x0/0xf0 returned 0 after 13 usecs
Oct 11 17:34:22 ryzen kernel: nvme 0000:01:00.0: PM: pci_pm_resume+0x0/0xf0 returned 0 after 1 usecs
Oct 11 17:34:22 ryzen kernel: pcieport 0000:02:00.2: PM: pci_pm_resume+0x0/0xf0 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: amdgpu 0000:05:00.0: PM: calling pci_pm_resume+0x0/0xf0 @ 314, parent: 0000:00:03.1
Oct 11 17:34:22 ryzen kernel: reg-dummy reg-dummy: PM: calling platform_pm_resume+0x0/0x50 @ 5277, parent: platform
Oct 11 17:34:22 ryzen kernel: pci 0000:00:18.6: PM: pci_pm_resume+0x0/0xf0 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: pcieport 0000:00:08.1: PM: pci_pm_resume+0x0/0xf0 returned 0 after 12 usecs
Oct 11 17:34:22 ryzen kernel: reg-dummy reg-dummy: PM: platform_pm_resume+0x0/0x50 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: regulator regulator.0: PM: calling regulator_resume+0x0/0x190 @ 5277, parent: reg-dummy
Oct 11 17:34:22 ryzen kernel: snd_hda_intel 0000:07:00.4: PM: calling pci_pm_resume+0x0/0xf0 @ 4587, parent: 0000:00:08.1
Oct 11 17:34:22 ryzen kernel: ccp 0000:07:00.1: PM: calling pci_pm_resume+0x0/0xf0 @ 4570, parent: 0000:00:08.1
Oct 11 17:34:22 ryzen kernel: pcieport 0000:03:09.0: PM: calling pci_pm_resume+0x0/0xf0 @ 96, parent: 0000:02:00.2
Oct 11 17:34:22 ryzen kernel: pci 0000:07:00.0: PM: calling pci_pm_resume+0x0/0xf0 @ 146, parent: 0000:00:08.1
Oct 11 17:34:22 ryzen kernel: regulator regulator.0: PM: regulator_resume+0x0/0x190 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: ccp 0000:07:00.1: PM: pci_pm_resume+0x0/0xf0 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: pcieport 0000:00:07.1: PM: pci_pm_resume+0x0/0xf0 returned 0 after 18 usecs
Oct 11 17:34:22 ryzen kernel: pci 0000:07:00.0: PM: pci_pm_resume+0x0/0xf0 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: xhci_hcd 0000:07:00.3: PM: calling pci_pm_resume+0x0/0xf0 @ 4534, parent: 0000:00:08.1
Oct 11 17:34:22 ryzen kernel: PCCT PCCT: PM: calling platform_pm_resume+0x0/0x50 @ 5277, parent: platform
Oct 11 17:34:22 ryzen kernel: PCCT PCCT: PM: platform_pm_resume+0x0/0x50 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: pci 0000:06:00.0: PM: calling pci_pm_resume+0x0/0xf0 @ 4560, parent: 0000:00:07.1
Oct 11 17:34:22 ryzen kernel: pci 0000:06:00.0: PM: pci_pm_resume+0x0/0xf0 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: button PNP0C0C:00: PM: calling acpi_button_resume+0x0/0x110 @ 5277, parent: LNXSYBUS:00
Oct 11 17:34:22 ryzen kernel: button PNP0C0C:00: PM: acpi_button_resume+0x0/0x110 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: pcieport 0000:03:09.0: PM: pci_pm_resume+0x0/0xf0 returned 0 after 25 usecs
Oct 11 17:34:22 ryzen kernel: r8169 0000:04:00.0: PM: calling pci_pm_resume+0x0/0xf0 @ 4579, parent: 0000:03:09.0
Oct 11 17:34:22 ryzen kernel: tpm_crb MSFT0101:00: PM: calling tpm_pm_resume+0x0/0x30 @ 5277, parent: LNXSYBUS:00
Oct 11 17:34:22 ryzen kernel: tpm_crb MSFT0101:00: PM: tpm_pm_resume+0x0/0x30 returned 0 after 6 usecs
Oct 11 17:34:22 ryzen kernel: thermal LNXTHERM:00: PM: calling acpi_thermal_resume+0x0/0xf0 @ 5277, parent: LNXSYBUS:01
Oct 11 17:34:22 ryzen kernel: xhci_hcd 0000:02:00.0: xHC error in resume, USBSTS 0x401, Reinit
Oct 11 17:34:22 ryzen kernel: usb usb1: root hub lost power or was reset
Oct 11 17:34:22 ryzen kernel: usb usb2: root hub lost power or was reset
Oct 11 17:34:22 ryzen kernel: thermal LNXTHERM:00: PM: acpi_thermal_resume+0x0/0xf0 returned 0 after 2 usecs
Oct 11 17:34:22 ryzen kernel: thermal LNXTHERM:01: PM: calling acpi_thermal_resume+0x0/0xf0 @ 5277, parent: LNXSYBUS:01
Oct 11 17:34:22 ryzen kernel: thermal LNXTHERM:01: PM: acpi_thermal_resume+0x0/0xf0 returned 0 after 1 usecs
Oct 11 17:34:22 ryzen kernel: ahci 0000:02:00.1: PM: pci_pm_resume+0x0/0xf0 returned 0 after 92 usecs
Oct 11 17:34:22 ryzen kernel: platform PNP0800:00: PM: calling platform_pm_resume+0x0/0x50 @ 5277, parent: 0000:00:14.3
Oct 11 17:34:22 ryzen kernel: ata1: PM: calling ata_port_pm_resume+0x0/0x60 @ 146, parent: 0000:02:00.1
Oct 11 17:34:22 ryzen kernel: ata3: PM: calling ata_port_pm_resume+0x0/0x60 @ 3813, parent: 0000:02:00.1
Oct 11 17:34:22 ryzen kernel: ata5: PM: calling ata_port_pm_resume+0x0/0x60 @ 4524, parent: 0000:02:00.1
Oct 11 17:34:22 ryzen kernel: platform PNP0800:00: PM: platform_pm_resume+0x0/0x50 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: ata4: PM: calling ata_port_pm_resume+0x0/0x60 @ 4555, parent: 0000:02:00.1
Oct 11 17:34:22 ryzen kernel: ata2: PM: calling ata_port_pm_resume+0x0/0x60 @ 4570, parent: 0000:02:00.1
Oct 11 17:34:22 ryzen kernel: platform PNP0C0C:00: PM: calling platform_pm_resume+0x0/0x50 @ 5277, parent: platform
Oct 11 17:34:22 ryzen kernel: ata1: PM: ata_port_pm_resume+0x0/0x60 returned 0 after 3 usecs
Oct 11 17:34:22 ryzen kernel: platform PNP0C0C:00: PM: platform_pm_resume+0x0/0x50 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: ata5: PM: ata_port_pm_resume+0x0/0x60 returned 0 after 6 usecs
Oct 11 17:34:22 ryzen kernel: amd_gpio AMDI0030:00: PM: calling acpi_subsys_resume+0x0/0x80 @ 5277, parent: platform
Oct 11 17:34:22 ryzen kernel: ata3: PM: ata_port_pm_resume+0x0/0x60 returned 0 after 9 usecs
Oct 11 17:34:22 ryzen kernel: scsi host0: PM: calling scsi_bus_resume+0x0/0x90 @ 4550, parent: ata1
Oct 11 17:34:22 ryzen kernel: amd_gpio AMDI0030:00: PM: acpi_subsys_resume+0x0/0x80 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: ata4: PM: ata_port_pm_resume+0x0/0x60 returned 0 after 11 usecs
Oct 11 17:34:22 ryzen kernel: scsi host0: PM: scsi_bus_resume+0x0/0x90 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: ata2: PM: ata_port_pm_resume+0x0/0x60 returned 0 after 11 usecs
Oct 11 17:34:22 ryzen kernel: platform MSFT0101:00: PM: calling platform_pm_resume+0x0/0x50 @ 5277, parent: platform
Oct 11 17:34:22 ryzen kernel: platform MSFT0101:00: PM: platform_pm_resume+0x0/0x50 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: scsi target0:0:0: PM: calling scsi_bus_resume+0x0/0x90 @ 96, parent: host0
Oct 11 17:34:22 ryzen kernel: acpi-cpufreq acpi-cpufreq: PM: calling platform_pm_resume+0x0/0x50 @ 5277, parent: platform
Oct 11 17:34:22 ryzen kernel: scsi target0:0:0: PM: scsi_bus_resume+0x0/0x90 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: acpi-cpufreq acpi-cpufreq: PM: platform_pm_resume+0x0/0x50 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: xhci_hcd 0000:07:00.3: PM: pci_pm_resume+0x0/0xf0 returned 0 after 113 usecs
Oct 11 17:34:22 ryzen kernel: pt-gpio AMDIF030:00: PM: calling acpi_subsys_resume+0x0/0x80 @ 5277, parent: platform
Oct 11 17:34:22 ryzen kernel: sd 0:0:0:0: PM: calling scsi_bus_resume+0x0/0x90 @ 4578, parent: target0:0:0
Oct 11 17:34:22 ryzen kernel: pt-gpio AMDIF030:00: PM: acpi_subsys_resume+0x0/0x80 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: sd 0:0:0:0: PM: scsi_bus_resume+0x0/0x90 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: platform PNP0103:00: PM: calling platform_pm_resume+0x0/0x50 @ 5277, parent: platform
Oct 11 17:34:22 ryzen kernel: platform PNP0103:00: PM: platform_pm_resume+0x0/0x50 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: scsi host2: PM: calling scsi_bus_resume+0x0/0x90 @ 145, parent: ata3
Oct 11 17:34:22 ryzen kernel: ata6: PM: calling ata_port_pm_resume+0x0/0x60 @ 4560, parent: 0000:02:00.1
Oct 11 17:34:22 ryzen kernel: acpi-wmi PNP0C14:00: PM: calling acpi_subsys_resume+0x0/0x80 @ 5277, parent: platform
Oct 11 17:34:22 ryzen kernel: scsi host4: PM: calling scsi_bus_resume+0x0/0x90 @ 4553, parent: ata5
Oct 11 17:34:22 ryzen kernel: scsi host4: PM: scsi_bus_resume+0x0/0x90 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: acpi-wmi PNP0C14:00: PM: acpi_subsys_resume+0x0/0x80 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: scsi host2: PM: scsi_bus_resume+0x0/0x90 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: ata6: PM: ata_port_pm_resume+0x0/0x60 returned 0 after 2 usecs
Oct 11 17:34:22 ryzen kernel: acpi-wmi PNP0C14:01: PM: calling acpi_subsys_resume+0x0/0x80 @ 5277, parent: platform
Oct 11 17:34:22 ryzen kernel: scsi host1: PM: calling scsi_bus_resume+0x0/0x90 @ 4525, parent: ata2
Oct 11 17:34:22 ryzen kernel: acpi-wmi PNP0C14:01: PM: acpi_subsys_resume+0x0/0x80 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: usb usb3: PM: calling usb_dev_resume+0x0/0x20 @ 4560, parent: 0000:07:00.3
Oct 11 17:34:22 ryzen kernel: scsi host1: PM: scsi_bus_resume+0x0/0x90 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: button LNXPWRBN:00: PM: calling acpi_button_resume+0x0/0x110 @ 5277, parent: LNXSYSTM:00
Oct 11 17:34:22 ryzen kernel: button LNXPWRBN:00: PM: acpi_button_resume+0x0/0x110 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: scsi target1:0:0: PM: calling scsi_bus_resume+0x0/0x90 @ 4585, parent: host1
Oct 11 17:34:22 ryzen kernel: platform rtc-efi.0: PM: calling platform_pm_resume+0x0/0x50 @ 5277, parent: platform
Oct 11 17:34:22 ryzen kernel: scsi target1:0:0: PM: scsi_bus_resume+0x0/0x90 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: platform rtc-efi.0: PM: platform_pm_resume+0x0/0x50 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: platform efivars.0: PM: calling platform_pm_resume+0x0/0x50 @ 5277, parent: platform
Oct 11 17:34:22 ryzen kernel: sr 1:0:0:0: PM: calling scsi_bus_resume+0x0/0x90 @ 5328, parent: target1:0:0
Oct 11 17:34:22 ryzen kernel: platform efivars.0: PM: platform_pm_resume+0x0/0x50 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: sr 1:0:0:0: PM: scsi_bus_resume+0x0/0x90 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: system 00:00: PM: calling pnp_bus_resume+0x0/0xa0 @ 5277, parent: pnp0
Oct 11 17:34:22 ryzen kernel: system 00:00: PM: pnp_bus_resume+0x0/0xa0 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: system 00:01: PM: calling pnp_bus_resume+0x0/0xa0 @ 5277, parent: pnp0
Oct 11 17:34:22 ryzen kernel: system 00:01: PM: pnp_bus_resume+0x0/0xa0 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: rtc_cmos 00:02: PM: calling pnp_bus_resume+0x0/0xa0 @ 5277, parent: pnp0
Oct 11 17:34:22 ryzen kernel: rtc_cmos 00:02: PM: pnp_bus_resume+0x0/0xa0 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: system 00:03: PM: calling pnp_bus_resume+0x0/0xa0 @ 5277, parent: pnp0
Oct 11 17:34:22 ryzen kernel: system 00:03: PM: pnp_bus_resume+0x0/0xa0 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: scsi host5: PM: calling scsi_bus_resume+0x0/0x90 @ 4582, parent: ata6
Oct 11 17:34:22 ryzen kernel: i8042 kbd 00:04: PM: calling pnp_bus_resume+0x0/0xa0 @ 5277, parent: pnp0
Oct 11 17:34:22 ryzen kernel: scsi host5: PM: scsi_bus_resume+0x0/0x90 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: scsi host3: PM: calling scsi_bus_resume+0x0/0x90 @ 4588, parent: ata4
Oct 11 17:34:22 ryzen kernel: scsi host3: PM: scsi_bus_resume+0x0/0x90 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: usb usb4: PM: calling usb_dev_resume+0x0/0x20 @ 5329, parent: 0000:07:00.3
Oct 11 17:34:22 ryzen kernel: r8169 0000:04:00.0: PM: pci_pm_resume+0x0/0xf0 returned 0 after 172 usecs
Oct 11 17:34:22 ryzen kernel: i8042 kbd 00:04: PM: pnp_bus_resume+0x0/0xa0 returned 0 after 49 usecs
Oct 11 17:34:22 ryzen kernel: serial 00:05: PM: calling pnp_bus_resume+0x0/0xa0 @ 5277, parent: pnp0
Oct 11 17:34:22 ryzen kernel: serial 00:05: activated
Oct 11 17:34:22 ryzen kernel: serial 00:05: PM: pnp_bus_resume+0x0/0xa0 returned 0 after 1023 usecs
Oct 11 17:34:22 ryzen kernel: system 00:06: PM: calling pnp_bus_resume+0x0/0xa0 @ 5277, parent: pnp0
Oct 11 17:34:22 ryzen kernel: system 00:06: PM: pnp_bus_resume+0x0/0xa0 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: pcspkr pcspkr: PM: calling platform_pm_resume+0x0/0x50 @ 5277, parent: platform
Oct 11 17:34:22 ryzen kernel: pcspkr pcspkr: PM: platform_pm_resume+0x0/0x50 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: input input0: PM: calling input_dev_resume+0x0/0x40 @ 5277, parent: PNP0C0C:00
Oct 11 17:34:22 ryzen kernel: input input0: PM: input_dev_resume+0x0/0x40 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: input input1: PM: calling input_dev_resume+0x0/0x40 @ 5277, parent: LNXPWRBN:00
Oct 11 17:34:22 ryzen kernel: input input1: PM: input_dev_resume+0x0/0x40 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: port 00:05:0.0: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 5277, parent: 00:05:0
Oct 11 17:34:22 ryzen kernel: port 00:05:0.0: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: serial8250 serial8250: PM: calling platform_pm_resume+0x0/0x50 @ 5277, parent: platform
Oct 11 17:34:22 ryzen kernel: serial8250 serial8250: PM: platform_pm_resume+0x0/0x50 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: port serial8250:0.1: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 5277, parent: serial8250:0
Oct 11 17:34:22 ryzen kernel: port serial8250:0.1: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: port serial8250:0.2: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 5277, parent: serial8250:0
Oct 11 17:34:22 ryzen kernel: port serial8250:0.2: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: port serial8250:0.3: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 5277, parent: serial8250:0
Oct 11 17:34:22 ryzen kernel: port serial8250:0.3: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: port serial8250:0.4: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 5277, parent: serial8250:0
Oct 11 17:34:22 ryzen kernel: port serial8250:0.4: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: port serial8250:0.5: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 5277, parent: serial8250:0
Oct 11 17:34:22 ryzen kernel: port serial8250:0.5: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: port serial8250:0.6: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 5277, parent: serial8250:0
Oct 11 17:34:22 ryzen kernel: port serial8250:0.6: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: port serial8250:0.7: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 5277, parent: serial8250:0
Oct 11 17:34:22 ryzen kernel: port serial8250:0.7: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: port serial8250:0.8: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 5277, parent: serial8250:0
Oct 11 17:34:22 ryzen kernel: port serial8250:0.8: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: port serial8250:0.9: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 5277, parent: serial8250:0
Oct 11 17:34:22 ryzen kernel: port serial8250:0.9: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: port serial8250:0.10: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 5277, parent: serial8250:0
Oct 11 17:34:22 ryzen kernel: port serial8250:0.10: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: port serial8250:0.11: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 5277, parent: serial8250:0
Oct 11 17:34:22 ryzen kernel: port serial8250:0.11: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: port serial8250:0.12: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 5277, parent: serial8250:0
Oct 11 17:34:22 ryzen kernel: port serial8250:0.12: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: port serial8250:0.13: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 5277, parent: serial8250:0
Oct 11 17:34:22 ryzen kernel: port serial8250:0.13: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: port serial8250:0.14: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 5277, parent: serial8250:0
Oct 11 17:34:22 ryzen kernel: port serial8250:0.14: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: port serial8250:0.15: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 5277, parent: serial8250:0
Oct 11 17:34:22 ryzen kernel: port serial8250:0.15: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: port serial8250:0.16: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 5277, parent: serial8250:0
Oct 11 17:34:22 ryzen kernel: port serial8250:0.16: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: port serial8250:0.17: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 5277, parent: serial8250:0
Oct 11 17:34:22 ryzen kernel: port serial8250:0.17: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: port serial8250:0.18: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 5277, parent: serial8250:0
Oct 11 17:34:22 ryzen kernel: port serial8250:0.18: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: port serial8250:0.19: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 5277, parent: serial8250:0
Oct 11 17:34:22 ryzen kernel: port serial8250:0.19: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: port serial8250:0.20: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 5277, parent: serial8250:0
Oct 11 17:34:22 ryzen kernel: port serial8250:0.20: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: port serial8250:0.21: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 5277, parent: serial8250:0
Oct 11 17:34:22 ryzen kernel: port serial8250:0.21: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: port serial8250:0.22: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 5277, parent: serial8250:0
Oct 11 17:34:22 ryzen kernel: port serial8250:0.22: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: port serial8250:0.23: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 5277, parent: serial8250:0
Oct 11 17:34:22 ryzen kernel: port serial8250:0.23: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: port serial8250:0.24: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 5277, parent: serial8250:0
Oct 11 17:34:22 ryzen kernel: port serial8250:0.24: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: port serial8250:0.25: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 5277, parent: serial8250:0
Oct 11 17:34:22 ryzen kernel: port serial8250:0.25: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: port serial8250:0.26: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 5277, parent: serial8250:0
Oct 11 17:34:22 ryzen kernel: port serial8250:0.26: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: port serial8250:0.27: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 5277, parent: serial8250:0
Oct 11 17:34:22 ryzen kernel: port serial8250:0.27: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: port serial8250:0.28: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 5277, parent: serial8250:0
Oct 11 17:34:22 ryzen kernel: port serial8250:0.28: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: port serial8250:0.29: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 5277, parent: serial8250:0
Oct 11 17:34:22 ryzen kernel: port serial8250:0.29: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: port serial8250:0.30: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 5277, parent: serial8250:0
Oct 11 17:34:22 ryzen kernel: port serial8250:0.30: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: port serial8250:0.31: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 5277, parent: serial8250:0
Oct 11 17:34:22 ryzen kernel: port serial8250:0.31: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: rtc rtc0: PM: calling rtc_resume+0x0/0x240 @ 5277, parent: 00:02
Oct 11 17:34:22 ryzen kernel: rtc rtc0: PM: rtc_resume+0x0/0x240 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: alarmtimer alarmtimer.0.auto: PM: calling platform_pm_resume+0x0/0x50 @ 5277, parent: rtc0
Oct 11 17:34:22 ryzen kernel: alarmtimer alarmtimer.0.auto: PM: platform_pm_resume+0x0/0x50 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: platform microcode: PM: calling platform_pm_resume+0x0/0x50 @ 5277, parent: platform
Oct 11 17:34:22 ryzen kernel: platform microcode: PM: platform_pm_resume+0x0/0x50 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: i8042 i8042: PM: calling platform_pm_resume+0x0/0x50 @ 5277, parent: platform
Oct 11 17:34:22 ryzen kernel: i8042 i8042: PM: platform_pm_resume+0x0/0x50 returned 0 after 44 usecs
Oct 11 17:34:22 ryzen kernel: atkbd serio0: PM: calling serio_resume+0x0/0xa0 [serio] @ 5277, parent: i8042
Oct 11 17:34:22 ryzen kernel: atkbd serio0: PM: serio_resume+0x0/0xa0 [serio] returned 0 after 2 usecs
Oct 11 17:34:22 ryzen kernel: input input2: PM: calling input_dev_resume+0x0/0x40 @ 5277, parent: serio0
Oct 11 17:34:22 ryzen kernel: input input2: PM: input_dev_resume+0x0/0x40 returned 0 after 1 usecs
Oct 11 17:34:22 ryzen kernel: leds input2::numlock: PM: calling led_resume+0x0/0x50 @ 5277, parent: input2
Oct 11 17:34:22 ryzen kernel: leds input2::numlock: PM: led_resume+0x0/0x50 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: leds input2::capslock: PM: calling led_resume+0x0/0x50 @ 5277, parent: input2
Oct 11 17:34:22 ryzen kernel: leds input2::capslock: PM: led_resume+0x0/0x50 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: leds input2::scrolllock: PM: calling led_resume+0x0/0x50 @ 5277, parent: input2
Oct 11 17:34:22 ryzen kernel: leds input2::scrolllock: PM: led_resume+0x0/0x50 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: snd_hda_intel 0000:07:00.4: PM: pci_pm_resume+0x0/0xf0 returned 0 after 4365 usecs
Oct 11 17:34:22 ryzen kernel: snd_hda_codec_realtek hdaudioC2D0: PM: calling hda_codec_pm_resume+0x0/0x20 [snd_hda_codec] @ 5323, parent: 0000:07:00.4
Oct 11 17:34:22 ryzen kernel: usb usb4: PM: usb_dev_resume+0x0/0x20 returned 0 after 26550 usecs
Oct 11 17:34:22 ryzen kernel: xhci_hcd 0000:02:00.0: PM: pci_pm_resume+0x0/0xf0 returned 0 after 56643 usecs
Oct 11 17:34:22 ryzen kernel: usb usb1: PM: calling usb_dev_resume+0x0/0x20 @ 5330, parent: 0000:02:00.0
Oct 11 17:34:22 ryzen kernel: usb usb2: PM: calling usb_dev_resume+0x0/0x20 @ 4534, parent: 0000:02:00.0
Oct 11 17:34:22 ryzen kernel: usb usb3: PM: usb_dev_resume+0x0/0x20 returned 0 after 57688 usecs
Oct 11 17:34:22 ryzen kernel: usb 3-2: PM: calling usb_dev_resume+0x0/0x20 @ 144, parent: usb3
Oct 11 17:34:22 ryzen kernel: nvme nvme0: Shutdown timeout set to 8 seconds
Oct 11 17:34:22 ryzen kernel: usb 3-2: PM: usb_dev_resume+0x0/0x20 returned 0 after 26299 usecs
Oct 11 17:34:22 ryzen kernel: input input3: PM: calling input_dev_resume+0x0/0x40 @ 5277, parent: 0003:1852:7022.0001
Oct 11 17:34:22 ryzen kernel: input input3: PM: input_dev_resume+0x0/0x40 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: nvme nvme0: 32/0/0 default/read/poll queues
Oct 11 17:34:22 ryzen kernel: usb usb1: PM: usb_dev_resume+0x0/0x20 returned 0 after 143407 usecs
Oct 11 17:34:22 ryzen kernel: usb 1-5: PM: calling usb_dev_resume+0x0/0x20 @ 5317, parent: usb1
Oct 11 17:34:22 ryzen kernel: usb 1-2: PM: calling usb_dev_resume+0x0/0x20 @ 4564, parent: usb1
Oct 11 17:34:22 ryzen kernel: usb 1-7: PM: calling usb_dev_resume+0x0/0x20 @ 1219, parent: usb1
Oct 11 17:34:22 ryzen kernel: usb 1-10: PM: calling usb_dev_resume+0x0/0x20 @ 4522, parent: usb1
Oct 11 17:34:22 ryzen kernel: snd_hda_codec_realtek hdaudioC2D0: PM: hda_codec_pm_resume+0x0/0x20 [snd_hda_codec] returned 0 after 215183 usecs
Oct 11 17:34:22 ryzen kernel: usb usb2: PM: usb_dev_resume+0x0/0x20 returned 0 after 213243 usecs
Oct 11 17:34:22 ryzen kernel: usb 2-4: PM: calling usb_dev_resume+0x0/0x20 @ 5311, parent: usb2
Oct 11 17:34:22 ryzen kernel: ata3: SATA link down (SStatus 0 SControl 330)
Oct 11 17:34:22 ryzen kernel: ata4: SATA link down (SStatus 0 SControl 330)
Oct 11 17:34:22 ryzen kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
Oct 11 17:34:22 ryzen kernel: ata2.00: configured for UDMA/100
Oct 11 17:34:22 ryzen kernel: [drm] PCIE GART of 256M enabled (table at 0x000000F400800000).
Oct 11 17:34:22 ryzen kernel: usb 1-5: reset low-speed USB device number 3 using xhci_hcd
Oct 11 17:34:22 ryzen kernel: usb 1-5: PM: usb_dev_resume+0x0/0x20 returned 0 after 668519 usecs
Oct 11 17:34:22 ryzen kernel: input input4: PM: calling input_dev_resume+0x0/0x40 @ 5277, parent: 0003:05F3:00FF.0002
Oct 11 17:34:22 ryzen kernel: input input4: PM: input_dev_resume+0x0/0x40 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: usb 1-10: reset full-speed USB device number 7 using xhci_hcd
Oct 11 17:34:22 ryzen kernel: ata6: failed to resume link (SControl 0)
Oct 11 17:34:22 ryzen kernel: ata6: SATA link down (SStatus 0 SControl 0)
Oct 11 17:34:22 ryzen kernel: ata5: failed to resume link (SControl 0)
Oct 11 17:34:22 ryzen kernel: ata5: SATA link down (SStatus 0 SControl 0)
Oct 11 17:34:22 ryzen kernel: usb 1-10: PM: usb_dev_resume+0x0/0x20 returned 0 after 1010576 usecs
Oct 11 17:34:22 ryzen kernel: [drm] Fence fallback timer expired on ring sdma0
Oct 11 17:34:22 ryzen kernel: usb 1-2: reset high-speed USB device number 2 using xhci_hcd
Oct 11 17:34:22 ryzen kernel: usb 1-7: reset full-speed USB device number 5 using xhci_hcd
Oct 11 17:34:22 ryzen kernel: usb 1-2: PM: usb_dev_resume+0x0/0x20 returned 0 after 1526875 usecs
Oct 11 17:34:22 ryzen kernel: usb 1-2.2: PM: calling usb_dev_resume+0x0/0x20 @ 4529, parent: 1-2
Oct 11 17:34:22 ryzen kernel: usb 1-2.1: PM: calling usb_dev_resume+0x0/0x20 @ 5310, parent: 1-2
Oct 11 17:34:22 ryzen kernel: usb 1-2.4: PM: calling usb_dev_resume+0x0/0x20 @ 4531, parent: 1-2
Oct 11 17:34:22 ryzen kernel: usb 1-2.3: PM: calling usb_dev_resume+0x0/0x20 @ 4561, parent: 1-2
Oct 11 17:34:22 ryzen kernel: [drm] Fence fallback timer expired on ring sdma0
Oct 11 17:34:22 ryzen kernel: usb 1-7: PM: usb_dev_resume+0x0/0x20 returned 0 after 1637227 usecs
Oct 11 17:34:22 ryzen kernel: usb 2-4: reset SuperSpeed USB device number 2 using xhci_hcd
Oct 11 17:34:22 ryzen kernel: usb 2-4: PM: usb_dev_resume+0x0/0x20 returned 0 after 1689521 usecs
Oct 11 17:34:22 ryzen kernel: scsi host6: PM: calling scsi_bus_resume+0x0/0x90 @ 4577, parent: 2-4:1.0
Oct 11 17:34:22 ryzen kernel: scsi host6: PM: scsi_bus_resume+0x0/0x90 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: scsi target6:0:0: PM: calling scsi_bus_resume+0x0/0x90 @ 4565, parent: host6
Oct 11 17:34:22 ryzen kernel: scsi target6:0:0: PM: scsi_bus_resume+0x0/0x90 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: sd 6:0:0:0: PM: calling scsi_bus_resume+0x0/0x90 @ 5316, parent: target6:0:0
Oct 11 17:34:22 ryzen kernel: sd 6:0:0:0: PM: scsi_bus_resume+0x0/0x90 returned 0 after 1 usecs
Oct 11 17:34:22 ryzen kernel: usb 1-2.2: reset full-speed USB device number 6 using xhci_hcd
Oct 11 17:34:22 ryzen kernel: [drm] Fence fallback timer expired on ring sdma0
Oct 11 17:34:22 ryzen kernel: usb 1-2.2: PM: usb_dev_resume+0x0/0x20 returned 0 after 569221 usecs
Oct 11 17:34:22 ryzen kernel: usb 1-2.4: reset full-speed USB device number 9 using xhci_hcd
Oct 11 17:34:22 ryzen kernel: usb 1-2.4: PM: usb_dev_resume+0x0/0x20 returned 0 after 845201 usecs
Oct 11 17:34:22 ryzen kernel: usb 1-2.1: reset full-speed USB device number 4 using xhci_hcd
Oct 11 17:34:22 ryzen kernel: [drm] Fence fallback timer expired on ring sdma0
Oct 11 17:34:22 ryzen kernel: [drm] Fence fallback timer expired on ring sdma0
Oct 11 17:34:22 ryzen kernel: [drm] Fence fallback timer expired on ring sdma0
Oct 11 17:34:22 ryzen kernel: [drm] Fence fallback timer expired on ring sdma0
Oct 11 17:34:22 ryzen kernel: [drm] Fence fallback timer expired on ring sdma0
Oct 11 17:34:22 ryzen kernel: [drm] UVD and UVD ENC initialized successfully.
Oct 11 17:34:22 ryzen kernel: [drm] VCE initialized successfully.
Oct 11 17:34:22 ryzen kernel: amdgpu 0000:05:00.0: PM: pci_pm_resume+0x0/0xf0 returned 0 after 5035376 usecs
Oct 11 17:34:22 ryzen kernel: snd_hda_intel 0000:05:00.1: PM: calling pci_pm_resume+0x0/0xf0 @ 4532, parent: 0000:00:03.1
Oct 11 17:34:22 ryzen kernel: snd_hda_intel 0000:05:00.1: PM: pci_pm_resume+0x0/0xf0 returned 0 after 2311 usecs
Oct 11 17:34:22 ryzen kernel: ata1: link is slow to respond, please be patient (ready=0)
Oct 11 17:34:22 ryzen kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Oct 11 17:34:22 ryzen kernel: ata1.00: configured for UDMA/133
Oct 11 17:34:22 ryzen kernel: usb 1-2.1: PM: usb_dev_resume+0x0/0x20 returned 0 after 6433974 usecs
Oct 11 17:34:22 ryzen kernel: input input5: PM: calling input_dev_resume+0x0/0x40 @ 5277, parent: 0003:0ECB:2057.0003
Oct 11 17:34:22 ryzen kernel: input input5: PM: input_dev_resume+0x0/0x40 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: input input6: PM: calling input_dev_resume+0x0/0x40 @ 5277, parent: 0003:29EA:0102.0005
Oct 11 17:34:22 ryzen kernel: input input6: PM: input_dev_resume+0x0/0x40 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: input input7: PM: calling input_dev_resume+0x0/0x40 @ 5277, parent: 0003:29EA:0102.0006
Oct 11 17:34:22 ryzen kernel: input input7: PM: input_dev_resume+0x0/0x40 returned 0 after 11 usecs
Oct 11 17:34:22 ryzen kernel: leds input7::numlock: PM: calling led_resume+0x0/0x50 @ 5277, parent: input7
Oct 11 17:34:22 ryzen kernel: leds input7::numlock: PM: led_resume+0x0/0x50 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: leds input7::capslock: PM: calling led_resume+0x0/0x50 @ 5277, parent: input7
Oct 11 17:34:22 ryzen kernel: leds input7::capslock: PM: led_resume+0x0/0x50 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: leds input7::scrolllock: PM: calling led_resume+0x0/0x50 @ 5277, parent: input7
Oct 11 17:34:22 ryzen kernel: leds input7::scrolllock: PM: led_resume+0x0/0x50 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: leds input7::compose: PM: calling led_resume+0x0/0x50 @ 5277, parent: input7
Oct 11 17:34:22 ryzen kernel: leds input7::compose: PM: led_resume+0x0/0x50 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: leds input7::kana: PM: calling led_resume+0x0/0x50 @ 5277, parent: input7
Oct 11 17:34:22 ryzen kernel: leds input7::kana: PM: led_resume+0x0/0x50 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: input input8: PM: calling input_dev_resume+0x0/0x40 @ 5277, parent: 0003:29EA:0102.0007
Oct 11 17:34:22 ryzen kernel: input input8: PM: input_dev_resume+0x0/0x40 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: input input9: PM: calling input_dev_resume+0x0/0x40 @ 5277, parent: 0003:29EA:0102.0007
Oct 11 17:34:22 ryzen kernel: input input9: PM: input_dev_resume+0x0/0x40 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: usb 1-2.3: reset full-speed USB device number 8 using xhci_hcd
Oct 11 17:34:22 ryzen kernel: usb 1-2.3: PM: usb_dev_resume+0x0/0x20 returned 0 after 6741521 usecs
Oct 11 17:34:22 ryzen kernel: input input10: PM: calling input_dev_resume+0x0/0x40 @ 5277, parent: 0003:046D:C092.0009
Oct 11 17:34:22 ryzen kernel: input input10: PM: input_dev_resume+0x0/0x40 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: input input11: PM: calling input_dev_resume+0x0/0x40 @ 5277, parent: 0003:046D:C092.000A
Oct 11 17:34:22 ryzen kernel: input input11: PM: input_dev_resume+0x0/0x40 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: sp5100-tco sp5100-tco: PM: calling platform_pm_resume+0x0/0x50 @ 5277, parent: platform
Oct 11 17:34:22 ryzen kernel: sp5100-tco sp5100-tco: PM: platform_pm_resume+0x0/0x50 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: input input14: PM: calling input_dev_resume+0x0/0x40 @ 5277, parent: pcspkr
Oct 11 17:34:22 ryzen kernel: input input14: PM: input_dev_resume+0x0/0x40 returned 0 after 11 usecs
Oct 11 17:34:22 ryzen kernel: input input15: PM: calling input_dev_resume+0x0/0x40 @ 5277, parent: card1
Oct 11 17:34:22 ryzen kernel: input input15: PM: input_dev_resume+0x0/0x40 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: input input16: PM: calling input_dev_resume+0x0/0x40 @ 5277, parent: card1
Oct 11 17:34:22 ryzen kernel: input input16: PM: input_dev_resume+0x0/0x40 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: input input17: PM: calling input_dev_resume+0x0/0x40 @ 5277, parent: card1
Oct 11 17:34:22 ryzen kernel: input input17: PM: input_dev_resume+0x0/0x40 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: input input18: PM: calling input_dev_resume+0x0/0x40 @ 5277, parent: card1
Oct 11 17:34:22 ryzen kernel: input input18: PM: input_dev_resume+0x0/0x40 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: input input19: PM: calling input_dev_resume+0x0/0x40 @ 5277, parent: card1
Oct 11 17:34:22 ryzen kernel: input input19: PM: input_dev_resume+0x0/0x40 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: input input20: PM: calling input_dev_resume+0x0/0x40 @ 5277, parent: card1
Oct 11 17:34:22 ryzen kernel: input input20: PM: input_dev_resume+0x0/0x40 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: input input21: PM: calling input_dev_resume+0x0/0x40 @ 5277, parent: card2
Oct 11 17:34:22 ryzen kernel: input input21: PM: input_dev_resume+0x0/0x40 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: input input22: PM: calling input_dev_resume+0x0/0x40 @ 5277, parent: card2
Oct 11 17:34:22 ryzen kernel: input input22: PM: input_dev_resume+0x0/0x40 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: input input23: PM: calling input_dev_resume+0x0/0x40 @ 5277, parent: card2
Oct 11 17:34:22 ryzen kernel: input input23: PM: input_dev_resume+0x0/0x40 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: input input24: PM: calling input_dev_resume+0x0/0x40 @ 5277, parent: card2
Oct 11 17:34:22 ryzen kernel: input input24: PM: input_dev_resume+0x0/0x40 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: input input25: PM: calling input_dev_resume+0x0/0x40 @ 5277, parent: card2
Oct 11 17:34:22 ryzen kernel: input input25: PM: input_dev_resume+0x0/0x40 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: Generic FE-GE Realtek PHY r8169-0-400:00: PM: calling mdio_bus_phy_resume+0x0/0x130 [libphy] @ 5277, parent: r8169-0-400
Oct 11 17:34:22 ryzen kernel: Generic FE-GE Realtek PHY r8169-0-400:00: PM: mdio_bus_phy_resume+0x0/0x130 [libphy] returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: intel_rapl_msr intel_rapl_msr.0: PM: calling platform_pm_resume+0x0/0x50 @ 5277, parent: platform
Oct 11 17:34:22 ryzen kernel: intel_rapl_msr intel_rapl_msr.0: PM: platform_pm_resume+0x0/0x50 returned 0 after 0 usecs
Oct 11 17:34:22 ryzen kernel: PM: resume of devices complete after 8468.870 msecs
Oct 11 17:34:22 ryzen kernel: OOM killer enabled.
Oct 11 17:34:22 ryzen kernel: Restarting tasks ... done.
Oct 11 17:34:22 ryzen kernel: random: crng reseeded on system resumption
Oct 11 17:34:22 ryzen kernel: PM: suspend exit
Oct 11 17:34:22 ryzen systemd-sleep[5277]: System returned from sleep state.
Oct 11 17:34:22 ryzen rtkit-daemon[1365]: The canary thread is apparently starving. Taking action.
Oct 11 17:34:22 ryzen systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
Oct 11 17:34:22 ryzen rtkit-daemon[1365]: Demoting known real-time threads.
Oct 11 17:34:22 ryzen systemd[1]: systemd-suspend.service: Deactivated successfully.
Oct 11 17:34:22 ryzen rtkit-daemon[1365]: Demoted 0 threads.
Oct 11 17:34:22 ryzen systemd[1]: Finished System Suspend.
Oct 11 17:34:22 ryzen /usr/bin/gpm[827]: *** info [mice.c(1990)]:
Oct 11 17:34:22 ryzen systemd[1]: systemd-suspend.service: Consumed 4.066s CPU time.
Oct 11 17:34:22 ryzen /usr/bin/gpm[827]: imps2: Auto-detected intellimouse PS/2
Oct 11 17:34:22 ryzen systemd[1]: Stopped target Sleep.
Oct 11 17:34:22 ryzen systemd[1]: Reached target Suspend.
Oct 11 17:34:22 ryzen systemd-udevd[364]: /etc/udev/rules.d/30-usbtmc.rules:5 Unknown group 'usbtmc', ignoring.
Oct 11 17:34:22 ryzen systemd[1]: Stopped target Suspend.
Oct 11 17:34:22 ryzen systemd-udevd[364]: /etc/udev/rules.d/30-usbtmc.rules:8 Unknown group 'usbtmc', ignoring.
Oct 11 17:34:22 ryzen systemd-udevd[364]: /etc/udev/rules.d/30-usbtmc.rules:11 Unknown group 'usbtmc', ignoring.
Oct 11 17:34:22 ryzen systemd-udevd[364]: /etc/udev/rules.d/30-usbtmc.rules:14 Unknown group 'usbtmc', ignoring.
Oct 11 17:34:22 ryzen systemd-udevd[364]: /etc/udev/rules.d/30-usbtmc.rules:15 Unknown group 'usbtmc', ignoring.
Oct 11 17:34:22 ryzen systemd-udevd[364]: /usr/lib/udev/rules.d/51-footcontroller.rules:10 Invalid value for OPTIONS key, ignoring: 'last_rule'
Oct 11 17:34:23 ryzen systemd-logind[830]: Operation 'sleep' finished.
Oct 11 17:34:23 ryzen NetworkManager[927]: <info> [1697070863.1060] manager: sleep: wake requested (sleeping: yes enabled: yes)
Oct 11 17:34:23 ryzen NetworkManager[927]: <info> [1697070863.1061] device (enp4s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Oct 11 17:34:23 ryzen kernel: Generic FE-GE Realtek PHY r8169-0-400:00: attached PHY driver (mii_bus:phy_addr=r8169-0-400:00, irq=MAC)
Oct 11 17:34:23 ryzen NetworkManager[927]: <info> [1697070863.3232] manager: NetworkManager state is now CONNECTED_LOCAL
Oct 11 17:34:23 ryzen kernel: r8169 0000:04:00.0 enp4s0: Link is Down
Oct 11 17:34:25 ryzen NetworkManager[927]: <info> [1697070865.9840] device (enp4s0): carrier: link connected
Oct 11 17:34:25 ryzen NetworkManager[927]: <info> [1697070865.9842] device (enp4s0): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed')
Oct 11 17:34:25 ryzen NetworkManager[927]: <info> [1697070865.9848] policy: auto-activating connection 'Wired connection 1' (1a78b687-138e-3a66-9ca0-dc365ee4d000)
Oct 11 17:34:25 ryzen NetworkManager[927]: <info> [1697070865.9850] device (enp4s0): Activation: starting connection 'Wired connection 1' (1a78b687-138e-3a66-9ca0-dc365ee4d000)
Oct 11 17:34:25 ryzen NetworkManager[927]: <info> [1697070865.9851] device (enp4s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Oct 11 17:34:25 ryzen NetworkManager[927]: <info> [1697070865.9851] manager: NetworkManager state is now CONNECTING
Oct 11 17:34:25 ryzen NetworkManager[927]: <info> [1697070865.9852] device (enp4s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Oct 11 17:34:25 ryzen NetworkManager[927]: <info> [1697070865.9855] device (enp4s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Oct 11 17:34:25 ryzen NetworkManager[927]: <info> [1697070865.9858] dhcp4 (enp4s0): activation: beginning transaction (timeout in 45 seconds)
Oct 11 17:34:25 ryzen kernel: r8169 0000:04:00.0 enp4s0: Link is Up - 1Gbps/Full - flow control rx/tx
Oct 11 17:34:25 ryzen dnsmasq[1089]: reading /etc/resolv.conf
Oct 11 17:34:25 ryzen dnsmasq[1089]: using nameserver 1.1.1.1#53
Oct 11 17:34:25 ryzen dnsmasq[1056]: reading /etc/resolv.conf
Oct 11 17:34:25 ryzen dnsmasq[1056]: using nameserver 1.1.1.1#53
Oct 11 17:34:25 ryzen NetworkManager[927]: <info> [1697070865.9931] dhcp4 (enp4s0): state changed new lease, address=192.168.0.91
Oct 11 17:34:25 ryzen NetworkManager[927]: <info> [1697070865.9933] policy: set 'Wired connection 1' (enp4s0) as default for IPv4 routing and DNS
Oct 11 17:34:25 ryzen dnsmasq[1089]: reading /etc/resolv.conf
Oct 11 17:34:25 ryzen dnsmasq[1056]: reading /etc/resolv.conf
Oct 11 17:34:25 ryzen dnsmasq[1089]: using nameserver 1.1.1.1#53
Oct 11 17:34:25 ryzen dnsmasq[1089]: using nameserver 8.8.8.8#53
Oct 11 17:34:25 ryzen dnsmasq[1056]: using nameserver 1.1.1.1#53
Oct 11 17:34:25 ryzen dnsmasq[1056]: using nameserver 8.8.8.8#53
Oct 11 17:34:25 ryzen avahi-daemon[823]: Joining mDNS multicast group on interface enp4s0.IPv4 with address 192.168.0.91.
Oct 11 17:34:25 ryzen avahi-daemon[823]: New relevant interface enp4s0.IPv4 for mDNS.
Oct 11 17:34:25 ryzen avahi-daemon[823]: Registering new address record for 192.168.0.91 on enp4s0.IPv4.
Oct 11 17:34:25 ryzen avahi-daemon[823]: Joining mDNS multicast group on interface enp4s0.IPv6 with address fe80::1b36:1dd4:a5cf:3b8f.
Oct 11 17:34:25 ryzen avahi-daemon[823]: New relevant interface enp4s0.IPv6 for mDNS.
Oct 11 17:34:25 ryzen avahi-daemon[823]: Registering new address record for fe80::1b36:1dd4:a5cf:3b8f on enp4s0.*.
Oct 11 17:34:26 ryzen dbus-daemon[824]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.4' (uid=0 pid=927 comm="/usr/bin/NetworkManager --no-daemon")
Oct 11 17:34:26 ryzen NetworkManager[927]: <info> [1697070866.0064] device (enp4s0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Oct 11 17:34:26 ryzen systemd[1]: Starting Network Manager Script Dispatcher Service...
Oct 11 17:34:26 ryzen dbus-daemon[824]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Oct 11 17:34:26 ryzen systemd[1]: Started Network Manager Script Dispatcher Service.
Oct 11 17:34:26 ryzen NetworkManager[927]: <info> [1697070866.0367] device (enp4s0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Oct 11 17:34:26 ryzen NetworkManager[927]: <info> [1697070866.0368] device (enp4s0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Oct 11 17:34:26 ryzen NetworkManager[927]: <info> [1697070866.0370] manager: NetworkManager state is now CONNECTED_SITE
Oct 11 17:34:26 ryzen NetworkManager[927]: <info> [1697070866.0371] device (enp4s0): Activation: successful, device activated.
Oct 11 17:34:26 ryzen NetworkManager[927]: <info> [1697070866.4532] manager: NetworkManager state is now CONNECTED_GLOBAL
Oct 11 17:34:26 ryzen PackageKit[1897]: get-updates transaction /8_ddaeeaab from uid 1001 finished with success after 2ms
Oct 11 17:34:27 ryzen NetworkManager[927]: <info> [1697070867.2562] dhcp6 (enp4s0): activation: beginning transaction (timeout in 45 seconds)
Oct 11 17:34:27 ryzen dnsmasq[1089]: reading /etc/resolv.conf
Oct 11 17:34:27 ryzen dnsmasq[1056]: reading /etc/resolv.conf
Oct 11 17:34:27 ryzen dnsmasq[1089]: using nameserver 1.1.1.1#53
Oct 11 17:34:27 ryzen dnsmasq[1089]: using nameserver 8.8.8.8#53
Oct 11 17:34:27 ryzen dnsmasq[1089]: using nameserver fde3:5408:101c::1#53
Oct 11 17:34:27 ryzen dnsmasq[1056]: using nameserver 1.1.1.1#53
Oct 11 17:34:27 ryzen dnsmasq[1056]: using nameserver 8.8.8.8#53
Oct 11 17:34:27 ryzen dnsmasq[1056]: using nameserver fde3:5408:101c::1#53
Oct 11 17:34:27 ryzen avahi-daemon[823]: Leaving mDNS multicast group on interface enp4s0.IPv6 with address fe80::1b36:1dd4:a5cf:3b8f.
Oct 11 17:34:27 ryzen avahi-daemon[823]: Joining mDNS multicast group on interface enp4s0.IPv6 with address fde3:5408:101c:0:7441:9d56:d3c1:1a95.
Oct 11 17:34:27 ryzen NetworkManager[927]: <info> [1697070867.2630] dhcp6 (enp4s0): state changed new lease, address=fde3:5408:101c::566
Oct 11 17:34:27 ryzen avahi-daemon[823]: Registering new address record for fde3:5408:101c:0:7441:9d56:d3c1:1a95 on enp4s0.*.
Oct 11 17:34:27 ryzen avahi-daemon[823]: Withdrawing address record for fe80::1b36:1dd4:a5cf:3b8f on enp4s0.
Oct 11 17:34:27 ryzen avahi-daemon[823]: Registering new address record for fde3:5408:101c::566 on enp4s0.*.
Oct 11 17:34:30 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 17:34:30 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 17:34:36 ryzen systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
Oct 11 17:35:44 ryzen systemd-timesyncd[815]: Contacted time server 65.100.46.166:123 (0.arch.pool.ntp.org).
Oct 11 17:36:01 ryzen systemd[1]: flatpak-system-helper.service: Deactivated successfully.
Oct 11 17:36:12 ryzen dbus-daemon[824]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.128' (uid=1001 pid=5218 comm="/usr/lib/kscreenlocker_greet --immediateLock --gra")
Oct 11 17:36:12 ryzen dbus-daemon[824]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.
Oct 11 17:36:57 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 17:36:57 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 17:37:01 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 17:37:01 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 17:37:24 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 17:37:24 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 17:38:07 ryzen systemd[1]: Starting Cleanup of Temporary Directories...
Oct 11 17:38:07 ryzen systemd[1]: systemd-tmpfiles-clean.service: Deactivated successfully.
Oct 11 17:38:07 ryzen systemd[1]: Finished Cleanup of Temporary Directories.
Oct 11 17:38:52 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 17:38:52 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 17:39:28 ryzen PackageKit[1897]: daemon quit
Oct 11 17:39:28 ryzen systemd[1]: packagekit.service: Deactivated successfully.
Oct 11 17:39:46 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 17:39:46 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 17:41:24 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 17:41:24 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 17:42:13 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 17:42:13 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 17:45:26 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 17:45:26 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 17:49:18 ryzen systemd[1]: Starting Daily man-db regeneration...
Oct 11 17:49:28 ryzen systemd[1]: man-db.service: Deactivated successfully.
Oct 11 17:49:28 ryzen systemd[1]: Finished Daily man-db regeneration.
Oct 11 17:49:28 ryzen systemd[1]: man-db.service: Consumed 8.384s CPU time.
Oct 11 17:57:26 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 17:57:26 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 17:57:31 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 17:57:31 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 17:59:14 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 17:59:14 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 18:00:17 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 18:00:17 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 18:01:05 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 18:01:05 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 18:01:05 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 18:01:05 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 18:01:25 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 18:01:25 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 18:01:25 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 18:01:25 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 18:01:30 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 18:01:30 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 18:04:50 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 18:04:50 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 18:05:22 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 18:05:22 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 18:05:22 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 18:05:22 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 18:05:22 ryzen rtkit-daemon[1365]: Successfully made thread 8886 of process 2726 owned by '1001' RT at priority 10.
Oct 11 18:05:22 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 18:05:26 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 18:05:26 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 18:05:31 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 18:05:31 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 18:05:44 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 18:05:44 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 18:06:03 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 18:06:03 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 18:06:13 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 18:06:13 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 18:08:16 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 18:08:16 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 18:08:19 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 18:08:19 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 18:09:29 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 18:09:29 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 18:10:15 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 18:10:15 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 18:10:15 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 18:10:15 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 18:10:51 ryzen systemd-udevd[364]: /etc/udev/rules.d/30-usbtmc.rules:5 Unknown group 'usbtmc', ignoring.
Oct 11 18:10:51 ryzen systemd-udevd[364]: /etc/udev/rules.d/30-usbtmc.rules:8 Unknown group 'usbtmc', ignoring.
Oct 11 18:10:51 ryzen systemd-udevd[364]: /etc/udev/rules.d/30-usbtmc.rules:11 Unknown group 'usbtmc', ignoring.
Oct 11 18:10:51 ryzen systemd-udevd[364]: /etc/udev/rules.d/30-usbtmc.rules:14 Unknown group 'usbtmc', ignoring.
Oct 11 18:10:51 ryzen systemd-udevd[364]: /etc/udev/rules.d/30-usbtmc.rules:15 Unknown group 'usbtmc', ignoring.
Oct 11 18:10:51 ryzen systemd-udevd[364]: /usr/lib/udev/rules.d/51-footcontroller.rules:10 Invalid value for OPTIONS key, ignoring: 'last_rule'
Oct 11 18:10:51 ryzen systemd[1]: tmp-.mount_kotatodWBiT0.mount: Deactivated successfully.
Oct 11 18:11:21 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 18:11:21 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 18:12:22 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 18:12:22 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 18:12:55 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 18:12:55 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 18:13:19 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 18:13:19 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 18:16:28 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 18:16:28 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 18:16:31 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 18:16:31 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 18:18:22 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 18:18:22 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 18:19:51 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 18:19:51 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 18:22:34 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 18:22:34 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 18:22:34 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 18:22:34 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 18:22:35 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 18:22:35 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 18:22:36 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 18:22:36 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 18:22:36 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 18:22:36 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 18:22:36 ryzen rtkit-daemon[1365]: Successfully made thread 10555 of process 10197 owned by '1001' RT at priority 10.
Oct 11 18:22:36 ryzen rtkit-daemon[1365]: Supervising 2 threads of 2 processes of 1 users.
Oct 11 18:24:24 ryzen dbus-daemon[824]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.177' (uid=1001 pid=10797 comm="/usr/lib/kscreenlocker_greet --immediateLock --gra")
Oct 11 18:24:24 ryzen dbus-daemon[824]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.
Oct 11 18:24:38 ryzen rtkit-daemon[1365]: Supervising 2 threads of 2 processes of 1 users.
Oct 11 18:24:38 ryzen rtkit-daemon[1365]: Supervising 2 threads of 2 processes of 1 users.
Oct 11 18:26:20 ryzen rtkit-daemon[1365]: Supervising 2 threads of 2 processes of 1 users.
Oct 11 18:26:20 ryzen rtkit-daemon[1365]: Supervising 2 threads of 2 processes of 1 users.
Oct 11 18:26:28 ryzen rtkit-daemon[1365]: Supervising 2 threads of 2 processes of 1 users.
Oct 11 18:26:28 ryzen rtkit-daemon[1365]: Supervising 2 threads of 2 processes of 1 users.
Oct 11 18:26:36 ryzen rtkit-daemon[1365]: Supervising 2 threads of 2 processes of 1 users.
Oct 11 18:26:36 ryzen rtkit-daemon[1365]: Supervising 2 threads of 2 processes of 1 users.
Oct 11 18:27:39 ryzen rtkit-daemon[1365]: Supervising 2 threads of 2 processes of 1 users.
Oct 11 18:27:39 ryzen rtkit-daemon[1365]: Supervising 2 threads of 2 processes of 1 users.
Oct 11 18:29:19 ryzen rtkit-daemon[1365]: Supervising 2 threads of 2 processes of 1 users.
Oct 11 18:29:19 ryzen rtkit-daemon[1365]: Supervising 2 threads of 2 processes of 1 users.
Oct 11 18:29:46 ryzen rtkit-daemon[1365]: Supervising 2 threads of 2 processes of 1 users.
Oct 11 18:29:46 ryzen rtkit-daemon[1365]: Supervising 2 threads of 2 processes of 1 users.
Oct 11 18:29:49 ryzen rtkit-daemon[1365]: Supervising 2 threads of 2 processes of 1 users.
Oct 11 18:29:49 ryzen rtkit-daemon[1365]: Supervising 2 threads of 2 processes of 1 users.
Oct 11 18:31:31 ryzen rtkit-daemon[1365]: Supervising 2 threads of 2 processes of 1 users.
Oct 11 18:31:31 ryzen rtkit-daemon[1365]: Supervising 2 threads of 2 processes of 1 users.
Oct 11 18:31:34 ryzen rtkit-daemon[1365]: Supervising 2 threads of 2 processes of 1 users.
Oct 11 18:31:34 ryzen rtkit-daemon[1365]: Supervising 2 threads of 2 processes of 1 users.
Oct 11 18:32:46 ryzen rtkit-daemon[1365]: Supervising 2 threads of 2 processes of 1 users.
Oct 11 18:32:46 ryzen rtkit-daemon[1365]: Supervising 2 threads of 2 processes of 1 users.
Oct 11 18:33:12 ryzen rtkit-daemon[1365]: Supervising 2 threads of 2 processes of 1 users.
Oct 11 18:33:12 ryzen rtkit-daemon[1365]: Supervising 2 threads of 2 processes of 1 users.
Oct 11 18:41:04 ryzen systemd-udevd[364]: /etc/udev/rules.d/30-usbtmc.rules:5 Unknown group 'usbtmc', ignoring.
Oct 11 18:41:04 ryzen systemd-udevd[364]: /etc/udev/rules.d/30-usbtmc.rules:8 Unknown group 'usbtmc', ignoring.
Oct 11 18:41:04 ryzen systemd-udevd[364]: /etc/udev/rules.d/30-usbtmc.rules:11 Unknown group 'usbtmc', ignoring.
Oct 11 18:41:04 ryzen systemd-udevd[364]: /etc/udev/rules.d/30-usbtmc.rules:14 Unknown group 'usbtmc', ignoring.
Oct 11 18:41:04 ryzen systemd-udevd[364]: /etc/udev/rules.d/30-usbtmc.rules:15 Unknown group 'usbtmc', ignoring.
Oct 11 18:41:04 ryzen systemd-udevd[364]: /usr/lib/udev/rules.d/51-footcontroller.rules:10 Invalid value for OPTIONS key, ignoring: 'last_rule'
Oct 11 18:41:05 ryzen rtkit-daemon[1365]: Supervising 2 threads of 2 processes of 1 users.
Oct 11 18:41:05 ryzen rtkit-daemon[1365]: Supervising 2 threads of 2 processes of 1 users.
Oct 11 18:49:12 ryzen systemd-udevd[364]: /etc/udev/rules.d/30-usbtmc.rules:5 Unknown group 'usbtmc', ignoring.
Oct 11 18:49:12 ryzen systemd-udevd[364]: /etc/udev/rules.d/30-usbtmc.rules:8 Unknown group 'usbtmc', ignoring.
Oct 11 18:49:12 ryzen systemd-udevd[364]: /etc/udev/rules.d/30-usbtmc.rules:11 Unknown group 'usbtmc', ignoring.
Oct 11 18:49:12 ryzen systemd-udevd[364]: /etc/udev/rules.d/30-usbtmc.rules:14 Unknown group 'usbtmc', ignoring.
Oct 11 18:49:12 ryzen systemd-udevd[364]: /etc/udev/rules.d/30-usbtmc.rules:15 Unknown group 'usbtmc', ignoring.
Oct 11 18:49:12 ryzen systemd-udevd[364]: /usr/lib/udev/rules.d/51-footcontroller.rules:10 Invalid value for OPTIONS key, ignoring: 'last_rule'
Oct 11 18:49:12 ryzen kernel: traps: VizCompositorTh[4027] trap int3 ip:55b34320d336 sp:7f68e33ec400 error:0 in electron[55b33bf37000+7aaf000]
Oct 11 18:49:12 ryzen systemd[1]: Created slice Slice /system/systemd-coredump.
Oct 11 18:49:12 ryzen systemd[1]: Started Process Core Dump (PID 12253/UID 0).
Oct 11 18:49:14 ryzen systemd[1]: systemd-coredump@0-12253-0.service: Deactivated successfully.
Oct 11 18:49:14 ryzen systemd[1]: systemd-coredump@0-12253-0.service: Consumed 2.440s CPU time.
Oct 11 18:49:16 ryzen dbus-daemon[824]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.192' (uid=1001 pid=11796 comm="/usr/lib/kscreenlocker_greet --immediateLock --gra")
Oct 11 18:49:16 ryzen dbus-daemon[824]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.
Oct 11 18:51:10 ryzen systemd-udevd[364]: /etc/udev/rules.d/30-usbtmc.rules:5 Unknown group 'usbtmc', ignoring.
Oct 11 18:51:10 ryzen systemd-udevd[364]: /etc/udev/rules.d/30-usbtmc.rules:8 Unknown group 'usbtmc', ignoring.
Oct 11 18:51:10 ryzen systemd-udevd[364]: /etc/udev/rules.d/30-usbtmc.rules:11 Unknown group 'usbtmc', ignoring.
Oct 11 18:51:10 ryzen systemd-udevd[364]: /etc/udev/rules.d/30-usbtmc.rules:14 Unknown group 'usbtmc', ignoring.
Oct 11 18:51:10 ryzen systemd-udevd[364]: /etc/udev/rules.d/30-usbtmc.rules:15 Unknown group 'usbtmc', ignoring.
Oct 11 18:51:10 ryzen systemd-udevd[364]: /usr/lib/udev/rules.d/51-footcontroller.rules:10 Invalid value for OPTIONS key, ignoring: 'last_rule'
Oct 11 18:51:46 ryzen rtkit-daemon[1365]: Supervising 2 threads of 2 processes of 1 users.
Oct 11 18:51:46 ryzen rtkit-daemon[1365]: Supervising 2 threads of 2 processes of 1 users.
Oct 11 18:52:24 ryzen rtkit-daemon[1365]: Supervising 2 threads of 2 processes of 1 users.
Oct 11 18:52:24 ryzen rtkit-daemon[1365]: Supervising 2 threads of 2 processes of 1 users.
Oct 11 18:52:39 ryzen kernel: usb 1-7: input irq status -75 received
Oct 11 18:52:39 ryzen kernel: usb 1-7: input irq status -75 received
Oct 11 18:52:40 ryzen dbus-daemon[824]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.198' (uid=0 pid=12984 comm="/usr/lib/polkit-1/polkit-agent-helper-1 nyanpasu64")
Oct 11 18:52:40 ryzen dbus-daemon[824]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.
Oct 11 18:52:40 ryzen polkitd[1159]: Operator of unix-session:2 successfully authenticated as unix-user:nyanpasu64 to gain TEMPORARY authorization for action org.freedesktop.udisks2.filesystem-mount-system for system-bus-name::1.137 [/usr/bin/dolphin] (owned by unix-user:nyanpasu64)
Oct 11 18:52:40 ryzen kernel: ntfs3: Max link count 4000
Oct 11 18:52:40 ryzen kernel: ntfs3: Enabled Linux POSIX ACLs support
Oct 11 18:52:40 ryzen kernel: ntfs3: Read-only LZX/Xpress compression included
Oct 11 18:52:40 ryzen systemd-udevd[364]: /etc/udev/rules.d/30-usbtmc.rules:5 Unknown group 'usbtmc', ignoring.
Oct 11 18:52:40 ryzen systemd-udevd[364]: /etc/udev/rules.d/30-usbtmc.rules:8 Unknown group 'usbtmc', ignoring.
Oct 11 18:52:40 ryzen systemd-udevd[364]: /etc/udev/rules.d/30-usbtmc.rules:11 Unknown group 'usbtmc', ignoring.
Oct 11 18:52:40 ryzen systemd-udevd[364]: /etc/udev/rules.d/30-usbtmc.rules:14 Unknown group 'usbtmc', ignoring.
Oct 11 18:52:40 ryzen systemd-udevd[364]: /etc/udev/rules.d/30-usbtmc.rules:15 Unknown group 'usbtmc', ignoring.
Oct 11 18:52:40 ryzen systemd-udevd[364]: /usr/lib/udev/rules.d/51-footcontroller.rules:10 Invalid value for OPTIONS key, ignoring: 'last_rule'
Oct 11 18:52:40 ryzen udisksd[1160]: Mounted /dev/nvme0n1p4 at /run/media/nyanpasu64/Windows 10 on behalf of uid 1001
Oct 11 18:52:53 ryzen rtkit-daemon[1365]: Supervising 2 threads of 2 processes of 1 users.
Oct 11 18:52:53 ryzen rtkit-daemon[1365]: Supervising 2 threads of 2 processes of 1 users.
Oct 11 18:53:58 ryzen rtkit-daemon[1365]: Supervising 2 threads of 2 processes of 1 users.
Oct 11 18:53:58 ryzen rtkit-daemon[1365]: Supervising 2 threads of 2 processes of 1 users.
Oct 11 18:54:24 ryzen rtkit-daemon[1365]: Supervising 2 threads of 2 processes of 1 users.
Oct 11 18:54:24 ryzen rtkit-daemon[1365]: Supervising 2 threads of 2 processes of 1 users.
Oct 11 18:55:14 ryzen rtkit-daemon[1365]: Supervising 2 threads of 2 processes of 1 users.
Oct 11 18:55:14 ryzen rtkit-daemon[1365]: Supervising 2 threads of 2 processes of 1 users.
Oct 11 18:55:14 ryzen rtkit-daemon[1365]: Supervising 2 threads of 2 processes of 1 users.
Oct 11 18:55:14 ryzen rtkit-daemon[1365]: Supervising 2 threads of 2 processes of 1 users.
Oct 11 18:55:14 ryzen rtkit-daemon[1365]: Successfully made thread 13924 of process 13715 owned by '1001' RT at priority 10.
Oct 11 18:55:14 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 18:56:00 ryzen kernel: usb 1-1: new high-speed USB device number 10 using xhci_hcd
Oct 11 18:56:00 ryzen kernel: usb 1-1: New USB device found, idVendor=058f, idProduct=6254, bcdDevice= 1.00
Oct 11 18:56:00 ryzen kernel: usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Oct 11 18:56:00 ryzen systemd-udevd[364]: /etc/udev/rules.d/30-usbtmc.rules:5 Unknown group 'usbtmc', ignoring.
Oct 11 18:56:00 ryzen systemd-udevd[364]: /etc/udev/rules.d/30-usbtmc.rules:8 Unknown group 'usbtmc', ignoring.
Oct 11 18:56:00 ryzen systemd-udevd[364]: /etc/udev/rules.d/30-usbtmc.rules:11 Unknown group 'usbtmc', ignoring.
Oct 11 18:56:00 ryzen systemd-udevd[364]: /etc/udev/rules.d/30-usbtmc.rules:14 Unknown group 'usbtmc', ignoring.
Oct 11 18:56:00 ryzen systemd-udevd[364]: /etc/udev/rules.d/30-usbtmc.rules:15 Unknown group 'usbtmc', ignoring.
Oct 11 18:56:00 ryzen kernel: hub 1-1:1.0: USB hub found
Oct 11 18:56:00 ryzen kernel: hub 1-1:1.0: 4 ports detected
Oct 11 18:56:00 ryzen systemd-udevd[364]: /usr/lib/udev/rules.d/51-footcontroller.rules:10 Invalid value for OPTIONS key, ignoring: 'last_rule'
Oct 11 18:56:00 ryzen kernel: usb 1-1.1: new low-speed USB device number 11 using xhci_hcd
Oct 11 18:56:01 ryzen kernel: usb 1-1.1: New USB device found, idVendor=09eb, idProduct=0131, bcdDevice= 1.01
Oct 11 18:56:01 ryzen kernel: usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Oct 11 18:56:01 ryzen kernel: usb 1-1.1: Product: USB
Oct 11 18:56:01 ryzen kernel: usb 1-1.1: Manufacturer: Rextron
Oct 11 18:56:01 ryzen kernel: input: Rextron USB as /devices/pci0000:00/0000:00:01.2/0000:02:00.0/usb1/1-1/1-1.1/1-1.1:1.0/0003:09EB:0131.000C/input/input26
Oct 11 18:56:01 ryzen kernel: hid-generic 0003:09EB:0131.000C: input,hidraw11: USB HID v1.10 Keyboard [Rextron USB] on usb-0000:02:00.0-1.1/input0
Oct 11 18:56:01 ryzen kernel: input: Rextron USB Mouse as /devices/pci0000:00/0000:00:01.2/0000:02:00.0/usb1/1-1/1-1.1/1-1.1:1.1/0003:09EB:0131.000D/input/input27
Oct 11 18:56:01 ryzen kernel: input: Rextron USB Consumer Control as /devices/pci0000:00/0000:00:01.2/0000:02:00.0/usb1/1-1/1-1.1/1-1.1:1.1/0003:09EB:0131.000D/input/input28
Oct 11 18:56:01 ryzen kernel: input: Rextron USB System Control as /devices/pci0000:00/0000:00:01.2/0000:02:00.0/usb1/1-1/1-1.1/1-1.1:1.1/0003:09EB:0131.000D/input/input29
Oct 11 18:56:01 ryzen kernel: hid-generic 0003:09EB:0131.000D: input,hidraw12: USB HID v1.00 Mouse [Rextron USB] on usb-0000:02:00.0-1.1/input1
Oct 11 18:56:01 ryzen mtp-probe[13962]: checking bus 1, device 11: "/sys/devices/pci0000:00/0000:00:01.2/0000:02:00.0/usb1/1-1/1-1.1"
Oct 11 18:56:01 ryzen mtp-probe[13962]: bus: 1, device: 11 was not an MTP device
Oct 11 18:56:01 ryzen kernel: usb 1-1.4: new low-speed USB device number 12 using xhci_hcd
Oct 11 18:56:01 ryzen systemd-logind[830]: Watching system buttons on /dev/input/event27 (Rextron USB System Control)
Oct 11 18:56:01 ryzen systemd-logind[830]: Watching system buttons on /dev/input/event26 (Rextron USB Consumer Control)
Oct 11 18:56:01 ryzen systemd-logind[830]: Watching system buttons on /dev/input/event24 (Rextron USB)
Oct 11 18:56:01 ryzen mtp-probe[14011]: checking bus 1, device 11: "/sys/devices/pci0000:00/0000:00:01.2/0000:02:00.0/usb1/1-1/1-1.1"
Oct 11 18:56:01 ryzen mtp-probe[14011]: bus: 1, device: 11 was not an MTP device
Oct 11 18:56:01 ryzen kernel: usb 1-1.4: New USB device found, idVendor=046d, idProduct=c016, bcdDevice= 3.40
Oct 11 18:56:01 ryzen kernel: usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Oct 11 18:56:01 ryzen kernel: usb 1-1.4: Product: Optical USB Mouse
Oct 11 18:56:01 ryzen kernel: usb 1-1.4: Manufacturer: Logitech
Oct 11 18:56:01 ryzen kernel: input: Logitech Optical USB Mouse as /devices/pci0000:00/0000:00:01.2/0000:02:00.0/usb1/1-1/1-1.4/1-1.4:1.0/0003:046D:C016.000E/input/input30
Oct 11 18:56:01 ryzen kernel: hid-generic 0003:046D:C016.000E: input,hidraw13: USB HID v1.10 Mouse [Logitech Optical USB Mouse] on usb-0000:02:00.0-1.4/input0
Oct 11 18:56:01 ryzen mtp-probe[14033]: checking bus 1, device 12: "/sys/devices/pci0000:00/0000:00:01.2/0000:02:00.0/usb1/1-1/1-1.4"
Oct 11 18:56:01 ryzen mtp-probe[14033]: bus: 1, device: 12 was not an MTP device
Oct 11 18:56:01 ryzen mtp-probe[14061]: checking bus 1, device 12: "/sys/devices/pci0000:00/0000:00:01.2/0000:02:00.0/usb1/1-1/1-1.4"
Oct 11 18:56:01 ryzen mtp-probe[14061]: bus: 1, device: 12 was not an MTP device
Oct 11 19:05:04 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:05:04 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:05:25 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:05:25 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:05:30 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:05:30 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:05:56 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:05:56 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:05:58 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:05:58 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:06:06 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:06:06 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:06:09 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:06:09 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:06:14 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:06:14 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:06:19 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:06:19 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:06:30 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:06:30 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:07:06 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:07:06 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:07:07 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:07:07 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:07:17 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:07:17 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:07:19 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:07:19 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:07:55 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:07:55 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:08:28 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:08:28 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:08:32 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:08:32 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:08:33 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:08:33 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:08:34 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:08:34 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:08:34 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:08:34 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:08:34 ryzen rtkit-daemon[1365]: Successfully made thread 15458 of process 15160 owned by '1001' RT at priority 10.
Oct 11 19:08:34 ryzen rtkit-daemon[1365]: Supervising 4 threads of 4 processes of 1 users.
Oct 11 19:13:56 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:13:56 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:14:09 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:14:09 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:14:17 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:14:17 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:14:21 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:14:21 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:14:24 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:14:24 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:14:24 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:14:24 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:14:35 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:14:35 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:14:42 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:14:42 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:15:28 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:15:28 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:15:51 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:15:51 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:15:58 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:15:58 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:15:59 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:15:59 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:16:15 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:16:15 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:16:18 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:16:18 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:16:23 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:16:23 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:16:40 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:16:40 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:23:20 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:23:20 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:23:30 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:23:30 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:25:02 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:25:02 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:25:05 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:25:05 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:25:42 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:25:42 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:25:44 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:25:44 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:25:55 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:25:55 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:26:08 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:26:08 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:26:37 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:26:37 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:26:37 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:26:37 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:26:40 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:26:40 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:26:40 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:26:40 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:27:00 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:27:00 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:27:09 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:27:09 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:27:09 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:27:09 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:34:46 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:34:46 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:34:49 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:34:49 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:34:49 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:34:49 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:34:49 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:34:49 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:34:49 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:34:49 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:34:49 ryzen rtkit-daemon[1365]: Successfully made thread 19004 of process 18277 owned by '1001' RT at priority 10.
Oct 11 19:34:49 ryzen rtkit-daemon[1365]: Supervising 4 threads of 4 processes of 1 users.
Oct 11 19:34:58 ryzen rtkit-daemon[1365]: Supervising 4 threads of 4 processes of 1 users.
Oct 11 19:34:58 ryzen rtkit-daemon[1365]: Supervising 4 threads of 4 processes of 1 users.
Oct 11 19:34:58 ryzen rtkit-daemon[1365]: Supervising 4 threads of 4 processes of 1 users.
Oct 11 19:34:58 ryzen rtkit-daemon[1365]: Supervising 4 threads of 4 processes of 1 users.
Oct 11 19:38:06 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:38:06 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:38:30 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:38:30 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:38:30 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:38:30 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:38:30 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:38:30 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:38:30 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:38:30 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:38:30 ryzen rtkit-daemon[1365]: Successfully made thread 19646 of process 19097 owned by '1001' RT at priority 10.
Oct 11 19:38:30 ryzen rtkit-daemon[1365]: Supervising 4 threads of 4 processes of 1 users.
Oct 11 19:39:25 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:39:25 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:39:25 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:39:25 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:39:46 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:39:46 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:52:58 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:52:58 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:52:58 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:52:58 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:52:58 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:52:58 ryzen rtkit-daemon[1365]: Supervising 3 threads of 3 processes of 1 users.
Oct 11 19:52:58 ryzen rtkit-daemon[1365]: Successfully made thread 20439 of process 19768 owned by '1001' RT at priority 10.
Oct 11 19:52:58 ryzen rtkit-daemon[1365]: Supervising 4 threads of 4 processes of 1 users.
Oct 11 19:55:47 ryzen dbus-daemon[824]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.297' (uid=1001 pid=20643 comm="/opt/visual-studio-code/code --unity-launch /home/")
Oct 11 19:55:47 ryzen systemd[1]: Bluetooth service was skipped because of an unmet condition check (ConditionPathIsDirectory=/sys/class/bluetooth).
Oct 11 19:56:12 ryzen dbus-daemon[824]: [system] Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms)
Oct 11 20:09:02 ryzen systemd-logind[830]: The system will suspend now!
Oct 11 20:09:02 ryzen NetworkManager[927]: <info> [1697080142.3573] manager: sleep: sleep requested (sleeping: no enabled: yes)
Oct 11 20:09:02 ryzen dbus-daemon[824]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.4' (uid=0 pid=927 comm="/usr/bin/NetworkManager --no-daemon")
Oct 11 20:09:02 ryzen NetworkManager[927]: <info> [1697080142.3574] manager: NetworkManager state is now ASLEEP
Oct 11 20:09:02 ryzen NetworkManager[927]: <info> [1697080142.3575] device (enp4s0): state change: activated -> deactivating (reason 'sleeping', sys-iface-state: 'managed')
Oct 11 20:09:02 ryzen systemd[1]: Starting Network Manager Script Dispatcher Service...
Oct 11 20:09:02 ryzen dbus-daemon[824]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Oct 11 20:09:02 ryzen systemd[1]: Started Network Manager Script Dispatcher Service.
Oct 11 20:09:02 ryzen NetworkManager[927]: <info> [1697080142.4131] device (enp4s0): state change: deactivating -> disconnected (reason 'sleeping', sys-iface-state: 'managed')
Oct 11 20:09:02 ryzen avahi-daemon[823]: Withdrawing address record for fde3:5408:101c::566 on enp4s0.
Oct 11 20:09:02 ryzen avahi-daemon[823]: Withdrawing address record for fde3:5408:101c:0:7441:9d56:d3c1:1a95 on enp4s0.
Oct 11 20:09:02 ryzen NetworkManager[927]: <info> [1697080142.4141] dhcp4 (enp4s0): canceled DHCP transaction
Oct 11 20:09:02 ryzen NetworkManager[927]: <info> [1697080142.4141] dhcp4 (enp4s0): activation: beginning transaction (timeout in 45 seconds)
Oct 11 20:09:02 ryzen avahi-daemon[823]: Leaving mDNS multicast group on interface enp4s0.IPv6 with address fde3:5408:101c:0:7441:9d56:d3c1:1a95.
Oct 11 20:09:02 ryzen NetworkManager[927]: <info> [1697080142.4141] dhcp4 (enp4s0): state changed no lease
Oct 11 20:09:02 ryzen avahi-daemon[823]: Joining mDNS multicast group on interface enp4s0.IPv6 with address fe80::1b36:1dd4:a5cf:3b8f.
Oct 11 20:09:02 ryzen NetworkManager[927]: <info> [1697080142.4142] dhcp6 (enp4s0): canceled DHCP transaction
Oct 11 20:09:02 ryzen avahi-daemon[823]: Registering new address record for fe80::1b36:1dd4:a5cf:3b8f on enp4s0.*.
Oct 11 20:09:02 ryzen NetworkManager[927]: <info> [1697080142.4142] dhcp6 (enp4s0): activation: beginning transaction (timeout in 45 seconds)
Oct 11 20:09:02 ryzen avahi-daemon[823]: Withdrawing address record for fe80::1b36:1dd4:a5cf:3b8f on enp4s0.
Oct 11 20:09:02 ryzen NetworkManager[927]: <info> [1697080142.4143] dhcp6 (enp4s0): state changed no lease
Oct 11 20:09:02 ryzen avahi-daemon[823]: Leaving mDNS multicast group on interface enp4s0.IPv6 with address fe80::1b36:1dd4:a5cf:3b8f.
Oct 11 20:09:02 ryzen avahi-daemon[823]: Interface enp4s0.IPv6 no longer relevant for mDNS.
Oct 11 20:09:02 ryzen dnsmasq[1089]: no servers found in /etc/resolv.conf, will retry
Oct 11 20:09:02 ryzen dnsmasq[1056]: no servers found in /etc/resolv.conf, will retry
Oct 11 20:09:02 ryzen avahi-daemon[823]: Withdrawing address record for 192.168.0.91 on enp4s0.
Oct 11 20:09:02 ryzen avahi-daemon[823]: Leaving mDNS multicast group on interface enp4s0.IPv4 with address 192.168.0.91.
Oct 11 20:09:02 ryzen avahi-daemon[823]: Interface enp4s0.IPv4 no longer relevant for mDNS.
Oct 11 20:09:02 ryzen NetworkManager[927]: <info> [1697080142.4631] device (enp4s0): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Oct 11 20:09:02 ryzen kernel: r8169 0000:04:00.0 enp4s0: Link is Down
Oct 11 20:09:02 ryzen systemd[1]: Reached target Sleep.
Oct 11 20:09:02 ryzen systemd[1]: Starting System Suspend...
Oct 11 20:09:02 ryzen systemd-sleep[21508]: Entering sleep state 'suspend'...
Oct 11 20:09:02 ryzen kernel: PM: suspend entry (deep)
Oct 11 20:09:02 ryzen kernel: Filesystems sync: 0.062 seconds
Oct 11 20:26:18 ryzen kernel: Freezing user space processes
Oct 11 20:26:18 ryzen kernel: Freezing user space processes completed (elapsed 0.003 seconds)
Oct 11 20:26:18 ryzen kernel: OOM killer disabled.
Oct 11 20:26:18 ryzen kernel: Freezing remaining freezable tasks
Oct 11 20:26:18 ryzen kernel: Freezing remaining freezable tasks completed (elapsed 0.000 seconds)
Oct 11 20:26:18 ryzen kernel: input input30: PM: calling input_dev_suspend+0x0/0x70 @ 21508, parent: 0003:046D:C016.000E
Oct 11 20:26:18 ryzen kernel: input input30: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: input input29: PM: calling input_dev_suspend+0x0/0x70 @ 21508, parent: 0003:09EB:0131.000D
Oct 11 20:26:18 ryzen kernel: usb 1-1.4: PM: calling usb_dev_suspend+0x0/0x20 @ 21514, parent: 1-1
Oct 11 20:26:18 ryzen kernel: input input29: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: input input28: PM: calling input_dev_suspend+0x0/0x70 @ 21508, parent: 0003:09EB:0131.000D
Oct 11 20:26:18 ryzen kernel: input input28: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: input input27: PM: calling input_dev_suspend+0x0/0x70 @ 21508, parent: 0003:09EB:0131.000D
Oct 11 20:26:18 ryzen kernel: input input27: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: leds input26::kana: PM: calling led_suspend+0x0/0x50 @ 21508, parent: input26
Oct 11 20:26:18 ryzen kernel: leds input26::kana: PM: led_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: leds input26::compose: PM: calling led_suspend+0x0/0x50 @ 21508, parent: input26
Oct 11 20:26:18 ryzen kernel: leds input26::compose: PM: led_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: leds input26::scrolllock: PM: calling led_suspend+0x0/0x50 @ 21508, parent: input26
Oct 11 20:26:18 ryzen kernel: leds input26::scrolllock: PM: led_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: leds input26::capslock: PM: calling led_suspend+0x0/0x50 @ 21508, parent: input26
Oct 11 20:26:18 ryzen kernel: leds input26::capslock: PM: led_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: leds input26::numlock: PM: calling led_suspend+0x0/0x50 @ 21508, parent: input26
Oct 11 20:26:18 ryzen kernel: leds input26::numlock: PM: led_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: input input26: PM: calling input_dev_suspend+0x0/0x70 @ 21508, parent: 0003:09EB:0131.000C
Oct 11 20:26:18 ryzen kernel: input input26: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: usb 1-1.1: PM: calling usb_dev_suspend+0x0/0x20 @ 21513, parent: 1-1
Oct 11 20:26:18 ryzen kernel: intel_rapl_msr intel_rapl_msr.0: PM: calling platform_pm_suspend+0x0/0x50 @ 21508, parent: platform
Oct 11 20:26:18 ryzen kernel: intel_rapl_msr intel_rapl_msr.0: PM: platform_pm_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: Generic FE-GE Realtek PHY r8169-0-400:00: PM: calling mdio_bus_phy_suspend+0x0/0x120 [libphy] @ 21508, parent: r8169-0-400
Oct 11 20:26:18 ryzen kernel: Generic FE-GE Realtek PHY r8169-0-400:00: PM: mdio_bus_phy_suspend+0x0/0x120 [libphy] returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: sound pcmC3D0c: PM: calling do_pcm_suspend+0x0/0x30 [snd_pcm] @ 21508, parent: card3
Oct 11 20:26:18 ryzen kernel: sound pcmC3D0c: PM: do_pcm_suspend+0x0/0x30 [snd_pcm] returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: sound pcmC3D0p: PM: calling do_pcm_suspend+0x0/0x30 [snd_pcm] @ 21508, parent: card3
Oct 11 20:26:18 ryzen kernel: sound pcmC3D0p: PM: do_pcm_suspend+0x0/0x30 [snd_pcm] returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: sound pcmC0D1p: PM: calling do_pcm_suspend+0x0/0x30 [snd_pcm] @ 21508, parent: card0
Oct 11 20:26:18 ryzen kernel: sound pcmC0D1p: PM: do_pcm_suspend+0x0/0x30 [snd_pcm] returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: sound pcmC0D0c: PM: calling do_pcm_suspend+0x0/0x30 [snd_pcm] @ 21508, parent: card0
Oct 11 20:26:18 ryzen kernel: sound pcmC0D0c: PM: do_pcm_suspend+0x0/0x30 [snd_pcm] returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: sound pcmC0D0p: PM: calling do_pcm_suspend+0x0/0x30 [snd_pcm] @ 21508, parent: card0
Oct 11 20:26:18 ryzen kernel: sound pcmC0D0p: PM: do_pcm_suspend+0x0/0x30 [snd_pcm] returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: input input25: PM: calling input_dev_suspend+0x0/0x70 @ 21508, parent: card2
Oct 11 20:26:18 ryzen kernel: input input25: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: input input24: PM: calling input_dev_suspend+0x0/0x70 @ 21508, parent: card2
Oct 11 20:26:18 ryzen kernel: input input24: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: input input23: PM: calling input_dev_suspend+0x0/0x70 @ 21508, parent: card2
Oct 11 20:26:18 ryzen kernel: input input23: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: input input22: PM: calling input_dev_suspend+0x0/0x70 @ 21508, parent: card2
Oct 11 20:26:18 ryzen kernel: input input22: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: input input21: PM: calling input_dev_suspend+0x0/0x70 @ 21508, parent: card2
Oct 11 20:26:18 ryzen kernel: input input21: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: sound pcmC2D2c: PM: calling do_pcm_suspend+0x0/0x30 [snd_pcm] @ 21508, parent: card2
Oct 11 20:26:18 ryzen kernel: sound pcmC2D2c: PM: do_pcm_suspend+0x0/0x30 [snd_pcm] returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: sound pcmC2D0c: PM: calling do_pcm_suspend+0x0/0x30 [snd_pcm] @ 21508, parent: card2
Oct 11 20:26:18 ryzen kernel: sound pcmC2D0c: PM: do_pcm_suspend+0x0/0x30 [snd_pcm] returned 0 after 28 usecs
Oct 11 20:26:18 ryzen kernel: sound pcmC2D0p: PM: calling do_pcm_suspend+0x0/0x30 [snd_pcm] @ 21508, parent: card2
Oct 11 20:26:18 ryzen kernel: sound pcmC2D0p: PM: do_pcm_suspend+0x0/0x30 [snd_pcm] returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: input input20: PM: calling input_dev_suspend+0x0/0x70 @ 21508, parent: card1
Oct 11 20:26:18 ryzen kernel: input input20: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: input input19: PM: calling input_dev_suspend+0x0/0x70 @ 21508, parent: card1
Oct 11 20:26:18 ryzen kernel: input input19: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: input input18: PM: calling input_dev_suspend+0x0/0x70 @ 21508, parent: card1
Oct 11 20:26:18 ryzen kernel: input input18: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: input input17: PM: calling input_dev_suspend+0x0/0x70 @ 21508, parent: card1
Oct 11 20:26:18 ryzen kernel: input input17: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: input input16: PM: calling input_dev_suspend+0x0/0x70 @ 21508, parent: card1
Oct 11 20:26:18 ryzen kernel: snd_hda_codec_realtek hdaudioC2D0: PM: calling hda_codec_pm_suspend+0x0/0x20 [snd_hda_codec] @ 8209, parent: 0000:07:00.4
Oct 11 20:26:18 ryzen kernel: input input16: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: input input15: PM: calling input_dev_suspend+0x0/0x70 @ 21508, parent: card1
Oct 11 20:26:18 ryzen kernel: input input15: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: sound pcmC1D11p: PM: calling do_pcm_suspend+0x0/0x30 [snd_pcm] @ 21508, parent: card1
Oct 11 20:26:18 ryzen kernel: sound pcmC1D11p: PM: do_pcm_suspend+0x0/0x30 [snd_pcm] returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: sound pcmC1D10p: PM: calling do_pcm_suspend+0x0/0x30 [snd_pcm] @ 21508, parent: card1
Oct 11 20:26:18 ryzen kernel: sound pcmC1D10p: PM: do_pcm_suspend+0x0/0x30 [snd_pcm] returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: sound pcmC1D9p: PM: calling do_pcm_suspend+0x0/0x30 [snd_pcm] @ 21508, parent: card1
Oct 11 20:26:18 ryzen kernel: sound pcmC1D9p: PM: do_pcm_suspend+0x0/0x30 [snd_pcm] returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: sound pcmC1D8p: PM: calling do_pcm_suspend+0x0/0x30 [snd_pcm] @ 21508, parent: card1
Oct 11 20:26:18 ryzen kernel: sound pcmC1D8p: PM: do_pcm_suspend+0x0/0x30 [snd_pcm] returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: sound pcmC1D7p: PM: calling do_pcm_suspend+0x0/0x30 [snd_pcm] @ 21508, parent: card1
Oct 11 20:26:18 ryzen kernel: sound pcmC1D7p: PM: do_pcm_suspend+0x0/0x30 [snd_pcm] returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: sound pcmC1D3p: PM: calling do_pcm_suspend+0x0/0x30 [snd_pcm] @ 21508, parent: card1
Oct 11 20:26:18 ryzen kernel: sound pcmC1D3p: PM: do_pcm_suspend+0x0/0x30 [snd_pcm] returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: input input14: PM: calling input_dev_suspend+0x0/0x70 @ 21508, parent: pcspkr
Oct 11 20:26:18 ryzen kernel: input input14: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: sp5100-tco sp5100-tco: PM: calling platform_pm_suspend+0x0/0x50 @ 21508, parent: platform
Oct 11 20:26:18 ryzen kernel: sp5100-tco sp5100-tco: PM: platform_pm_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: input input11: PM: calling input_dev_suspend+0x0/0x70 @ 21508, parent: 0003:046D:C092.000A
Oct 11 20:26:18 ryzen kernel: input input11: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: usb 1-2.4: PM: calling usb_dev_suspend+0x0/0x20 @ 21515, parent: 1-2
Oct 11 20:26:18 ryzen kernel: input input10: PM: calling input_dev_suspend+0x0/0x70 @ 21508, parent: 0003:046D:C092.0009
Oct 11 20:26:18 ryzen kernel: input input10: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: usb 1-1.4: PM: usb_dev_suspend+0x0/0x20 returned 0 after 493 usecs
Oct 11 20:26:18 ryzen kernel: usb 1-2.4: PM: usb_dev_suspend+0x0/0x20 returned 0 after 10 usecs
Oct 11 20:26:18 ryzen kernel: input input9: PM: calling input_dev_suspend+0x0/0x70 @ 21508, parent: 0003:29EA:0102.0007
Oct 11 20:26:18 ryzen kernel: input input9: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: input input8: PM: calling input_dev_suspend+0x0/0x70 @ 21508, parent: 0003:29EA:0102.0007
Oct 11 20:26:18 ryzen kernel: usb 1-10: PM: calling usb_dev_suspend+0x0/0x20 @ 21191, parent: usb1
Oct 11 20:26:18 ryzen kernel: input input8: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: usb 1-2.3: PM: calling usb_dev_suspend+0x0/0x20 @ 19708, parent: 1-2
Oct 11 20:26:18 ryzen kernel: leds input7::kana: PM: calling led_suspend+0x0/0x50 @ 21508, parent: input7
Oct 11 20:26:18 ryzen kernel: usb 1-10: PM: usb_dev_suspend+0x0/0x20 returned 0 after 3 usecs
Oct 11 20:26:18 ryzen kernel: leds input7::kana: PM: led_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: leds input7::compose: PM: calling led_suspend+0x0/0x50 @ 21508, parent: input7
Oct 11 20:26:18 ryzen kernel: leds input7::compose: PM: led_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: leds input7::scrolllock: PM: calling led_suspend+0x0/0x50 @ 21508, parent: input7
Oct 11 20:26:18 ryzen kernel: leds input7::scrolllock: PM: led_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: leds input7::capslock: PM: calling led_suspend+0x0/0x50 @ 21508, parent: input7
Oct 11 20:26:18 ryzen kernel: leds input7::capslock: PM: led_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: leds input7::numlock: PM: calling led_suspend+0x0/0x50 @ 21508, parent: input7
Oct 11 20:26:18 ryzen kernel: leds input7::numlock: PM: led_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: input input7: PM: calling input_dev_suspend+0x0/0x70 @ 21508, parent: 0003:29EA:0102.0006
Oct 11 20:26:18 ryzen kernel: input input7: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: input input6: PM: calling input_dev_suspend+0x0/0x70 @ 21508, parent: 0003:29EA:0102.0005
Oct 11 20:26:18 ryzen kernel: input input6: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: usb 1-2.2: PM: calling usb_dev_suspend+0x0/0x20 @ 21515, parent: 1-2
Oct 11 20:26:18 ryzen kernel: usb 1-7: PM: calling usb_dev_suspend+0x0/0x20 @ 21191, parent: usb1
Oct 11 20:26:18 ryzen kernel: input input5: PM: calling input_dev_suspend+0x0/0x70 @ 21508, parent: 0003:0ECB:2057.0003
Oct 11 20:26:18 ryzen kernel: input input5: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: usb 1-7: PM: usb_dev_suspend+0x0/0x20 returned 0 after 2 usecs
Oct 11 20:26:18 ryzen kernel: input input4: PM: calling input_dev_suspend+0x0/0x70 @ 21508, parent: 0003:05F3:00FF.0002
Oct 11 20:26:18 ryzen kernel: input input4: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: sd 6:0:0:0: PM: calling scsi_bus_suspend+0x0/0xc0 @ 21191, parent: target6:0:0
Oct 11 20:26:18 ryzen kernel: input input3: PM: calling input_dev_suspend+0x0/0x70 @ 21508, parent: 0003:1852:7022.0001
Oct 11 20:26:18 ryzen kernel: input input3: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: leds input2::scrolllock: PM: calling led_suspend+0x0/0x50 @ 21508, parent: input2
Oct 11 20:26:18 ryzen kernel: leds input2::scrolllock: PM: led_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: leds input2::capslock: PM: calling led_suspend+0x0/0x50 @ 21508, parent: input2
Oct 11 20:26:18 ryzen kernel: leds input2::capslock: PM: led_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: leds input2::numlock: PM: calling led_suspend+0x0/0x50 @ 21508, parent: input2
Oct 11 20:26:18 ryzen kernel: leds input2::numlock: PM: led_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: input input2: PM: calling input_dev_suspend+0x0/0x70 @ 21508, parent: serio0
Oct 11 20:26:18 ryzen kernel: input input2: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: atkbd serio0: PM: calling serio_suspend+0x0/0x50 [serio] @ 21508, parent: i8042
Oct 11 20:26:18 ryzen kernel: usb 1-2.1: PM: calling usb_dev_suspend+0x0/0x20 @ 21514, parent: 1-2
Oct 11 20:26:18 ryzen kernel: usb 1-5: PM: calling usb_dev_suspend+0x0/0x20 @ 20209, parent: usb1
Oct 11 20:26:18 ryzen kernel: usb 3-2: PM: calling usb_dev_suspend+0x0/0x20 @ 21542, parent: usb3
Oct 11 20:26:18 ryzen kernel: usb usb4: PM: calling usb_dev_suspend+0x0/0x20 @ 21543, parent: 0000:07:00.3
Oct 11 20:26:18 ryzen kernel: usb 3-2: PM: usb_dev_suspend+0x0/0x20 returned 0 after 57 usecs
Oct 11 20:26:18 ryzen kernel: usb usb3: PM: calling usb_dev_suspend+0x0/0x20 @ 21542, parent: 0000:07:00.3
Oct 11 20:26:18 ryzen kernel: usb 1-2.3: PM: usb_dev_suspend+0x0/0x20 returned 0 after 1114 usecs
Oct 11 20:26:18 ryzen kernel: usb 1-5: PM: usb_dev_suspend+0x0/0x20 returned 0 after 1521 usecs
Oct 11 20:26:18 ryzen kernel: usb 1-2.1: PM: usb_dev_suspend+0x0/0x20 returned 0 after 2183 usecs
Oct 11 20:26:18 ryzen kernel: atkbd serio0: PM: serio_suspend+0x0/0x50 [serio] returned 0 after 2857 usecs
Oct 11 20:26:18 ryzen kernel: i8042 i8042: PM: calling platform_pm_suspend+0x0/0x50 @ 21508, parent: platform
Oct 11 20:26:18 ryzen kernel: i8042 i8042: PM: platform_pm_suspend+0x0/0x50 returned 0 after 75 usecs
Oct 11 20:26:18 ryzen kernel: platform microcode: PM: calling platform_pm_suspend+0x0/0x50 @ 21508, parent: platform
Oct 11 20:26:18 ryzen kernel: sr 1:0:0:0: PM: calling scsi_bus_suspend+0x0/0xc0 @ 21514, parent: target1:0:0
Oct 11 20:26:18 ryzen kernel: platform microcode: PM: platform_pm_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: alarmtimer alarmtimer.0.auto: PM: calling platform_pm_suspend+0x0/0x50 @ 21508, parent: rtc0
Oct 11 20:26:18 ryzen kernel: alarmtimer alarmtimer.0.auto: PM: platform_pm_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: rtc rtc0: PM: calling rtc_suspend+0x0/0x1f0 @ 21508, parent: 00:02
Oct 11 20:26:18 ryzen kernel: rtc rtc0: PM: rtc_suspend+0x0/0x1f0 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: sd 0:0:0:0: PM: calling scsi_bus_suspend+0x0/0xc0 @ 21548, parent: target0:0:0
Oct 11 20:26:18 ryzen kernel: port serial8250:0.31: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 21508, parent: serial8250:0
Oct 11 20:26:18 ryzen kernel: port serial8250:0.31: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: port serial8250:0.30: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 21508, parent: serial8250:0
Oct 11 20:26:18 ryzen kernel: port serial8250:0.30: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: port serial8250:0.29: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 21508, parent: serial8250:0
Oct 11 20:26:18 ryzen kernel: scsi host5: PM: calling scsi_bus_suspend+0x0/0xc0 @ 21547, parent: ata6
Oct 11 20:26:18 ryzen kernel: port serial8250:0.29: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: scsi host5: PM: scsi_bus_suspend+0x0/0xc0 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: port serial8250:0.28: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 21508, parent: serial8250:0
Oct 11 20:26:18 ryzen kernel: scsi host4: PM: calling scsi_bus_suspend+0x0/0xc0 @ 21547, parent: ata5
Oct 11 20:26:18 ryzen kernel: port serial8250:0.28: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: scsi host4: PM: scsi_bus_suspend+0x0/0xc0 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: port serial8250:0.27: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 21508, parent: serial8250:0
Oct 11 20:26:18 ryzen kernel: scsi host3: PM: calling scsi_bus_suspend+0x0/0xc0 @ 21547, parent: ata4
Oct 11 20:26:18 ryzen kernel: port serial8250:0.27: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: scsi host3: PM: scsi_bus_suspend+0x0/0xc0 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: port serial8250:0.26: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 21508, parent: serial8250:0
Oct 11 20:26:18 ryzen kernel: scsi host2: PM: calling scsi_bus_suspend+0x0/0xc0 @ 21547, parent: ata3
Oct 11 20:26:18 ryzen kernel: port serial8250:0.26: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: scsi host2: PM: scsi_bus_suspend+0x0/0xc0 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: port serial8250:0.25: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 21508, parent: serial8250:0
Oct 11 20:26:18 ryzen kernel: port serial8250:0.25: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: port serial8250:0.24: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 21508, parent: serial8250:0
Oct 11 20:26:18 ryzen kernel: port serial8250:0.24: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: port serial8250:0.23: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 21508, parent: serial8250:0
Oct 11 20:26:18 ryzen kernel: port serial8250:0.23: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: port serial8250:0.22: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 21508, parent: serial8250:0
Oct 11 20:26:18 ryzen kernel: port serial8250:0.22: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: port serial8250:0.21: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 21508, parent: serial8250:0
Oct 11 20:26:18 ryzen kernel: port serial8250:0.21: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: port serial8250:0.20: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 21508, parent: serial8250:0
Oct 11 20:26:18 ryzen kernel: ata6: PM: calling ata_port_pm_suspend+0x0/0x50 @ 21550, parent: 0000:02:00.1
Oct 11 20:26:18 ryzen kernel: port serial8250:0.20: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: port serial8250:0.19: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 21508, parent: serial8250:0
Oct 11 20:26:18 ryzen kernel: port serial8250:0.19: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: port serial8250:0.18: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 21508, parent: serial8250:0
Oct 11 20:26:18 ryzen kernel: port serial8250:0.18: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: port serial8250:0.17: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 21508, parent: serial8250:0
Oct 11 20:26:18 ryzen kernel: port serial8250:0.17: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: port serial8250:0.16: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 21508, parent: serial8250:0
Oct 11 20:26:18 ryzen kernel: ata5: PM: calling ata_port_pm_suspend+0x0/0x50 @ 21551, parent: 0000:02:00.1
Oct 11 20:26:18 ryzen kernel: ata6: PM: ata_port_pm_suspend+0x0/0x50 returned 0 after 25 usecs
Oct 11 20:26:18 ryzen kernel: port serial8250:0.16: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: port serial8250:0.15: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 21508, parent: serial8250:0
Oct 11 20:26:18 ryzen kernel: ata4: PM: calling ata_port_pm_suspend+0x0/0x50 @ 21550, parent: 0000:02:00.1
Oct 11 20:26:18 ryzen kernel: port serial8250:0.15: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: port serial8250:0.14: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 21508, parent: serial8250:0
Oct 11 20:26:18 ryzen kernel: port serial8250:0.14: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: port serial8250:0.13: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 21508, parent: serial8250:0
Oct 11 20:26:18 ryzen kernel: port serial8250:0.13: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: ata3: PM: calling ata_port_pm_suspend+0x0/0x50 @ 21552, parent: 0000:02:00.1
Oct 11 20:26:18 ryzen kernel: port serial8250:0.12: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 21508, parent: serial8250:0
Oct 11 20:26:18 ryzen kernel: ata5: PM: ata_port_pm_suspend+0x0/0x50 returned 0 after 24 usecs
Oct 11 20:26:18 ryzen kernel: port serial8250:0.12: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: port serial8250:0.11: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 21508, parent: serial8250:0
Oct 11 20:26:18 ryzen kernel: port serial8250:0.11: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: port serial8250:0.10: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 21508, parent: serial8250:0
Oct 11 20:26:18 ryzen kernel: ata4: PM: ata_port_pm_suspend+0x0/0x50 returned 0 after 34 usecs
Oct 11 20:26:18 ryzen kernel: port serial8250:0.10: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: port serial8250:0.9: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 21508, parent: serial8250:0
Oct 11 20:26:18 ryzen kernel: port serial8250:0.9: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: port serial8250:0.8: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 21508, parent: serial8250:0
Oct 11 20:26:18 ryzen kernel: port serial8250:0.8: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: ata3: PM: ata_port_pm_suspend+0x0/0x50 returned 0 after 30 usecs
Oct 11 20:26:18 ryzen kernel: port serial8250:0.7: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 21508, parent: serial8250:0
Oct 11 20:26:18 ryzen kernel: port serial8250:0.7: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: port serial8250:0.6: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 21508, parent: serial8250:0
Oct 11 20:26:18 ryzen kernel: port serial8250:0.6: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: port serial8250:0.5: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 21508, parent: serial8250:0
Oct 11 20:26:18 ryzen kernel: port serial8250:0.5: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: port serial8250:0.4: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 21508, parent: serial8250:0
Oct 11 20:26:18 ryzen kernel: port serial8250:0.4: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: port serial8250:0.3: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 21508, parent: serial8250:0
Oct 11 20:26:18 ryzen kernel: port serial8250:0.3: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: port serial8250:0.2: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 21508, parent: serial8250:0
Oct 11 20:26:18 ryzen kernel: port serial8250:0.2: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: port serial8250:0.1: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 21508, parent: serial8250:0
Oct 11 20:26:18 ryzen kernel: port serial8250:0.1: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: serial8250 serial8250: PM: calling platform_pm_suspend+0x0/0x50 @ 21508, parent: platform
Oct 11 20:26:18 ryzen kernel: serial8250 serial8250: PM: platform_pm_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: port 00:05:0.0: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 21508, parent: 00:05:0
Oct 11 20:26:18 ryzen kernel: port 00:05:0.0: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: input input1: PM: calling input_dev_suspend+0x0/0x70 @ 21508, parent: LNXPWRBN:00
Oct 11 20:26:18 ryzen kernel: input input1: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: input input0: PM: calling input_dev_suspend+0x0/0x70 @ 21508, parent: PNP0C0C:00
Oct 11 20:26:18 ryzen kernel: input input0: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: pcspkr pcspkr: PM: calling platform_pm_suspend+0x0/0x50 @ 21508, parent: platform
Oct 11 20:26:18 ryzen kernel: pcspkr pcspkr: PM: platform_pm_suspend+0x0/0x50 returned 0 after 4 usecs
Oct 11 20:26:18 ryzen kernel: snd_hda_intel 0000:05:00.1: PM: calling pci_pm_suspend+0x0/0x170 @ 21553, parent: 0000:00:03.1
Oct 11 20:26:18 ryzen kernel: system 00:06: PM: calling pnp_bus_suspend+0x0/0x20 @ 21508, parent: pnp0
Oct 11 20:26:18 ryzen kernel: system 00:06: PM: pnp_bus_suspend+0x0/0x20 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: serial 00:05: PM: calling pnp_bus_suspend+0x0/0x20 @ 21508, parent: pnp0
Oct 11 20:26:18 ryzen kernel: serial 00:05: PM: pnp_bus_suspend+0x0/0x20 returned 0 after 4 usecs
Oct 11 20:26:18 ryzen kernel: i8042 kbd 00:04: PM: calling pnp_bus_suspend+0x0/0x20 @ 21508, parent: pnp0
Oct 11 20:26:18 ryzen kernel: i8042 kbd 00:04: PM: pnp_bus_suspend+0x0/0x20 returned 0 after 52 usecs
Oct 11 20:26:18 ryzen kernel: system 00:03: PM: calling pnp_bus_suspend+0x0/0x20 @ 21508, parent: pnp0
Oct 11 20:26:18 ryzen kernel: system 00:03: PM: pnp_bus_suspend+0x0/0x20 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: rtc_cmos 00:02: PM: calling pnp_bus_suspend+0x0/0x20 @ 21508, parent: pnp0
Oct 11 20:26:18 ryzen kernel: rtc_cmos 00:02: PM: pnp_bus_suspend+0x0/0x20 returned 0 after 23 usecs
Oct 11 20:26:18 ryzen kernel: system 00:01: PM: calling pnp_bus_suspend+0x0/0x20 @ 21508, parent: pnp0
Oct 11 20:26:18 ryzen kernel: system 00:01: PM: pnp_bus_suspend+0x0/0x20 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: system 00:00: PM: calling pnp_bus_suspend+0x0/0x20 @ 21508, parent: pnp0
Oct 11 20:26:18 ryzen kernel: system 00:00: PM: pnp_bus_suspend+0x0/0x20 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: platform efivars.0: PM: calling platform_pm_suspend+0x0/0x50 @ 21508, parent: platform
Oct 11 20:26:18 ryzen kernel: platform efivars.0: PM: platform_pm_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: platform rtc-efi.0: PM: calling platform_pm_suspend+0x0/0x50 @ 21508, parent: platform
Oct 11 20:26:18 ryzen kernel: platform rtc-efi.0: PM: platform_pm_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: button LNXPWRBN:00: PM: calling acpi_button_suspend+0x0/0x20 @ 21508, parent: LNXSYSTM:00
Oct 11 20:26:18 ryzen kernel: button LNXPWRBN:00: PM: acpi_button_suspend+0x0/0x20 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: acpi-wmi PNP0C14:01: PM: calling acpi_subsys_suspend+0x0/0x60 @ 21508, parent: platform
Oct 11 20:26:18 ryzen kernel: acpi-wmi PNP0C14:01: PM: acpi_subsys_suspend+0x0/0x60 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: acpi-wmi PNP0C14:00: PM: calling acpi_subsys_suspend+0x0/0x60 @ 21508, parent: platform
Oct 11 20:26:18 ryzen kernel: acpi-wmi PNP0C14:00: PM: acpi_subsys_suspend+0x0/0x60 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: platform PNP0103:00: PM: calling platform_pm_suspend+0x0/0x50 @ 21508, parent: platform
Oct 11 20:26:18 ryzen kernel: platform PNP0103:00: PM: platform_pm_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: pt-gpio AMDIF030:00: PM: calling acpi_subsys_suspend+0x0/0x60 @ 21508, parent: platform
Oct 11 20:26:18 ryzen kernel: pt-gpio AMDIF030:00: PM: acpi_subsys_suspend+0x0/0x60 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: acpi-cpufreq acpi-cpufreq: PM: calling platform_pm_suspend+0x0/0x50 @ 21508, parent: platform
Oct 11 20:26:18 ryzen kernel: acpi-cpufreq acpi-cpufreq: PM: platform_pm_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: platform MSFT0101:00: PM: calling platform_pm_suspend+0x0/0x50 @ 21508, parent: platform
Oct 11 20:26:18 ryzen kernel: platform MSFT0101:00: PM: platform_pm_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: amd_gpio AMDI0030:00: PM: calling acpi_subsys_suspend+0x0/0x60 @ 21508, parent: platform
Oct 11 20:26:18 ryzen kernel: amd_gpio AMDI0030:00: PM: acpi_subsys_suspend+0x0/0x60 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: platform PNP0C0C:00: PM: calling platform_pm_suspend+0x0/0x50 @ 21508, parent: platform
Oct 11 20:26:18 ryzen kernel: platform PNP0C0C:00: PM: platform_pm_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: platform PNP0800:00: PM: calling platform_pm_suspend+0x0/0x50 @ 21508, parent: 0000:00:14.3
Oct 11 20:26:18 ryzen kernel: platform PNP0800:00: PM: platform_pm_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: thermal LNXTHERM:01: PM: calling acpi_thermal_suspend+0x0/0x20 @ 21508, parent: LNXSYBUS:01
Oct 11 20:26:18 ryzen kernel: thermal LNXTHERM:01: PM: acpi_thermal_suspend+0x0/0x20 returned 0 after 1 usecs
Oct 11 20:26:18 ryzen kernel: thermal LNXTHERM:00: PM: calling acpi_thermal_suspend+0x0/0x20 @ 21508, parent: LNXSYBUS:01
Oct 11 20:26:18 ryzen kernel: thermal LNXTHERM:00: PM: acpi_thermal_suspend+0x0/0x20 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: ccp 0000:07:00.1: PM: calling pci_pm_suspend+0x0/0x170 @ 21554, parent: 0000:00:08.1
Oct 11 20:26:18 ryzen kernel: ccp 0000:07:00.1: PM: pci_pm_suspend+0x0/0x170 returned 0 after 1 usecs
Oct 11 20:26:18 ryzen kernel: pci 0000:07:00.0: PM: calling pci_pm_suspend+0x0/0x170 @ 21554, parent: 0000:00:08.1
Oct 11 20:26:18 ryzen kernel: pci 0000:07:00.0: PM: pci_pm_suspend+0x0/0x170 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: pci 0000:06:00.0: PM: calling pci_pm_suspend+0x0/0x170 @ 21554, parent: 0000:00:07.1
Oct 11 20:26:18 ryzen kernel: tpm_crb MSFT0101:00: PM: calling tpm_pm_suspend+0x0/0xd0 @ 21508, parent: LNXSYBUS:00
Oct 11 20:26:18 ryzen kernel: pci 0000:06:00.0: PM: pci_pm_suspend+0x0/0x170 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: r8169 0000:04:00.0: PM: calling pci_pm_suspend+0x0/0x170 @ 21554, parent: 0000:03:09.0
Oct 11 20:26:18 ryzen kernel: r8169 0000:04:00.0: PM: pci_pm_suspend+0x0/0x170 returned 0 after 1 usecs
Oct 11 20:26:18 ryzen kernel: pcieport 0000:03:09.0: PM: calling pci_pm_suspend+0x0/0x170 @ 21554, parent: 0000:02:00.2
Oct 11 20:26:18 ryzen kernel: pcieport 0000:03:09.0: PM: pci_pm_suspend+0x0/0x170 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: pcieport 0000:02:00.2: PM: calling pci_pm_suspend+0x0/0x170 @ 21557, parent: 0000:00:01.2
Oct 11 20:26:18 ryzen kernel: pcieport 0000:02:00.2: PM: pci_pm_suspend+0x0/0x170 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: nvme 0000:01:00.0: PM: calling pci_pm_suspend+0x0/0x170 @ 21558, parent: 0000:00:01.1
Oct 11 20:26:18 ryzen kernel: pci 0000:00:18.7: PM: calling pci_pm_suspend+0x0/0x170 @ 21559, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pci 0000:00:18.7: PM: pci_pm_suspend+0x0/0x170 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: pci 0000:00:18.6: PM: calling pci_pm_suspend+0x0/0x170 @ 21559, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pci 0000:00:18.6: PM: pci_pm_suspend+0x0/0x170 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: pci 0000:00:18.5: PM: calling pci_pm_suspend+0x0/0x170 @ 21559, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pci 0000:00:18.5: PM: pci_pm_suspend+0x0/0x170 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: pci 0000:00:18.4: PM: calling pci_pm_suspend+0x0/0x170 @ 21559, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pci 0000:00:18.4: PM: pci_pm_suspend+0x0/0x170 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: k10temp 0000:00:18.3: PM: calling pci_pm_suspend+0x0/0x170 @ 21560, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pci 0000:00:18.2: PM: calling pci_pm_suspend+0x0/0x170 @ 21559, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: k10temp 0000:00:18.3: PM: pci_pm_suspend+0x0/0x170 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: pci 0000:00:18.2: PM: pci_pm_suspend+0x0/0x170 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: pci 0000:00:18.1: PM: calling pci_pm_suspend+0x0/0x170 @ 21560, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pci 0000:00:18.0: PM: calling pci_pm_suspend+0x0/0x170 @ 21559, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pci 0000:00:18.1: PM: pci_pm_suspend+0x0/0x170 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: pci 0000:00:18.0: PM: pci_pm_suspend+0x0/0x170 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: pci 0000:00:14.3: PM: calling pci_pm_suspend+0x0/0x170 @ 21560, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: piix4_smbus 0000:00:14.0: PM: calling pci_pm_suspend+0x0/0x170 @ 21559, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pci 0000:00:14.3: PM: pci_pm_suspend+0x0/0x170 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: piix4_smbus 0000:00:14.0: PM: pci_pm_suspend+0x0/0x170 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: pci 0000:00:08.0: PM: calling pci_pm_suspend+0x0/0x170 @ 21559, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pcieport 0000:00:07.1: PM: calling pci_pm_suspend+0x0/0x170 @ 21561, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pci 0000:00:08.0: PM: pci_pm_suspend+0x0/0x170 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: pci 0000:00:07.0: PM: calling pci_pm_suspend+0x0/0x170 @ 21559, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pcieport 0000:00:07.1: PM: pci_pm_suspend+0x0/0x170 returned 0 after 2 usecs
Oct 11 20:26:18 ryzen kernel: pci 0000:00:07.0: PM: pci_pm_suspend+0x0/0x170 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: pci 0000:00:05.0: PM: calling pci_pm_suspend+0x0/0x170 @ 21561, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pci 0000:00:04.0: PM: calling pci_pm_suspend+0x0/0x170 @ 21559, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pci 0000:00:04.0: PM: pci_pm_suspend+0x0/0x170 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: pci 0000:00:05.0: PM: pci_pm_suspend+0x0/0x170 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: pci 0000:00:03.0: PM: calling pci_pm_suspend+0x0/0x170 @ 21561, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pci 0000:00:02.0: PM: calling pci_pm_suspend+0x0/0x170 @ 21562, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pci 0000:00:03.0: PM: pci_pm_suspend+0x0/0x170 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: pci 0000:00:02.0: PM: pci_pm_suspend+0x0/0x170 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: pci 0000:00:01.0: PM: calling pci_pm_suspend+0x0/0x170 @ 21563, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pci 0000:00:01.0: PM: pci_pm_suspend+0x0/0x170 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: pci 0000:00:00.2: PM: calling pci_pm_suspend+0x0/0x170 @ 21563, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pci 0000:00:00.2: PM: pci_pm_suspend+0x0/0x170 returned 0 after 1 usecs
Oct 11 20:26:18 ryzen kernel: pci 0000:00:00.0: PM: calling pci_pm_suspend+0x0/0x170 @ 21563, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pci 0000:00:00.0: PM: pci_pm_suspend+0x0/0x170 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: usb usb3: PM: usb_dev_suspend+0x0/0x20 returned 0 after 10055 usecs
Oct 11 20:26:18 ryzen kernel: snd_hda_codec_realtek hdaudioC2D0: PM: hda_codec_pm_suspend+0x0/0x20 [snd_hda_codec] returned 0 after 16330 usecs
Oct 11 20:26:18 ryzen kernel: snd_hda_intel 0000:07:00.4: PM: calling pci_pm_suspend+0x0/0x170 @ 21555, parent: 0000:00:08.1
Oct 11 20:26:18 ryzen kernel: snd_hda_intel 0000:07:00.4: PM: pci_pm_suspend+0x0/0x170 returned 0 after 1079 usecs
Oct 11 20:26:18 ryzen kernel: snd_hda_intel 0000:05:00.1: PM: pci_pm_suspend+0x0/0x170 returned 0 after 13986 usecs
Oct 11 20:26:18 ryzen kernel: amdgpu 0000:05:00.0: PM: calling pci_pm_suspend+0x0/0x170 @ 21556, parent: 0000:00:03.1
Oct 11 20:26:18 ryzen kernel: sd 6:0:0:0: PM: scsi_bus_suspend+0x0/0xc0 returned 0 after 25037 usecs
Oct 11 20:26:18 ryzen kernel: scsi target6:0:0: PM: calling scsi_bus_suspend+0x0/0xc0 @ 21367, parent: host6
Oct 11 20:26:18 ryzen kernel: usb usb4: PM: usb_dev_suspend+0x0/0x20 returned 0 after 24814 usecs
Oct 11 20:26:18 ryzen kernel: scsi target6:0:0: PM: scsi_bus_suspend+0x0/0xc0 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: xhci_hcd 0000:07:00.3: PM: calling pci_pm_suspend+0x0/0x170 @ 21552, parent: 0000:00:08.1
Oct 11 20:26:18 ryzen kernel: scsi host6: PM: calling scsi_bus_suspend+0x0/0xc0 @ 21516, parent: 2-4:1.0
Oct 11 20:26:18 ryzen kernel: scsi host6: PM: scsi_bus_suspend+0x0/0xc0 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: usb 2-4: PM: calling usb_dev_suspend+0x0/0x20 @ 21541, parent: usb2
Oct 11 20:26:18 ryzen kernel: xhci_hcd 0000:07:00.3: PM: pci_pm_suspend+0x0/0x170 returned 0 after 160 usecs
Oct 11 20:26:18 ryzen kernel: pcieport 0000:00:08.1: PM: calling pci_pm_suspend+0x0/0x170 @ 21560, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pcieport 0000:00:08.1: PM: pci_pm_suspend+0x0/0x170 returned 0 after 2 usecs
Oct 11 20:26:18 ryzen kernel: usb 1-1.1: PM: usb_dev_suspend+0x0/0x20 returned 0 after 28860 usecs
Oct 11 20:26:18 ryzen kernel: usb 1-1: PM: calling usb_dev_suspend+0x0/0x20 @ 21512, parent: usb1
Oct 11 20:26:18 ryzen kernel: usb 1-2.2: PM: usb_dev_suspend+0x0/0x20 returned 0 after 31701 usecs
Oct 11 20:26:18 ryzen kernel: usb 1-2: PM: calling usb_dev_suspend+0x0/0x20 @ 21544, parent: usb1
Oct 11 20:26:18 ryzen kernel: tpm_crb MSFT0101:00: PM: tpm_pm_suspend+0x0/0xd0 returned 0 after 28090 usecs
Oct 11 20:26:18 ryzen kernel: button PNP0C0C:00: PM: calling acpi_button_suspend+0x0/0x20 @ 21508, parent: LNXSYBUS:00
Oct 11 20:26:18 ryzen kernel: button PNP0C0C:00: PM: acpi_button_suspend+0x0/0x20 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: PCCT PCCT: PM: calling platform_pm_suspend+0x0/0x50 @ 21508, parent: platform
Oct 11 20:26:18 ryzen kernel: PCCT PCCT: PM: platform_pm_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: regulator regulator.0: PM: calling regulator_suspend+0x0/0x120 @ 21508, parent: reg-dummy
Oct 11 20:26:18 ryzen kernel: regulator regulator.0: PM: regulator_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: reg-dummy reg-dummy: PM: calling platform_pm_suspend+0x0/0x50 @ 21508, parent: platform
Oct 11 20:26:18 ryzen kernel: reg-dummy reg-dummy: PM: platform_pm_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Oct 11 20:26:18 ryzen kernel: sd 0:0:0:0: [sda] Stopping disk
Oct 11 20:26:18 ryzen kernel: sr 1:0:0:0: PM: scsi_bus_suspend+0x0/0xc0 returned 0 after 38793 usecs
Oct 11 20:26:18 ryzen kernel: scsi target1:0:0: PM: calling scsi_bus_suspend+0x0/0xc0 @ 20209, parent: host1
Oct 11 20:26:18 ryzen kernel: scsi target1:0:0: PM: scsi_bus_suspend+0x0/0xc0 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: scsi host1: PM: calling scsi_bus_suspend+0x0/0xc0 @ 21547, parent: ata2
Oct 11 20:26:18 ryzen kernel: scsi host1: PM: scsi_bus_suspend+0x0/0xc0 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: ata2: PM: calling ata_port_pm_suspend+0x0/0x50 @ 21551, parent: 0000:02:00.1
Oct 11 20:26:18 ryzen kernel: ata2: PM: ata_port_pm_suspend+0x0/0x50 returned 0 after 24 usecs
Oct 11 20:26:18 ryzen kernel: usb 2-4: PM: usb_dev_suspend+0x0/0x20 returned 0 after 23261 usecs
Oct 11 20:26:18 ryzen kernel: usb usb2: PM: calling usb_dev_suspend+0x0/0x20 @ 21545, parent: 0000:02:00.0
Oct 11 20:26:18 ryzen kernel: usb usb2: PM: usb_dev_suspend+0x0/0x20 returned 0 after 14 usecs
Oct 11 20:26:18 ryzen kernel: usb 1-1: PM: usb_dev_suspend+0x0/0x20 returned 0 after 36644 usecs
Oct 11 20:26:18 ryzen kernel: usb 1-2: PM: usb_dev_suspend+0x0/0x20 returned 0 after 33328 usecs
Oct 11 20:26:18 ryzen kernel: usb usb1: PM: calling usb_dev_suspend+0x0/0x20 @ 21546, parent: 0000:02:00.0
Oct 11 20:26:18 ryzen kernel: usb usb1: PM: usb_dev_suspend+0x0/0x20 returned 0 after 9969 usecs
Oct 11 20:26:18 ryzen kernel: xhci_hcd 0000:02:00.0: PM: calling pci_pm_suspend+0x0/0x170 @ 21557, parent: 0000:00:01.2
Oct 11 20:26:18 ryzen kernel: xhci_hcd 0000:02:00.0: PM: pci_pm_suspend+0x0/0x170 returned 0 after 1123 usecs
Oct 11 20:26:18 ryzen kernel: amdgpu 0000:05:00.0: PM: pci_pm_suspend+0x0/0x170 returned 0 after 233066 usecs
Oct 11 20:26:18 ryzen kernel: pcieport 0000:00:03.1: PM: calling pci_pm_suspend+0x0/0x170 @ 21559, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pcieport 0000:00:03.1: PM: pci_pm_suspend+0x0/0x170 returned 0 after 1 usecs
Oct 11 20:26:18 ryzen kernel: nvme 0000:01:00.0: PM: pci_pm_suspend+0x0/0x170 returned 0 after 427429 usecs
Oct 11 20:26:18 ryzen kernel: pcieport 0000:00:01.1: PM: calling pci_pm_suspend+0x0/0x170 @ 21562, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pcieport 0000:00:01.1: PM: pci_pm_suspend+0x0/0x170 returned 0 after 5 usecs
Oct 11 20:26:18 ryzen kernel: sd 0:0:0:0: PM: scsi_bus_suspend+0x0/0xc0 returned 0 after 445345 usecs
Oct 11 20:26:18 ryzen kernel: scsi target0:0:0: PM: calling scsi_bus_suspend+0x0/0xc0 @ 19708, parent: host0
Oct 11 20:26:18 ryzen kernel: scsi target0:0:0: PM: scsi_bus_suspend+0x0/0xc0 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: scsi host0: PM: calling scsi_bus_suspend+0x0/0xc0 @ 21549, parent: ata1
Oct 11 20:26:18 ryzen kernel: scsi host0: PM: scsi_bus_suspend+0x0/0xc0 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: ata1: PM: calling ata_port_pm_suspend+0x0/0x50 @ 21550, parent: 0000:02:00.1
Oct 11 20:26:18 ryzen kernel: ata1: PM: ata_port_pm_suspend+0x0/0x50 returned 0 after 26 usecs
Oct 11 20:26:18 ryzen kernel: ahci 0000:02:00.1: PM: calling pci_pm_suspend+0x0/0x170 @ 21554, parent: 0000:00:01.2
Oct 11 20:26:18 ryzen kernel: ahci 0000:02:00.1: PM: pci_pm_suspend+0x0/0x170 returned 0 after 2 usecs
Oct 11 20:26:18 ryzen kernel: pcieport 0000:00:01.2: PM: calling pci_pm_suspend+0x0/0x170 @ 21561, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pcieport 0000:00:01.2: PM: pci_pm_suspend+0x0/0x170 returned 0 after 2 usecs
Oct 11 20:26:18 ryzen kernel: PM: suspend of devices complete after 449.436 msecs
Oct 11 20:26:18 ryzen kernel: PM: start suspend of devices complete after 7300.209 msecs
Oct 11 20:26:18 ryzen kernel: snd_hda_intel 0000:05:00.1: PM: calling pci_pm_suspend_late+0x0/0x40 @ 21548, parent: 0000:00:03.1
Oct 11 20:26:18 ryzen kernel: snd_hda_intel 0000:05:00.1: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: acpi-wmi PNP0C14:01: PM: calling acpi_subsys_suspend_late+0x0/0x50 @ 21508, parent: platform
Oct 11 20:26:18 ryzen kernel: acpi-wmi PNP0C14:01: PM: acpi_subsys_suspend_late+0x0/0x50 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: acpi-wmi PNP0C14:00: PM: calling acpi_subsys_suspend_late+0x0/0x50 @ 21508, parent: platform
Oct 11 20:26:18 ryzen kernel: acpi-wmi PNP0C14:00: PM: acpi_subsys_suspend_late+0x0/0x50 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: pt-gpio AMDIF030:00: PM: calling acpi_subsys_suspend_late+0x0/0x50 @ 21508, parent: platform
Oct 11 20:26:18 ryzen kernel: pt-gpio AMDIF030:00: PM: acpi_subsys_suspend_late+0x0/0x50 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: amd_gpio AMDI0030:00: PM: calling acpi_subsys_suspend_late+0x0/0x50 @ 21508, parent: platform
Oct 11 20:26:18 ryzen kernel: amd_gpio AMDI0030:00: PM: acpi_subsys_suspend_late+0x0/0x50 returned 0 after 8 usecs
Oct 11 20:26:18 ryzen kernel: snd_hda_intel 0000:07:00.4: PM: calling pci_pm_suspend_late+0x0/0x40 @ 21548, parent: 0000:00:08.1
Oct 11 20:26:18 ryzen kernel: snd_hda_intel 0000:07:00.4: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: xhci_hcd 0000:07:00.3: PM: calling pci_pm_suspend_late+0x0/0x40 @ 21550, parent: 0000:00:08.1
Oct 11 20:26:18 ryzen kernel: xhci_hcd 0000:07:00.3: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: ccp 0000:07:00.1: PM: calling pci_pm_suspend_late+0x0/0x40 @ 21548, parent: 0000:00:08.1
Oct 11 20:26:18 ryzen kernel: pci 0000:07:00.0: PM: calling pci_pm_suspend_late+0x0/0x40 @ 21550, parent: 0000:00:08.1
Oct 11 20:26:18 ryzen kernel: ccp 0000:07:00.1: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: pci 0000:07:00.0: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: pci 0000:06:00.0: PM: calling pci_pm_suspend_late+0x0/0x40 @ 21548, parent: 0000:00:07.1
Oct 11 20:26:18 ryzen kernel: pci 0000:06:00.0: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: r8169 0000:04:00.0: PM: calling pci_pm_suspend_late+0x0/0x40 @ 21550, parent: 0000:03:09.0
Oct 11 20:26:18 ryzen kernel: amdgpu 0000:05:00.0: PM: calling pci_pm_suspend_late+0x0/0x40 @ 21549, parent: 0000:00:03.1
Oct 11 20:26:18 ryzen kernel: r8169 0000:04:00.0: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: ahci 0000:02:00.1: PM: calling pci_pm_suspend_late+0x0/0x40 @ 21563, parent: 0000:00:01.2
Oct 11 20:26:18 ryzen kernel: xhci_hcd 0000:02:00.0: PM: calling pci_pm_suspend_late+0x0/0x40 @ 21561, parent: 0000:00:01.2
Oct 11 20:26:18 ryzen kernel: nvme 0000:01:00.0: PM: calling pci_pm_suspend_late+0x0/0x40 @ 21550, parent: 0000:00:01.1
Oct 11 20:26:18 ryzen kernel: amdgpu 0000:05:00.0: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: pcieport 0000:03:09.0: PM: calling pci_pm_suspend_late+0x0/0x40 @ 21554, parent: 0000:02:00.2
Oct 11 20:26:18 ryzen kernel: xhci_hcd 0000:02:00.0: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: nvme 0000:01:00.0: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: ahci 0000:02:00.1: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: pci 0000:00:18.6: PM: calling pci_pm_suspend_late+0x0/0x40 @ 21549, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pci 0000:00:18.7: PM: calling pci_pm_suspend_late+0x0/0x40 @ 19708, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pci 0000:00:18.5: PM: calling pci_pm_suspend_late+0x0/0x40 @ 21561, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pci 0000:00:18.4: PM: calling pci_pm_suspend_late+0x0/0x40 @ 21550, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pcieport 0000:03:09.0: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: pci 0000:00:18.6: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: pci 0000:00:18.5: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: k10temp 0000:00:18.3: PM: calling pci_pm_suspend_late+0x0/0x40 @ 21562, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pci 0000:00:18.4: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: pci 0000:00:18.2: PM: calling pci_pm_suspend_late+0x0/0x40 @ 21563, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pci 0000:00:18.7: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: pci 0000:00:18.1: PM: calling pci_pm_suspend_late+0x0/0x40 @ 21549, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pci 0000:00:18.0: PM: calling pci_pm_suspend_late+0x0/0x40 @ 21561, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: k10temp 0000:00:18.3: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: pci 0000:00:18.1: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: pci 0000:00:14.3: PM: calling pci_pm_suspend_late+0x0/0x40 @ 21558, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: piix4_smbus 0000:00:14.0: PM: calling pci_pm_suspend_late+0x0/0x40 @ 21550, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pci 0000:00:08.0: PM: calling pci_pm_suspend_late+0x0/0x40 @ 19708, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pcieport 0000:00:08.1: PM: calling pci_pm_suspend_late+0x0/0x40 @ 21554, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pci 0000:00:18.2: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: pci 0000:00:18.0: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: pci 0000:00:08.0: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: pcieport 0000:00:08.1: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: pci 0000:00:14.3: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: pcieport 0000:00:07.1: PM: calling pci_pm_suspend_late+0x0/0x40 @ 21562, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: piix4_smbus 0000:00:14.0: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: pci 0000:00:05.0: PM: calling pci_pm_suspend_late+0x0/0x40 @ 21549, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pci 0000:00:07.0: PM: calling pci_pm_suspend_late+0x0/0x40 @ 21559, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pci 0000:00:04.0: PM: calling pci_pm_suspend_late+0x0/0x40 @ 21563, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pcieport 0000:00:07.1: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: pcieport 0000:00:03.1: PM: calling pci_pm_suspend_late+0x0/0x40 @ 21561, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pci 0000:00:03.0: PM: calling pci_pm_suspend_late+0x0/0x40 @ 21558, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pci 0000:00:05.0: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: pci 0000:00:02.0: PM: calling pci_pm_suspend_late+0x0/0x40 @ 19708, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pci 0000:00:07.0: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: pci 0000:00:04.0: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: pcieport 0000:00:03.1: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: pci 0000:00:03.0: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: pci 0000:00:01.0: PM: calling pci_pm_suspend_late+0x0/0x40 @ 21554, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pci 0000:00:00.2: PM: calling pci_pm_suspend_late+0x0/0x40 @ 21549, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pci 0000:00:02.0: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: pcieport 0000:00:01.1: PM: calling pci_pm_suspend_late+0x0/0x40 @ 21556, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pci 0000:00:00.0: PM: calling pci_pm_suspend_late+0x0/0x40 @ 21559, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pci 0000:00:01.0: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: pci 0000:00:00.2: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: pcieport 0000:00:01.1: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: pci 0000:00:00.0: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: pcieport 0000:02:00.2: PM: calling pci_pm_suspend_late+0x0/0x40 @ 21548, parent: 0000:00:01.2
Oct 11 20:26:18 ryzen kernel: pcieport 0000:02:00.2: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: pcieport 0000:00:01.2: PM: calling pci_pm_suspend_late+0x0/0x40 @ 21550, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pcieport 0000:00:01.2: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: PM: late suspend of devices complete after 0.555 msecs
Oct 11 20:26:18 ryzen kernel: snd_hda_intel 0000:05:00.1: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 21563, parent: 0000:00:03.1
Oct 11 20:26:18 ryzen kernel: acpi-wmi PNP0C14:01: PM: calling acpi_subsys_suspend_noirq+0x0/0x50 @ 21508, parent: platform
Oct 11 20:26:18 ryzen kernel: acpi-wmi PNP0C14:01: PM: acpi_subsys_suspend_noirq+0x0/0x50 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: acpi-wmi PNP0C14:00: PM: calling acpi_subsys_suspend_noirq+0x0/0x50 @ 21508, parent: platform
Oct 11 20:26:18 ryzen kernel: acpi-wmi PNP0C14:00: PM: acpi_subsys_suspend_noirq+0x0/0x50 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: pt-gpio AMDIF030:00: PM: calling acpi_subsys_suspend_noirq+0x0/0x50 @ 21508, parent: platform
Oct 11 20:26:18 ryzen kernel: pt-gpio AMDIF030:00: PM: acpi_subsys_suspend_noirq+0x0/0x50 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: amd_gpio AMDI0030:00: PM: calling acpi_subsys_suspend_noirq+0x0/0x50 @ 21508, parent: platform
Oct 11 20:26:18 ryzen kernel: amd_gpio AMDI0030:00: PM: acpi_subsys_suspend_noirq+0x0/0x50 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: snd_hda_intel 0000:07:00.4: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 21556, parent: 0000:00:08.1
Oct 11 20:26:18 ryzen kernel: xhci_hcd 0000:07:00.3: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 21554, parent: 0000:00:08.1
Oct 11 20:26:18 ryzen kernel: ccp 0000:07:00.1: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 21559, parent: 0000:00:08.1
Oct 11 20:26:18 ryzen kernel: pci 0000:07:00.0: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 21550, parent: 0000:00:08.1
Oct 11 20:26:18 ryzen kernel: pci 0000:06:00.0: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 21548, parent: 0000:00:07.1
Oct 11 20:26:18 ryzen kernel: r8169 0000:04:00.0: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 21561, parent: 0000:03:09.0
Oct 11 20:26:18 ryzen kernel: ahci 0000:02:00.1: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 21558, parent: 0000:00:01.2
Oct 11 20:26:18 ryzen kernel: xhci_hcd 0000:02:00.0: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 21562, parent: 0000:00:01.2
Oct 11 20:26:18 ryzen kernel: nvme 0000:01:00.0: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 21546, parent: 0000:00:01.1
Oct 11 20:26:18 ryzen kernel: pci 0000:00:18.7: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 21544, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pci 0000:00:18.6: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 21512, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pci 0000:00:18.5: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 21545, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pci 0000:00:18.7: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 147 usecs
Oct 11 20:26:18 ryzen kernel: pci 0000:00:18.4: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 21544, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pci 0000:00:18.6: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 147 usecs
Oct 11 20:26:18 ryzen kernel: k10temp 0000:00:18.3: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 21512, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pci 0000:00:18.5: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 147 usecs
Oct 11 20:26:18 ryzen kernel: pci 0000:00:18.2: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 21545, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pci 0000:00:18.1: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 21541, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pci 0000:00:18.0: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 21551, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pci 0000:00:14.3: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 21547, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pci 0000:07:00.0: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 306 usecs
Oct 11 20:26:18 ryzen kernel: piix4_smbus 0000:00:14.0: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 21550, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pci 0000:06:00.0: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 327 usecs
Oct 11 20:26:18 ryzen kernel: pci 0000:00:08.0: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 21514, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pcieport 0000:00:07.1: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 21548, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pci 0000:00:18.4: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 172 usecs
Oct 11 20:26:18 ryzen kernel: pci 0000:00:07.0: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 21544, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: k10temp 0000:00:18.3: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 173 usecs
Oct 11 20:26:18 ryzen kernel: pci 0000:00:05.0: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 21512, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pci 0000:00:18.2: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 176 usecs
Oct 11 20:26:18 ryzen kernel: pci 0000:00:04.0: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 21545, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pci 0000:00:18.1: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 159 usecs
Oct 11 20:26:18 ryzen kernel: pci 0000:00:18.0: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 156 usecs
Oct 11 20:26:18 ryzen kernel: pci 0000:00:14.3: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 156 usecs
Oct 11 20:26:18 ryzen kernel: pci 0000:00:03.0: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 21551, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pci 0000:00:02.0: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 21547, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pci 0000:00:01.0: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 21560, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pci 0000:00:00.2: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 21552, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pci 0000:00:00.0: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 21517, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: piix4_smbus 0000:00:14.0: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 144 usecs
Oct 11 20:26:18 ryzen kernel: pci 0000:00:08.0: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 137 usecs
Oct 11 20:26:18 ryzen kernel: pci 0000:00:07.0: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 123 usecs
Oct 11 20:26:18 ryzen kernel: pci 0000:00:05.0: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 120 usecs
Oct 11 20:26:18 ryzen kernel: pci 0000:00:04.0: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 118 usecs
Oct 11 20:26:18 ryzen kernel: pci 0000:00:02.0: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 124 usecs
Oct 11 20:26:18 ryzen kernel: pci 0000:00:03.0: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 129 usecs
Oct 11 20:26:18 ryzen kernel: pci 0000:00:01.0: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 126 usecs
Oct 11 20:26:18 ryzen kernel: pci 0000:00:00.0: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 126 usecs
Oct 11 20:26:18 ryzen kernel: pci 0000:00:00.2: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 132 usecs
Oct 11 20:26:18 ryzen kernel: snd_hda_intel 0000:05:00.1: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 12085 usecs
Oct 11 20:26:18 ryzen kernel: amdgpu 0000:05:00.0: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 21549, parent: 0000:00:03.1
Oct 11 20:26:18 ryzen kernel: amdgpu 0000:05:00.0: amdgpu: PCI CONFIG reset
Oct 11 20:26:18 ryzen kernel: ccp 0000:07:00.1: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 12109 usecs
Oct 11 20:26:18 ryzen kernel: snd_hda_intel 0000:07:00.4: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 12116 usecs
Oct 11 20:26:18 ryzen kernel: pcieport 0000:00:07.1: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 11774 usecs
Oct 11 20:26:18 ryzen kernel: r8169 0000:04:00.0: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 12189 usecs
Oct 11 20:26:18 ryzen kernel: xhci_hcd 0000:07:00.3: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 12210 usecs
Oct 11 20:26:18 ryzen kernel: pcieport 0000:03:09.0: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 21557, parent: 0000:02:00.2
Oct 11 20:26:18 ryzen kernel: pcieport 0000:00:08.1: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 20209, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: ahci 0000:02:00.1: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 12295 usecs
Oct 11 20:26:18 ryzen kernel: nvme 0000:01:00.0: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 12427 usecs
Oct 11 20:26:18 ryzen kernel: pcieport 0000:00:01.1: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 21513, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: xhci_hcd 0000:02:00.0: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 12442 usecs
Oct 11 20:26:18 ryzen kernel: pcieport 0000:03:09.0: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 12283 usecs
Oct 11 20:26:18 ryzen kernel: pcieport 0000:02:00.2: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 19708, parent: 0000:00:01.2
Oct 11 20:26:18 ryzen kernel: amdgpu 0000:05:00.0: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 12458 usecs
Oct 11 20:26:18 ryzen kernel: pcieport 0000:00:08.1: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 12294 usecs
Oct 11 20:26:18 ryzen kernel: pcieport 0000:00:03.1: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 21541, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pcieport 0000:00:01.1: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 12076 usecs
Oct 11 20:26:18 ryzen kernel: pcieport 0000:02:00.2: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 12488 usecs
Oct 11 20:26:18 ryzen kernel: pcieport 0000:00:03.1: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 12459 usecs
Oct 11 20:26:18 ryzen kernel: pcieport 0000:00:01.2: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 21515, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pcieport 0000:00:01.2: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 12334 usecs
Oct 11 20:26:18 ryzen kernel: PM: noirq suspend of devices complete after 49.722 msecs
Oct 11 20:26:18 ryzen kernel: ACPI: PM: Preparing to enter system sleep state S3
Oct 11 20:26:18 ryzen kernel: ACPI: PM: Saving platform NVS memory
Oct 11 20:26:18 ryzen kernel: Disabling non-boot CPUs ...
Oct 11 20:26:18 ryzen kernel: smpboot: CPU 1 is now offline
Oct 11 20:26:18 ryzen kernel: smpboot: CPU 2 is now offline
Oct 11 20:26:18 ryzen kernel: smpboot: CPU 3 is now offline
Oct 11 20:26:18 ryzen kernel: smpboot: CPU 4 is now offline
Oct 11 20:26:18 ryzen kernel: smpboot: CPU 5 is now offline
Oct 11 20:26:18 ryzen kernel: smpboot: CPU 6 is now offline
Oct 11 20:26:18 ryzen kernel: Spectre V2 : Update user space SMT mitigation: STIBP off
Oct 11 20:26:18 ryzen kernel: smpboot: CPU 7 is now offline
Oct 11 20:26:18 ryzen kernel: smpboot: CPU 8 is now offline
Oct 11 20:26:18 ryzen kernel: smpboot: CPU 9 is now offline
Oct 11 20:26:18 ryzen kernel: smpboot: CPU 10 is now offline
Oct 11 20:26:18 ryzen kernel: smpboot: CPU 11 is now offline
Oct 11 20:26:18 ryzen kernel: Checking wakeup interrupts
Oct 11 20:26:18 ryzen kernel: Calling mce_syscore_suspend+0x0/0x20
Oct 11 20:26:18 ryzen kernel: Calling ledtrig_cpu_syscore_suspend+0x0/0x20
Oct 11 20:26:18 ryzen kernel: Calling timekeeping_suspend+0x0/0x2f0
Oct 11 20:26:18 ryzen kernel: Calling irq_gc_suspend+0x0/0x80
Oct 11 20:26:18 ryzen kernel: Calling save_ioapic_entries+0x0/0xd0
Oct 11 20:26:18 ryzen kernel: Calling i8259A_suspend+0x0/0x30
Oct 11 20:26:18 ryzen kernel: Calling perf_ibs_suspend+0x0/0x40
Oct 11 20:26:18 ryzen kernel: Calling amd_iommu_suspend+0x0/0x50
Oct 11 20:26:18 ryzen kernel: Calling fw_suspend+0x0/0x20
Oct 11 20:26:18 ryzen kernel: Calling acpi_save_bm_rld+0x0/0x30
Oct 11 20:26:18 ryzen kernel: Calling lapic_suspend+0x0/0x210
Oct 11 20:26:18 ryzen kernel: ACPI: PM: Low-level resume complete
Oct 11 20:26:18 ryzen kernel: ACPI: PM: Restoring platform NVS memory
Oct 11 20:26:18 ryzen kernel: Calling lapic_resume+0x0/0x2e0
Oct 11 20:26:18 ryzen kernel: Calling acpi_restore_bm_rld+0x0/0x70
Oct 11 20:26:18 ryzen kernel: Calling irqrouter_resume+0x0/0x50
Oct 11 20:26:18 ryzen kernel: Calling amd_iommu_resume+0x0/0x50
Oct 11 20:26:18 ryzen kernel: Calling perf_ibs_resume+0x0/0x30
Oct 11 20:26:18 ryzen kernel: LVT offset 0 assigned for vector 0x400
Oct 11 20:26:18 ryzen kernel: Calling i8259A_resume+0x0/0x40
Oct 11 20:26:18 ryzen kernel: Calling i8237A_resume+0x0/0xb0
Oct 11 20:26:18 ryzen kernel: Calling ioapic_resume+0x0/0xc0
Oct 11 20:26:18 ryzen kernel: Calling irq_gc_resume+0x0/0x70
Oct 11 20:26:18 ryzen kernel: Calling irq_pm_syscore_resume+0x0/0x20
Oct 11 20:26:18 ryzen kernel: Calling timekeeping_resume+0x0/0x1e0
Oct 11 20:26:18 ryzen kernel: Timekeeping suspended for 1017.048 seconds
Oct 11 20:26:18 ryzen kernel: Calling init_counter_refs+0x0/0x40
Oct 11 20:26:18 ryzen kernel: Calling ledtrig_cpu_syscore_resume+0x0/0x20
Oct 11 20:26:18 ryzen kernel: Calling mce_syscore_resume+0x0/0x30
Oct 11 20:26:18 ryzen kernel: Calling microcode_bsp_resume+0x0/0x40
Oct 11 20:26:18 ryzen kernel: Enabling non-boot CPUs ...
Oct 11 20:26:18 ryzen kernel: smpboot: Booting Node 0 Processor 1 APIC 0x2
Oct 11 20:26:18 ryzen kernel: ACPI: \_SB_.PLTF.C002: Found 2 idle states
Oct 11 20:26:18 ryzen kernel: CPU1 is up
Oct 11 20:26:18 ryzen kernel: smpboot: Booting Node 0 Processor 2 APIC 0x4
Oct 11 20:26:18 ryzen kernel: ACPI: \_SB_.PLTF.C004: Found 2 idle states
Oct 11 20:26:18 ryzen kernel: CPU2 is up
Oct 11 20:26:18 ryzen kernel: smpboot: Booting Node 0 Processor 3 APIC 0x6
Oct 11 20:26:18 ryzen kernel: ACPI: \_SB_.PLTF.C006: Found 2 idle states
Oct 11 20:26:18 ryzen kernel: CPU3 is up
Oct 11 20:26:18 ryzen kernel: smpboot: Booting Node 0 Processor 4 APIC 0x8
Oct 11 20:26:18 ryzen kernel: ACPI: \_SB_.PLTF.C008: Found 2 idle states
Oct 11 20:26:18 ryzen kernel: CPU4 is up
Oct 11 20:26:18 ryzen kernel: smpboot: Booting Node 0 Processor 5 APIC 0xa
Oct 11 20:26:18 ryzen kernel: ACPI: \_SB_.PLTF.C00A: Found 2 idle states
Oct 11 20:26:18 ryzen kernel: CPU5 is up
Oct 11 20:26:18 ryzen kernel: smpboot: Booting Node 0 Processor 6 APIC 0x1
Oct 11 20:26:18 ryzen kernel: ACPI: \_SB_.PLTF.C001: Found 2 idle states
Oct 11 20:26:18 ryzen kernel: Spectre V2 : Update user space SMT mitigation: STIBP always-on
Oct 11 20:26:18 ryzen kernel: CPU6 is up
Oct 11 20:26:18 ryzen kernel: smpboot: Booting Node 0 Processor 7 APIC 0x3
Oct 11 20:26:18 ryzen kernel: ACPI: \_SB_.PLTF.C003: Found 2 idle states
Oct 11 20:26:18 ryzen kernel: CPU7 is up
Oct 11 20:26:18 ryzen kernel: smpboot: Booting Node 0 Processor 8 APIC 0x5
Oct 11 20:26:18 ryzen kernel: ACPI: \_SB_.PLTF.C005: Found 2 idle states
Oct 11 20:26:18 ryzen kernel: CPU8 is up
Oct 11 20:26:18 ryzen kernel: smpboot: Booting Node 0 Processor 9 APIC 0x7
Oct 11 20:26:18 ryzen kernel: ACPI: \_SB_.PLTF.C007: Found 2 idle states
Oct 11 20:26:18 ryzen kernel: CPU9 is up
Oct 11 20:26:18 ryzen kernel: smpboot: Booting Node 0 Processor 10 APIC 0x9
Oct 11 20:26:18 ryzen kernel: ACPI: \_SB_.PLTF.C009: Found 2 idle states
Oct 11 20:26:18 ryzen kernel: CPU10 is up
Oct 11 20:26:18 ryzen kernel: smpboot: Booting Node 0 Processor 11 APIC 0xb
Oct 11 20:26:18 ryzen kernel: ACPI: \_SB_.PLTF.C00B: Found 2 idle states
Oct 11 20:26:18 ryzen kernel: CPU11 is up
Oct 11 20:26:18 ryzen kernel: ACPI: PM: Waking up from system sleep state S3
Oct 11 20:26:18 ryzen kernel: pcieport 0000:00:01.2: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 20209, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pci 0000:00:00.0: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 21515, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pci 0000:00:05.0: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 21516, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pcieport 0000:00:03.1: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 21562, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pci 0000:00:02.0: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 21549, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pci 0000:00:01.0: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 19708, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pci 0000:00:04.0: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 21546, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pcieport 0000:00:01.1: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 21513, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pci 0000:00:03.0: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 21557, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pci 0000:00:00.2: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 21541, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pci 0000:00:07.0: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 21558, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pci 0000:00:05.0: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 220 usecs
Oct 11 20:26:18 ryzen kernel: pci 0000:00:02.0: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 221 usecs
Oct 11 20:26:18 ryzen kernel: pci 0000:00:03.0: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 224 usecs
Oct 11 20:26:18 ryzen kernel: pcieport 0000:00:07.1: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 21516, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pci 0000:00:08.0: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 21549, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pci 0000:00:04.0: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 226 usecs
Oct 11 20:26:18 ryzen kernel: pci 0000:00:01.0: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 226 usecs
Oct 11 20:26:18 ryzen kernel: pci 0000:00:07.0: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 227 usecs
Oct 11 20:26:18 ryzen kernel: pcieport 0000:00:08.1: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 21557, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: piix4_smbus 0000:00:14.0: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 21546, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pci 0000:00:14.3: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 21558, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pci 0000:00:18.0: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 19708, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pci 0000:00:00.0: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 238 usecs
Oct 11 20:26:18 ryzen kernel: pci 0000:00:18.1: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 21515, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pci 0000:00:00.2: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 414 usecs
Oct 11 20:26:18 ryzen kernel: pci 0000:00:08.0: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 190 usecs
Oct 11 20:26:18 ryzen kernel: pci 0000:00:18.2: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 21541, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: k10temp 0000:00:18.3: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 21549, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pci 0000:00:18.0: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 184 usecs
Oct 11 20:26:18 ryzen kernel: pci 0000:00:14.3: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 190 usecs
Oct 11 20:26:18 ryzen kernel: pci 0000:00:18.4: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 19708, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: piix4_smbus 0000:00:14.0: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 194 usecs
Oct 11 20:26:18 ryzen kernel: pci 0000:00:18.5: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 21558, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pci 0000:00:18.1: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 184 usecs
Oct 11 20:26:18 ryzen kernel: pci 0000:00:18.6: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 21546, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: amd_gpio AMDI0030:00: PM: calling acpi_subsys_resume_noirq+0x0/0x30 @ 21508, parent: platform
Oct 11 20:26:18 ryzen kernel: pci 0000:00:18.7: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 21515, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: amd_gpio AMDI0030:00: PM: acpi_subsys_resume_noirq+0x0/0x30 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: pt-gpio AMDIF030:00: PM: calling acpi_subsys_resume_noirq+0x0/0x30 @ 21508, parent: platform
Oct 11 20:26:18 ryzen kernel: pt-gpio AMDIF030:00: PM: acpi_subsys_resume_noirq+0x0/0x30 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: acpi-wmi PNP0C14:00: PM: calling acpi_subsys_resume_noirq+0x0/0x30 @ 21508, parent: platform
Oct 11 20:26:18 ryzen kernel: acpi-wmi PNP0C14:00: PM: acpi_subsys_resume_noirq+0x0/0x30 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: acpi-wmi PNP0C14:01: PM: calling acpi_subsys_resume_noirq+0x0/0x30 @ 21508, parent: platform
Oct 11 20:26:18 ryzen kernel: acpi-wmi PNP0C14:01: PM: acpi_subsys_resume_noirq+0x0/0x30 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: i8042 i8042: PM: calling i8042_pm_resume_noirq+0x0/0x30 [i8042] @ 21508, parent: platform
Oct 11 20:26:18 ryzen kernel: i8042 i8042: PM: i8042_pm_resume_noirq+0x0/0x30 [i8042] returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: pci 0000:00:18.2: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 102 usecs
Oct 11 20:26:18 ryzen kernel: k10temp 0000:00:18.3: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 101 usecs
Oct 11 20:26:18 ryzen kernel: pci 0000:00:18.4: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 99 usecs
Oct 11 20:26:18 ryzen kernel: pci 0000:00:18.5: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 100 usecs
Oct 11 20:26:18 ryzen kernel: pci 0000:00:18.6: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 101 usecs
Oct 11 20:26:18 ryzen kernel: pci 0000:00:18.7: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 100 usecs
Oct 11 20:26:18 ryzen kernel: pcieport 0000:00:01.1: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 554 usecs
Oct 11 20:26:18 ryzen kernel: pcieport 0000:00:03.1: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 561 usecs
Oct 11 20:26:18 ryzen kernel: nvme 0000:01:00.0: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 21554, parent: 0000:00:01.1
Oct 11 20:26:18 ryzen kernel: pcieport 0000:00:01.2: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 563 usecs
Oct 11 20:26:18 ryzen kernel: amdgpu 0000:05:00.0: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 21556, parent: 0000:00:03.1
Oct 11 20:26:18 ryzen kernel: xhci_hcd 0000:02:00.0: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 21561, parent: 0000:00:01.2
Oct 11 20:26:18 ryzen kernel: pcieport 0000:02:00.2: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 21541, parent: 0000:00:01.2
Oct 11 20:26:18 ryzen kernel: ahci 0000:02:00.1: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 21549, parent: 0000:00:01.2
Oct 11 20:26:18 ryzen kernel: pcieport 0000:00:07.1: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 492 usecs
Oct 11 20:26:18 ryzen kernel: pci 0000:06:00.0: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 21558, parent: 0000:00:07.1
Oct 11 20:26:18 ryzen kernel: pcieport 0000:00:08.1: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 500 usecs
Oct 11 20:26:18 ryzen kernel: pci 0000:07:00.0: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 21559, parent: 0000:00:08.1
Oct 11 20:26:18 ryzen kernel: ccp 0000:07:00.1: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 21546, parent: 0000:00:08.1
Oct 11 20:26:18 ryzen kernel: snd_hda_intel 0000:07:00.4: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 21515, parent: 0000:00:08.1
Oct 11 20:26:18 ryzen kernel: xhci_hcd 0000:07:00.3: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 21563, parent: 0000:00:08.1
Oct 11 20:26:18 ryzen kernel: nvme 0000:01:00.0: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 644 usecs
Oct 11 20:26:18 ryzen kernel: pcieport 0000:02:00.2: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 709 usecs
Oct 11 20:26:18 ryzen kernel: pcieport 0000:03:09.0: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 19708, parent: 0000:02:00.2
Oct 11 20:26:18 ryzen kernel: pci 0000:06:00.0: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 565 usecs
Oct 11 20:26:18 ryzen kernel: pci 0000:07:00.0: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 565 usecs
Oct 11 20:26:18 ryzen kernel: ahci 0000:02:00.1: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 739 usecs
Oct 11 20:26:18 ryzen kernel: xhci_hcd 0000:02:00.0: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 756 usecs
Oct 11 20:26:18 ryzen kernel: snd_hda_intel 0000:07:00.4: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 607 usecs
Oct 11 20:26:18 ryzen kernel: ccp 0000:07:00.1: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 651 usecs
Oct 11 20:26:18 ryzen kernel: amdgpu 0000:05:00.0: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 834 usecs
Oct 11 20:26:18 ryzen kernel: snd_hda_intel 0000:05:00.1: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 21517, parent: 0000:00:03.1
Oct 11 20:26:18 ryzen kernel: xhci_hcd 0000:07:00.3: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 672 usecs
Oct 11 20:26:18 ryzen kernel: pcieport 0000:03:09.0: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 225 usecs
Oct 11 20:26:18 ryzen kernel: r8169 0000:04:00.0: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 21548, parent: 0000:03:09.0
Oct 11 20:26:18 ryzen kernel: snd_hda_intel 0000:05:00.1: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 166 usecs
Oct 11 20:26:18 ryzen kernel: r8169 0000:04:00.0: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 235 usecs
Oct 11 20:26:18 ryzen kernel: PM: noirq resume of devices complete after 1.984 msecs
Oct 11 20:26:18 ryzen kernel: pci 0000:00:01.0: PM: calling pci_pm_resume_early+0x0/0x30 @ 21605, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pci 0000:00:00.2: PM: calling pci_pm_resume_early+0x0/0x30 @ 19708, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pcieport 0000:00:03.1: PM: calling pci_pm_resume_early+0x0/0x30 @ 21597, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pcieport 0000:00:01.2: PM: calling pci_pm_resume_early+0x0/0x30 @ 21598, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pci 0000:00:05.0: PM: calling pci_pm_resume_early+0x0/0x30 @ 21548, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pci 0000:00:02.0: PM: calling pci_pm_resume_early+0x0/0x30 @ 21593, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pcieport 0000:00:01.1: PM: calling pci_pm_resume_early+0x0/0x30 @ 21599, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pci 0000:00:04.0: PM: calling pci_pm_resume_early+0x0/0x30 @ 21596, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pci 0000:00:03.0: PM: calling pci_pm_resume_early+0x0/0x30 @ 21590, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pci 0000:00:00.0: PM: calling pci_pm_resume_early+0x0/0x30 @ 21517, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pcieport 0000:00:01.2: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: pci 0000:00:01.0: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: pci 0000:00:03.0: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: pci 0000:00:00.2: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: pci 0000:00:00.0: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: pci 0000:00:05.0: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: pci 0000:00:04.0: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: pcieport 0000:00:03.1: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: pcieport 0000:00:01.1: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: pcieport 0000:00:07.1: PM: calling pci_pm_resume_early+0x0/0x30 @ 21605, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pci 0000:00:07.0: PM: calling pci_pm_resume_early+0x0/0x30 @ 21598, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pci 0000:00:08.0: PM: calling pci_pm_resume_early+0x0/0x30 @ 19708, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pcieport 0000:00:08.1: PM: calling pci_pm_resume_early+0x0/0x30 @ 21590, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: piix4_smbus 0000:00:14.0: PM: calling pci_pm_resume_early+0x0/0x30 @ 21517, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pci 0000:00:14.3: PM: calling pci_pm_resume_early+0x0/0x30 @ 21548, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pci 0000:00:18.0: PM: calling pci_pm_resume_early+0x0/0x30 @ 21596, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pci 0000:00:18.1: PM: calling pci_pm_resume_early+0x0/0x30 @ 21597, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pci 0000:00:18.2: PM: calling pci_pm_resume_early+0x0/0x30 @ 21599, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pci 0000:00:02.0: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: pci 0000:00:07.0: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: pci 0000:00:08.0: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: pcieport 0000:00:08.1: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: piix4_smbus 0000:00:14.0: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: pci 0000:00:14.3: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: pci 0000:00:18.0: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: pcieport 0000:00:07.1: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: pci 0000:00:18.2: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: k10temp 0000:00:18.3: PM: calling pci_pm_resume_early+0x0/0x30 @ 21593, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pci 0000:00:18.1: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: pci 0000:00:18.4: PM: calling pci_pm_resume_early+0x0/0x30 @ 21598, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pci 0000:00:18.5: PM: calling pci_pm_resume_early+0x0/0x30 @ 21548, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pci 0000:00:18.6: PM: calling pci_pm_resume_early+0x0/0x30 @ 21517, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pci 0000:00:18.7: PM: calling pci_pm_resume_early+0x0/0x30 @ 21590, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: xhci_hcd 0000:02:00.0: PM: calling pci_pm_resume_early+0x0/0x30 @ 21605, parent: 0000:00:01.2
Oct 11 20:26:18 ryzen kernel: nvme 0000:01:00.0: PM: calling pci_pm_resume_early+0x0/0x30 @ 21596, parent: 0000:00:01.1
Oct 11 20:26:18 ryzen kernel: ahci 0000:02:00.1: PM: calling pci_pm_resume_early+0x0/0x30 @ 21599, parent: 0000:00:01.2
Oct 11 20:26:18 ryzen kernel: pcieport 0000:02:00.2: PM: calling pci_pm_resume_early+0x0/0x30 @ 19708, parent: 0000:00:01.2
Oct 11 20:26:18 ryzen kernel: k10temp 0000:00:18.3: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: pci 0000:00:18.5: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: pci 0000:00:18.7: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: pci 0000:00:18.6: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: xhci_hcd 0000:02:00.0: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: ahci 0000:02:00.1: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: nvme 0000:01:00.0: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: pcieport 0000:02:00.2: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: amdgpu 0000:05:00.0: PM: calling pci_pm_resume_early+0x0/0x30 @ 21548, parent: 0000:00:03.1
Oct 11 20:26:18 ryzen kernel: pci 0000:00:18.4: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: pci 0000:06:00.0: PM: calling pci_pm_resume_early+0x0/0x30 @ 21595, parent: 0000:00:07.1
Oct 11 20:26:18 ryzen kernel: pci 0000:07:00.0: PM: calling pci_pm_resume_early+0x0/0x30 @ 21590, parent: 0000:00:08.1
Oct 11 20:26:18 ryzen kernel: ccp 0000:07:00.1: PM: calling pci_pm_resume_early+0x0/0x30 @ 21517, parent: 0000:00:08.1
Oct 11 20:26:18 ryzen kernel: xhci_hcd 0000:07:00.3: PM: calling pci_pm_resume_early+0x0/0x30 @ 21605, parent: 0000:00:08.1
Oct 11 20:26:18 ryzen kernel: snd_hda_intel 0000:07:00.4: PM: calling pci_pm_resume_early+0x0/0x30 @ 21596, parent: 0000:00:08.1
Oct 11 20:26:18 ryzen kernel: amdgpu 0000:05:00.0: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: pci 0000:07:00.0: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: pci 0000:06:00.0: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: xhci_hcd 0000:07:00.3: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: ccp 0000:07:00.1: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: pcieport 0000:03:09.0: PM: calling pci_pm_resume_early+0x0/0x30 @ 21597, parent: 0000:02:00.2
Oct 11 20:26:18 ryzen kernel: snd_hda_intel 0000:07:00.4: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: pcieport 0000:03:09.0: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: snd_hda_intel 0000:05:00.1: PM: calling pci_pm_resume_early+0x0/0x30 @ 21599, parent: 0000:00:03.1
Oct 11 20:26:18 ryzen kernel: snd_hda_intel 0000:05:00.1: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: amd_gpio AMDI0030:00: PM: calling acpi_subsys_resume_early+0x0/0x80 @ 21508, parent: platform
Oct 11 20:26:18 ryzen kernel: amd_gpio AMDI0030:00: PM: acpi_subsys_resume_early+0x0/0x80 returned 0 after 12 usecs
Oct 11 20:26:18 ryzen kernel: pt-gpio AMDIF030:00: PM: calling acpi_subsys_resume_early+0x0/0x80 @ 21508, parent: platform
Oct 11 20:26:18 ryzen kernel: pt-gpio AMDIF030:00: PM: acpi_subsys_resume_early+0x0/0x80 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: acpi-wmi PNP0C14:00: PM: calling acpi_subsys_resume_early+0x0/0x80 @ 21508, parent: platform
Oct 11 20:26:18 ryzen kernel: acpi-wmi PNP0C14:00: PM: acpi_subsys_resume_early+0x0/0x80 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: r8169 0000:04:00.0: PM: calling pci_pm_resume_early+0x0/0x30 @ 21593, parent: 0000:03:09.0
Oct 11 20:26:18 ryzen kernel: acpi-wmi PNP0C14:01: PM: calling acpi_subsys_resume_early+0x0/0x80 @ 21508, parent: platform
Oct 11 20:26:18 ryzen kernel: r8169 0000:04:00.0: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: acpi-wmi PNP0C14:01: PM: acpi_subsys_resume_early+0x0/0x80 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: PM: early resume of devices complete after 0.223 msecs
Oct 11 20:26:18 ryzen kernel: pci 0000:00:00.2: PM: calling pci_pm_resume+0x0/0xf0 @ 21605, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pci 0000:00:01.0: PM: calling pci_pm_resume+0x0/0xf0 @ 21595, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pci 0000:00:05.0: PM: calling pci_pm_resume+0x0/0xf0 @ 21517, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pcieport 0000:00:03.1: PM: calling pci_pm_resume+0x0/0xf0 @ 19708, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pcieport 0000:00:01.2: PM: calling pci_pm_resume+0x0/0xf0 @ 21590, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pci 0000:00:04.0: PM: calling pci_pm_resume+0x0/0xf0 @ 21599, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pcieport 0000:00:01.1: PM: calling pci_pm_resume+0x0/0xf0 @ 21597, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pci 0000:00:03.0: PM: calling pci_pm_resume+0x0/0xf0 @ 21598, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pci 0000:00:02.0: PM: calling pci_pm_resume+0x0/0xf0 @ 21596, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pci 0000:00:07.0: PM: calling pci_pm_resume+0x0/0xf0 @ 21593, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pci 0000:00:00.0: PM: calling pci_pm_resume+0x0/0xf0 @ 21592, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pci 0000:00:01.0: PM: pci_pm_resume+0x0/0xf0 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: pci 0000:00:05.0: PM: pci_pm_resume+0x0/0xf0 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: pci 0000:00:02.0: PM: pci_pm_resume+0x0/0xf0 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: pci 0000:00:03.0: PM: pci_pm_resume+0x0/0xf0 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: pci 0000:00:07.0: PM: pci_pm_resume+0x0/0xf0 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: pci 0000:00:04.0: PM: pci_pm_resume+0x0/0xf0 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: pci 0000:00:00.0: PM: pci_pm_resume+0x0/0xf0 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: pcieport 0000:00:07.1: PM: calling pci_pm_resume+0x0/0xf0 @ 21595, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pci 0000:00:00.2: PM: pci_pm_resume+0x0/0xf0 returned 0 after 2 usecs
Oct 11 20:26:18 ryzen kernel: pci 0000:00:08.0: PM: calling pci_pm_resume+0x0/0xf0 @ 21517, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pcieport 0000:00:08.1: PM: calling pci_pm_resume+0x0/0xf0 @ 21596, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: piix4_smbus 0000:00:14.0: PM: calling pci_pm_resume+0x0/0xf0 @ 21599, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pci 0000:00:14.3: PM: calling pci_pm_resume+0x0/0xf0 @ 21593, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pcieport 0000:00:01.2: PM: pci_pm_resume+0x0/0xf0 returned 0 after 1 usecs
Oct 11 20:26:18 ryzen kernel: pci 0000:00:18.0: PM: calling pci_pm_resume+0x0/0xf0 @ 21592, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pci 0000:00:08.0: PM: pci_pm_resume+0x0/0xf0 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: pci 0000:00:18.1: PM: calling pci_pm_resume+0x0/0xf0 @ 21605, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pci 0000:00:14.3: PM: pci_pm_resume+0x0/0xf0 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: piix4_smbus 0000:00:14.0: PM: pci_pm_resume+0x0/0xf0 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: pci 0000:00:18.2: PM: calling pci_pm_resume+0x0/0xf0 @ 21598, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pcieport 0000:00:01.1: PM: pci_pm_resume+0x0/0xf0 returned 0 after 7 usecs
Oct 11 20:26:18 ryzen kernel: pci 0000:00:18.0: PM: pci_pm_resume+0x0/0xf0 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: pci 0000:00:18.1: PM: pci_pm_resume+0x0/0xf0 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: k10temp 0000:00:18.3: PM: calling pci_pm_resume+0x0/0xf0 @ 21517, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pci 0000:00:18.2: PM: pci_pm_resume+0x0/0xf0 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: pci 0000:00:18.4: PM: calling pci_pm_resume+0x0/0xf0 @ 21599, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pci 0000:00:18.5: PM: calling pci_pm_resume+0x0/0xf0 @ 21590, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: pci 0000:00:18.6: PM: calling pci_pm_resume+0x0/0xf0 @ 21597, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: k10temp 0000:00:18.3: PM: pci_pm_resume+0x0/0xf0 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: pci 0000:00:18.7: PM: calling pci_pm_resume+0x0/0xf0 @ 21592, parent: pci0000:00
Oct 11 20:26:18 ryzen kernel: nvme 0000:01:00.0: PM: calling pci_pm_resume+0x0/0xf0 @ 21605, parent: 0000:00:01.1
Oct 11 20:26:18 ryzen kernel: xhci_hcd 0000:02:00.0: PM: calling pci_pm_resume+0x0/0xf0 @ 21593, parent: 0000:00:01.2
Oct 11 20:26:18 ryzen kernel: pcieport 0000:00:03.1: PM: pci_pm_resume+0x0/0xf0 returned 0 after 12 usecs
Oct 11 20:26:18 ryzen kernel: ahci 0000:02:00.1: PM: calling pci_pm_resume+0x0/0xf0 @ 21598, parent: 0000:00:01.2
Oct 11 20:26:18 ryzen kernel: pci 0000:00:18.6: PM: pci_pm_resume+0x0/0xf0 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: pci 0000:00:18.5: PM: pci_pm_resume+0x0/0xf0 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: pci 0000:00:18.4: PM: pci_pm_resume+0x0/0xf0 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: pci 0000:00:18.7: PM: pci_pm_resume+0x0/0xf0 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: reg-dummy reg-dummy: PM: calling platform_pm_resume+0x0/0x50 @ 21508, parent: platform
Oct 11 20:26:18 ryzen kernel: pcieport 0000:02:00.2: PM: calling pci_pm_resume+0x0/0xf0 @ 21517, parent: 0000:00:01.2
Oct 11 20:26:18 ryzen kernel: amdgpu 0000:05:00.0: PM: calling pci_pm_resume+0x0/0xf0 @ 21590, parent: 0000:00:03.1
Oct 11 20:26:18 ryzen kernel: pcieport 0000:00:07.1: PM: pci_pm_resume+0x0/0xf0 returned 0 after 11 usecs
Oct 11 20:26:18 ryzen kernel: reg-dummy reg-dummy: PM: platform_pm_resume+0x0/0x50 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: pcieport 0000:02:00.2: PM: pci_pm_resume+0x0/0xf0 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: nvme 0000:01:00.0: PM: pci_pm_resume+0x0/0xf0 returned 0 after 1 usecs
Oct 11 20:26:18 ryzen kernel: regulator regulator.0: PM: calling regulator_resume+0x0/0x190 @ 21508, parent: reg-dummy
Oct 11 20:26:18 ryzen kernel: pci 0000:06:00.0: PM: calling pci_pm_resume+0x0/0xf0 @ 21599, parent: 0000:00:07.1
Oct 11 20:26:18 ryzen kernel: pcieport 0000:03:09.0: PM: calling pci_pm_resume+0x0/0xf0 @ 19708, parent: 0000:02:00.2
Oct 11 20:26:18 ryzen kernel: pcieport 0000:00:08.1: PM: pci_pm_resume+0x0/0xf0 returned 0 after 15 usecs
Oct 11 20:26:18 ryzen kernel: pci 0000:06:00.0: PM: pci_pm_resume+0x0/0xf0 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: regulator regulator.0: PM: regulator_resume+0x0/0x190 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: pci 0000:07:00.0: PM: calling pci_pm_resume+0x0/0xf0 @ 21592, parent: 0000:00:08.1
Oct 11 20:26:18 ryzen kernel: PCCT PCCT: PM: calling platform_pm_resume+0x0/0x50 @ 21508, parent: platform
Oct 11 20:26:18 ryzen kernel: ccp 0000:07:00.1: PM: calling pci_pm_resume+0x0/0xf0 @ 21595, parent: 0000:00:08.1
Oct 11 20:26:18 ryzen kernel: xhci_hcd 0000:07:00.3: PM: calling pci_pm_resume+0x0/0xf0 @ 21517, parent: 0000:00:08.1
Oct 11 20:26:18 ryzen kernel: snd_hda_intel 0000:07:00.4: PM: calling pci_pm_resume+0x0/0xf0 @ 21591, parent: 0000:00:08.1
Oct 11 20:26:18 ryzen kernel: PCCT PCCT: PM: platform_pm_resume+0x0/0x50 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: ccp 0000:07:00.1: PM: pci_pm_resume+0x0/0xf0 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: pci 0000:07:00.0: PM: pci_pm_resume+0x0/0xf0 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: button PNP0C0C:00: PM: calling acpi_button_resume+0x0/0x110 @ 21508, parent: LNXSYBUS:00
Oct 11 20:26:18 ryzen kernel: button PNP0C0C:00: PM: acpi_button_resume+0x0/0x110 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: pcieport 0000:03:09.0: PM: pci_pm_resume+0x0/0xf0 returned 0 after 27 usecs
Oct 11 20:26:18 ryzen kernel: r8169 0000:04:00.0: PM: calling pci_pm_resume+0x0/0xf0 @ 21597, parent: 0000:03:09.0
Oct 11 20:26:18 ryzen kernel: tpm_crb MSFT0101:00: PM: calling tpm_pm_resume+0x0/0x30 @ 21508, parent: LNXSYBUS:00
Oct 11 20:26:18 ryzen kernel: tpm_crb MSFT0101:00: PM: tpm_pm_resume+0x0/0x30 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: thermal LNXTHERM:00: PM: calling acpi_thermal_resume+0x0/0xf0 @ 21508, parent: LNXSYBUS:01
Oct 11 20:26:18 ryzen kernel: thermal LNXTHERM:00: PM: acpi_thermal_resume+0x0/0xf0 returned 0 after 2 usecs
Oct 11 20:26:18 ryzen kernel: xhci_hcd 0000:02:00.0: xHC error in resume, USBSTS 0x401, Reinit
Oct 11 20:26:18 ryzen kernel: thermal LNXTHERM:01: PM: calling acpi_thermal_resume+0x0/0xf0 @ 21508, parent: LNXSYBUS:01
Oct 11 20:26:18 ryzen kernel: usb usb1: root hub lost power or was reset
Oct 11 20:26:18 ryzen kernel: usb usb2: root hub lost power or was reset
Oct 11 20:26:18 ryzen kernel: thermal LNXTHERM:01: PM: acpi_thermal_resume+0x0/0xf0 returned 0 after 1 usecs
Oct 11 20:26:18 ryzen kernel: platform PNP0800:00: PM: calling platform_pm_resume+0x0/0x50 @ 21508, parent: 0000:00:14.3
Oct 11 20:26:18 ryzen kernel: ahci 0000:02:00.1: PM: pci_pm_resume+0x0/0xf0 returned 0 after 81 usecs
Oct 11 20:26:18 ryzen kernel: platform PNP0800:00: PM: platform_pm_resume+0x0/0x50 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: platform PNP0C0C:00: PM: calling platform_pm_resume+0x0/0x50 @ 21508, parent: platform
Oct 11 20:26:18 ryzen kernel: platform PNP0C0C:00: PM: platform_pm_resume+0x0/0x50 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: amd_gpio AMDI0030:00: PM: calling acpi_subsys_resume+0x0/0x80 @ 21508, parent: platform
Oct 11 20:26:18 ryzen kernel: ata1: PM: calling ata_port_pm_resume+0x0/0x60 @ 21548, parent: 0000:02:00.1
Oct 11 20:26:18 ryzen kernel: ata2: PM: calling ata_port_pm_resume+0x0/0x60 @ 21599, parent: 0000:02:00.1
Oct 11 20:26:18 ryzen kernel: ata4: PM: calling ata_port_pm_resume+0x0/0x60 @ 21595, parent: 0000:02:00.1
Oct 11 20:26:18 ryzen kernel: ata3: PM: calling ata_port_pm_resume+0x0/0x60 @ 21596, parent: 0000:02:00.1
Oct 11 20:26:18 ryzen kernel: amd_gpio AMDI0030:00: PM: acpi_subsys_resume+0x0/0x80 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: platform MSFT0101:00: PM: calling platform_pm_resume+0x0/0x50 @ 21508, parent: platform
Oct 11 20:26:18 ryzen kernel: platform MSFT0101:00: PM: platform_pm_resume+0x0/0x50 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: ata2: PM: ata_port_pm_resume+0x0/0x60 returned 0 after 3 usecs
Oct 11 20:26:18 ryzen kernel: acpi-cpufreq acpi-cpufreq: PM: calling platform_pm_resume+0x0/0x50 @ 21508, parent: platform
Oct 11 20:26:18 ryzen kernel: ata4: PM: ata_port_pm_resume+0x0/0x60 returned 0 after 6 usecs
Oct 11 20:26:18 ryzen kernel: acpi-cpufreq acpi-cpufreq: PM: platform_pm_resume+0x0/0x50 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: ata3: PM: ata_port_pm_resume+0x0/0x60 returned 0 after 9 usecs
Oct 11 20:26:18 ryzen kernel: pt-gpio AMDIF030:00: PM: calling acpi_subsys_resume+0x0/0x80 @ 21508, parent: platform
Oct 11 20:26:18 ryzen kernel: ata1: PM: ata_port_pm_resume+0x0/0x60 returned 0 after 10 usecs
Oct 11 20:26:18 ryzen kernel: pt-gpio AMDIF030:00: PM: acpi_subsys_resume+0x0/0x80 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: scsi host1: PM: calling scsi_bus_resume+0x0/0x90 @ 21604, parent: ata2
Oct 11 20:26:18 ryzen kernel: scsi host2: PM: calling scsi_bus_resume+0x0/0x90 @ 21558, parent: ata3
Oct 11 20:26:18 ryzen kernel: platform PNP0103:00: PM: calling platform_pm_resume+0x0/0x50 @ 21508, parent: platform
Oct 11 20:26:18 ryzen kernel: ata6: PM: calling ata_port_pm_resume+0x0/0x60 @ 21589, parent: 0000:02:00.1
Oct 11 20:26:18 ryzen kernel: scsi host1: PM: scsi_bus_resume+0x0/0x90 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: scsi host2: PM: scsi_bus_resume+0x0/0x90 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: scsi host0: PM: calling scsi_bus_resume+0x0/0x90 @ 21559, parent: ata1
Oct 11 20:26:18 ryzen kernel: platform PNP0103:00: PM: platform_pm_resume+0x0/0x50 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: scsi host0: PM: scsi_bus_resume+0x0/0x90 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: acpi-wmi PNP0C14:00: PM: calling acpi_subsys_resume+0x0/0x80 @ 21508, parent: platform
Oct 11 20:26:18 ryzen kernel: ata6: PM: ata_port_pm_resume+0x0/0x60 returned 0 after 2 usecs
Oct 11 20:26:18 ryzen kernel: scsi host3: PM: calling scsi_bus_resume+0x0/0x90 @ 19708, parent: ata4
Oct 11 20:26:18 ryzen kernel: acpi-wmi PNP0C14:00: PM: acpi_subsys_resume+0x0/0x80 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: scsi host3: PM: scsi_bus_resume+0x0/0x90 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: scsi target1:0:0: PM: calling scsi_bus_resume+0x0/0x90 @ 21546, parent: host1
Oct 11 20:26:18 ryzen kernel: acpi-wmi PNP0C14:01: PM: calling acpi_subsys_resume+0x0/0x80 @ 21508, parent: platform
Oct 11 20:26:18 ryzen kernel: scsi target0:0:0: PM: calling scsi_bus_resume+0x0/0x90 @ 21563, parent: host0
Oct 11 20:26:18 ryzen kernel: acpi-wmi PNP0C14:01: PM: acpi_subsys_resume+0x0/0x80 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: scsi target0:0:0: PM: scsi_bus_resume+0x0/0x90 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: xhci_hcd 0000:07:00.3: PM: pci_pm_resume+0x0/0xf0 returned 0 after 110 usecs
Oct 11 20:26:18 ryzen kernel: scsi target1:0:0: PM: scsi_bus_resume+0x0/0x90 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: scsi host5: PM: calling scsi_bus_resume+0x0/0x90 @ 21588, parent: ata6
Oct 11 20:26:18 ryzen kernel: button LNXPWRBN:00: PM: calling acpi_button_resume+0x0/0x110 @ 21508, parent: LNXSYSTM:00
Oct 11 20:26:18 ryzen kernel: scsi host5: PM: scsi_bus_resume+0x0/0x90 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: button LNXPWRBN:00: PM: acpi_button_resume+0x0/0x110 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: sr 1:0:0:0: PM: calling scsi_bus_resume+0x0/0x90 @ 21555, parent: target1:0:0
Oct 11 20:26:18 ryzen kernel: platform rtc-efi.0: PM: calling platform_pm_resume+0x0/0x50 @ 21508, parent: platform
Oct 11 20:26:18 ryzen kernel: sd 0:0:0:0: PM: calling scsi_bus_resume+0x0/0x90 @ 21556, parent: target0:0:0
Oct 11 20:26:18 ryzen kernel: sr 1:0:0:0: PM: scsi_bus_resume+0x0/0x90 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: platform rtc-efi.0: PM: platform_pm_resume+0x0/0x50 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: usb usb3: PM: calling usb_dev_resume+0x0/0x20 @ 21596, parent: 0000:07:00.3
Oct 11 20:26:18 ryzen kernel: usb usb4: PM: calling usb_dev_resume+0x0/0x20 @ 19708, parent: 0000:07:00.3
Oct 11 20:26:18 ryzen kernel: sd 0:0:0:0: PM: scsi_bus_resume+0x0/0x90 returned 0 after 1 usecs
Oct 11 20:26:18 ryzen kernel: platform efivars.0: PM: calling platform_pm_resume+0x0/0x50 @ 21508, parent: platform
Oct 11 20:26:18 ryzen kernel: platform efivars.0: PM: platform_pm_resume+0x0/0x50 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: system 00:00: PM: calling pnp_bus_resume+0x0/0xa0 @ 21508, parent: pnp0
Oct 11 20:26:18 ryzen kernel: system 00:00: PM: pnp_bus_resume+0x0/0xa0 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: system 00:01: PM: calling pnp_bus_resume+0x0/0xa0 @ 21508, parent: pnp0
Oct 11 20:26:18 ryzen kernel: system 00:01: PM: pnp_bus_resume+0x0/0xa0 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: rtc_cmos 00:02: PM: calling pnp_bus_resume+0x0/0xa0 @ 21508, parent: pnp0
Oct 11 20:26:18 ryzen kernel: rtc_cmos 00:02: PM: pnp_bus_resume+0x0/0xa0 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: system 00:03: PM: calling pnp_bus_resume+0x0/0xa0 @ 21508, parent: pnp0
Oct 11 20:26:18 ryzen kernel: system 00:03: PM: pnp_bus_resume+0x0/0xa0 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: i8042 kbd 00:04: PM: calling pnp_bus_resume+0x0/0xa0 @ 21508, parent: pnp0
Oct 11 20:26:18 ryzen kernel: r8169 0000:04:00.0: PM: pci_pm_resume+0x0/0xf0 returned 0 after 166 usecs
Oct 11 20:26:18 ryzen kernel: ata5: PM: calling ata_port_pm_resume+0x0/0x60 @ 21592, parent: 0000:02:00.1
Oct 11 20:26:18 ryzen kernel: i8042 kbd 00:04: PM: pnp_bus_resume+0x0/0xa0 returned 0 after 58 usecs
Oct 11 20:26:18 ryzen kernel: ata5: PM: ata_port_pm_resume+0x0/0x60 returned 0 after 3 usecs
Oct 11 20:26:18 ryzen kernel: serial 00:05: PM: calling pnp_bus_resume+0x0/0xa0 @ 21508, parent: pnp0
Oct 11 20:26:18 ryzen kernel: scsi host4: PM: calling scsi_bus_resume+0x0/0x90 @ 21594, parent: ata5
Oct 11 20:26:18 ryzen kernel: scsi host4: PM: scsi_bus_resume+0x0/0x90 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: serial 00:05: activated
Oct 11 20:26:18 ryzen kernel: serial 00:05: PM: pnp_bus_resume+0x0/0xa0 returned 0 after 905 usecs
Oct 11 20:26:18 ryzen kernel: system 00:06: PM: calling pnp_bus_resume+0x0/0xa0 @ 21508, parent: pnp0
Oct 11 20:26:18 ryzen kernel: system 00:06: PM: pnp_bus_resume+0x0/0xa0 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: pcspkr pcspkr: PM: calling platform_pm_resume+0x0/0x50 @ 21508, parent: platform
Oct 11 20:26:18 ryzen kernel: pcspkr pcspkr: PM: platform_pm_resume+0x0/0x50 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: input input0: PM: calling input_dev_resume+0x0/0x40 @ 21508, parent: PNP0C0C:00
Oct 11 20:26:18 ryzen kernel: input input0: PM: input_dev_resume+0x0/0x40 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: input input1: PM: calling input_dev_resume+0x0/0x40 @ 21508, parent: LNXPWRBN:00
Oct 11 20:26:18 ryzen kernel: input input1: PM: input_dev_resume+0x0/0x40 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: port 00:05:0.0: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 21508, parent: 00:05:0
Oct 11 20:26:18 ryzen kernel: port 00:05:0.0: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: serial8250 serial8250: PM: calling platform_pm_resume+0x0/0x50 @ 21508, parent: platform
Oct 11 20:26:18 ryzen kernel: serial8250 serial8250: PM: platform_pm_resume+0x0/0x50 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: port serial8250:0.1: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 21508, parent: serial8250:0
Oct 11 20:26:18 ryzen kernel: port serial8250:0.1: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: port serial8250:0.2: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 21508, parent: serial8250:0
Oct 11 20:26:18 ryzen kernel: port serial8250:0.2: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: port serial8250:0.3: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 21508, parent: serial8250:0
Oct 11 20:26:18 ryzen kernel: port serial8250:0.3: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: port serial8250:0.4: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 21508, parent: serial8250:0
Oct 11 20:26:18 ryzen kernel: port serial8250:0.4: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: port serial8250:0.5: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 21508, parent: serial8250:0
Oct 11 20:26:18 ryzen kernel: port serial8250:0.5: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: port serial8250:0.6: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 21508, parent: serial8250:0
Oct 11 20:26:18 ryzen kernel: port serial8250:0.6: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: port serial8250:0.7: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 21508, parent: serial8250:0
Oct 11 20:26:18 ryzen kernel: port serial8250:0.7: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: port serial8250:0.8: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 21508, parent: serial8250:0
Oct 11 20:26:18 ryzen kernel: port serial8250:0.8: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: port serial8250:0.9: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 21508, parent: serial8250:0
Oct 11 20:26:18 ryzen kernel: port serial8250:0.9: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: port serial8250:0.10: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 21508, parent: serial8250:0
Oct 11 20:26:18 ryzen kernel: port serial8250:0.10: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: port serial8250:0.11: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 21508, parent: serial8250:0
Oct 11 20:26:18 ryzen kernel: port serial8250:0.11: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: port serial8250:0.12: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 21508, parent: serial8250:0
Oct 11 20:26:18 ryzen kernel: port serial8250:0.12: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: port serial8250:0.13: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 21508, parent: serial8250:0
Oct 11 20:26:18 ryzen kernel: port serial8250:0.13: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: port serial8250:0.14: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 21508, parent: serial8250:0
Oct 11 20:26:18 ryzen kernel: port serial8250:0.14: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: port serial8250:0.15: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 21508, parent: serial8250:0
Oct 11 20:26:18 ryzen kernel: port serial8250:0.15: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: port serial8250:0.16: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 21508, parent: serial8250:0
Oct 11 20:26:18 ryzen kernel: port serial8250:0.16: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: port serial8250:0.17: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 21508, parent: serial8250:0
Oct 11 20:26:18 ryzen kernel: port serial8250:0.17: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: port serial8250:0.18: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 21508, parent: serial8250:0
Oct 11 20:26:18 ryzen kernel: port serial8250:0.18: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: port serial8250:0.19: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 21508, parent: serial8250:0
Oct 11 20:26:18 ryzen kernel: port serial8250:0.19: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: port serial8250:0.20: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 21508, parent: serial8250:0
Oct 11 20:26:18 ryzen kernel: port serial8250:0.20: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: port serial8250:0.21: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 21508, parent: serial8250:0
Oct 11 20:26:18 ryzen kernel: port serial8250:0.21: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: port serial8250:0.22: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 21508, parent: serial8250:0
Oct 11 20:26:18 ryzen kernel: port serial8250:0.22: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: port serial8250:0.23: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 21508, parent: serial8250:0
Oct 11 20:26:18 ryzen kernel: port serial8250:0.23: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: port serial8250:0.24: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 21508, parent: serial8250:0
Oct 11 20:26:18 ryzen kernel: port serial8250:0.24: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: port serial8250:0.25: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 21508, parent: serial8250:0
Oct 11 20:26:18 ryzen kernel: port serial8250:0.25: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: port serial8250:0.26: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 21508, parent: serial8250:0
Oct 11 20:26:18 ryzen kernel: port serial8250:0.26: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: port serial8250:0.27: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 21508, parent: serial8250:0
Oct 11 20:26:18 ryzen kernel: port serial8250:0.27: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: port serial8250:0.28: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 21508, parent: serial8250:0
Oct 11 20:26:18 ryzen kernel: port serial8250:0.28: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: port serial8250:0.29: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 21508, parent: serial8250:0
Oct 11 20:26:18 ryzen kernel: port serial8250:0.29: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: port serial8250:0.30: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 21508, parent: serial8250:0
Oct 11 20:26:18 ryzen kernel: port serial8250:0.30: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: port serial8250:0.31: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 21508, parent: serial8250:0
Oct 11 20:26:18 ryzen kernel: port serial8250:0.31: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: rtc rtc0: PM: calling rtc_resume+0x0/0x240 @ 21508, parent: 00:02
Oct 11 20:26:18 ryzen kernel: rtc rtc0: PM: rtc_resume+0x0/0x240 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: alarmtimer alarmtimer.0.auto: PM: calling platform_pm_resume+0x0/0x50 @ 21508, parent: rtc0
Oct 11 20:26:18 ryzen kernel: alarmtimer alarmtimer.0.auto: PM: platform_pm_resume+0x0/0x50 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: platform microcode: PM: calling platform_pm_resume+0x0/0x50 @ 21508, parent: platform
Oct 11 20:26:18 ryzen kernel: platform microcode: PM: platform_pm_resume+0x0/0x50 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: i8042 i8042: PM: calling platform_pm_resume+0x0/0x50 @ 21508, parent: platform
Oct 11 20:26:18 ryzen kernel: i8042 i8042: PM: platform_pm_resume+0x0/0x50 returned 0 after 57 usecs
Oct 11 20:26:18 ryzen kernel: atkbd serio0: PM: calling serio_resume+0x0/0xa0 [serio] @ 21508, parent: i8042
Oct 11 20:26:18 ryzen kernel: atkbd serio0: PM: serio_resume+0x0/0xa0 [serio] returned 0 after 2 usecs
Oct 11 20:26:18 ryzen kernel: input input2: PM: calling input_dev_resume+0x0/0x40 @ 21508, parent: serio0
Oct 11 20:26:18 ryzen kernel: input input2: PM: input_dev_resume+0x0/0x40 returned 0 after 1 usecs
Oct 11 20:26:18 ryzen kernel: leds input2::numlock: PM: calling led_resume+0x0/0x50 @ 21508, parent: input2
Oct 11 20:26:18 ryzen kernel: leds input2::numlock: PM: led_resume+0x0/0x50 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: leds input2::capslock: PM: calling led_resume+0x0/0x50 @ 21508, parent: input2
Oct 11 20:26:18 ryzen kernel: leds input2::capslock: PM: led_resume+0x0/0x50 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: leds input2::scrolllock: PM: calling led_resume+0x0/0x50 @ 21508, parent: input2
Oct 11 20:26:18 ryzen kernel: leds input2::scrolllock: PM: led_resume+0x0/0x50 returned 0 after 0 usecs
Oct 11 20:26:18 ryzen kernel: snd_hda_intel 0000:07:00.4: PM: pci_pm_resume+0x0/0xf0 returned 0 after 4367 usecs
Oct 11 20:26:18 ryzen kernel: snd_hda_codec_realtek hdaudioC2D0: PM: calling hda_codec_pm_resume+0x0/0x20 [snd_hda_codec] @ 21612, parent: 0000:07:00.4
Oct 11 20:26:18 ryzen kernel: usb usb4: PM: usb_dev_resume+0x0/0x20 returned 0 after 26521 usecs
Oct 11 20:26:18 ryzen kernel: xhci_hcd 0000:02:00.0: PM: pci_pm_resume+0x0/0xf0 returned 0 after 56853 usecs
Oct 11 20:26:18 ryzen kernel: usb usb2: PM: calling usb_dev_resume+0x0/0x20 @ 21545, parent: 0000:02:00.0
Oct 11 20:26:18 ryzen kernel: usb usb1: PM: calling usb_dev_resume+0x0/0x20 @ 21553, parent: 0000:02:00.0
Oct 11 20:26:18 ryzen kernel: usb usb3: PM: usb_dev_resume+0x0/0x20 returned 0 after 57532 usecs
Oct 11 20:26:19 ryzen kernel: usb 3-2: PM: calling usb_dev_resume+0x0/0x20 @ 21514, parent: usb3
Oct 11 20:26:19 ryzen kernel: nvme nvme0: Shutdown timeout set to 8 seconds
Oct 11 20:26:19 ryzen kernel: usb 3-2: PM: usb_dev_resume+0x0/0x20 returned 0 after 26448 usecs
Oct 11 20:26:19 ryzen kernel: input input3: PM: calling input_dev_resume+0x0/0x40 @ 21508, parent: 0003:1852:7022.0001
Oct 11 20:26:19 ryzen kernel: input input3: PM: input_dev_resume+0x0/0x40 returned 0 after 0 usecs
Oct 11 20:26:19 ryzen kernel: nvme nvme0: 32/0/0 default/read/poll queues
Oct 11 20:26:19 ryzen kernel: usb usb1: PM: usb_dev_resume+0x0/0x20 returned 0 after 143079 usecs
Oct 11 20:26:19 ryzen kernel: usb 1-2: PM: calling usb_dev_resume+0x0/0x20 @ 21555, parent: usb1
Oct 11 20:26:19 ryzen kernel: usb 1-10: PM: calling usb_dev_resume+0x0/0x20 @ 21584, parent: usb1
Oct 11 20:26:19 ryzen kernel: usb 1-7: PM: calling usb_dev_resume+0x0/0x20 @ 21585, parent: usb1
Oct 11 20:26:19 ryzen kernel: usb 1-5: PM: calling usb_dev_resume+0x0/0x20 @ 21578, parent: usb1
Oct 11 20:26:19 ryzen kernel: usb 1-1: PM: calling usb_dev_resume+0x0/0x20 @ 21613, parent: usb1
Oct 11 20:26:19 ryzen kernel: snd_hda_codec_realtek hdaudioC2D0: PM: hda_codec_pm_resume+0x0/0x20 [snd_hda_codec] returned 0 after 215226 usecs
Oct 11 20:26:19 ryzen kernel: usb usb2: PM: usb_dev_resume+0x0/0x20 returned 0 after 213082 usecs
Oct 11 20:26:19 ryzen kernel: usb 2-4: PM: calling usb_dev_resume+0x0/0x20 @ 21587, parent: usb2
Oct 11 20:26:19 ryzen kernel: ata4: SATA link down (SStatus 0 SControl 330)
Oct 11 20:26:19 ryzen kernel: ata3: SATA link down (SStatus 0 SControl 330)
Oct 11 20:26:19 ryzen kernel: usb 1-10: reset full-speed USB device number 7 using xhci_hcd
Oct 11 20:26:19 ryzen kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
Oct 11 20:26:19 ryzen kernel: ata2.00: configured for UDMA/100
Oct 11 20:26:19 ryzen kernel: [drm] PCIE GART of 256M enabled (table at 0x000000F400800000).
Oct 11 20:26:19 ryzen kernel: usb 1-10: PM: usb_dev_resume+0x0/0x20 returned 0 after 444808 usecs
Oct 11 20:26:19 ryzen kernel: usb 1-5: reset low-speed USB device number 3 using xhci_hcd
Oct 11 20:26:19 ryzen kernel: ata6: failed to resume link (SControl 0)
Oct 11 20:26:19 ryzen kernel: ata6: SATA link down (SStatus 0 SControl 0)
Oct 11 20:26:19 ryzen kernel: ata5: failed to resume link (SControl 0)
Oct 11 20:26:19 ryzen kernel: ata5: SATA link down (SStatus 0 SControl 0)
Oct 11 20:26:19 ryzen kernel: usb 1-5: PM: usb_dev_resume+0x0/0x20 returned 0 after 1080011 usecs
Oct 11 20:26:19 ryzen kernel: input input4: PM: calling input_dev_resume+0x0/0x40 @ 21508, parent: 0003:05F3:00FF.0002
Oct 11 20:26:19 ryzen kernel: input input4: PM: input_dev_resume+0x0/0x40 returned 0 after 0 usecs
Oct 11 20:26:19 ryzen kernel: [drm] Fence fallback timer expired on ring sdma0
Oct 11 20:26:19 ryzen kernel: usb 1-1: reset high-speed USB device number 10 using xhci_hcd
Oct 11 20:26:19 ryzen kernel: usb 1-2: reset high-speed USB device number 2 using xhci_hcd
Oct 11 20:26:19 ryzen kernel: usb 1-1: PM: usb_dev_resume+0x0/0x20 returned 0 after 1570132 usecs
Oct 11 20:26:19 ryzen kernel: usb 1-1.1: PM: calling usb_dev_resume+0x0/0x20 @ 21619, parent: 1-1
Oct 11 20:26:19 ryzen kernel: usb 1-1.4: PM: calling usb_dev_resume+0x0/0x20 @ 21624, parent: 1-1
Oct 11 20:26:19 ryzen kernel: [drm] Fence fallback timer expired on ring sdma0
Oct 11 20:26:19 ryzen kernel: usb 1-7: reset full-speed USB device number 5 using xhci_hcd
Oct 11 20:26:19 ryzen kernel: usb 1-2: PM: usb_dev_resume+0x0/0x20 returned 0 after 1920372 usecs
Oct 11 20:26:19 ryzen kernel: usb 1-2.1: PM: calling usb_dev_resume+0x0/0x20 @ 21586, parent: 1-2
Oct 11 20:26:19 ryzen kernel: usb 1-2.2: PM: calling usb_dev_resume+0x0/0x20 @ 21607, parent: 1-2
Oct 11 20:26:19 ryzen kernel: usb 1-2.4: PM: calling usb_dev_resume+0x0/0x20 @ 21611, parent: 1-2
Oct 11 20:26:19 ryzen kernel: usb 1-2.3: PM: calling usb_dev_resume+0x0/0x20 @ 21606, parent: 1-2
Oct 11 20:26:19 ryzen kernel: [drm] Fence fallback timer expired on ring sdma0
Oct 11 20:26:19 ryzen kernel: usb 1-7: PM: usb_dev_resume+0x0/0x20 returned 0 after 2163025 usecs
Oct 11 20:26:19 ryzen kernel: usb 2-4: reset SuperSpeed USB device number 2 using xhci_hcd
Oct 11 20:26:19 ryzen kernel: usb 2-4: PM: usb_dev_resume+0x0/0x20 returned 0 after 2216531 usecs
Oct 11 20:26:19 ryzen kernel: scsi host6: PM: calling scsi_bus_resume+0x0/0x90 @ 21516, parent: 2-4:1.0
Oct 11 20:26:19 ryzen kernel: scsi host6: PM: scsi_bus_resume+0x0/0x90 returned 0 after 0 usecs
Oct 11 20:26:19 ryzen kernel: scsi target6:0:0: PM: calling scsi_bus_resume+0x0/0x90 @ 21554, parent: host6
Oct 11 20:26:19 ryzen kernel: scsi target6:0:0: PM: scsi_bus_resume+0x0/0x90 returned 0 after 0 usecs
Oct 11 20:26:19 ryzen kernel: sd 6:0:0:0: PM: calling scsi_bus_resume+0x0/0x90 @ 21582, parent: target6:0:0
Oct 11 20:26:19 ryzen kernel: sd 6:0:0:0: PM: scsi_bus_resume+0x0/0x90 returned 0 after 1 usecs
Oct 11 20:26:19 ryzen kernel: usb 1-1.1: reset low-speed USB device number 11 using xhci_hcd
Oct 11 20:26:19 ryzen kernel: [drm] Fence fallback timer expired on ring sdma0
Oct 11 20:26:19 ryzen kernel: usb 1-1.1: PM: usb_dev_resume+0x0/0x20 returned 0 after 1456203 usecs
Oct 11 20:26:19 ryzen kernel: [drm] Fence fallback timer expired on ring sdma0
Oct 11 20:26:19 ryzen kernel: usb 1-1.4: reset low-speed USB device number 12 using xhci_hcd
Oct 11 20:26:19 ryzen kernel: usb 1-1.4: PM: usb_dev_resume+0x0/0x20 returned 0 after 2085187 usecs
Oct 11 20:26:19 ryzen kernel: [drm] Fence fallback timer expired on ring sdma0
Oct 11 20:26:19 ryzen kernel: usb 1-2.2: reset full-speed USB device number 6 using xhci_hcd
Oct 11 20:26:19 ryzen kernel: usb 1-2.2: PM: usb_dev_resume+0x0/0x20 returned 0 after 2059044 usecs
Oct 11 20:26:19 ryzen kernel: usb 1-2.1: reset full-speed USB device number 4 using xhci_hcd
Oct 11 20:26:19 ryzen kernel: [drm] Fence fallback timer expired on ring sdma0
Oct 11 20:26:19 ryzen kernel: [drm] Fence fallback timer expired on ring sdma0
Oct 11 20:26:19 ryzen kernel: [drm] UVD and UVD ENC initialized successfully.
Oct 11 20:26:19 ryzen kernel: [drm] VCE initialized successfully.
Oct 11 20:26:19 ryzen kernel: amdgpu 0000:05:00.0: PM: pci_pm_resume+0x0/0xf0 returned 0 after 5136707 usecs
Oct 11 20:26:19 ryzen kernel: snd_hda_intel 0000:05:00.1: PM: calling pci_pm_resume+0x0/0xf0 @ 21605, parent: 0000:00:03.1
Oct 11 20:26:19 ryzen kernel: snd_hda_intel 0000:05:00.1: PM: pci_pm_resume+0x0/0xf0 returned 0 after 2358 usecs
Oct 11 20:26:19 ryzen kernel: ata1: link is slow to respond, please be patient (ready=0)
Oct 11 20:26:19 ryzen kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Oct 11 20:26:19 ryzen kernel: ata1.00: configured for UDMA/133
Oct 11 20:26:19 ryzen kernel: usb 1-2.1: PM: usb_dev_resume+0x0/0x20 returned 0 after 7817907 usecs
Oct 11 20:26:19 ryzen kernel: input input5: PM: calling input_dev_resume+0x0/0x40 @ 21508, parent: 0003:0ECB:2057.0003
Oct 11 20:26:19 ryzen kernel: input input5: PM: input_dev_resume+0x0/0x40 returned 0 after 0 usecs
Oct 11 20:26:19 ryzen kernel: input input6: PM: calling input_dev_resume+0x0/0x40 @ 21508, parent: 0003:29EA:0102.0005
Oct 11 20:26:19 ryzen kernel: input input6: PM: input_dev_resume+0x0/0x40 returned 0 after 0 usecs
Oct 11 20:26:19 ryzen kernel: input input7: PM: calling input_dev_resume+0x0/0x40 @ 21508, parent: 0003:29EA:0102.0006
Oct 11 20:26:19 ryzen kernel: input input7: PM: input_dev_resume+0x0/0x40 returned 0 after 9 usecs
Oct 11 20:26:19 ryzen kernel: leds input7::numlock: PM: calling led_resume+0x0/0x50 @ 21508, parent: input7
Oct 11 20:26:19 ryzen kernel: leds input7::numlock: PM: led_resume+0x0/0x50 returned 0 after 0 usecs
Oct 11 20:26:19 ryzen kernel: leds input7::capslock: PM: calling led_resume+0x0/0x50 @ 21508, parent: input7
Oct 11 20:26:19 ryzen kernel: leds input7::capslock: PM: led_resume+0x0/0x50 returned 0 after 0 usecs
Oct 11 20:26:19 ryzen kernel: leds input7::scrolllock: PM: calling led_resume+0x0/0x50 @ 21508, parent: input7
Oct 11 20:26:19 ryzen kernel: leds input7::scrolllock: PM: led_resume+0x0/0x50 returned 0 after 0 usecs
Oct 11 20:26:19 ryzen kernel: leds input7::compose: PM: calling led_resume+0x0/0x50 @ 21508, parent: input7
Oct 11 20:26:19 ryzen kernel: leds input7::compose: PM: led_resume+0x0/0x50 returned 0 after 0 usecs
Oct 11 20:26:19 ryzen kernel: leds input7::kana: PM: calling led_resume+0x0/0x50 @ 21508, parent: input7
Oct 11 20:26:19 ryzen kernel: leds input7::kana: PM: led_resume+0x0/0x50 returned 0 after 0 usecs
Oct 11 20:26:19 ryzen kernel: input input8: PM: calling input_dev_resume+0x0/0x40 @ 21508, parent: 0003:29EA:0102.0007
Oct 11 20:26:19 ryzen kernel: input input8: PM: input_dev_resume+0x0/0x40 returned 0 after 0 usecs
Oct 11 20:26:19 ryzen kernel: input input9: PM: calling input_dev_resume+0x0/0x40 @ 21508, parent: 0003:29EA:0102.0007
Oct 11 20:26:19 ryzen kernel: input input9: PM: input_dev_resume+0x0/0x40 returned 0 after 0 usecs
Oct 11 20:26:19 ryzen kernel: usb 1-2.4: reset full-speed USB device number 9 using xhci_hcd
Oct 11 20:26:19 ryzen kernel: usb 1-2.4: PM: usb_dev_resume+0x0/0x20 returned 0 after 8118870 usecs
Oct 11 20:26:19 ryzen kernel: usb 1-2.3: reset full-speed USB device number 8 using xhci_hcd
Oct 11 20:26:19 ryzen kernel: usb 1-2.3: PM: usb_dev_resume+0x0/0x20 returned 0 after 8417421 usecs
Oct 11 20:26:19 ryzen kernel: input input10: PM: calling input_dev_resume+0x0/0x40 @ 21508, parent: 0003:046D:C092.0009
Oct 11 20:26:19 ryzen kernel: input input10: PM: input_dev_resume+0x0/0x40 returned 0 after 0 usecs
Oct 11 20:26:19 ryzen kernel: input input11: PM: calling input_dev_resume+0x0/0x40 @ 21508, parent: 0003:046D:C092.000A
Oct 11 20:26:19 ryzen kernel: input input11: PM: input_dev_resume+0x0/0x40 returned 0 after 0 usecs
Oct 11 20:26:19 ryzen kernel: sp5100-tco sp5100-tco: PM: calling platform_pm_resume+0x0/0x50 @ 21508, parent: platform
Oct 11 20:26:19 ryzen kernel: sp5100-tco sp5100-tco: PM: platform_pm_resume+0x0/0x50 returned 0 after 0 usecs
Oct 11 20:26:19 ryzen kernel: input input14: PM: calling input_dev_resume+0x0/0x40 @ 21508, parent: pcspkr
Oct 11 20:26:19 ryzen kernel: input input14: PM: input_dev_resume+0x0/0x40 returned 0 after 11 usecs
Oct 11 20:26:19 ryzen kernel: input input15: PM: calling input_dev_resume+0x0/0x40 @ 21508, parent: card1
Oct 11 20:26:19 ryzen kernel: input input15: PM: input_dev_resume+0x0/0x40 returned 0 after 0 usecs
Oct 11 20:26:19 ryzen kernel: input input16: PM: calling input_dev_resume+0x0/0x40 @ 21508, parent: card1
Oct 11 20:26:19 ryzen kernel: input input16: PM: input_dev_resume+0x0/0x40 returned 0 after 0 usecs
Oct 11 20:26:19 ryzen kernel: input input17: PM: calling input_dev_resume+0x0/0x40 @ 21508, parent: card1
Oct 11 20:26:19 ryzen kernel: input input17: PM: input_dev_resume+0x0/0x40 returned 0 after 0 usecs
Oct 11 20:26:19 ryzen kernel: input input18: PM: calling input_dev_resume+0x0/0x40 @ 21508, parent: card1
Oct 11 20:26:19 ryzen kernel: input input18: PM: input_dev_resume+0x0/0x40 returned 0 after 0 usecs
Oct 11 20:26:19 ryzen kernel: input input19: PM: calling input_dev_resume+0x0/0x40 @ 21508, parent: card1
Oct 11 20:26:19 ryzen kernel: input input19: PM: input_dev_resume+0x0/0x40 returned 0 after 0 usecs
Oct 11 20:26:19 ryzen kernel: input input20: PM: calling input_dev_resume+0x0/0x40 @ 21508, parent: card1
Oct 11 20:26:19 ryzen kernel: input input20: PM: input_dev_resume+0x0/0x40 returned 0 after 0 usecs
Oct 11 20:26:19 ryzen kernel: input input21: PM: calling input_dev_resume+0x0/0x40 @ 21508, parent: card2
Oct 11 20:26:19 ryzen kernel: input input21: PM: input_dev_resume+0x0/0x40 returned 0 after 0 usecs
Oct 11 20:26:19 ryzen kernel: input input22: PM: calling input_dev_resume+0x0/0x40 @ 21508, parent: card2
Oct 11 20:26:19 ryzen kernel: input input22: PM: input_dev_resume+0x0/0x40 returned 0 after 0 usecs
Oct 11 20:26:19 ryzen kernel: input input23: PM: calling input_dev_resume+0x0/0x40 @ 21508, parent: card2
Oct 11 20:26:19 ryzen kernel: input input23: PM: input_dev_resume+0x0/0x40 returned 0 after 0 usecs
Oct 11 20:26:19 ryzen kernel: input input24: PM: calling input_dev_resume+0x0/0x40 @ 21508, parent: card2
Oct 11 20:26:19 ryzen kernel: input input24: PM: input_dev_resume+0x0/0x40 returned 0 after 0 usecs
Oct 11 20:26:19 ryzen kernel: input input25: PM: calling input_dev_resume+0x0/0x40 @ 21508, parent: card2
Oct 11 20:26:19 ryzen kernel: input input25: PM: input_dev_resume+0x0/0x40 returned 0 after 0 usecs
Oct 11 20:26:19 ryzen kernel: Generic FE-GE Realtek PHY r8169-0-400:00: PM: calling mdio_bus_phy_resume+0x0/0x130 [libphy] @ 21508, parent: r8169-0-400
Oct 11 20:26:19 ryzen kernel: Generic FE-GE Realtek PHY r8169-0-400:00: PM: mdio_bus_phy_resume+0x0/0x130 [libphy] returned 0 after 0 usecs
Oct 11 20:26:19 ryzen kernel: intel_rapl_msr intel_rapl_msr.0: PM: calling platform_pm_resume+0x0/0x50 @ 21508, parent: platform
Oct 11 20:26:19 ryzen kernel: intel_rapl_msr intel_rapl_msr.0: PM: platform_pm_resume+0x0/0x50 returned 0 after 0 usecs
Oct 11 20:26:19 ryzen kernel: input input26: PM: calling input_dev_resume+0x0/0x40 @ 21508, parent: 0003:09EB:0131.000C
Oct 11 20:26:19 ryzen kernel: input input26: PM: input_dev_resume+0x0/0x40 returned 0 after 9 usecs
Oct 11 20:26:19 ryzen kernel: leds input26::numlock: PM: calling led_resume+0x0/0x50 @ 21508, parent: input26
Oct 11 20:26:19 ryzen kernel: leds input26::numlock: PM: led_resume+0x0/0x50 returned 0 after 0 usecs
Oct 11 20:26:19 ryzen kernel: leds input26::capslock: PM: calling led_resume+0x0/0x50 @ 21508, parent: input26
Oct 11 20:26:19 ryzen kernel: leds input26::capslock: PM: led_resume+0x0/0x50 returned 0 after 0 usecs
Oct 11 20:26:19 ryzen kernel: leds input26::scrolllock: PM: calling led_resume+0x0/0x50 @ 21508, parent: input26
Oct 11 20:26:19 ryzen kernel: leds input26::scrolllock: PM: led_resume+0x0/0x50 returned 0 after 0 usecs
Oct 11 20:26:19 ryzen kernel: leds input26::compose: PM: calling led_resume+0x0/0x50 @ 21508, parent: input26
Oct 11 20:26:19 ryzen kernel: leds input26::compose: PM: led_resume+0x0/0x50 returned 0 after 0 usecs
Oct 11 20:26:19 ryzen kernel: leds input26::kana: PM: calling led_resume+0x0/0x50 @ 21508, parent: input26
Oct 11 20:26:19 ryzen kernel: leds input26::kana: PM: led_resume+0x0/0x50 returned 0 after 0 usecs
Oct 11 20:26:19 ryzen kernel: input input27: PM: calling input_dev_resume+0x0/0x40 @ 21508, parent: 0003:09EB:0131.000D
Oct 11 20:26:19 ryzen kernel: input input27: PM: input_dev_resume+0x0/0x40 returned 0 after 0 usecs
Oct 11 20:26:19 ryzen kernel: input input28: PM: calling input_dev_resume+0x0/0x40 @ 21508, parent: 0003:09EB:0131.000D
Oct 11 20:26:19 ryzen kernel: input input28: PM: input_dev_resume+0x0/0x40 returned 0 after 0 usecs
Oct 11 20:26:19 ryzen kernel: input input29: PM: calling input_dev_resume+0x0/0x40 @ 21508, parent: 0003:09EB:0131.000D
Oct 11 20:26:19 ryzen kernel: input input29: PM: input_dev_resume+0x0/0x40 returned 0 after 0 usecs
Oct 11 20:26:19 ryzen kernel: input input30: PM: calling input_dev_resume+0x0/0x40 @ 21508, parent: 0003:046D:C016.000E
Oct 11 20:26:19 ryzen kernel: input input30: PM: input_dev_resume+0x0/0x40 returned 0 after 0 usecs
Oct 11 20:26:19 ryzen kernel: PM: resume of devices complete after 10538.245 msecs
Oct 11 20:26:19 ryzen kernel: OOM killer enabled.
Oct 11 20:26:19 ryzen kernel: Restarting tasks ... done.
Oct 11 20:26:19 ryzen kernel: random: crng reseeded on system resumption
Oct 11 20:26:19 ryzen kernel: PM: suspend exit
Oct 11 20:26:18 ryzen rtkit-daemon[1365]: The canary thread is apparently starving. Taking action.
Oct 11 20:26:18 ryzen systemd-sleep[21508]: System returned from sleep state.
Oct 11 20:26:18 ryzen rtkit-daemon[1365]: Demoting known real-time threads.
Oct 11 20:26:18 ryzen systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
Oct 11 20:26:18 ryzen rtkit-daemon[1365]: Successfully demoted thread 13924 of process 13715.
Oct 11 20:26:18 ryzen systemd-udevd[364]: /etc/udev/rules.d/30-usbtmc.rules:5 Unknown group 'usbtmc', ignoring.
Oct 11 20:26:18 ryzen rtkit-daemon[1365]: Successfully demoted thread 10555 of process 10197.
Oct 11 20:26:18 ryzen systemd-udevd[364]: /etc/udev/rules.d/30-usbtmc.rules:8 Unknown group 'usbtmc', ignoring.
Oct 11 20:26:18 ryzen rtkit-daemon[1365]: Successfully demoted thread 8886 of process 2726.
Oct 11 20:26:18 ryzen systemd-udevd[364]: /etc/udev/rules.d/30-usbtmc.rules:11 Unknown group 'usbtmc', ignoring.
Oct 11 20:26:18 ryzen rtkit-daemon[1365]: Demoted 3 threads.
Oct 11 20:26:18 ryzen systemd-udevd[364]: /etc/udev/rules.d/30-usbtmc.rules:14 Unknown group 'usbtmc', ignoring.
Oct 11 20:26:18 ryzen /usr/bin/gpm[827]: *** info [mice.c(1990)]:
Oct 11 20:26:18 ryzen systemd-udevd[364]: /etc/udev/rules.d/30-usbtmc.rules:15 Unknown group 'usbtmc', ignoring.
Oct 11 20:26:18 ryzen /usr/bin/gpm[827]: imps2: Auto-detected intellimouse PS/2
Oct 11 20:26:18 ryzen systemd-udevd[364]: /usr/lib/udev/rules.d/51-footcontroller.rules:10 Invalid value for OPTIONS key, ignoring: 'last_rule'
Oct 11 20:26:18 ryzen systemd[1]: systemd-suspend.service: Deactivated successfully.
Oct 11 20:26:19 ryzen systemd[1]: Finished System Suspend.
Oct 11 20:26:19 ryzen systemd[1]: systemd-suspend.service: Consumed 6.966s CPU time.
Oct 11 20:26:19 ryzen systemd[1]: Stopped target Sleep.
Oct 11 20:26:19 ryzen systemd[1]: Reached target Suspend.
Oct 11 20:26:19 ryzen systemd[1]: Stopped target Suspend.
Oct 11 20:26:19 ryzen systemd-logind[830]: Operation 'sleep' finished.
Oct 11 20:26:19 ryzen NetworkManager[927]: <info> [1697081179.9632] manager: sleep: wake requested (sleeping: yes enabled: yes)
Oct 11 20:26:19 ryzen NetworkManager[927]: <info> [1697081179.9633] device (enp4s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Oct 11 20:26:19 ryzen kernel: Generic FE-GE Realtek PHY r8169-0-400:00: attached PHY driver (mii_bus:phy_addr=r8169-0-400:00, irq=MAC)
Oct 11 20:26:20 ryzen NetworkManager[927]: <info> [1697081180.1946] manager: NetworkManager state is now CONNECTED_LOCAL
Oct 11 20:26:20 ryzen kernel: r8169 0000:04:00.0 enp4s0: Link is Down
Oct 11 20:26:20 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 20:26:20 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 20:26:20 ryzen kernel: snd_hda_codec_hdmi hdaudioC1D0: HDMI: Unknown ELD version 0
Oct 11 20:26:20 ryzen dbus-daemon[824]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.306' (uid=1001 pid=21392 comm="/usr/lib/kscreenlocker_greet --graceTime 5000 --ks")
Oct 11 20:26:20 ryzen dbus-daemon[824]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.
Oct 11 20:26:22 ryzen NetworkManager[927]: <info> [1697081182.8578] device (enp4s0): carrier: link connected
Oct 11 20:26:22 ryzen NetworkManager[927]: <info> [1697081182.8580] device (enp4s0): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed')
Oct 11 20:26:22 ryzen NetworkManager[927]: <info> [1697081182.8586] policy: auto-activating connection 'Wired connection 1' (1a78b687-138e-3a66-9ca0-dc365ee4d000)
Oct 11 20:26:22 ryzen NetworkManager[927]: <info> [1697081182.8588] device (enp4s0): Activation: starting connection 'Wired connection 1' (1a78b687-138e-3a66-9ca0-dc365ee4d000)
Oct 11 20:26:22 ryzen NetworkManager[927]: <info> [1697081182.8589] device (enp4s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Oct 11 20:26:22 ryzen NetworkManager[927]: <info> [1697081182.8590] manager: NetworkManager state is now CONNECTING
Oct 11 20:26:22 ryzen NetworkManager[927]: <info> [1697081182.8591] device (enp4s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Oct 11 20:26:22 ryzen NetworkManager[927]: <info> [1697081182.8594] device (enp4s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Oct 11 20:26:22 ryzen NetworkManager[927]: <info> [1697081182.8598] dhcp4 (enp4s0): activation: beginning transaction (timeout in 45 seconds)
Oct 11 20:26:22 ryzen kernel: r8169 0000:04:00.0 enp4s0: Link is Up - 1Gbps/Full - flow control rx/tx
Oct 11 20:26:22 ryzen dnsmasq[1089]: reading /etc/resolv.conf
Oct 11 20:26:22 ryzen dnsmasq[1089]: using nameserver 1.1.1.1#53
Oct 11 20:26:22 ryzen dnsmasq[1056]: reading /etc/resolv.conf
Oct 11 20:26:22 ryzen dnsmasq[1056]: using nameserver 1.1.1.1#53
Oct 11 20:26:22 ryzen NetworkManager[927]: <info> [1697081182.8667] dhcp4 (enp4s0): state changed new lease, address=192.168.0.91
Oct 11 20:26:22 ryzen NetworkManager[927]: <info> [1697081182.8669] policy: set 'Wired connection 1' (enp4s0) as default for IPv4 routing and DNS
Oct 11 20:26:22 ryzen dnsmasq[1089]: reading /etc/resolv.conf
Oct 11 20:26:22 ryzen dnsmasq[1056]: reading /etc/resolv.conf
Oct 11 20:26:22 ryzen dnsmasq[1089]: using nameserver 1.1.1.1#53
Oct 11 20:26:22 ryzen dnsmasq[1089]: using nameserver 8.8.8.8#53
Oct 11 20:26:22 ryzen dnsmasq[1056]: using nameserver 1.1.1.1#53
Oct 11 20:26:22 ryzen dnsmasq[1056]: using nameserver 8.8.8.8#53
Oct 11 20:26:22 ryzen avahi-daemon[823]: Joining mDNS multicast group on interface enp4s0.IPv4 with address 192.168.0.91.
Oct 11 20:26:22 ryzen avahi-daemon[823]: New relevant interface enp4s0.IPv4 for mDNS.
Oct 11 20:26:22 ryzen avahi-daemon[823]: Registering new address record for 192.168.0.91 on enp4s0.IPv4.
Oct 11 20:26:22 ryzen avahi-daemon[823]: Joining mDNS multicast group on interface enp4s0.IPv6 with address fe80::1b36:1dd4:a5cf:3b8f.
Oct 11 20:26:22 ryzen avahi-daemon[823]: New relevant interface enp4s0.IPv6 for mDNS.
Oct 11 20:26:22 ryzen avahi-daemon[823]: Registering new address record for fe80::1b36:1dd4:a5cf:3b8f on enp4s0.*.
Oct 11 20:26:22 ryzen dbus-daemon[824]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.4' (uid=0 pid=927 comm="/usr/bin/NetworkManager --no-daemon")
Oct 11 20:26:22 ryzen NetworkManager[927]: <info> [1697081182.8802] device (enp4s0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Oct 11 20:26:22 ryzen systemd[1]: Starting Network Manager Script Dispatcher Service...
Oct 11 20:26:22 ryzen dbus-daemon[824]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Oct 11 20:26:22 ryzen systemd[1]: Started Network Manager Script Dispatcher Service.
Oct 11 20:26:22 ryzen NetworkManager[927]: <info> [1697081182.9188] device (enp4s0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Oct 11 20:26:22 ryzen NetworkManager[927]: <info> [1697081182.9189] device (enp4s0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Oct 11 20:26:22 ryzen NetworkManager[927]: <info> [1697081182.9193] manager: NetworkManager state is now CONNECTED_SITE
Oct 11 20:26:22 ryzen NetworkManager[927]: <info> [1697081182.9196] device (enp4s0): Activation: successful, device activated.
Oct 11 20:26:23 ryzen NetworkManager[927]: <info> [1697081183.6298] manager: NetworkManager state is now CONNECTED_GLOBAL
Oct 11 20:26:24 ryzen NetworkManager[927]: <info> [1697081184.2437] dhcp6 (enp4s0): activation: beginning transaction (timeout in 45 seconds)
Oct 11 20:26:24 ryzen dnsmasq[1089]: reading /etc/resolv.conf
Oct 11 20:26:24 ryzen dnsmasq[1056]: reading /etc/resolv.conf
Oct 11 20:26:24 ryzen dnsmasq[1089]: using nameserver 1.1.1.1#53
Oct 11 20:26:24 ryzen dnsmasq[1089]: using nameserver 8.8.8.8#53
Oct 11 20:26:24 ryzen dnsmasq[1089]: using nameserver fde3:5408:101c::1#53
Oct 11 20:26:24 ryzen dnsmasq[1056]: using nameserver 1.1.1.1#53
Oct 11 20:26:24 ryzen dnsmasq[1056]: using nameserver 8.8.8.8#53
Oct 11 20:26:24 ryzen dnsmasq[1056]: using nameserver fde3:5408:101c::1#53
Oct 11 20:26:24 ryzen avahi-daemon[823]: Leaving mDNS multicast group on interface enp4s0.IPv6 with address fe80::1b36:1dd4:a5cf:3b8f.
Oct 11 20:26:24 ryzen avahi-daemon[823]: Joining mDNS multicast group on interface enp4s0.IPv6 with address fde3:5408:101c:0:7441:9d56:d3c1:1a95.
Oct 11 20:26:24 ryzen NetworkManager[927]: <info> [1697081184.2502] dhcp6 (enp4s0): state changed new lease, address=fde3:5408:101c::566
Oct 11 20:26:24 ryzen avahi-daemon[823]: Registering new address record for fde3:5408:101c:0:7441:9d56:d3c1:1a95 on enp4s0.*.
Oct 11 20:26:24 ryzen avahi-daemon[823]: Withdrawing address record for fe80::1b36:1dd4:a5cf:3b8f on enp4s0.
Oct 11 20:26:24 ryzen avahi-daemon[823]: Registering new address record for fde3:5408:101c::566 on enp4s0.*.
Oct 11 20:26:27 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 20:26:27 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 20:26:32 ryzen systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
Oct 11 20:27:11 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 20:27:11 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 20:28:47 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 20:28:47 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 20:28:51 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 20:28:51 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 20:32:45 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 20:32:45 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 20:34:08 ryzen kernel: sched: RT throttling activated
Oct 11 20:37:34 ryzen kernel: usb 1-3: new full-speed USB device number 13 using xhci_hcd
Oct 11 20:37:35 ryzen kernel: usb 1-3: New USB device found, idVendor=413c, idProduct=1004, bcdDevice=48.00
Oct 11 20:37:35 ryzen kernel: usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Oct 11 20:37:35 ryzen kernel: usb 1-3: Product: Dell USB Keyboard Hub
Oct 11 20:37:35 ryzen kernel: usb 1-3: Manufacturer: Dell
Oct 11 20:37:35 ryzen systemd-udevd[364]: /etc/udev/rules.d/30-usbtmc.rules:5 Unknown group 'usbtmc', ignoring.
Oct 11 20:37:35 ryzen systemd-udevd[364]: /etc/udev/rules.d/30-usbtmc.rules:8 Unknown group 'usbtmc', ignoring.
Oct 11 20:37:35 ryzen systemd-udevd[364]: /etc/udev/rules.d/30-usbtmc.rules:11 Unknown group 'usbtmc', ignoring.
Oct 11 20:37:35 ryzen systemd-udevd[364]: /etc/udev/rules.d/30-usbtmc.rules:14 Unknown group 'usbtmc', ignoring.
Oct 11 20:37:35 ryzen systemd-udevd[364]: /etc/udev/rules.d/30-usbtmc.rules:15 Unknown group 'usbtmc', ignoring.
Oct 11 20:37:35 ryzen systemd-udevd[364]: /usr/lib/udev/rules.d/51-footcontroller.rules:10 Invalid value for OPTIONS key, ignoring: 'last_rule'
Oct 11 20:37:35 ryzen kernel: hub 1-3:1.0: USB hub found
Oct 11 20:37:35 ryzen kernel: hub 1-3:1.0: 3 ports detected
Oct 11 20:37:35 ryzen kernel: usb 1-3.1: new low-speed USB device number 14 using xhci_hcd
Oct 11 20:37:35 ryzen kernel: usb 1-3.1: New USB device found, idVendor=413c, idProduct=2006, bcdDevice=48.00
Oct 11 20:37:35 ryzen kernel: usb 1-3.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Oct 11 20:37:35 ryzen kernel: usb 1-3.1: Product: Dell USB Keyboard Hub
Oct 11 20:37:35 ryzen kernel: usb 1-3.1: Manufacturer: Dell
Oct 11 20:37:35 ryzen kernel: input: Dell Dell USB Keyboard Hub as /devices/pci0000:00/0000:00:01.2/0000:02:00.0/usb1/1-3/1-3.1/1-3.1:1.0/0003:413C:2006.000F/input/input31
Oct 11 20:37:35 ryzen kernel: hid-generic 0003:413C:2006.000F: input,hidraw14: USB HID v1.10 Keyboard [Dell Dell USB Keyboard Hub] on usb-0000:02:00.0-3.1/input0
Oct 11 20:37:35 ryzen kernel: input: Dell Dell USB Keyboard Hub Consumer Control as /devices/pci0000:00/0000:00:01.2/0000:02:00.0/usb1/1-3/1-3.1/1-3.1:1.1/0003:413C:2006.0010/input/input32
Oct 11 20:37:35 ryzen kernel: input: Dell Dell USB Keyboard Hub System Control as /devices/pci0000:00/0000:00:01.2/0000:02:00.0/usb1/1-3/1-3.1/1-3.1:1.1/0003:413C:2006.0010/input/input33
Oct 11 20:37:35 ryzen kernel: hid-generic 0003:413C:2006.0010: input,hidraw15: USB HID v1.10 Device [Dell Dell USB Keyboard Hub] on usb-0000:02:00.0-3.1/input1
Oct 11 20:37:35 ryzen mtp-probe[23247]: checking bus 1, device 14: "/sys/devices/pci0000:00/0000:00:01.2/0000:02:00.0/usb1/1-3/1-3.1"
Oct 11 20:37:35 ryzen mtp-probe[23247]: bus: 1, device: 14 was not an MTP device
Oct 11 20:37:35 ryzen systemd-logind[830]: Watching system buttons on /dev/input/event29 (Dell Dell USB Keyboard Hub)
Oct 11 20:37:35 ryzen systemd-logind[830]: Watching system buttons on /dev/input/event31 (Dell Dell USB Keyboard Hub System Control)
Oct 11 20:37:35 ryzen mtp-probe[23295]: checking bus 1, device 14: "/sys/devices/pci0000:00/0000:00:01.2/0000:02:00.0/usb1/1-3/1-3.1"
Oct 11 20:37:35 ryzen mtp-probe[23295]: bus: 1, device: 14 was not an MTP device
Oct 11 20:39:36 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 20:39:36 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 20:45:00 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 20:45:00 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 20:45:26 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 20:45:26 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 20:48:34 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 20:48:34 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 20:49:59 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 20:49:59 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 20:50:26 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 20:50:26 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 20:50:46 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 20:50:46 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 20:50:46 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 20:50:46 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 20:50:46 ryzen rtkit-daemon[1365]: Successfully made thread 24443 of process 24190 owned by '1001' RT at priority 10.
Oct 11 20:50:46 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 20:50:47 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 20:50:47 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 20:51:02 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 20:51:02 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 20:51:05 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 1 users.
Oct 11 20:51:05 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 1 users.
Oct 11 20:52:26 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 20:52:26 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 20:52:26 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 20:52:26 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 20:52:26 ryzen rtkit-daemon[1365]: Successfully made thread 24703 of process 24513 owned by '1001' RT at priority 10.
Oct 11 20:52:26 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 20:52:26 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 20:52:26 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 20:52:26 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 20:52:26 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 20:53:48 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 20:53:48 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 21:00:15 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 21:00:15 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 21:00:17 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 21:00:17 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 21:00:27 ryzen systemd-timesyncd[815]: Contacted time server 104.194.8.227:123 (0.arch.pool.ntp.org).
Oct 11 21:15:35 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 21:15:35 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 21:19:21 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 21:19:21 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 21:19:21 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 21:19:21 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 21:20:26 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 21:20:26 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 21:24:25 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 21:24:25 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 21:24:44 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 21:24:44 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 21:24:44 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 21:24:44 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 21:24:44 ryzen rtkit-daemon[1365]: Successfully made thread 27327 of process 25193 owned by '1001' RT at priority 10.
Oct 11 21:24:44 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 21:26:07 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 21:26:07 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 21:26:07 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 21:26:07 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 21:26:08 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 21:26:08 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 21:26:12 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 21:26:12 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 21:26:12 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 21:26:12 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 21:26:12 ryzen rtkit-daemon[1365]: Successfully made thread 27738 of process 27211 owned by '1001' RT at priority 10.
Oct 11 21:26:12 ryzen rtkit-daemon[1365]: Supervising 2 threads of 2 processes of 1 users.
Oct 11 21:26:38 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 21:26:38 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 21:26:38 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 21:26:38 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 21:26:38 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 21:26:38 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 21:26:38 ryzen rtkit-daemon[1365]: Successfully made thread 27901 of process 27619 owned by '1001' RT at priority 10.
Oct 11 21:26:38 ryzen rtkit-daemon[1365]: Supervising 2 threads of 2 processes of 1 users.
Oct 11 21:29:31 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 21:29:31 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 21:32:04 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 21:32:04 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 21:37:00 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 21:37:00 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 21:41:50 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 21:41:50 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 21:42:09 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 21:42:09 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 21:42:30 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 21:42:30 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 21:44:46 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 21:44:46 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 21:45:09 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 21:45:09 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 21:45:38 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 21:45:38 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 21:45:47 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 21:45:47 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 21:46:07 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 21:46:07 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 21:47:49 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 21:47:49 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 21:49:21 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 21:49:21 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 21:49:28 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 21:49:28 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 21:52:20 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 21:52:20 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 21:52:20 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 21:52:20 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 21:52:22 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 21:52:22 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 21:54:17 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 21:54:17 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 21:54:30 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 21:54:30 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 21:57:15 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 21:57:15 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 21:57:26 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 21:57:26 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 21:57:48 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 21:57:48 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 22:02:12 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 22:02:12 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 22:07:41 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 22:07:41 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 22:07:44 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 22:07:44 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 22:23:46 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 22:23:46 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 22:23:56 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 22:23:56 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 22:24:25 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 22:24:25 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 22:24:27 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 22:24:27 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 22:31:35 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 22:31:35 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 22:31:43 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 22:31:43 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 22:34:31 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 22:34:31 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 22:36:54 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 22:36:54 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 22:36:57 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 22:36:57 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 22:37:29 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 22:37:29 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 22:37:32 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 22:37:32 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 22:38:06 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 22:38:06 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 22:38:06 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 22:38:06 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 22:38:06 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 22:38:06 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 22:38:06 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 22:38:06 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 22:38:06 ryzen rtkit-daemon[1365]: Successfully made thread 34706 of process 34459 owned by '1001' RT at priority 10.
Oct 11 22:38:06 ryzen rtkit-daemon[1365]: Supervising 2 threads of 2 processes of 1 users.
Oct 11 22:40:02 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 22:40:02 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 22:40:13 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 22:40:13 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 22:42:48 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 22:42:48 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 22:42:53 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 22:42:53 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 22:44:53 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 22:44:53 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 22:45:40 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 22:45:40 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 22:46:11 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 22:46:11 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 22:47:00 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 22:47:00 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 22:48:56 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 22:48:56 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 22:48:59 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 22:48:59 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 22:51:08 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 22:51:08 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 22:53:36 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 22:53:36 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 22:53:39 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 22:53:39 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 22:54:55 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 22:54:55 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 22:55:21 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 22:55:21 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 11 23:11:10 ryzen systemd-logind[830]: The system will suspend now!
Oct 11 23:11:10 ryzen NetworkManager[927]: <info> [1697091070.8260] manager: sleep: sleep requested (sleeping: no enabled: yes)
Oct 11 23:11:10 ryzen dbus-daemon[824]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.4' (uid=0 pid=927 comm="/usr/bin/NetworkManager --no-daemon")
Oct 11 23:11:10 ryzen NetworkManager[927]: <info> [1697091070.8261] manager: NetworkManager state is now ASLEEP
Oct 11 23:11:10 ryzen NetworkManager[927]: <info> [1697091070.8262] device (enp4s0): state change: activated -> deactivating (reason 'sleeping', sys-iface-state: 'managed')
Oct 11 23:11:10 ryzen systemd[1]: Starting Network Manager Script Dispatcher Service...
Oct 11 23:11:10 ryzen dbus-daemon[824]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Oct 11 23:11:10 ryzen systemd[1]: Started Network Manager Script Dispatcher Service.
Oct 11 23:11:10 ryzen NetworkManager[927]: <info> [1697091070.8680] device (enp4s0): state change: deactivating -> disconnected (reason 'sleeping', sys-iface-state: 'managed')
Oct 11 23:11:10 ryzen avahi-daemon[823]: Withdrawing address record for fde3:5408:101c::566 on enp4s0.
Oct 11 23:11:10 ryzen avahi-daemon[823]: Withdrawing address record for fde3:5408:101c:0:7441:9d56:d3c1:1a95 on enp4s0.
Oct 11 23:11:10 ryzen NetworkManager[927]: <info> [1697091070.8695] dhcp4 (enp4s0): canceled DHCP transaction
Oct 11 23:11:10 ryzen avahi-daemon[823]: Leaving mDNS multicast group on interface enp4s0.IPv6 with address fde3:5408:101c:0:7441:9d56:d3c1:1a95.
Oct 11 23:11:10 ryzen NetworkManager[927]: <info> [1697091070.8695] dhcp4 (enp4s0): activation: beginning transaction (timeout in 45 seconds)
Oct 11 23:11:10 ryzen avahi-daemon[823]: Joining mDNS multicast group on interface enp4s0.IPv6 with address fe80::1b36:1dd4:a5cf:3b8f.
Oct 11 23:11:10 ryzen NetworkManager[927]: <info> [1697091070.8695] dhcp4 (enp4s0): state changed no lease
Oct 11 23:11:10 ryzen avahi-daemon[823]: Registering new address record for fe80::1b36:1dd4:a5cf:3b8f on enp4s0.*.
Oct 11 23:11:10 ryzen NetworkManager[927]: <info> [1697091070.8696] dhcp6 (enp4s0): canceled DHCP transaction
Oct 11 23:11:10 ryzen avahi-daemon[823]: Withdrawing address record for fe80::1b36:1dd4:a5cf:3b8f on enp4s0.
Oct 11 23:11:10 ryzen NetworkManager[927]: <info> [1697091070.8696] dhcp6 (enp4s0): activation: beginning transaction (timeout in 45 seconds)
Oct 11 23:11:10 ryzen avahi-daemon[823]: Leaving mDNS multicast group on interface enp4s0.IPv6 with address fe80::1b36:1dd4:a5cf:3b8f.
Oct 11 23:11:10 ryzen NetworkManager[927]: <info> [1697091070.8696] dhcp6 (enp4s0): state changed no lease
Oct 11 23:11:10 ryzen avahi-daemon[823]: Interface enp4s0.IPv6 no longer relevant for mDNS.
Oct 11 23:11:10 ryzen dnsmasq[1089]: no servers found in /etc/resolv.conf, will retry
Oct 11 23:11:10 ryzen dnsmasq[1056]: no servers found in /etc/resolv.conf, will retry
Oct 11 23:11:10 ryzen avahi-daemon[823]: Withdrawing address record for 192.168.0.91 on enp4s0.
Oct 11 23:11:10 ryzen avahi-daemon[823]: Leaving mDNS multicast group on interface enp4s0.IPv4 with address 192.168.0.91.
Oct 11 23:11:10 ryzen avahi-daemon[823]: Interface enp4s0.IPv4 no longer relevant for mDNS.
Oct 11 23:11:10 ryzen NetworkManager[927]: <info> [1697091070.9100] device (enp4s0): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Oct 11 23:11:10 ryzen kernel: r8169 0000:04:00.0 enp4s0: Link is Down
Oct 11 23:11:10 ryzen systemd[1]: Reached target Sleep.
Oct 11 23:11:10 ryzen systemd[1]: Starting System Suspend...
Oct 11 23:11:10 ryzen systemd-sleep[36842]: Entering sleep state 'suspend'...
Oct 11 23:11:10 ryzen kernel: PM: suspend entry (deep)
Oct 11 23:11:10 ryzen kernel: Filesystems sync: 0.054 seconds
Oct 11 23:11:10 ryzen kernel: Freezing user space processes
Oct 11 23:21:42 ryzen kernel: Freezing user space processes completed (elapsed 0.128 seconds)
Oct 11 23:21:42 ryzen kernel: OOM killer disabled.
Oct 11 23:21:42 ryzen kernel: Freezing remaining freezable tasks
Oct 11 23:21:42 ryzen kernel: Freezing remaining freezable tasks completed (elapsed 0.001 seconds)
Oct 11 23:21:42 ryzen kernel: input input33: PM: calling input_dev_suspend+0x0/0x70 @ 36842, parent: 0003:413C:2006.0010
Oct 11 23:21:42 ryzen kernel: input input33: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: input input32: PM: calling input_dev_suspend+0x0/0x70 @ 36842, parent: 0003:413C:2006.0010
Oct 11 23:21:42 ryzen kernel: input input32: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: leds input31::kana: PM: calling led_suspend+0x0/0x50 @ 36842, parent: input31
Oct 11 23:21:42 ryzen kernel: leds input31::kana: PM: led_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: leds input31::compose: PM: calling led_suspend+0x0/0x50 @ 36842, parent: input31
Oct 11 23:21:42 ryzen kernel: leds input31::compose: PM: led_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: leds input31::scrolllock: PM: calling led_suspend+0x0/0x50 @ 36842, parent: input31
Oct 11 23:21:42 ryzen kernel: leds input31::scrolllock: PM: led_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: leds input31::capslock: PM: calling led_suspend+0x0/0x50 @ 36842, parent: input31
Oct 11 23:21:42 ryzen kernel: leds input31::capslock: PM: led_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: leds input31::numlock: PM: calling led_suspend+0x0/0x50 @ 36842, parent: input31
Oct 11 23:21:42 ryzen kernel: leds input31::numlock: PM: led_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: input input31: PM: calling input_dev_suspend+0x0/0x70 @ 36842, parent: 0003:413C:2006.000F
Oct 11 23:21:42 ryzen kernel: input input31: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: usb 1-3.1: PM: calling usb_dev_suspend+0x0/0x20 @ 26010, parent: 1-3
Oct 11 23:21:42 ryzen kernel: input input30: PM: calling input_dev_suspend+0x0/0x70 @ 36842, parent: 0003:046D:C016.000E
Oct 11 23:21:42 ryzen kernel: input input30: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: input input29: PM: calling input_dev_suspend+0x0/0x70 @ 36842, parent: 0003:09EB:0131.000D
Oct 11 23:21:42 ryzen kernel: input input29: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: input input28: PM: calling input_dev_suspend+0x0/0x70 @ 36842, parent: 0003:09EB:0131.000D
Oct 11 23:21:42 ryzen kernel: input input28: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: input input27: PM: calling input_dev_suspend+0x0/0x70 @ 36842, parent: 0003:09EB:0131.000D
Oct 11 23:21:42 ryzen kernel: usb 1-1.4: PM: calling usb_dev_suspend+0x0/0x20 @ 33848, parent: 1-1
Oct 11 23:21:42 ryzen kernel: input input27: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: leds input26::kana: PM: calling led_suspend+0x0/0x50 @ 36842, parent: input26
Oct 11 23:21:42 ryzen kernel: leds input26::kana: PM: led_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: leds input26::compose: PM: calling led_suspend+0x0/0x50 @ 36842, parent: input26
Oct 11 23:21:42 ryzen kernel: leds input26::compose: PM: led_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: leds input26::scrolllock: PM: calling led_suspend+0x0/0x50 @ 36842, parent: input26
Oct 11 23:21:42 ryzen kernel: leds input26::scrolllock: PM: led_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: leds input26::capslock: PM: calling led_suspend+0x0/0x50 @ 36842, parent: input26
Oct 11 23:21:42 ryzen kernel: leds input26::capslock: PM: led_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: leds input26::numlock: PM: calling led_suspend+0x0/0x50 @ 36842, parent: input26
Oct 11 23:21:42 ryzen kernel: leds input26::numlock: PM: led_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: input input26: PM: calling input_dev_suspend+0x0/0x70 @ 36842, parent: 0003:09EB:0131.000C
Oct 11 23:21:42 ryzen kernel: input input26: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: usb 1-1.1: PM: calling usb_dev_suspend+0x0/0x20 @ 33485, parent: 1-1
Oct 11 23:21:42 ryzen kernel: intel_rapl_msr intel_rapl_msr.0: PM: calling platform_pm_suspend+0x0/0x50 @ 36842, parent: platform
Oct 11 23:21:42 ryzen kernel: intel_rapl_msr intel_rapl_msr.0: PM: platform_pm_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: Generic FE-GE Realtek PHY r8169-0-400:00: PM: calling mdio_bus_phy_suspend+0x0/0x120 [libphy] @ 36842, parent: r8169-0-400
Oct 11 23:21:42 ryzen kernel: Generic FE-GE Realtek PHY r8169-0-400:00: PM: mdio_bus_phy_suspend+0x0/0x120 [libphy] returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: sound pcmC3D0c: PM: calling do_pcm_suspend+0x0/0x30 [snd_pcm] @ 36842, parent: card3
Oct 11 23:21:42 ryzen kernel: sound pcmC3D0c: PM: do_pcm_suspend+0x0/0x30 [snd_pcm] returned 0 after 2 usecs
Oct 11 23:21:42 ryzen kernel: sound pcmC3D0p: PM: calling do_pcm_suspend+0x0/0x30 [snd_pcm] @ 36842, parent: card3
Oct 11 23:21:42 ryzen kernel: sound pcmC3D0p: PM: do_pcm_suspend+0x0/0x30 [snd_pcm] returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: sound pcmC0D1p: PM: calling do_pcm_suspend+0x0/0x30 [snd_pcm] @ 36842, parent: card0
Oct 11 23:21:42 ryzen kernel: sound pcmC0D1p: PM: do_pcm_suspend+0x0/0x30 [snd_pcm] returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: sound pcmC0D0c: PM: calling do_pcm_suspend+0x0/0x30 [snd_pcm] @ 36842, parent: card0
Oct 11 23:21:42 ryzen kernel: sound pcmC0D0c: PM: do_pcm_suspend+0x0/0x30 [snd_pcm] returned 0 after 1 usecs
Oct 11 23:21:42 ryzen kernel: sound pcmC0D0p: PM: calling do_pcm_suspend+0x0/0x30 [snd_pcm] @ 36842, parent: card0
Oct 11 23:21:42 ryzen kernel: sound pcmC0D0p: PM: do_pcm_suspend+0x0/0x30 [snd_pcm] returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: input input25: PM: calling input_dev_suspend+0x0/0x70 @ 36842, parent: card2
Oct 11 23:21:42 ryzen kernel: input input25: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: input input24: PM: calling input_dev_suspend+0x0/0x70 @ 36842, parent: card2
Oct 11 23:21:42 ryzen kernel: input input24: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: input input23: PM: calling input_dev_suspend+0x0/0x70 @ 36842, parent: card2
Oct 11 23:21:42 ryzen kernel: input input23: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: input input22: PM: calling input_dev_suspend+0x0/0x70 @ 36842, parent: card2
Oct 11 23:21:42 ryzen kernel: input input22: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: input input21: PM: calling input_dev_suspend+0x0/0x70 @ 36842, parent: card2
Oct 11 23:21:42 ryzen kernel: input input21: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: sound pcmC2D2c: PM: calling do_pcm_suspend+0x0/0x30 [snd_pcm] @ 36842, parent: card2
Oct 11 23:21:42 ryzen kernel: sound pcmC2D2c: PM: do_pcm_suspend+0x0/0x30 [snd_pcm] returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: sound pcmC2D0c: PM: calling do_pcm_suspend+0x0/0x30 [snd_pcm] @ 36842, parent: card2
Oct 11 23:21:42 ryzen kernel: sound pcmC2D0c: PM: do_pcm_suspend+0x0/0x30 [snd_pcm] returned 0 after 49 usecs
Oct 11 23:21:42 ryzen kernel: sound pcmC2D0p: PM: calling do_pcm_suspend+0x0/0x30 [snd_pcm] @ 36842, parent: card2
Oct 11 23:21:42 ryzen kernel: sound pcmC2D0p: PM: do_pcm_suspend+0x0/0x30 [snd_pcm] returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: input input20: PM: calling input_dev_suspend+0x0/0x70 @ 36842, parent: card1
Oct 11 23:21:42 ryzen kernel: input input20: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: input input19: PM: calling input_dev_suspend+0x0/0x70 @ 36842, parent: card1
Oct 11 23:21:42 ryzen kernel: input input19: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: input input18: PM: calling input_dev_suspend+0x0/0x70 @ 36842, parent: card1
Oct 11 23:21:42 ryzen kernel: input input18: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: input input17: PM: calling input_dev_suspend+0x0/0x70 @ 36842, parent: card1
Oct 11 23:21:42 ryzen kernel: input input17: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: input input16: PM: calling input_dev_suspend+0x0/0x70 @ 36842, parent: card1
Oct 11 23:21:42 ryzen kernel: snd_hda_codec_realtek hdaudioC2D0: PM: calling hda_codec_pm_suspend+0x0/0x20 [snd_hda_codec] @ 23656, parent: 0000:07:00.4
Oct 11 23:21:42 ryzen kernel: input input16: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: input input15: PM: calling input_dev_suspend+0x0/0x70 @ 36842, parent: card1
Oct 11 23:21:42 ryzen kernel: input input15: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: sound pcmC1D11p: PM: calling do_pcm_suspend+0x0/0x30 [snd_pcm] @ 36842, parent: card1
Oct 11 23:21:42 ryzen kernel: sound pcmC1D11p: PM: do_pcm_suspend+0x0/0x30 [snd_pcm] returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: sound pcmC1D10p: PM: calling do_pcm_suspend+0x0/0x30 [snd_pcm] @ 36842, parent: card1
Oct 11 23:21:42 ryzen kernel: sound pcmC1D10p: PM: do_pcm_suspend+0x0/0x30 [snd_pcm] returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: sound pcmC1D9p: PM: calling do_pcm_suspend+0x0/0x30 [snd_pcm] @ 36842, parent: card1
Oct 11 23:21:42 ryzen kernel: sound pcmC1D9p: PM: do_pcm_suspend+0x0/0x30 [snd_pcm] returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: sound pcmC1D8p: PM: calling do_pcm_suspend+0x0/0x30 [snd_pcm] @ 36842, parent: card1
Oct 11 23:21:42 ryzen kernel: sound pcmC1D8p: PM: do_pcm_suspend+0x0/0x30 [snd_pcm] returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: sound pcmC1D7p: PM: calling do_pcm_suspend+0x0/0x30 [snd_pcm] @ 36842, parent: card1
Oct 11 23:21:42 ryzen kernel: sound pcmC1D7p: PM: do_pcm_suspend+0x0/0x30 [snd_pcm] returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: sound pcmC1D3p: PM: calling do_pcm_suspend+0x0/0x30 [snd_pcm] @ 36842, parent: card1
Oct 11 23:21:42 ryzen kernel: sound pcmC1D3p: PM: do_pcm_suspend+0x0/0x30 [snd_pcm] returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: input input14: PM: calling input_dev_suspend+0x0/0x70 @ 36842, parent: pcspkr
Oct 11 23:21:42 ryzen kernel: input input14: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: sp5100-tco sp5100-tco: PM: calling platform_pm_suspend+0x0/0x50 @ 36842, parent: platform
Oct 11 23:21:42 ryzen kernel: sp5100-tco sp5100-tco: PM: platform_pm_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: input input11: PM: calling input_dev_suspend+0x0/0x70 @ 36842, parent: 0003:046D:C092.000A
Oct 11 23:21:42 ryzen kernel: input input11: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: usb 1-2.4: PM: calling usb_dev_suspend+0x0/0x20 @ 32851, parent: 1-2
Oct 11 23:21:42 ryzen kernel: input input10: PM: calling input_dev_suspend+0x0/0x70 @ 36842, parent: 0003:046D:C092.0009
Oct 11 23:21:42 ryzen kernel: input input10: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: usb 1-2.4: PM: usb_dev_suspend+0x0/0x20 returned 0 after 5 usecs
Oct 11 23:21:42 ryzen kernel: input input9: PM: calling input_dev_suspend+0x0/0x70 @ 36842, parent: 0003:29EA:0102.0007
Oct 11 23:21:42 ryzen kernel: input input9: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: input input8: PM: calling input_dev_suspend+0x0/0x70 @ 36842, parent: 0003:29EA:0102.0007
Oct 11 23:21:42 ryzen kernel: input input8: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: leds input7::kana: PM: calling led_suspend+0x0/0x50 @ 36842, parent: input7
Oct 11 23:21:42 ryzen kernel: usb 1-2.3: PM: calling usb_dev_suspend+0x0/0x20 @ 32851, parent: 1-2
Oct 11 23:21:42 ryzen kernel: leds input7::kana: PM: led_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: leds input7::compose: PM: calling led_suspend+0x0/0x50 @ 36842, parent: input7
Oct 11 23:21:42 ryzen kernel: leds input7::compose: PM: led_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: leds input7::scrolllock: PM: calling led_suspend+0x0/0x50 @ 36842, parent: input7
Oct 11 23:21:42 ryzen kernel: leds input7::scrolllock: PM: led_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: leds input7::capslock: PM: calling led_suspend+0x0/0x50 @ 36842, parent: input7
Oct 11 23:21:42 ryzen kernel: usb 1-10: PM: calling usb_dev_suspend+0x0/0x20 @ 35357, parent: usb1
Oct 11 23:21:42 ryzen kernel: leds input7::capslock: PM: led_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: leds input7::numlock: PM: calling led_suspend+0x0/0x50 @ 36842, parent: input7
Oct 11 23:21:42 ryzen kernel: leds input7::numlock: PM: led_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: usb 1-10: PM: usb_dev_suspend+0x0/0x20 returned 0 after 4 usecs
Oct 11 23:21:42 ryzen kernel: input input7: PM: calling input_dev_suspend+0x0/0x70 @ 36842, parent: 0003:29EA:0102.0006
Oct 11 23:21:42 ryzen kernel: input input7: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: input input6: PM: calling input_dev_suspend+0x0/0x70 @ 36842, parent: 0003:29EA:0102.0005
Oct 11 23:21:42 ryzen kernel: input input6: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: usb 1-2.2: PM: calling usb_dev_suspend+0x0/0x20 @ 36860, parent: 1-2
Oct 11 23:21:42 ryzen kernel: usb 1-7: PM: calling usb_dev_suspend+0x0/0x20 @ 35357, parent: usb1
Oct 11 23:21:42 ryzen kernel: input input5: PM: calling input_dev_suspend+0x0/0x70 @ 36842, parent: 0003:0ECB:2057.0003
Oct 11 23:21:42 ryzen kernel: input input5: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: usb 1-7: PM: usb_dev_suspend+0x0/0x20 returned 0 after 4 usecs
Oct 11 23:21:42 ryzen kernel: input input4: PM: calling input_dev_suspend+0x0/0x70 @ 36842, parent: 0003:05F3:00FF.0002
Oct 11 23:21:42 ryzen kernel: input input4: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: sd 6:0:0:0: PM: calling scsi_bus_suspend+0x0/0xc0 @ 35357, parent: target6:0:0
Oct 11 23:21:42 ryzen kernel: input input3: PM: calling input_dev_suspend+0x0/0x70 @ 36842, parent: 0003:1852:7022.0001
Oct 11 23:21:42 ryzen kernel: input input3: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: leds input2::scrolllock: PM: calling led_suspend+0x0/0x50 @ 36842, parent: input2
Oct 11 23:21:42 ryzen kernel: leds input2::scrolllock: PM: led_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: leds input2::capslock: PM: calling led_suspend+0x0/0x50 @ 36842, parent: input2
Oct 11 23:21:42 ryzen kernel: leds input2::capslock: PM: led_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: leds input2::numlock: PM: calling led_suspend+0x0/0x50 @ 36842, parent: input2
Oct 11 23:21:42 ryzen kernel: leds input2::numlock: PM: led_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: input input2: PM: calling input_dev_suspend+0x0/0x70 @ 36842, parent: serio0
Oct 11 23:21:42 ryzen kernel: input input2: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: usb 1-2.1: PM: calling usb_dev_suspend+0x0/0x20 @ 36862, parent: 1-2
Oct 11 23:21:42 ryzen kernel: atkbd serio0: PM: calling serio_suspend+0x0/0x50 [serio] @ 36842, parent: i8042
Oct 11 23:21:42 ryzen kernel: usb 1-5: PM: calling usb_dev_suspend+0x0/0x20 @ 36863, parent: usb1
Oct 11 23:21:42 ryzen kernel: usb 3-2: PM: calling usb_dev_suspend+0x0/0x20 @ 36867, parent: usb3
Oct 11 23:21:42 ryzen kernel: usb usb4: PM: calling usb_dev_suspend+0x0/0x20 @ 36869, parent: 0000:07:00.3
Oct 11 23:21:42 ryzen kernel: usb 3-2: PM: usb_dev_suspend+0x0/0x20 returned 0 after 107 usecs
Oct 11 23:21:42 ryzen kernel: usb 1-1.4: PM: usb_dev_suspend+0x0/0x20 returned 0 after 814 usecs
Oct 11 23:21:42 ryzen kernel: usb usb3: PM: calling usb_dev_suspend+0x0/0x20 @ 36870, parent: 0000:07:00.3
Oct 11 23:21:42 ryzen kernel: usb 1-5: PM: usb_dev_suspend+0x0/0x20 returned 0 after 1881 usecs
Oct 11 23:21:42 ryzen kernel: atkbd serio0: PM: serio_suspend+0x0/0x50 [serio] returned 0 after 2822 usecs
Oct 11 23:21:42 ryzen kernel: usb 1-2.3: PM: usb_dev_suspend+0x0/0x20 returned 0 after 2966 usecs
Oct 11 23:21:42 ryzen kernel: i8042 i8042: PM: calling platform_pm_suspend+0x0/0x50 @ 36842, parent: platform
Oct 11 23:21:42 ryzen kernel: i8042 i8042: PM: platform_pm_suspend+0x0/0x50 returned 0 after 74 usecs
Oct 11 23:21:42 ryzen kernel: sr 1:0:0:0: PM: calling scsi_bus_suspend+0x0/0xc0 @ 32851, parent: target1:0:0
Oct 11 23:21:42 ryzen kernel: platform microcode: PM: calling platform_pm_suspend+0x0/0x50 @ 36842, parent: platform
Oct 11 23:21:42 ryzen kernel: platform microcode: PM: platform_pm_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: sd 0:0:0:0: PM: calling scsi_bus_suspend+0x0/0xc0 @ 36874, parent: target0:0:0
Oct 11 23:21:42 ryzen kernel: alarmtimer alarmtimer.0.auto: PM: calling platform_pm_suspend+0x0/0x50 @ 36842, parent: rtc0
Oct 11 23:21:42 ryzen kernel: alarmtimer alarmtimer.0.auto: PM: platform_pm_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: rtc rtc0: PM: calling rtc_suspend+0x0/0x1f0 @ 36842, parent: 00:02
Oct 11 23:21:42 ryzen kernel: rtc rtc0: PM: rtc_suspend+0x0/0x1f0 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: scsi host5: PM: calling scsi_bus_suspend+0x0/0xc0 @ 33848, parent: ata6
Oct 11 23:21:42 ryzen kernel: scsi host5: PM: scsi_bus_suspend+0x0/0xc0 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: scsi host4: PM: calling scsi_bus_suspend+0x0/0xc0 @ 33848, parent: ata5
Oct 11 23:21:42 ryzen kernel: scsi host4: PM: scsi_bus_suspend+0x0/0xc0 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: scsi host3: PM: calling scsi_bus_suspend+0x0/0xc0 @ 33848, parent: ata4
Oct 11 23:21:42 ryzen kernel: port serial8250:0.31: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 36842, parent: serial8250:0
Oct 11 23:21:42 ryzen kernel: scsi host3: PM: scsi_bus_suspend+0x0/0xc0 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: port serial8250:0.31: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: scsi host2: PM: calling scsi_bus_suspend+0x0/0xc0 @ 33848, parent: ata3
Oct 11 23:21:42 ryzen kernel: scsi host2: PM: scsi_bus_suspend+0x0/0xc0 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: port serial8250:0.30: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 36842, parent: serial8250:0
Oct 11 23:21:42 ryzen kernel: port serial8250:0.30: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: port serial8250:0.29: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 36842, parent: serial8250:0
Oct 11 23:21:42 ryzen kernel: port serial8250:0.29: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: port serial8250:0.28: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 36842, parent: serial8250:0
Oct 11 23:21:42 ryzen kernel: port serial8250:0.28: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: port serial8250:0.27: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 36842, parent: serial8250:0
Oct 11 23:21:42 ryzen kernel: ata6: PM: calling ata_port_pm_suspend+0x0/0x50 @ 36875, parent: 0000:02:00.1
Oct 11 23:21:42 ryzen kernel: port serial8250:0.27: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: port serial8250:0.26: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 36842, parent: serial8250:0
Oct 11 23:21:42 ryzen kernel: port serial8250:0.26: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: port serial8250:0.25: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 36842, parent: serial8250:0
Oct 11 23:21:42 ryzen kernel: port serial8250:0.25: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: port serial8250:0.24: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 36842, parent: serial8250:0
Oct 11 23:21:42 ryzen kernel: port serial8250:0.24: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: ata5: PM: calling ata_port_pm_suspend+0x0/0x50 @ 36876, parent: 0000:02:00.1
Oct 11 23:21:42 ryzen kernel: port serial8250:0.23: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 36842, parent: serial8250:0
Oct 11 23:21:42 ryzen kernel: ata6: PM: ata_port_pm_suspend+0x0/0x50 returned 0 after 26 usecs
Oct 11 23:21:42 ryzen kernel: port serial8250:0.23: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: port serial8250:0.22: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 36842, parent: serial8250:0
Oct 11 23:21:42 ryzen kernel: ata4: PM: calling ata_port_pm_suspend+0x0/0x50 @ 36875, parent: 0000:02:00.1
Oct 11 23:21:42 ryzen kernel: port serial8250:0.22: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: port serial8250:0.21: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 36842, parent: serial8250:0
Oct 11 23:21:42 ryzen kernel: port serial8250:0.21: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: ata5: PM: ata_port_pm_suspend+0x0/0x50 returned 0 after 23 usecs
Oct 11 23:21:42 ryzen kernel: port serial8250:0.20: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 36842, parent: serial8250:0
Oct 11 23:21:42 ryzen kernel: ata3: PM: calling ata_port_pm_suspend+0x0/0x50 @ 36877, parent: 0000:02:00.1
Oct 11 23:21:42 ryzen kernel: port serial8250:0.20: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: port serial8250:0.19: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 36842, parent: serial8250:0
Oct 11 23:21:42 ryzen kernel: port serial8250:0.19: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: ata4: PM: ata_port_pm_suspend+0x0/0x50 returned 0 after 27 usecs
Oct 11 23:21:42 ryzen kernel: port serial8250:0.18: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 36842, parent: serial8250:0
Oct 11 23:21:42 ryzen kernel: port serial8250:0.18: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: port serial8250:0.17: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 36842, parent: serial8250:0
Oct 11 23:21:42 ryzen kernel: port serial8250:0.17: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: ata3: PM: ata_port_pm_suspend+0x0/0x50 returned 0 after 24 usecs
Oct 11 23:21:42 ryzen kernel: port serial8250:0.16: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 36842, parent: serial8250:0
Oct 11 23:21:42 ryzen kernel: port serial8250:0.16: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: port serial8250:0.15: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 36842, parent: serial8250:0
Oct 11 23:21:42 ryzen kernel: port serial8250:0.15: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: port serial8250:0.14: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 36842, parent: serial8250:0
Oct 11 23:21:42 ryzen kernel: port serial8250:0.14: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: port serial8250:0.13: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 36842, parent: serial8250:0
Oct 11 23:21:42 ryzen kernel: port serial8250:0.13: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: port serial8250:0.12: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 36842, parent: serial8250:0
Oct 11 23:21:42 ryzen kernel: usb 1-2.1: PM: usb_dev_suspend+0x0/0x20 returned 0 after 3145 usecs
Oct 11 23:21:42 ryzen kernel: port serial8250:0.12: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: port serial8250:0.11: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 36842, parent: serial8250:0
Oct 11 23:21:42 ryzen kernel: port serial8250:0.11: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: port serial8250:0.10: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 36842, parent: serial8250:0
Oct 11 23:21:42 ryzen kernel: port serial8250:0.10: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: port serial8250:0.9: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 36842, parent: serial8250:0
Oct 11 23:21:42 ryzen kernel: port serial8250:0.9: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: port serial8250:0.8: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 36842, parent: serial8250:0
Oct 11 23:21:42 ryzen kernel: port serial8250:0.8: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: port serial8250:0.7: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 36842, parent: serial8250:0
Oct 11 23:21:42 ryzen kernel: port serial8250:0.7: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: port serial8250:0.6: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 36842, parent: serial8250:0
Oct 11 23:21:42 ryzen kernel: port serial8250:0.6: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: port serial8250:0.5: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 36842, parent: serial8250:0
Oct 11 23:21:42 ryzen kernel: port serial8250:0.5: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: port serial8250:0.4: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 36842, parent: serial8250:0
Oct 11 23:21:42 ryzen kernel: port serial8250:0.4: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: port serial8250:0.3: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 36842, parent: serial8250:0
Oct 11 23:21:42 ryzen kernel: port serial8250:0.3: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: port serial8250:0.2: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 36842, parent: serial8250:0
Oct 11 23:21:42 ryzen kernel: port serial8250:0.2: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: port serial8250:0.1: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 36842, parent: serial8250:0
Oct 11 23:21:42 ryzen kernel: port serial8250:0.1: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: serial8250 serial8250: PM: calling platform_pm_suspend+0x0/0x50 @ 36842, parent: platform
Oct 11 23:21:42 ryzen kernel: serial8250 serial8250: PM: platform_pm_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: port 00:05:0.0: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 36842, parent: 00:05:0
Oct 11 23:21:42 ryzen kernel: port 00:05:0.0: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: input input1: PM: calling input_dev_suspend+0x0/0x70 @ 36842, parent: LNXPWRBN:00
Oct 11 23:21:42 ryzen kernel: input input1: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: input input0: PM: calling input_dev_suspend+0x0/0x70 @ 36842, parent: PNP0C0C:00
Oct 11 23:21:42 ryzen kernel: input input0: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: pcspkr pcspkr: PM: calling platform_pm_suspend+0x0/0x50 @ 36842, parent: platform
Oct 11 23:21:42 ryzen kernel: pcspkr pcspkr: PM: platform_pm_suspend+0x0/0x50 returned 0 after 7 usecs
Oct 11 23:21:42 ryzen kernel: snd_hda_intel 0000:05:00.1: PM: calling pci_pm_suspend+0x0/0x170 @ 36878, parent: 0000:00:03.1
Oct 11 23:21:42 ryzen kernel: system 00:06: PM: calling pnp_bus_suspend+0x0/0x20 @ 36842, parent: pnp0
Oct 11 23:21:42 ryzen kernel: system 00:06: PM: pnp_bus_suspend+0x0/0x20 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: serial 00:05: PM: calling pnp_bus_suspend+0x0/0x20 @ 36842, parent: pnp0
Oct 11 23:21:42 ryzen kernel: serial 00:05: PM: pnp_bus_suspend+0x0/0x20 returned 0 after 4 usecs
Oct 11 23:21:42 ryzen kernel: i8042 kbd 00:04: PM: calling pnp_bus_suspend+0x0/0x20 @ 36842, parent: pnp0
Oct 11 23:21:42 ryzen kernel: i8042 kbd 00:04: PM: pnp_bus_suspend+0x0/0x20 returned 0 after 52 usecs
Oct 11 23:21:42 ryzen kernel: system 00:03: PM: calling pnp_bus_suspend+0x0/0x20 @ 36842, parent: pnp0
Oct 11 23:21:42 ryzen kernel: system 00:03: PM: pnp_bus_suspend+0x0/0x20 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: rtc_cmos 00:02: PM: calling pnp_bus_suspend+0x0/0x20 @ 36842, parent: pnp0
Oct 11 23:21:42 ryzen kernel: rtc_cmos 00:02: PM: pnp_bus_suspend+0x0/0x20 returned 0 after 26 usecs
Oct 11 23:21:42 ryzen kernel: system 00:01: PM: calling pnp_bus_suspend+0x0/0x20 @ 36842, parent: pnp0
Oct 11 23:21:42 ryzen kernel: system 00:01: PM: pnp_bus_suspend+0x0/0x20 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: system 00:00: PM: calling pnp_bus_suspend+0x0/0x20 @ 36842, parent: pnp0
Oct 11 23:21:42 ryzen kernel: system 00:00: PM: pnp_bus_suspend+0x0/0x20 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: platform efivars.0: PM: calling platform_pm_suspend+0x0/0x50 @ 36842, parent: platform
Oct 11 23:21:42 ryzen kernel: platform efivars.0: PM: platform_pm_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: platform rtc-efi.0: PM: calling platform_pm_suspend+0x0/0x50 @ 36842, parent: platform
Oct 11 23:21:42 ryzen kernel: platform rtc-efi.0: PM: platform_pm_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: button LNXPWRBN:00: PM: calling acpi_button_suspend+0x0/0x20 @ 36842, parent: LNXSYSTM:00
Oct 11 23:21:42 ryzen kernel: button LNXPWRBN:00: PM: acpi_button_suspend+0x0/0x20 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: acpi-wmi PNP0C14:01: PM: calling acpi_subsys_suspend+0x0/0x60 @ 36842, parent: platform
Oct 11 23:21:42 ryzen kernel: acpi-wmi PNP0C14:01: PM: acpi_subsys_suspend+0x0/0x60 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: acpi-wmi PNP0C14:00: PM: calling acpi_subsys_suspend+0x0/0x60 @ 36842, parent: platform
Oct 11 23:21:42 ryzen kernel: acpi-wmi PNP0C14:00: PM: acpi_subsys_suspend+0x0/0x60 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: platform PNP0103:00: PM: calling platform_pm_suspend+0x0/0x50 @ 36842, parent: platform
Oct 11 23:21:42 ryzen kernel: platform PNP0103:00: PM: platform_pm_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: pt-gpio AMDIF030:00: PM: calling acpi_subsys_suspend+0x0/0x60 @ 36842, parent: platform
Oct 11 23:21:42 ryzen kernel: pt-gpio AMDIF030:00: PM: acpi_subsys_suspend+0x0/0x60 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: acpi-cpufreq acpi-cpufreq: PM: calling platform_pm_suspend+0x0/0x50 @ 36842, parent: platform
Oct 11 23:21:42 ryzen kernel: acpi-cpufreq acpi-cpufreq: PM: platform_pm_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: platform MSFT0101:00: PM: calling platform_pm_suspend+0x0/0x50 @ 36842, parent: platform
Oct 11 23:21:42 ryzen kernel: platform MSFT0101:00: PM: platform_pm_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: amd_gpio AMDI0030:00: PM: calling acpi_subsys_suspend+0x0/0x60 @ 36842, parent: platform
Oct 11 23:21:42 ryzen kernel: amd_gpio AMDI0030:00: PM: acpi_subsys_suspend+0x0/0x60 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: platform PNP0C0C:00: PM: calling platform_pm_suspend+0x0/0x50 @ 36842, parent: platform
Oct 11 23:21:42 ryzen kernel: platform PNP0C0C:00: PM: platform_pm_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: platform PNP0800:00: PM: calling platform_pm_suspend+0x0/0x50 @ 36842, parent: 0000:00:14.3
Oct 11 23:21:42 ryzen kernel: platform PNP0800:00: PM: platform_pm_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: thermal LNXTHERM:01: PM: calling acpi_thermal_suspend+0x0/0x20 @ 36842, parent: LNXSYBUS:01
Oct 11 23:21:42 ryzen kernel: thermal LNXTHERM:01: PM: acpi_thermal_suspend+0x0/0x20 returned 0 after 2 usecs
Oct 11 23:21:42 ryzen kernel: thermal LNXTHERM:00: PM: calling acpi_thermal_suspend+0x0/0x20 @ 36842, parent: LNXSYBUS:01
Oct 11 23:21:42 ryzen kernel: ccp 0000:07:00.1: PM: calling pci_pm_suspend+0x0/0x170 @ 36862, parent: 0000:00:08.1
Oct 11 23:21:42 ryzen kernel: thermal LNXTHERM:00: PM: acpi_thermal_suspend+0x0/0x20 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: ccp 0000:07:00.1: PM: pci_pm_suspend+0x0/0x170 returned 0 after 1 usecs
Oct 11 23:21:42 ryzen kernel: pci 0000:07:00.0: PM: calling pci_pm_suspend+0x0/0x170 @ 36862, parent: 0000:00:08.1
Oct 11 23:21:42 ryzen kernel: pci 0000:07:00.0: PM: pci_pm_suspend+0x0/0x170 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: pci 0000:06:00.0: PM: calling pci_pm_suspend+0x0/0x170 @ 36862, parent: 0000:00:07.1
Oct 11 23:21:42 ryzen kernel: pci 0000:06:00.0: PM: pci_pm_suspend+0x0/0x170 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: r8169 0000:04:00.0: PM: calling pci_pm_suspend+0x0/0x170 @ 36880, parent: 0000:03:09.0
Oct 11 23:21:42 ryzen kernel: tpm_crb MSFT0101:00: PM: calling tpm_pm_suspend+0x0/0xd0 @ 36842, parent: LNXSYBUS:00
Oct 11 23:21:42 ryzen kernel: r8169 0000:04:00.0: PM: pci_pm_suspend+0x0/0x170 returned 0 after 1 usecs
Oct 11 23:21:42 ryzen kernel: pcieport 0000:03:09.0: PM: calling pci_pm_suspend+0x0/0x170 @ 36880, parent: 0000:02:00.2
Oct 11 23:21:42 ryzen kernel: pcieport 0000:03:09.0: PM: pci_pm_suspend+0x0/0x170 returned 0 after 1 usecs
Oct 11 23:21:42 ryzen kernel: pcieport 0000:02:00.2: PM: calling pci_pm_suspend+0x0/0x170 @ 36880, parent: 0000:00:01.2
Oct 11 23:21:42 ryzen kernel: pcieport 0000:02:00.2: PM: pci_pm_suspend+0x0/0x170 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: nvme 0000:01:00.0: PM: calling pci_pm_suspend+0x0/0x170 @ 36882, parent: 0000:00:01.1
Oct 11 23:21:42 ryzen kernel: pci 0000:00:18.7: PM: calling pci_pm_suspend+0x0/0x170 @ 36883, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pci 0000:00:18.7: PM: pci_pm_suspend+0x0/0x170 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: pci 0000:00:18.6: PM: calling pci_pm_suspend+0x0/0x170 @ 36883, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pci 0000:00:18.6: PM: pci_pm_suspend+0x0/0x170 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: pci 0000:00:18.5: PM: calling pci_pm_suspend+0x0/0x170 @ 36883, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pci 0000:00:18.5: PM: pci_pm_suspend+0x0/0x170 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: pci 0000:00:18.4: PM: calling pci_pm_suspend+0x0/0x170 @ 36883, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: k10temp 0000:00:18.3: PM: calling pci_pm_suspend+0x0/0x170 @ 36884, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pci 0000:00:18.4: PM: pci_pm_suspend+0x0/0x170 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: pci 0000:00:18.2: PM: calling pci_pm_suspend+0x0/0x170 @ 36883, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: k10temp 0000:00:18.3: PM: pci_pm_suspend+0x0/0x170 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: pci 0000:00:18.2: PM: pci_pm_suspend+0x0/0x170 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: pci 0000:00:18.1: PM: calling pci_pm_suspend+0x0/0x170 @ 36884, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pci 0000:00:18.0: PM: calling pci_pm_suspend+0x0/0x170 @ 36883, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pci 0000:00:18.1: PM: pci_pm_suspend+0x0/0x170 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: pci 0000:00:18.0: PM: pci_pm_suspend+0x0/0x170 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: pci 0000:00:14.3: PM: calling pci_pm_suspend+0x0/0x170 @ 36883, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: piix4_smbus 0000:00:14.0: PM: calling pci_pm_suspend+0x0/0x170 @ 36884, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pci 0000:00:14.3: PM: pci_pm_suspend+0x0/0x170 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: piix4_smbus 0000:00:14.0: PM: pci_pm_suspend+0x0/0x170 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: pci 0000:00:08.0: PM: calling pci_pm_suspend+0x0/0x170 @ 36883, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pcieport 0000:00:07.1: PM: calling pci_pm_suspend+0x0/0x170 @ 36884, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pci 0000:00:08.0: PM: pci_pm_suspend+0x0/0x170 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: pci 0000:00:07.0: PM: calling pci_pm_suspend+0x0/0x170 @ 36883, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pcieport 0000:00:07.1: PM: pci_pm_suspend+0x0/0x170 returned 0 after 3 usecs
Oct 11 23:21:42 ryzen kernel: pci 0000:00:07.0: PM: pci_pm_suspend+0x0/0x170 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: pci 0000:00:05.0: PM: calling pci_pm_suspend+0x0/0x170 @ 36884, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pci 0000:00:04.0: PM: calling pci_pm_suspend+0x0/0x170 @ 36883, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pci 0000:00:04.0: PM: pci_pm_suspend+0x0/0x170 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: pci 0000:00:05.0: PM: pci_pm_suspend+0x0/0x170 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: pci 0000:00:03.0: PM: calling pci_pm_suspend+0x0/0x170 @ 36883, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pci 0000:00:02.0: PM: calling pci_pm_suspend+0x0/0x170 @ 36884, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pci 0000:00:03.0: PM: pci_pm_suspend+0x0/0x170 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: pci 0000:00:02.0: PM: pci_pm_suspend+0x0/0x170 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: pci 0000:00:01.0: PM: calling pci_pm_suspend+0x0/0x170 @ 36887, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pci 0000:00:01.0: PM: pci_pm_suspend+0x0/0x170 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: pci 0000:00:00.2: PM: calling pci_pm_suspend+0x0/0x170 @ 36887, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pci 0000:00:00.2: PM: pci_pm_suspend+0x0/0x170 returned 0 after 1 usecs
Oct 11 23:21:42 ryzen kernel: pci 0000:00:00.0: PM: calling pci_pm_suspend+0x0/0x170 @ 36887, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pci 0000:00:00.0: PM: pci_pm_suspend+0x0/0x170 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: usb usb3: PM: usb_dev_suspend+0x0/0x20 returned 0 after 8927 usecs
Oct 11 23:21:42 ryzen kernel: snd_hda_codec_realtek hdaudioC2D0: PM: hda_codec_pm_suspend+0x0/0x20 [snd_hda_codec] returned 0 after 17122 usecs
Oct 11 23:21:42 ryzen kernel: snd_hda_intel 0000:07:00.4: PM: calling pci_pm_suspend+0x0/0x170 @ 36879, parent: 0000:00:08.1
Oct 11 23:21:42 ryzen kernel: snd_hda_intel 0000:05:00.1: PM: pci_pm_suspend+0x0/0x170 returned 0 after 14344 usecs
Oct 11 23:21:42 ryzen kernel: amdgpu 0000:05:00.0: PM: calling pci_pm_suspend+0x0/0x170 @ 36862, parent: 0000:00:03.1
Oct 11 23:21:42 ryzen kernel: snd_hda_intel 0000:07:00.4: PM: pci_pm_suspend+0x0/0x170 returned 0 after 1072 usecs
Oct 11 23:21:42 ryzen kernel: sd 6:0:0:0: PM: scsi_bus_suspend+0x0/0xc0 returned 0 after 19173 usecs
Oct 11 23:21:42 ryzen kernel: scsi target6:0:0: PM: calling scsi_bus_suspend+0x0/0xc0 @ 36861, parent: host6
Oct 11 23:21:42 ryzen kernel: scsi target6:0:0: PM: scsi_bus_suspend+0x0/0xc0 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: scsi host6: PM: calling scsi_bus_suspend+0x0/0xc0 @ 36864, parent: 2-4:1.0
Oct 11 23:21:42 ryzen kernel: scsi host6: PM: scsi_bus_suspend+0x0/0xc0 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: usb 2-4: PM: calling usb_dev_suspend+0x0/0x20 @ 36866, parent: usb2
Oct 11 23:21:42 ryzen kernel: usb 1-3.1: PM: usb_dev_suspend+0x0/0x20 returned 0 after 23077 usecs
Oct 11 23:21:42 ryzen kernel: usb 1-3: PM: calling usb_dev_suspend+0x0/0x20 @ 36846, parent: usb1
Oct 11 23:21:42 ryzen kernel: usb usb4: PM: usb_dev_suspend+0x0/0x20 returned 0 after 25674 usecs
Oct 11 23:21:42 ryzen kernel: xhci_hcd 0000:07:00.3: PM: calling pci_pm_suspend+0x0/0x170 @ 36877, parent: 0000:00:08.1
Oct 11 23:21:42 ryzen kernel: xhci_hcd 0000:07:00.3: PM: pci_pm_suspend+0x0/0x170 returned 0 after 163 usecs
Oct 11 23:21:42 ryzen kernel: pcieport 0000:00:08.1: PM: calling pci_pm_suspend+0x0/0x170 @ 36885, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pcieport 0000:00:08.1: PM: pci_pm_suspend+0x0/0x170 returned 0 after 2 usecs
Oct 11 23:21:42 ryzen kernel: usb 1-2.2: PM: usb_dev_suspend+0x0/0x20 returned 0 after 29186 usecs
Oct 11 23:21:42 ryzen kernel: usb 1-2: PM: calling usb_dev_suspend+0x0/0x20 @ 36868, parent: usb1
Oct 11 23:21:42 ryzen kernel: usb 1-1.1: PM: usb_dev_suspend+0x0/0x20 returned 0 after 32998 usecs
Oct 11 23:21:42 ryzen kernel: usb 1-1: PM: calling usb_dev_suspend+0x0/0x20 @ 36817, parent: usb1
Oct 11 23:21:42 ryzen kernel: tpm_crb MSFT0101:00: PM: tpm_pm_suspend+0x0/0xd0 returned 0 after 28875 usecs
Oct 11 23:21:42 ryzen kernel: button PNP0C0C:00: PM: calling acpi_button_suspend+0x0/0x20 @ 36842, parent: LNXSYBUS:00
Oct 11 23:21:42 ryzen kernel: button PNP0C0C:00: PM: acpi_button_suspend+0x0/0x20 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: PCCT PCCT: PM: calling platform_pm_suspend+0x0/0x50 @ 36842, parent: platform
Oct 11 23:21:42 ryzen kernel: PCCT PCCT: PM: platform_pm_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: regulator regulator.0: PM: calling regulator_suspend+0x0/0x120 @ 36842, parent: reg-dummy
Oct 11 23:21:42 ryzen kernel: regulator regulator.0: PM: regulator_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: reg-dummy reg-dummy: PM: calling platform_pm_suspend+0x0/0x50 @ 36842, parent: platform
Oct 11 23:21:42 ryzen kernel: reg-dummy reg-dummy: PM: platform_pm_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: sr 1:0:0:0: PM: scsi_bus_suspend+0x0/0xc0 returned 0 after 36214 usecs
Oct 11 23:21:42 ryzen kernel: scsi target1:0:0: PM: calling scsi_bus_suspend+0x0/0xc0 @ 36863, parent: host1
Oct 11 23:21:42 ryzen kernel: scsi target1:0:0: PM: scsi_bus_suspend+0x0/0xc0 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Oct 11 23:21:42 ryzen kernel: scsi host1: PM: calling scsi_bus_suspend+0x0/0xc0 @ 36867, parent: ata2
Oct 11 23:21:42 ryzen kernel: scsi host1: PM: scsi_bus_suspend+0x0/0xc0 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: ata2: PM: calling ata_port_pm_suspend+0x0/0x50 @ 36876, parent: 0000:02:00.1
Oct 11 23:21:42 ryzen kernel: ata2: PM: ata_port_pm_suspend+0x0/0x50 returned 0 after 25 usecs
Oct 11 23:21:42 ryzen kernel: sd 0:0:0:0: [sda] Stopping disk
Oct 11 23:21:42 ryzen kernel: usb 2-4: PM: usb_dev_suspend+0x0/0x20 returned 0 after 23282 usecs
Oct 11 23:21:42 ryzen kernel: usb usb2: PM: calling usb_dev_suspend+0x0/0x20 @ 36871, parent: 0000:02:00.0
Oct 11 23:21:42 ryzen kernel: usb usb2: PM: usb_dev_suspend+0x0/0x20 returned 0 after 11 usecs
Oct 11 23:21:42 ryzen kernel: usb 1-3: PM: usb_dev_suspend+0x0/0x20 returned 0 after 33316 usecs
Oct 11 23:21:42 ryzen kernel: usb 1-2: PM: usb_dev_suspend+0x0/0x20 returned 0 after 33313 usecs
Oct 11 23:21:42 ryzen kernel: usb 1-1: PM: usb_dev_suspend+0x0/0x20 returned 0 after 33336 usecs
Oct 11 23:21:42 ryzen kernel: usb usb1: PM: calling usb_dev_suspend+0x0/0x20 @ 36872, parent: 0000:02:00.0
Oct 11 23:21:42 ryzen kernel: usb usb1: PM: usb_dev_suspend+0x0/0x20 returned 0 after 9960 usecs
Oct 11 23:21:42 ryzen kernel: xhci_hcd 0000:02:00.0: PM: calling pci_pm_suspend+0x0/0x170 @ 36880, parent: 0000:00:01.2
Oct 11 23:21:42 ryzen kernel: xhci_hcd 0000:02:00.0: PM: pci_pm_suspend+0x0/0x170 returned 0 after 1133 usecs
Oct 11 23:21:42 ryzen kernel: amdgpu 0000:05:00.0: PM: pci_pm_suspend+0x0/0x170 returned 0 after 256416 usecs
Oct 11 23:21:42 ryzen kernel: pcieport 0000:00:03.1: PM: calling pci_pm_suspend+0x0/0x170 @ 36886, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pcieport 0000:00:03.1: PM: pci_pm_suspend+0x0/0x170 returned 0 after 2 usecs
Oct 11 23:21:42 ryzen kernel: sd 0:0:0:0: PM: scsi_bus_suspend+0x0/0xc0 returned 0 after 445940 usecs
Oct 11 23:21:42 ryzen kernel: scsi target0:0:0: PM: calling scsi_bus_suspend+0x0/0xc0 @ 36873, parent: host0
Oct 11 23:21:42 ryzen kernel: scsi target0:0:0: PM: scsi_bus_suspend+0x0/0xc0 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: scsi host0: PM: calling scsi_bus_suspend+0x0/0xc0 @ 33848, parent: ata1
Oct 11 23:21:42 ryzen kernel: scsi host0: PM: scsi_bus_suspend+0x0/0xc0 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: ata1: PM: calling ata_port_pm_suspend+0x0/0x50 @ 36875, parent: 0000:02:00.1
Oct 11 23:21:42 ryzen kernel: ata1: PM: ata_port_pm_suspend+0x0/0x50 returned 0 after 36 usecs
Oct 11 23:21:42 ryzen kernel: ahci 0000:02:00.1: PM: calling pci_pm_suspend+0x0/0x170 @ 36881, parent: 0000:00:01.2
Oct 11 23:21:42 ryzen kernel: ahci 0000:02:00.1: PM: pci_pm_suspend+0x0/0x170 returned 0 after 2 usecs
Oct 11 23:21:42 ryzen kernel: pcieport 0000:00:01.2: PM: calling pci_pm_suspend+0x0/0x170 @ 36883, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pcieport 0000:00:01.2: PM: pci_pm_suspend+0x0/0x170 returned 0 after 2 usecs
Oct 11 23:21:42 ryzen kernel: nvme 0000:01:00.0: PM: pci_pm_suspend+0x0/0x170 returned 0 after 458165 usecs
Oct 11 23:21:42 ryzen kernel: pcieport 0000:00:01.1: PM: calling pci_pm_suspend+0x0/0x170 @ 36884, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pcieport 0000:00:01.1: PM: pci_pm_suspend+0x0/0x170 returned 0 after 5 usecs
Oct 11 23:21:42 ryzen kernel: PM: suspend of devices complete after 462.909 msecs
Oct 11 23:21:42 ryzen kernel: PM: start suspend of devices complete after 3418.473 msecs
Oct 11 23:21:42 ryzen kernel: snd_hda_intel 0000:05:00.1: PM: calling pci_pm_suspend_late+0x0/0x40 @ 36881, parent: 0000:00:03.1
Oct 11 23:21:42 ryzen kernel: snd_hda_intel 0000:05:00.1: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: acpi-wmi PNP0C14:01: PM: calling acpi_subsys_suspend_late+0x0/0x50 @ 36842, parent: platform
Oct 11 23:21:42 ryzen kernel: acpi-wmi PNP0C14:01: PM: acpi_subsys_suspend_late+0x0/0x50 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: acpi-wmi PNP0C14:00: PM: calling acpi_subsys_suspend_late+0x0/0x50 @ 36842, parent: platform
Oct 11 23:21:42 ryzen kernel: acpi-wmi PNP0C14:00: PM: acpi_subsys_suspend_late+0x0/0x50 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: pt-gpio AMDIF030:00: PM: calling acpi_subsys_suspend_late+0x0/0x50 @ 36842, parent: platform
Oct 11 23:21:42 ryzen kernel: pt-gpio AMDIF030:00: PM: acpi_subsys_suspend_late+0x0/0x50 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: amd_gpio AMDI0030:00: PM: calling acpi_subsys_suspend_late+0x0/0x50 @ 36842, parent: platform
Oct 11 23:21:42 ryzen kernel: amd_gpio AMDI0030:00: PM: acpi_subsys_suspend_late+0x0/0x50 returned 0 after 8 usecs
Oct 11 23:21:42 ryzen kernel: snd_hda_intel 0000:07:00.4: PM: calling pci_pm_suspend_late+0x0/0x40 @ 36881, parent: 0000:00:08.1
Oct 11 23:21:42 ryzen kernel: snd_hda_intel 0000:07:00.4: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: xhci_hcd 0000:07:00.3: PM: calling pci_pm_suspend_late+0x0/0x40 @ 36881, parent: 0000:00:08.1
Oct 11 23:21:42 ryzen kernel: xhci_hcd 0000:07:00.3: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: ccp 0000:07:00.1: PM: calling pci_pm_suspend_late+0x0/0x40 @ 36881, parent: 0000:00:08.1
Oct 11 23:21:42 ryzen kernel: ccp 0000:07:00.1: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: pci 0000:06:00.0: PM: calling pci_pm_suspend_late+0x0/0x40 @ 36881, parent: 0000:00:07.1
Oct 11 23:21:42 ryzen kernel: pci 0000:07:00.0: PM: calling pci_pm_suspend_late+0x0/0x40 @ 36883, parent: 0000:00:08.1
Oct 11 23:21:42 ryzen kernel: pci 0000:06:00.0: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: amdgpu 0000:05:00.0: PM: calling pci_pm_suspend_late+0x0/0x40 @ 36887, parent: 0000:00:03.1
Oct 11 23:21:42 ryzen kernel: r8169 0000:04:00.0: PM: calling pci_pm_suspend_late+0x0/0x40 @ 36884, parent: 0000:03:09.0
Oct 11 23:21:42 ryzen kernel: amdgpu 0000:05:00.0: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: pci 0000:07:00.0: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: r8169 0000:04:00.0: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: ahci 0000:02:00.1: PM: calling pci_pm_suspend_late+0x0/0x40 @ 36887, parent: 0000:00:01.2
Oct 11 23:21:42 ryzen kernel: xhci_hcd 0000:02:00.0: PM: calling pci_pm_suspend_late+0x0/0x40 @ 36883, parent: 0000:00:01.2
Oct 11 23:21:42 ryzen kernel: nvme 0000:01:00.0: PM: calling pci_pm_suspend_late+0x0/0x40 @ 36884, parent: 0000:00:01.1
Oct 11 23:21:42 ryzen kernel: pcieport 0000:03:09.0: PM: calling pci_pm_suspend_late+0x0/0x40 @ 36881, parent: 0000:02:00.2
Oct 11 23:21:42 ryzen kernel: ahci 0000:02:00.1: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: pcieport 0000:03:09.0: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: nvme 0000:01:00.0: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: xhci_hcd 0000:02:00.0: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: pci 0000:00:18.7: PM: calling pci_pm_suspend_late+0x0/0x40 @ 36887, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pci 0000:00:18.7: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: pci 0000:00:18.5: PM: calling pci_pm_suspend_late+0x0/0x40 @ 36881, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pci 0000:00:18.4: PM: calling pci_pm_suspend_late+0x0/0x40 @ 36884, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pci 0000:00:18.6: PM: calling pci_pm_suspend_late+0x0/0x40 @ 36875, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: k10temp 0000:00:18.3: PM: calling pci_pm_suspend_late+0x0/0x40 @ 36883, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pci 0000:00:18.5: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: pcieport 0000:02:00.2: PM: calling pci_pm_suspend_late+0x0/0x40 @ 36882, parent: 0000:00:01.2
Oct 11 23:21:42 ryzen kernel: pci 0000:00:18.4: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: pci 0000:00:18.1: PM: calling pci_pm_suspend_late+0x0/0x40 @ 36887, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pci 0000:00:18.2: PM: calling pci_pm_suspend_late+0x0/0x40 @ 33848, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pci 0000:00:18.0: PM: calling pci_pm_suspend_late+0x0/0x40 @ 36881, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: k10temp 0000:00:18.3: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: pcieport 0000:02:00.2: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: pci 0000:00:18.6: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: pci 0000:00:18.1: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: pci 0000:00:18.0: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: pci 0000:00:18.2: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: pci 0000:00:14.3: PM: calling pci_pm_suspend_late+0x0/0x40 @ 36873, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pci 0000:00:08.0: PM: calling pci_pm_suspend_late+0x0/0x40 @ 36875, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: piix4_smbus 0000:00:14.0: PM: calling pci_pm_suspend_late+0x0/0x40 @ 36884, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pci 0000:00:07.0: PM: calling pci_pm_suspend_late+0x0/0x40 @ 36887, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pcieport 0000:00:08.1: PM: calling pci_pm_suspend_late+0x0/0x40 @ 36882, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pcieport 0000:00:07.1: PM: calling pci_pm_suspend_late+0x0/0x40 @ 36881, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pci 0000:00:05.0: PM: calling pci_pm_suspend_late+0x0/0x40 @ 33848, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pci 0000:00:04.0: PM: calling pci_pm_suspend_late+0x0/0x40 @ 36883, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pci 0000:00:14.3: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: piix4_smbus 0000:00:14.0: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: pci 0000:00:07.0: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: pcieport 0000:00:08.1: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: pcieport 0000:00:03.1: PM: calling pci_pm_suspend_late+0x0/0x40 @ 36874, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pcieport 0000:00:03.1: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: pcieport 0000:00:07.1: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 5 usecs
Oct 11 23:21:42 ryzen kernel: pci 0000:00:05.0: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: pci 0000:00:03.0: PM: calling pci_pm_suspend_late+0x0/0x40 @ 36862, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pci 0000:00:04.0: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: pci 0000:00:02.0: PM: calling pci_pm_suspend_late+0x0/0x40 @ 36882, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pci 0000:00:08.0: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: pcieport 0000:00:01.1: PM: calling pci_pm_suspend_late+0x0/0x40 @ 36884, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pcieport 0000:00:01.2: PM: calling pci_pm_suspend_late+0x0/0x40 @ 36873, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pci 0000:00:01.0: PM: calling pci_pm_suspend_late+0x0/0x40 @ 36874, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pci 0000:00:00.2: PM: calling pci_pm_suspend_late+0x0/0x40 @ 33848, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pci 0000:00:00.0: PM: calling pci_pm_suspend_late+0x0/0x40 @ 36881, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pci 0000:00:03.0: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: pci 0000:00:02.0: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: pcieport 0000:00:01.1: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: pci 0000:00:01.0: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: pcieport 0000:00:01.2: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: pci 0000:00:00.0: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: pci 0000:00:00.2: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: PM: late suspend of devices complete after 0.620 msecs
Oct 11 23:21:42 ryzen kernel: snd_hda_intel 0000:05:00.1: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 33848, parent: 0000:00:03.1
Oct 11 23:21:42 ryzen kernel: acpi-wmi PNP0C14:01: PM: calling acpi_subsys_suspend_noirq+0x0/0x50 @ 36842, parent: platform
Oct 11 23:21:42 ryzen kernel: acpi-wmi PNP0C14:01: PM: acpi_subsys_suspend_noirq+0x0/0x50 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: acpi-wmi PNP0C14:00: PM: calling acpi_subsys_suspend_noirq+0x0/0x50 @ 36842, parent: platform
Oct 11 23:21:42 ryzen kernel: acpi-wmi PNP0C14:00: PM: acpi_subsys_suspend_noirq+0x0/0x50 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: pt-gpio AMDIF030:00: PM: calling acpi_subsys_suspend_noirq+0x0/0x50 @ 36842, parent: platform
Oct 11 23:21:42 ryzen kernel: pt-gpio AMDIF030:00: PM: acpi_subsys_suspend_noirq+0x0/0x50 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: amd_gpio AMDI0030:00: PM: calling acpi_subsys_suspend_noirq+0x0/0x50 @ 36842, parent: platform
Oct 11 23:21:42 ryzen kernel: amd_gpio AMDI0030:00: PM: acpi_subsys_suspend_noirq+0x0/0x50 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: snd_hda_intel 0000:07:00.4: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 36881, parent: 0000:00:08.1
Oct 11 23:21:42 ryzen kernel: xhci_hcd 0000:07:00.3: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 36886, parent: 0000:00:08.1
Oct 11 23:21:42 ryzen kernel: ccp 0000:07:00.1: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 36873, parent: 0000:00:08.1
Oct 11 23:21:42 ryzen kernel: pci 0000:07:00.0: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 36887, parent: 0000:00:08.1
Oct 11 23:21:42 ryzen kernel: pci 0000:06:00.0: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 36875, parent: 0000:00:07.1
Oct 11 23:21:42 ryzen kernel: r8169 0000:04:00.0: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 36884, parent: 0000:03:09.0
Oct 11 23:21:42 ryzen kernel: ahci 0000:02:00.1: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 36883, parent: 0000:00:01.2
Oct 11 23:21:42 ryzen kernel: xhci_hcd 0000:02:00.0: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 36880, parent: 0000:00:01.2
Oct 11 23:21:42 ryzen kernel: nvme 0000:01:00.0: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 36872, parent: 0000:00:01.1
Oct 11 23:21:42 ryzen kernel: pci 0000:00:18.7: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 36817, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pci 0000:00:18.5: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 36846, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pci 0000:00:18.7: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 162 usecs
Oct 11 23:21:42 ryzen kernel: pci 0000:00:18.4: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 36817, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pci 0000:00:18.5: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 162 usecs
Oct 11 23:21:42 ryzen kernel: k10temp 0000:00:18.3: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 36846, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pci 0000:07:00.0: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 303 usecs
Oct 11 23:21:42 ryzen kernel: pci 0000:00:18.2: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 36887, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pci 0000:00:18.4: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 108 usecs
Oct 11 23:21:42 ryzen kernel: k10temp 0000:00:18.3: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 101 usecs
Oct 11 23:21:42 ryzen kernel: pci 0000:00:18.1: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 36817, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pci 0000:00:18.0: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 36846, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pci 0000:00:18.1: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 30 usecs
Oct 11 23:21:42 ryzen kernel: pci 0000:00:18.2: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 34 usecs
Oct 11 23:21:42 ryzen kernel: pci 0000:00:18.0: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 29 usecs
Oct 11 23:21:42 ryzen kernel: pci 0000:00:14.3: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 36887, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: piix4_smbus 0000:00:14.0: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 36846, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pci 0000:06:00.0: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 365 usecs
Oct 11 23:21:42 ryzen kernel: pci 0000:00:08.0: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 36875, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pcieport 0000:00:07.1: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 36871, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pci 0000:00:07.0: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 36866, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pci 0000:00:05.0: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 36876, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pci 0000:00:04.0: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 36867, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pci 0000:00:03.0: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 32851, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pci 0000:00:02.0: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 33485, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pci 0000:00:01.0: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 36877, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pci 0000:00:00.2: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 36869, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: piix4_smbus 0000:00:14.0: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 114 usecs
Oct 11 23:21:42 ryzen kernel: pci 0000:00:00.0: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 26010, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pci 0000:00:14.3: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 119 usecs
Oct 11 23:21:42 ryzen kernel: pci 0000:00:18.6: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 36868, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pci 0000:00:08.0: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 102 usecs
Oct 11 23:21:42 ryzen kernel: pci 0000:00:07.0: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 90 usecs
Oct 11 23:21:42 ryzen kernel: pci 0000:00:05.0: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 93 usecs
Oct 11 23:21:42 ryzen kernel: pci 0000:00:04.0: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 93 usecs
Oct 11 23:21:42 ryzen kernel: pci 0000:00:03.0: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 90 usecs
Oct 11 23:21:42 ryzen kernel: pci 0000:00:02.0: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 90 usecs
Oct 11 23:21:42 ryzen kernel: pci 0000:00:01.0: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 84 usecs
Oct 11 23:21:42 ryzen kernel: pci 0000:00:18.6: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 72 usecs
Oct 11 23:21:42 ryzen kernel: pci 0000:00:00.0: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 82 usecs
Oct 11 23:21:42 ryzen kernel: pci 0000:00:00.2: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 87 usecs
Oct 11 23:21:42 ryzen kernel: snd_hda_intel 0000:05:00.1: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 12072 usecs
Oct 11 23:21:42 ryzen kernel: amdgpu 0000:05:00.0: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 36874, parent: 0000:00:03.1
Oct 11 23:21:42 ryzen kernel: amdgpu 0000:05:00.0: amdgpu: PCI CONFIG reset
Oct 11 23:21:42 ryzen kernel: snd_hda_intel 0000:07:00.4: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 12259 usecs
Oct 11 23:21:42 ryzen kernel: ahci 0000:02:00.1: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 12324 usecs
Oct 11 23:21:42 ryzen kernel: xhci_hcd 0000:07:00.3: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 12363 usecs
Oct 11 23:21:42 ryzen kernel: ccp 0000:07:00.1: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 12387 usecs
Oct 11 23:21:42 ryzen kernel: pcieport 0000:00:08.1: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 36817, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: r8169 0000:04:00.0: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 12496 usecs
Oct 11 23:21:42 ryzen kernel: nvme 0000:01:00.0: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 12612 usecs
Oct 11 23:21:42 ryzen kernel: xhci_hcd 0000:02:00.0: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 12618 usecs
Oct 11 23:21:42 ryzen kernel: pcieport 0000:00:07.1: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 12211 usecs
Oct 11 23:21:42 ryzen kernel: pcieport 0000:03:09.0: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 36882, parent: 0000:02:00.2
Oct 11 23:21:42 ryzen kernel: pcieport 0000:00:01.1: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 36885, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pcieport 0000:00:01.1: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 10200 usecs
Oct 11 23:21:42 ryzen kernel: amdgpu 0000:05:00.0: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 12203 usecs
Oct 11 23:21:42 ryzen kernel: pcieport 0000:00:08.1: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 11844 usecs
Oct 11 23:21:42 ryzen kernel: pcieport 0000:00:03.1: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 36863, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pcieport 0000:03:09.0: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 12094 usecs
Oct 11 23:21:42 ryzen kernel: pcieport 0000:02:00.2: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 36862, parent: 0000:00:01.2
Oct 11 23:21:42 ryzen kernel: pcieport 0000:00:03.1: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 12090 usecs
Oct 11 23:21:42 ryzen kernel: pcieport 0000:02:00.2: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 12251 usecs
Oct 11 23:21:42 ryzen kernel: pcieport 0000:00:01.2: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 36860, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pcieport 0000:00:01.2: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 12306 usecs
Oct 11 23:21:42 ryzen kernel: PM: noirq suspend of devices complete after 49.703 msecs
Oct 11 23:21:42 ryzen kernel: ACPI: PM: Preparing to enter system sleep state S3
Oct 11 23:21:42 ryzen kernel: ACPI: PM: Saving platform NVS memory
Oct 11 23:21:42 ryzen kernel: Disabling non-boot CPUs ...
Oct 11 23:21:42 ryzen kernel: smpboot: CPU 1 is now offline
Oct 11 23:21:42 ryzen kernel: smpboot: CPU 2 is now offline
Oct 11 23:21:42 ryzen kernel: smpboot: CPU 3 is now offline
Oct 11 23:21:42 ryzen kernel: smpboot: CPU 4 is now offline
Oct 11 23:21:42 ryzen kernel: smpboot: CPU 5 is now offline
Oct 11 23:21:42 ryzen kernel: smpboot: CPU 6 is now offline
Oct 11 23:21:42 ryzen kernel: Spectre V2 : Update user space SMT mitigation: STIBP off
Oct 11 23:21:42 ryzen kernel: smpboot: CPU 7 is now offline
Oct 11 23:21:42 ryzen kernel: smpboot: CPU 8 is now offline
Oct 11 23:21:42 ryzen kernel: smpboot: CPU 9 is now offline
Oct 11 23:21:42 ryzen kernel: smpboot: CPU 10 is now offline
Oct 11 23:21:42 ryzen kernel: smpboot: CPU 11 is now offline
Oct 11 23:21:42 ryzen kernel: Checking wakeup interrupts
Oct 11 23:21:42 ryzen kernel: Calling mce_syscore_suspend+0x0/0x20
Oct 11 23:21:42 ryzen kernel: Calling ledtrig_cpu_syscore_suspend+0x0/0x20
Oct 11 23:21:42 ryzen kernel: Calling timekeeping_suspend+0x0/0x2f0
Oct 11 23:21:42 ryzen kernel: Calling irq_gc_suspend+0x0/0x80
Oct 11 23:21:42 ryzen kernel: Calling save_ioapic_entries+0x0/0xd0
Oct 11 23:21:42 ryzen kernel: Calling i8259A_suspend+0x0/0x30
Oct 11 23:21:42 ryzen kernel: Calling perf_ibs_suspend+0x0/0x40
Oct 11 23:21:42 ryzen kernel: Calling amd_iommu_suspend+0x0/0x50
Oct 11 23:21:42 ryzen kernel: Calling fw_suspend+0x0/0x20
Oct 11 23:21:42 ryzen kernel: Calling acpi_save_bm_rld+0x0/0x30
Oct 11 23:21:42 ryzen kernel: Calling lapic_suspend+0x0/0x210
Oct 11 23:21:42 ryzen kernel: ACPI: PM: Low-level resume complete
Oct 11 23:21:42 ryzen kernel: ACPI: PM: Restoring platform NVS memory
Oct 11 23:21:42 ryzen kernel: Calling lapic_resume+0x0/0x2e0
Oct 11 23:21:42 ryzen kernel: Calling acpi_restore_bm_rld+0x0/0x70
Oct 11 23:21:42 ryzen kernel: Calling irqrouter_resume+0x0/0x50
Oct 11 23:21:42 ryzen kernel: Calling amd_iommu_resume+0x0/0x50
Oct 11 23:21:42 ryzen kernel: Calling perf_ibs_resume+0x0/0x30
Oct 11 23:21:42 ryzen kernel: LVT offset 0 assigned for vector 0x400
Oct 11 23:21:42 ryzen kernel: Calling i8259A_resume+0x0/0x40
Oct 11 23:21:42 ryzen kernel: Calling i8237A_resume+0x0/0xb0
Oct 11 23:21:42 ryzen kernel: Calling ioapic_resume+0x0/0xc0
Oct 11 23:21:42 ryzen kernel: Calling irq_gc_resume+0x0/0x70
Oct 11 23:21:42 ryzen kernel: Calling irq_pm_syscore_resume+0x0/0x20
Oct 11 23:21:42 ryzen kernel: Calling timekeeping_resume+0x0/0x1e0
Oct 11 23:21:42 ryzen kernel: Timekeeping suspended for 615.610 seconds
Oct 11 23:21:42 ryzen kernel: Calling init_counter_refs+0x0/0x40
Oct 11 23:21:42 ryzen kernel: Calling ledtrig_cpu_syscore_resume+0x0/0x20
Oct 11 23:21:42 ryzen kernel: Calling mce_syscore_resume+0x0/0x30
Oct 11 23:21:42 ryzen kernel: Calling microcode_bsp_resume+0x0/0x40
Oct 11 23:21:42 ryzen kernel: Enabling non-boot CPUs ...
Oct 11 23:21:42 ryzen kernel: smpboot: Booting Node 0 Processor 1 APIC 0x2
Oct 11 23:21:42 ryzen kernel: ACPI: \_SB_.PLTF.C002: Found 2 idle states
Oct 11 23:21:42 ryzen kernel: CPU1 is up
Oct 11 23:21:42 ryzen kernel: smpboot: Booting Node 0 Processor 2 APIC 0x4
Oct 11 23:21:42 ryzen kernel: ACPI: \_SB_.PLTF.C004: Found 2 idle states
Oct 11 23:21:42 ryzen kernel: CPU2 is up
Oct 11 23:21:42 ryzen kernel: smpboot: Booting Node 0 Processor 3 APIC 0x6
Oct 11 23:21:42 ryzen kernel: ACPI: \_SB_.PLTF.C006: Found 2 idle states
Oct 11 23:21:42 ryzen kernel: CPU3 is up
Oct 11 23:21:42 ryzen kernel: smpboot: Booting Node 0 Processor 4 APIC 0x8
Oct 11 23:21:42 ryzen kernel: ACPI: \_SB_.PLTF.C008: Found 2 idle states
Oct 11 23:21:42 ryzen kernel: CPU4 is up
Oct 11 23:21:42 ryzen kernel: smpboot: Booting Node 0 Processor 5 APIC 0xa
Oct 11 23:21:42 ryzen kernel: ACPI: \_SB_.PLTF.C00A: Found 2 idle states
Oct 11 23:21:42 ryzen kernel: CPU5 is up
Oct 11 23:21:42 ryzen kernel: smpboot: Booting Node 0 Processor 6 APIC 0x1
Oct 11 23:21:42 ryzen kernel: ACPI: \_SB_.PLTF.C001: Found 2 idle states
Oct 11 23:21:42 ryzen kernel: Spectre V2 : Update user space SMT mitigation: STIBP always-on
Oct 11 23:21:42 ryzen kernel: CPU6 is up
Oct 11 23:21:42 ryzen kernel: smpboot: Booting Node 0 Processor 7 APIC 0x3
Oct 11 23:21:42 ryzen kernel: ACPI: \_SB_.PLTF.C003: Found 2 idle states
Oct 11 23:21:42 ryzen kernel: CPU7 is up
Oct 11 23:21:42 ryzen kernel: smpboot: Booting Node 0 Processor 8 APIC 0x5
Oct 11 23:21:42 ryzen kernel: ACPI: \_SB_.PLTF.C005: Found 2 idle states
Oct 11 23:21:42 ryzen kernel: CPU8 is up
Oct 11 23:21:42 ryzen kernel: smpboot: Booting Node 0 Processor 9 APIC 0x7
Oct 11 23:21:42 ryzen kernel: ACPI: \_SB_.PLTF.C007: Found 2 idle states
Oct 11 23:21:42 ryzen kernel: CPU9 is up
Oct 11 23:21:42 ryzen kernel: smpboot: Booting Node 0 Processor 10 APIC 0x9
Oct 11 23:21:42 ryzen kernel: ACPI: \_SB_.PLTF.C009: Found 2 idle states
Oct 11 23:21:42 ryzen kernel: CPU10 is up
Oct 11 23:21:42 ryzen kernel: smpboot: Booting Node 0 Processor 11 APIC 0xb
Oct 11 23:21:42 ryzen kernel: ACPI: \_SB_.PLTF.C00B: Found 2 idle states
Oct 11 23:21:42 ryzen kernel: CPU11 is up
Oct 11 23:21:42 ryzen kernel: ACPI: PM: Waking up from system sleep state S3
Oct 11 23:21:42 ryzen kernel: pcieport 0000:00:01.2: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 36817, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pci 0000:00:04.0: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 36871, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pci 0000:00:03.0: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 36885, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pci 0000:00:05.0: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 36846, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pcieport 0000:00:03.1: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 36872, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pci 0000:00:00.0: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 36860, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pci 0000:00:02.0: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 36874, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pci 0000:00:00.2: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 36862, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pci 0000:00:01.0: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 36863, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pcieport 0000:00:01.1: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 36882, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pci 0000:00:07.0: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 36880, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pcieport 0000:00:07.1: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 36884, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pci 0000:00:08.0: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 36873, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pcieport 0000:00:08.1: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 36886, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pci 0000:00:14.3: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 36881, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: piix4_smbus 0000:00:14.0: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 36883, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pci 0000:00:18.0: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 33848, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pci 0000:00:03.0: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 206 usecs
Oct 11 23:21:42 ryzen kernel: pci 0000:00:01.0: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 208 usecs
Oct 11 23:21:42 ryzen kernel: pci 0000:00:18.1: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 36885, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pci 0000:00:02.0: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 212 usecs
Oct 11 23:21:42 ryzen kernel: pci 0000:00:05.0: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 213 usecs
Oct 11 23:21:42 ryzen kernel: pci 0000:00:18.2: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 36863, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pci 0000:00:04.0: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 212 usecs
Oct 11 23:21:42 ryzen kernel: k10temp 0000:00:18.3: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 36874, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pci 0000:00:18.4: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 36846, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pci 0000:00:18.5: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 36871, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pci 0000:00:00.0: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 221 usecs
Oct 11 23:21:42 ryzen kernel: pci 0000:00:08.0: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 198 usecs
Oct 11 23:21:42 ryzen kernel: pci 0000:00:18.6: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 36860, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pci 0000:00:18.7: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 36873, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pci 0000:00:18.0: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 178 usecs
Oct 11 23:21:42 ryzen kernel: pci 0000:00:18.1: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 83 usecs
Oct 11 23:21:42 ryzen kernel: pci 0000:00:18.2: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 82 usecs
Oct 11 23:21:42 ryzen kernel: k10temp 0000:00:18.3: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 82 usecs
Oct 11 23:21:42 ryzen kernel: pci 0000:00:18.5: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 82 usecs
Oct 11 23:21:42 ryzen kernel: pci 0000:00:18.4: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 83 usecs
Oct 11 23:21:42 ryzen kernel: pci 0000:00:07.0: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 305 usecs
Oct 11 23:21:42 ryzen kernel: pci 0000:00:18.6: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 84 usecs
Oct 11 23:21:42 ryzen kernel: pci 0000:00:18.7: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 83 usecs
Oct 11 23:21:42 ryzen kernel: pcieport 0000:00:01.2: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 477 usecs
Oct 11 23:21:42 ryzen kernel: xhci_hcd 0000:02:00.0: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 36885, parent: 0000:00:01.2
Oct 11 23:21:42 ryzen kernel: pcieport 0000:02:00.2: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 36869, parent: 0000:00:01.2
Oct 11 23:21:42 ryzen kernel: ahci 0000:02:00.1: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 36863, parent: 0000:00:01.2
Oct 11 23:21:42 ryzen kernel: pcieport 0000:00:01.1: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 491 usecs
Oct 11 23:21:42 ryzen kernel: nvme 0000:01:00.0: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 33848, parent: 0000:00:01.1
Oct 11 23:21:42 ryzen kernel: pci 0000:00:14.3: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 471 usecs
Oct 11 23:21:42 ryzen kernel: piix4_smbus 0000:00:14.0: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 477 usecs
Oct 11 23:21:42 ryzen kernel: amd_gpio AMDI0030:00: PM: calling acpi_subsys_resume_noirq+0x0/0x30 @ 36842, parent: platform
Oct 11 23:21:42 ryzen kernel: pcieport 0000:00:03.1: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 526 usecs
Oct 11 23:21:42 ryzen kernel: amd_gpio AMDI0030:00: PM: acpi_subsys_resume_noirq+0x0/0x30 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: pt-gpio AMDIF030:00: PM: calling acpi_subsys_resume_noirq+0x0/0x30 @ 36842, parent: platform
Oct 11 23:21:42 ryzen kernel: amdgpu 0000:05:00.0: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 36846, parent: 0000:00:03.1
Oct 11 23:21:42 ryzen kernel: pt-gpio AMDIF030:00: PM: acpi_subsys_resume_noirq+0x0/0x30 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: acpi-wmi PNP0C14:00: PM: calling acpi_subsys_resume_noirq+0x0/0x30 @ 36842, parent: platform
Oct 11 23:21:42 ryzen kernel: acpi-wmi PNP0C14:00: PM: acpi_subsys_resume_noirq+0x0/0x30 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: acpi-wmi PNP0C14:01: PM: calling acpi_subsys_resume_noirq+0x0/0x30 @ 36842, parent: platform
Oct 11 23:21:42 ryzen kernel: acpi-wmi PNP0C14:01: PM: acpi_subsys_resume_noirq+0x0/0x30 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: i8042 i8042: PM: calling i8042_pm_resume_noirq+0x0/0x30 [i8042] @ 36842, parent: platform
Oct 11 23:21:42 ryzen kernel: i8042 i8042: PM: i8042_pm_resume_noirq+0x0/0x30 [i8042] returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: pci 0000:00:00.2: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 708 usecs
Oct 11 23:21:42 ryzen kernel: nvme 0000:01:00.0: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 460 usecs
Oct 11 23:21:42 ryzen kernel: pcieport 0000:02:00.2: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 493 usecs
Oct 11 23:21:42 ryzen kernel: pcieport 0000:03:09.0: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 36874, parent: 0000:02:00.2
Oct 11 23:21:42 ryzen kernel: pcieport 0000:00:07.1: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 970 usecs
Oct 11 23:21:42 ryzen kernel: pcieport 0000:00:08.1: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 964 usecs
Oct 11 23:21:42 ryzen kernel: pci 0000:06:00.0: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 26010, parent: 0000:00:07.1
Oct 11 23:21:42 ryzen kernel: pci 0000:07:00.0: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 36880, parent: 0000:00:08.1
Oct 11 23:21:42 ryzen kernel: ccp 0000:07:00.1: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 36860, parent: 0000:00:08.1
Oct 11 23:21:42 ryzen kernel: xhci_hcd 0000:07:00.3: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 36868, parent: 0000:00:08.1
Oct 11 23:21:42 ryzen kernel: snd_hda_intel 0000:07:00.4: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 36873, parent: 0000:00:08.1
Oct 11 23:21:42 ryzen kernel: ahci 0000:02:00.1: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 551 usecs
Oct 11 23:21:42 ryzen kernel: xhci_hcd 0000:02:00.0: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 556 usecs
Oct 11 23:21:42 ryzen kernel: amdgpu 0000:05:00.0: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 641 usecs
Oct 11 23:21:42 ryzen kernel: snd_hda_intel 0000:05:00.1: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 36877, parent: 0000:00:03.1
Oct 11 23:21:42 ryzen kernel: pci 0000:06:00.0: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 461 usecs
Oct 11 23:21:42 ryzen kernel: pci 0000:07:00.0: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 461 usecs
Oct 11 23:21:42 ryzen kernel: snd_hda_intel 0000:07:00.4: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 494 usecs
Oct 11 23:21:42 ryzen kernel: snd_hda_intel 0000:05:00.1: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 326 usecs
Oct 11 23:21:42 ryzen kernel: pcieport 0000:03:09.0: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 537 usecs
Oct 11 23:21:42 ryzen kernel: ccp 0000:07:00.1: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 523 usecs
Oct 11 23:21:42 ryzen kernel: r8169 0000:04:00.0: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 36871, parent: 0000:03:09.0
Oct 11 23:21:42 ryzen kernel: xhci_hcd 0000:07:00.3: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 539 usecs
Oct 11 23:21:42 ryzen kernel: r8169 0000:04:00.0: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 220 usecs
Oct 11 23:21:42 ryzen kernel: PM: noirq resume of devices complete after 1.960 msecs
Oct 11 23:21:42 ryzen kernel: pci 0000:00:01.0: PM: calling pci_pm_resume_early+0x0/0x30 @ 36926, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pci 0000:00:00.2: PM: calling pci_pm_resume_early+0x0/0x30 @ 36917, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pci 0000:00:05.0: PM: calling pci_pm_resume_early+0x0/0x30 @ 36912, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pci 0000:00:02.0: PM: calling pci_pm_resume_early+0x0/0x30 @ 36916, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pci 0000:00:04.0: PM: calling pci_pm_resume_early+0x0/0x30 @ 36915, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pcieport 0000:00:07.1: PM: calling pci_pm_resume_early+0x0/0x30 @ 36871, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pcieport 0000:00:01.2: PM: calling pci_pm_resume_early+0x0/0x30 @ 36913, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pci 0000:00:03.0: PM: calling pci_pm_resume_early+0x0/0x30 @ 36927, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pcieport 0000:00:01.1: PM: calling pci_pm_resume_early+0x0/0x30 @ 36919, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pci 0000:00:07.0: PM: calling pci_pm_resume_early+0x0/0x30 @ 33848, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pci 0000:00:00.0: PM: calling pci_pm_resume_early+0x0/0x30 @ 36869, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pci 0000:00:00.2: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: pcieport 0000:00:01.2: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: pcieport 0000:00:01.1: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: pci 0000:00:04.0: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: pci 0000:00:02.0: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: pci 0000:00:03.0: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: pcieport 0000:00:07.1: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: pci 0000:00:00.0: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: pci 0000:00:01.0: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: pci 0000:00:05.0: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: pci 0000:00:08.0: PM: calling pci_pm_resume_early+0x0/0x30 @ 36917, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pcieport 0000:00:08.1: PM: calling pci_pm_resume_early+0x0/0x30 @ 36919, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: piix4_smbus 0000:00:14.0: PM: calling pci_pm_resume_early+0x0/0x30 @ 36913, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pci 0000:00:14.3: PM: calling pci_pm_resume_early+0x0/0x30 @ 36915, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pci 0000:00:18.0: PM: calling pci_pm_resume_early+0x0/0x30 @ 36927, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pci 0000:00:18.1: PM: calling pci_pm_resume_early+0x0/0x30 @ 36916, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pci 0000:00:18.2: PM: calling pci_pm_resume_early+0x0/0x30 @ 36871, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: k10temp 0000:00:18.3: PM: calling pci_pm_resume_early+0x0/0x30 @ 36869, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pci 0000:00:18.4: PM: calling pci_pm_resume_early+0x0/0x30 @ 36912, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pci 0000:00:18.5: PM: calling pci_pm_resume_early+0x0/0x30 @ 36926, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pci 0000:00:08.0: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: pcieport 0000:00:08.1: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: piix4_smbus 0000:00:14.0: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: pci 0000:00:14.3: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: pci 0000:00:18.0: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: pci 0000:00:18.1: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: pci 0000:00:18.2: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: k10temp 0000:00:18.3: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: pci 0000:00:18.5: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: pci 0000:00:18.4: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: pci 0000:00:18.6: PM: calling pci_pm_resume_early+0x0/0x30 @ 36917, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pci 0000:00:18.7: PM: calling pci_pm_resume_early+0x0/0x30 @ 36919, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pci 0000:00:07.0: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: nvme 0000:01:00.0: PM: calling pci_pm_resume_early+0x0/0x30 @ 36915, parent: 0000:00:01.1
Oct 11 23:21:42 ryzen kernel: xhci_hcd 0000:02:00.0: PM: calling pci_pm_resume_early+0x0/0x30 @ 36913, parent: 0000:00:01.2
Oct 11 23:21:42 ryzen kernel: ahci 0000:02:00.1: PM: calling pci_pm_resume_early+0x0/0x30 @ 36916, parent: 0000:00:01.2
Oct 11 23:21:42 ryzen kernel: pcieport 0000:02:00.2: PM: calling pci_pm_resume_early+0x0/0x30 @ 36871, parent: 0000:00:01.2
Oct 11 23:21:42 ryzen kernel: pci 0000:00:18.6: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: pci 0000:00:18.7: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: nvme 0000:01:00.0: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: xhci_hcd 0000:02:00.0: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: pci 0000:06:00.0: PM: calling pci_pm_resume_early+0x0/0x30 @ 36927, parent: 0000:00:07.1
Oct 11 23:21:42 ryzen kernel: pcieport 0000:02:00.2: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: ahci 0000:02:00.1: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: ccp 0000:07:00.1: PM: calling pci_pm_resume_early+0x0/0x30 @ 36919, parent: 0000:00:08.1
Oct 11 23:21:42 ryzen kernel: pci 0000:07:00.0: PM: calling pci_pm_resume_early+0x0/0x30 @ 33848, parent: 0000:00:08.1
Oct 11 23:21:42 ryzen kernel: xhci_hcd 0000:07:00.3: PM: calling pci_pm_resume_early+0x0/0x30 @ 36917, parent: 0000:00:08.1
Oct 11 23:21:42 ryzen kernel: pci 0000:06:00.0: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: snd_hda_intel 0000:07:00.4: PM: calling pci_pm_resume_early+0x0/0x30 @ 36913, parent: 0000:00:08.1
Oct 11 23:21:42 ryzen kernel: pci 0000:07:00.0: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: xhci_hcd 0000:07:00.3: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: pcieport 0000:03:09.0: PM: calling pci_pm_resume_early+0x0/0x30 @ 36869, parent: 0000:02:00.2
Oct 11 23:21:42 ryzen kernel: snd_hda_intel 0000:07:00.4: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: ccp 0000:07:00.1: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: pcieport 0000:03:09.0: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: r8169 0000:04:00.0: PM: calling pci_pm_resume_early+0x0/0x30 @ 36926, parent: 0000:03:09.0
Oct 11 23:21:42 ryzen kernel: r8169 0000:04:00.0: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: amd_gpio AMDI0030:00: PM: calling acpi_subsys_resume_early+0x0/0x80 @ 36842, parent: platform
Oct 11 23:21:42 ryzen kernel: amd_gpio AMDI0030:00: PM: acpi_subsys_resume_early+0x0/0x80 returned 0 after 11 usecs
Oct 11 23:21:42 ryzen kernel: pt-gpio AMDIF030:00: PM: calling acpi_subsys_resume_early+0x0/0x80 @ 36842, parent: platform
Oct 11 23:21:42 ryzen kernel: pt-gpio AMDIF030:00: PM: acpi_subsys_resume_early+0x0/0x80 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: acpi-wmi PNP0C14:00: PM: calling acpi_subsys_resume_early+0x0/0x80 @ 36842, parent: platform
Oct 11 23:21:42 ryzen kernel: acpi-wmi PNP0C14:00: PM: acpi_subsys_resume_early+0x0/0x80 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: pcieport 0000:00:03.1: PM: calling pci_pm_resume_early+0x0/0x30 @ 36918, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: acpi-wmi PNP0C14:01: PM: calling acpi_subsys_resume_early+0x0/0x80 @ 36842, parent: platform
Oct 11 23:21:42 ryzen kernel: acpi-wmi PNP0C14:01: PM: acpi_subsys_resume_early+0x0/0x80 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: pcieport 0000:00:03.1: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: amdgpu 0000:05:00.0: PM: calling pci_pm_resume_early+0x0/0x30 @ 36912, parent: 0000:00:03.1
Oct 11 23:21:42 ryzen kernel: amdgpu 0000:05:00.0: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: snd_hda_intel 0000:05:00.1: PM: calling pci_pm_resume_early+0x0/0x30 @ 36916, parent: 0000:00:03.1
Oct 11 23:21:42 ryzen kernel: snd_hda_intel 0000:05:00.1: PM: pci_pm_resume_early+0x0/0x30 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: PM: early resume of devices complete after 0.237 msecs
Oct 11 23:21:42 ryzen kernel: pci 0000:00:01.0: PM: calling pci_pm_resume+0x0/0xf0 @ 36909, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pci 0000:00:00.2: PM: calling pci_pm_resume+0x0/0xf0 @ 36918, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pcieport 0000:00:03.1: PM: calling pci_pm_resume+0x0/0xf0 @ 36917, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pcieport 0000:00:01.2: PM: calling pci_pm_resume+0x0/0xf0 @ 36919, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pci 0000:00:04.0: PM: calling pci_pm_resume+0x0/0xf0 @ 36927, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pci 0000:00:03.0: PM: calling pci_pm_resume+0x0/0xf0 @ 36911, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pci 0000:00:02.0: PM: calling pci_pm_resume+0x0/0xf0 @ 36869, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pci 0000:00:05.0: PM: calling pci_pm_resume+0x0/0xf0 @ 36913, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pcieport 0000:00:01.1: PM: calling pci_pm_resume+0x0/0xf0 @ 36910, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pci 0000:00:00.0: PM: calling pci_pm_resume+0x0/0xf0 @ 36912, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pci 0000:00:04.0: PM: pci_pm_resume+0x0/0xf0 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: pci 0000:00:01.0: PM: pci_pm_resume+0x0/0xf0 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: pci 0000:00:00.0: PM: pci_pm_resume+0x0/0xf0 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: pci 0000:00:07.0: PM: calling pci_pm_resume+0x0/0xf0 @ 36916, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pci 0000:00:03.0: PM: pci_pm_resume+0x0/0xf0 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: pcieport 0000:00:01.2: PM: pci_pm_resume+0x0/0xf0 returned 0 after 2 usecs
Oct 11 23:21:42 ryzen kernel: pci 0000:00:05.0: PM: pci_pm_resume+0x0/0xf0 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: pci 0000:00:02.0: PM: pci_pm_resume+0x0/0xf0 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: pcieport 0000:00:07.1: PM: calling pci_pm_resume+0x0/0xf0 @ 36927, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pci 0000:00:08.0: PM: calling pci_pm_resume+0x0/0xf0 @ 36909, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pci 0000:00:07.0: PM: pci_pm_resume+0x0/0xf0 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: pcieport 0000:00:08.1: PM: calling pci_pm_resume+0x0/0xf0 @ 36912, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: piix4_smbus 0000:00:14.0: PM: calling pci_pm_resume+0x0/0xf0 @ 36911, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pci 0000:00:14.3: PM: calling pci_pm_resume+0x0/0xf0 @ 36869, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pci 0000:00:18.0: PM: calling pci_pm_resume+0x0/0xf0 @ 36913, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pci 0000:00:18.1: PM: calling pci_pm_resume+0x0/0xf0 @ 36919, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pci 0000:00:08.0: PM: pci_pm_resume+0x0/0xf0 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: piix4_smbus 0000:00:14.0: PM: pci_pm_resume+0x0/0xf0 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: pci 0000:00:18.2: PM: calling pci_pm_resume+0x0/0xf0 @ 36916, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pci 0000:00:14.3: PM: pci_pm_resume+0x0/0xf0 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: pci 0000:00:18.0: PM: pci_pm_resume+0x0/0xf0 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: pci 0000:00:18.1: PM: pci_pm_resume+0x0/0xf0 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: pcieport 0000:00:01.1: PM: pci_pm_resume+0x0/0xf0 returned 0 after 7 usecs
Oct 11 23:21:42 ryzen kernel: k10temp 0000:00:18.3: PM: calling pci_pm_resume+0x0/0xf0 @ 36909, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pci 0000:00:18.2: PM: pci_pm_resume+0x0/0xf0 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: pci 0000:00:18.4: PM: calling pci_pm_resume+0x0/0xf0 @ 36911, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pci 0000:00:18.5: PM: calling pci_pm_resume+0x0/0xf0 @ 36869, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pci 0000:00:18.7: PM: calling pci_pm_resume+0x0/0xf0 @ 36919, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: pci 0000:00:18.6: PM: calling pci_pm_resume+0x0/0xf0 @ 36913, parent: pci0000:00
Oct 11 23:21:42 ryzen kernel: nvme 0000:01:00.0: PM: calling pci_pm_resume+0x0/0xf0 @ 36910, parent: 0000:00:01.1
Oct 11 23:21:42 ryzen kernel: pci 0000:00:18.4: PM: pci_pm_resume+0x0/0xf0 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: xhci_hcd 0000:02:00.0: PM: calling pci_pm_resume+0x0/0xf0 @ 36916, parent: 0000:00:01.2
Oct 11 23:21:42 ryzen kernel: pci 0000:00:18.5: PM: pci_pm_resume+0x0/0xf0 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: pci 0000:00:18.7: PM: pci_pm_resume+0x0/0xf0 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: pci 0000:00:18.6: PM: pci_pm_resume+0x0/0xf0 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: pci 0000:00:00.2: PM: pci_pm_resume+0x0/0xf0 returned 0 after 2 usecs
Oct 11 23:21:42 ryzen kernel: ahci 0000:02:00.1: PM: calling pci_pm_resume+0x0/0xf0 @ 36911, parent: 0000:00:01.2
Oct 11 23:21:42 ryzen kernel: nvme 0000:01:00.0: PM: pci_pm_resume+0x0/0xf0 returned 0 after 1 usecs
Oct 11 23:21:42 ryzen kernel: reg-dummy reg-dummy: PM: calling platform_pm_resume+0x0/0x50 @ 36842, parent: platform
Oct 11 23:21:42 ryzen kernel: k10temp 0000:00:18.3: PM: pci_pm_resume+0x0/0xf0 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: pcieport 0000:02:00.2: PM: calling pci_pm_resume+0x0/0xf0 @ 36869, parent: 0000:00:01.2
Oct 11 23:21:42 ryzen kernel: pcieport 0000:00:03.1: PM: pci_pm_resume+0x0/0xf0 returned 0 after 15 usecs
Oct 11 23:21:42 ryzen kernel: reg-dummy reg-dummy: PM: platform_pm_resume+0x0/0x50 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: pcieport 0000:02:00.2: PM: pci_pm_resume+0x0/0xf0 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: pcieport 0000:00:07.1: PM: pci_pm_resume+0x0/0xf0 returned 0 after 14 usecs
Oct 11 23:21:42 ryzen kernel: amdgpu 0000:05:00.0: PM: calling pci_pm_resume+0x0/0xf0 @ 36918, parent: 0000:00:03.1
Oct 11 23:21:42 ryzen kernel: regulator regulator.0: PM: calling regulator_resume+0x0/0x190 @ 36842, parent: reg-dummy
Oct 11 23:21:42 ryzen kernel: regulator regulator.0: PM: regulator_resume+0x0/0x190 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: pcieport 0000:03:09.0: PM: calling pci_pm_resume+0x0/0xf0 @ 36919, parent: 0000:02:00.2
Oct 11 23:21:42 ryzen kernel: pci 0000:06:00.0: PM: calling pci_pm_resume+0x0/0xf0 @ 36910, parent: 0000:00:07.1
Oct 11 23:21:42 ryzen kernel: pcieport 0000:00:08.1: PM: pci_pm_resume+0x0/0xf0 returned 0 after 20 usecs
Oct 11 23:21:42 ryzen kernel: PCCT PCCT: PM: calling platform_pm_resume+0x0/0x50 @ 36842, parent: platform
Oct 11 23:21:42 ryzen kernel: pci 0000:06:00.0: PM: pci_pm_resume+0x0/0xf0 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: PCCT PCCT: PM: platform_pm_resume+0x0/0x50 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: ccp 0000:07:00.1: PM: calling pci_pm_resume+0x0/0xf0 @ 36917, parent: 0000:00:08.1
Oct 11 23:21:42 ryzen kernel: pci 0000:07:00.0: PM: calling pci_pm_resume+0x0/0xf0 @ 36909, parent: 0000:00:08.1
Oct 11 23:21:42 ryzen kernel: xhci_hcd 0000:07:00.3: PM: calling pci_pm_resume+0x0/0xf0 @ 36915, parent: 0000:00:08.1
Oct 11 23:21:42 ryzen kernel: pci 0000:07:00.0: PM: pci_pm_resume+0x0/0xf0 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: ccp 0000:07:00.1: PM: pci_pm_resume+0x0/0xf0 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: snd_hda_intel 0000:07:00.4: PM: calling pci_pm_resume+0x0/0xf0 @ 36871, parent: 0000:00:08.1
Oct 11 23:21:42 ryzen kernel: button PNP0C0C:00: PM: calling acpi_button_resume+0x0/0x110 @ 36842, parent: LNXSYBUS:00
Oct 11 23:21:42 ryzen kernel: button PNP0C0C:00: PM: acpi_button_resume+0x0/0x110 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: pcieport 0000:03:09.0: PM: pci_pm_resume+0x0/0xf0 returned 0 after 30 usecs
Oct 11 23:21:42 ryzen kernel: tpm_crb MSFT0101:00: PM: calling tpm_pm_resume+0x0/0x30 @ 36842, parent: LNXSYBUS:00
Oct 11 23:21:42 ryzen kernel: r8169 0000:04:00.0: PM: calling pci_pm_resume+0x0/0xf0 @ 36913, parent: 0000:03:09.0
Oct 11 23:21:42 ryzen kernel: tpm_crb MSFT0101:00: PM: tpm_pm_resume+0x0/0x30 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: thermal LNXTHERM:00: PM: calling acpi_thermal_resume+0x0/0xf0 @ 36842, parent: LNXSYBUS:01
Oct 11 23:21:42 ryzen kernel: thermal LNXTHERM:00: PM: acpi_thermal_resume+0x0/0xf0 returned 0 after 2 usecs
Oct 11 23:21:42 ryzen kernel: xhci_hcd 0000:02:00.0: xHC error in resume, USBSTS 0x401, Reinit
Oct 11 23:21:42 ryzen kernel: usb usb1: root hub lost power or was reset
Oct 11 23:21:42 ryzen kernel: usb usb2: root hub lost power or was reset
Oct 11 23:21:42 ryzen kernel: ahci 0000:02:00.1: PM: pci_pm_resume+0x0/0xf0 returned 0 after 83 usecs
Oct 11 23:21:42 ryzen kernel: ata2: PM: calling ata_port_pm_resume+0x0/0x60 @ 36926, parent: 0000:02:00.1
Oct 11 23:21:42 ryzen kernel: ata1: PM: calling ata_port_pm_resume+0x0/0x60 @ 36927, parent: 0000:02:00.1
Oct 11 23:21:42 ryzen kernel: ata3: PM: calling ata_port_pm_resume+0x0/0x60 @ 33848, parent: 0000:02:00.1
Oct 11 23:21:42 ryzen kernel: ata5: PM: calling ata_port_pm_resume+0x0/0x60 @ 36914, parent: 0000:02:00.1
Oct 11 23:21:42 ryzen kernel: ata4: PM: calling ata_port_pm_resume+0x0/0x60 @ 36910, parent: 0000:02:00.1
Oct 11 23:21:42 ryzen kernel: ata3: PM: ata_port_pm_resume+0x0/0x60 returned 0 after 4 usecs
Oct 11 23:21:42 ryzen kernel: ata1: PM: ata_port_pm_resume+0x0/0x60 returned 0 after 6 usecs
Oct 11 23:21:42 ryzen kernel: thermal LNXTHERM:01: PM: calling acpi_thermal_resume+0x0/0xf0 @ 36842, parent: LNXSYBUS:01
Oct 11 23:21:42 ryzen kernel: thermal LNXTHERM:01: PM: acpi_thermal_resume+0x0/0xf0 returned 0 after 1 usecs
Oct 11 23:21:42 ryzen kernel: ata2: PM: ata_port_pm_resume+0x0/0x60 returned 0 after 45 usecs
Oct 11 23:21:42 ryzen kernel: platform PNP0800:00: PM: calling platform_pm_resume+0x0/0x50 @ 36842, parent: 0000:00:14.3
Oct 11 23:21:42 ryzen kernel: platform PNP0800:00: PM: platform_pm_resume+0x0/0x50 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: scsi host1: PM: calling scsi_bus_resume+0x0/0x90 @ 36917, parent: ata2
Oct 11 23:21:42 ryzen kernel: platform PNP0C0C:00: PM: calling platform_pm_resume+0x0/0x50 @ 36842, parent: platform
Oct 11 23:21:42 ryzen kernel: xhci_hcd 0000:07:00.3: PM: pci_pm_resume+0x0/0xf0 returned 0 after 127 usecs
Oct 11 23:21:42 ryzen kernel: ata6: PM: calling ata_port_pm_resume+0x0/0x60 @ 36912, parent: 0000:02:00.1
Oct 11 23:21:42 ryzen kernel: scsi host1: PM: scsi_bus_resume+0x0/0x90 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: platform PNP0C0C:00: PM: platform_pm_resume+0x0/0x50 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: amd_gpio AMDI0030:00: PM: calling acpi_subsys_resume+0x0/0x80 @ 36842, parent: platform
Oct 11 23:21:42 ryzen kernel: scsi host2: PM: calling scsi_bus_resume+0x0/0x90 @ 36908, parent: ata3
Oct 11 23:21:42 ryzen kernel: scsi target1:0:0: PM: calling scsi_bus_resume+0x0/0x90 @ 36919, parent: host1
Oct 11 23:21:42 ryzen kernel: scsi host2: PM: scsi_bus_resume+0x0/0x90 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: ata6: PM: ata_port_pm_resume+0x0/0x60 returned 0 after 3 usecs
Oct 11 23:21:42 ryzen kernel: amd_gpio AMDI0030:00: PM: acpi_subsys_resume+0x0/0x80 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: scsi target1:0:0: PM: scsi_bus_resume+0x0/0x90 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: usb usb3: PM: calling usb_dev_resume+0x0/0x20 @ 36867, parent: 0000:07:00.3
Oct 11 23:21:42 ryzen kernel: platform MSFT0101:00: PM: calling platform_pm_resume+0x0/0x50 @ 36842, parent: platform
Oct 11 23:21:42 ryzen kernel: usb usb4: PM: calling usb_dev_resume+0x0/0x20 @ 36912, parent: 0000:07:00.3
Oct 11 23:21:42 ryzen kernel: scsi host5: PM: calling scsi_bus_resume+0x0/0x90 @ 36860, parent: ata6
Oct 11 23:21:42 ryzen kernel: platform MSFT0101:00: PM: platform_pm_resume+0x0/0x50 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: scsi host5: PM: scsi_bus_resume+0x0/0x90 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: acpi-cpufreq acpi-cpufreq: PM: calling platform_pm_resume+0x0/0x50 @ 36842, parent: platform
Oct 11 23:21:42 ryzen kernel: acpi-cpufreq acpi-cpufreq: PM: platform_pm_resume+0x0/0x50 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: pt-gpio AMDIF030:00: PM: calling acpi_subsys_resume+0x0/0x80 @ 36842, parent: platform
Oct 11 23:21:42 ryzen kernel: pt-gpio AMDIF030:00: PM: acpi_subsys_resume+0x0/0x80 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: platform PNP0103:00: PM: calling platform_pm_resume+0x0/0x50 @ 36842, parent: platform
Oct 11 23:21:42 ryzen kernel: platform PNP0103:00: PM: platform_pm_resume+0x0/0x50 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: acpi-wmi PNP0C14:00: PM: calling acpi_subsys_resume+0x0/0x80 @ 36842, parent: platform
Oct 11 23:21:42 ryzen kernel: acpi-wmi PNP0C14:00: PM: acpi_subsys_resume+0x0/0x80 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: acpi-wmi PNP0C14:01: PM: calling acpi_subsys_resume+0x0/0x80 @ 36842, parent: platform
Oct 11 23:21:42 ryzen kernel: acpi-wmi PNP0C14:01: PM: acpi_subsys_resume+0x0/0x80 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: button LNXPWRBN:00: PM: calling acpi_button_resume+0x0/0x110 @ 36842, parent: LNXSYSTM:00
Oct 11 23:21:42 ryzen kernel: button LNXPWRBN:00: PM: acpi_button_resume+0x0/0x110 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: ata4: PM: ata_port_pm_resume+0x0/0x60 returned 0 after 100 usecs
Oct 11 23:21:42 ryzen kernel: platform rtc-efi.0: PM: calling platform_pm_resume+0x0/0x50 @ 36842, parent: platform
Oct 11 23:21:42 ryzen kernel: platform rtc-efi.0: PM: platform_pm_resume+0x0/0x50 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: platform efivars.0: PM: calling platform_pm_resume+0x0/0x50 @ 36842, parent: platform
Oct 11 23:21:42 ryzen kernel: platform efivars.0: PM: platform_pm_resume+0x0/0x50 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: scsi host0: PM: calling scsi_bus_resume+0x0/0x90 @ 36909, parent: ata1
Oct 11 23:21:42 ryzen kernel: scsi host0: PM: scsi_bus_resume+0x0/0x90 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: system 00:00: PM: calling pnp_bus_resume+0x0/0xa0 @ 36842, parent: pnp0
Oct 11 23:21:42 ryzen kernel: system 00:00: PM: pnp_bus_resume+0x0/0xa0 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: scsi target0:0:0: PM: calling scsi_bus_resume+0x0/0x90 @ 36877, parent: host0
Oct 11 23:21:42 ryzen kernel: system 00:01: PM: calling pnp_bus_resume+0x0/0xa0 @ 36842, parent: pnp0
Oct 11 23:21:42 ryzen kernel: scsi target0:0:0: PM: scsi_bus_resume+0x0/0x90 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: scsi host3: PM: calling scsi_bus_resume+0x0/0x90 @ 36868, parent: ata4
Oct 11 23:21:42 ryzen kernel: system 00:01: PM: pnp_bus_resume+0x0/0xa0 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: rtc_cmos 00:02: PM: calling pnp_bus_resume+0x0/0xa0 @ 36842, parent: pnp0
Oct 11 23:21:42 ryzen kernel: scsi host3: PM: scsi_bus_resume+0x0/0x90 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: sd 0:0:0:0: PM: calling scsi_bus_resume+0x0/0x90 @ 36904, parent: target0:0:0
Oct 11 23:21:42 ryzen kernel: rtc_cmos 00:02: PM: pnp_bus_resume+0x0/0xa0 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: sd 0:0:0:0: PM: scsi_bus_resume+0x0/0x90 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: system 00:03: PM: calling pnp_bus_resume+0x0/0xa0 @ 36842, parent: pnp0
Oct 11 23:21:42 ryzen kernel: r8169 0000:04:00.0: PM: pci_pm_resume+0x0/0xf0 returned 0 after 178 usecs
Oct 11 23:21:42 ryzen kernel: system 00:03: PM: pnp_bus_resume+0x0/0xa0 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: i8042 kbd 00:04: PM: calling pnp_bus_resume+0x0/0xa0 @ 36842, parent: pnp0
Oct 11 23:21:42 ryzen kernel: sr 1:0:0:0: PM: calling scsi_bus_resume+0x0/0x90 @ 36873, parent: target1:0:0
Oct 11 23:21:42 ryzen kernel: sr 1:0:0:0: PM: scsi_bus_resume+0x0/0x90 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: ata5: PM: ata_port_pm_resume+0x0/0x60 returned 0 after 181 usecs
Oct 11 23:21:42 ryzen kernel: scsi host4: PM: calling scsi_bus_resume+0x0/0x90 @ 36874, parent: ata5
Oct 11 23:21:42 ryzen kernel: i8042 kbd 00:04: PM: pnp_bus_resume+0x0/0xa0 returned 0 after 47 usecs
Oct 11 23:21:42 ryzen kernel: scsi host4: PM: scsi_bus_resume+0x0/0x90 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: serial 00:05: PM: calling pnp_bus_resume+0x0/0xa0 @ 36842, parent: pnp0
Oct 11 23:21:42 ryzen kernel: serial 00:05: activated
Oct 11 23:21:42 ryzen kernel: serial 00:05: PM: pnp_bus_resume+0x0/0xa0 returned 0 after 958 usecs
Oct 11 23:21:42 ryzen kernel: system 00:06: PM: calling pnp_bus_resume+0x0/0xa0 @ 36842, parent: pnp0
Oct 11 23:21:42 ryzen kernel: system 00:06: PM: pnp_bus_resume+0x0/0xa0 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: pcspkr pcspkr: PM: calling platform_pm_resume+0x0/0x50 @ 36842, parent: platform
Oct 11 23:21:42 ryzen kernel: pcspkr pcspkr: PM: platform_pm_resume+0x0/0x50 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: input input0: PM: calling input_dev_resume+0x0/0x40 @ 36842, parent: PNP0C0C:00
Oct 11 23:21:42 ryzen kernel: input input0: PM: input_dev_resume+0x0/0x40 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: input input1: PM: calling input_dev_resume+0x0/0x40 @ 36842, parent: LNXPWRBN:00
Oct 11 23:21:42 ryzen kernel: input input1: PM: input_dev_resume+0x0/0x40 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: port 00:05:0.0: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 36842, parent: 00:05:0
Oct 11 23:21:42 ryzen kernel: port 00:05:0.0: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: serial8250 serial8250: PM: calling platform_pm_resume+0x0/0x50 @ 36842, parent: platform
Oct 11 23:21:42 ryzen kernel: serial8250 serial8250: PM: platform_pm_resume+0x0/0x50 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: port serial8250:0.1: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 36842, parent: serial8250:0
Oct 11 23:21:42 ryzen kernel: port serial8250:0.1: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: port serial8250:0.2: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 36842, parent: serial8250:0
Oct 11 23:21:42 ryzen kernel: port serial8250:0.2: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: port serial8250:0.3: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 36842, parent: serial8250:0
Oct 11 23:21:42 ryzen kernel: port serial8250:0.3: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: port serial8250:0.4: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 36842, parent: serial8250:0
Oct 11 23:21:42 ryzen kernel: port serial8250:0.4: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: port serial8250:0.5: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 36842, parent: serial8250:0
Oct 11 23:21:42 ryzen kernel: port serial8250:0.5: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: port serial8250:0.6: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 36842, parent: serial8250:0
Oct 11 23:21:42 ryzen kernel: port serial8250:0.6: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: port serial8250:0.7: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 36842, parent: serial8250:0
Oct 11 23:21:42 ryzen kernel: port serial8250:0.7: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: port serial8250:0.8: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 36842, parent: serial8250:0
Oct 11 23:21:42 ryzen kernel: port serial8250:0.8: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: port serial8250:0.9: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 36842, parent: serial8250:0
Oct 11 23:21:42 ryzen kernel: port serial8250:0.9: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: port serial8250:0.10: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 36842, parent: serial8250:0
Oct 11 23:21:42 ryzen kernel: port serial8250:0.10: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: port serial8250:0.11: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 36842, parent: serial8250:0
Oct 11 23:21:42 ryzen kernel: port serial8250:0.11: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: port serial8250:0.12: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 36842, parent: serial8250:0
Oct 11 23:21:42 ryzen kernel: port serial8250:0.12: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: port serial8250:0.13: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 36842, parent: serial8250:0
Oct 11 23:21:42 ryzen kernel: port serial8250:0.13: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: port serial8250:0.14: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 36842, parent: serial8250:0
Oct 11 23:21:42 ryzen kernel: port serial8250:0.14: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: port serial8250:0.15: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 36842, parent: serial8250:0
Oct 11 23:21:42 ryzen kernel: port serial8250:0.15: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: port serial8250:0.16: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 36842, parent: serial8250:0
Oct 11 23:21:42 ryzen kernel: port serial8250:0.16: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: port serial8250:0.17: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 36842, parent: serial8250:0
Oct 11 23:21:42 ryzen kernel: port serial8250:0.17: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: port serial8250:0.18: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 36842, parent: serial8250:0
Oct 11 23:21:42 ryzen kernel: port serial8250:0.18: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: port serial8250:0.19: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 36842, parent: serial8250:0
Oct 11 23:21:42 ryzen kernel: port serial8250:0.19: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: port serial8250:0.20: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 36842, parent: serial8250:0
Oct 11 23:21:42 ryzen kernel: port serial8250:0.20: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: port serial8250:0.21: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 36842, parent: serial8250:0
Oct 11 23:21:42 ryzen kernel: port serial8250:0.21: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: port serial8250:0.22: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 36842, parent: serial8250:0
Oct 11 23:21:42 ryzen kernel: port serial8250:0.22: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: port serial8250:0.23: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 36842, parent: serial8250:0
Oct 11 23:21:42 ryzen kernel: port serial8250:0.23: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: port serial8250:0.24: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 36842, parent: serial8250:0
Oct 11 23:21:42 ryzen kernel: port serial8250:0.24: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: port serial8250:0.25: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 36842, parent: serial8250:0
Oct 11 23:21:42 ryzen kernel: port serial8250:0.25: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: port serial8250:0.26: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 36842, parent: serial8250:0
Oct 11 23:21:42 ryzen kernel: port serial8250:0.26: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: port serial8250:0.27: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 36842, parent: serial8250:0
Oct 11 23:21:42 ryzen kernel: port serial8250:0.27: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: port serial8250:0.28: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 36842, parent: serial8250:0
Oct 11 23:21:42 ryzen kernel: port serial8250:0.28: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: port serial8250:0.29: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 36842, parent: serial8250:0
Oct 11 23:21:42 ryzen kernel: port serial8250:0.29: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: port serial8250:0.30: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 36842, parent: serial8250:0
Oct 11 23:21:42 ryzen kernel: port serial8250:0.30: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: port serial8250:0.31: PM: calling pm_runtime_force_resume+0x0/0xe0 @ 36842, parent: serial8250:0
Oct 11 23:21:42 ryzen kernel: port serial8250:0.31: PM: pm_runtime_force_resume+0x0/0xe0 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: rtc rtc0: PM: calling rtc_resume+0x0/0x240 @ 36842, parent: 00:02
Oct 11 23:21:42 ryzen kernel: rtc rtc0: PM: rtc_resume+0x0/0x240 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: alarmtimer alarmtimer.0.auto: PM: calling platform_pm_resume+0x0/0x50 @ 36842, parent: rtc0
Oct 11 23:21:42 ryzen kernel: alarmtimer alarmtimer.0.auto: PM: platform_pm_resume+0x0/0x50 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: platform microcode: PM: calling platform_pm_resume+0x0/0x50 @ 36842, parent: platform
Oct 11 23:21:42 ryzen kernel: platform microcode: PM: platform_pm_resume+0x0/0x50 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: i8042 i8042: PM: calling platform_pm_resume+0x0/0x50 @ 36842, parent: platform
Oct 11 23:21:42 ryzen kernel: i8042 i8042: PM: platform_pm_resume+0x0/0x50 returned 0 after 55 usecs
Oct 11 23:21:42 ryzen kernel: atkbd serio0: PM: calling serio_resume+0x0/0xa0 [serio] @ 36842, parent: i8042
Oct 11 23:21:42 ryzen kernel: atkbd serio0: PM: serio_resume+0x0/0xa0 [serio] returned 0 after 2 usecs
Oct 11 23:21:42 ryzen kernel: input input2: PM: calling input_dev_resume+0x0/0x40 @ 36842, parent: serio0
Oct 11 23:21:42 ryzen kernel: input input2: PM: input_dev_resume+0x0/0x40 returned 0 after 1 usecs
Oct 11 23:21:42 ryzen kernel: leds input2::numlock: PM: calling led_resume+0x0/0x50 @ 36842, parent: input2
Oct 11 23:21:42 ryzen kernel: leds input2::numlock: PM: led_resume+0x0/0x50 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: leds input2::capslock: PM: calling led_resume+0x0/0x50 @ 36842, parent: input2
Oct 11 23:21:42 ryzen kernel: leds input2::capslock: PM: led_resume+0x0/0x50 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: leds input2::scrolllock: PM: calling led_resume+0x0/0x50 @ 36842, parent: input2
Oct 11 23:21:42 ryzen kernel: leds input2::scrolllock: PM: led_resume+0x0/0x50 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: snd_hda_intel 0000:07:00.4: PM: pci_pm_resume+0x0/0xf0 returned 0 after 4377 usecs
Oct 11 23:21:42 ryzen kernel: snd_hda_codec_realtek hdaudioC2D0: PM: calling hda_codec_pm_resume+0x0/0x20 [snd_hda_codec] @ 36888, parent: 0000:07:00.4
Oct 11 23:21:42 ryzen kernel: usb usb4: PM: usb_dev_resume+0x0/0x20 returned 0 after 26430 usecs
Oct 11 23:21:42 ryzen kernel: xhci_hcd 0000:02:00.0: PM: pci_pm_resume+0x0/0xf0 returned 0 after 56513 usecs
Oct 11 23:21:42 ryzen kernel: usb usb2: PM: calling usb_dev_resume+0x0/0x20 @ 23656, parent: 0000:02:00.0
Oct 11 23:21:42 ryzen kernel: usb usb1: PM: calling usb_dev_resume+0x0/0x20 @ 35357, parent: 0000:02:00.0
Oct 11 23:21:42 ryzen kernel: usb usb3: PM: usb_dev_resume+0x0/0x20 returned 0 after 57506 usecs
Oct 11 23:21:42 ryzen kernel: usb 3-2: PM: calling usb_dev_resume+0x0/0x20 @ 36864, parent: usb3
Oct 11 23:21:42 ryzen kernel: nvme nvme0: Shutdown timeout set to 8 seconds
Oct 11 23:21:42 ryzen kernel: usb 3-2: PM: usb_dev_resume+0x0/0x20 returned 0 after 26489 usecs
Oct 11 23:21:42 ryzen kernel: input input3: PM: calling input_dev_resume+0x0/0x40 @ 36842, parent: 0003:1852:7022.0001
Oct 11 23:21:42 ryzen kernel: input input3: PM: input_dev_resume+0x0/0x40 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: nvme nvme0: 32/0/0 default/read/poll queues
Oct 11 23:21:42 ryzen kernel: snd_hda_codec_realtek hdaudioC2D0: PM: hda_codec_pm_resume+0x0/0x20 [snd_hda_codec] returned 0 after 161642 usecs
Oct 11 23:21:42 ryzen kernel: usb usb1: PM: usb_dev_resume+0x0/0x20 returned 0 after 143356 usecs
Oct 11 23:21:42 ryzen kernel: usb 1-7: PM: calling usb_dev_resume+0x0/0x20 @ 36902, parent: usb1
Oct 11 23:21:42 ryzen kernel: usb 1-3: PM: calling usb_dev_resume+0x0/0x20 @ 36945, parent: usb1
Oct 11 23:21:42 ryzen kernel: usb 1-2: PM: calling usb_dev_resume+0x0/0x20 @ 36929, parent: usb1
Oct 11 23:21:42 ryzen kernel: usb 1-5: PM: calling usb_dev_resume+0x0/0x20 @ 36872, parent: usb1
Oct 11 23:21:42 ryzen kernel: usb 1-1: PM: calling usb_dev_resume+0x0/0x20 @ 32851, parent: usb1
Oct 11 23:21:42 ryzen kernel: usb 1-10: PM: calling usb_dev_resume+0x0/0x20 @ 36899, parent: usb1
Oct 11 23:21:42 ryzen kernel: usb usb2: PM: usb_dev_resume+0x0/0x20 returned 0 after 213355 usecs
Oct 11 23:21:42 ryzen kernel: usb 2-4: PM: calling usb_dev_resume+0x0/0x20 @ 36904, parent: usb2
Oct 11 23:21:42 ryzen kernel: ata3: SATA link down (SStatus 0 SControl 330)
Oct 11 23:21:42 ryzen kernel: ata5: SATA link down (SStatus 0 SControl 330)
Oct 11 23:21:42 ryzen kernel: ata4: SATA link down (SStatus 0 SControl 330)
Oct 11 23:21:42 ryzen kernel: usb 1-2: reset high-speed USB device number 2 using xhci_hcd
Oct 11 23:21:42 ryzen kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
Oct 11 23:21:42 ryzen kernel: ata2.00: configured for UDMA/100
Oct 11 23:21:42 ryzen kernel: [drm] PCIE GART of 256M enabled (table at 0x000000F400800000).
Oct 11 23:21:42 ryzen kernel: usb 1-3: reset full-speed USB device number 13 using xhci_hcd
Oct 11 23:21:42 ryzen kernel: usb 1-2: PM: usb_dev_resume+0x0/0x20 returned 0 after 606638 usecs
Oct 11 23:21:42 ryzen kernel: usb 1-2.1: PM: calling usb_dev_resume+0x0/0x20 @ 36873, parent: 1-2
Oct 11 23:21:42 ryzen kernel: usb 1-2.2: PM: calling usb_dev_resume+0x0/0x20 @ 36874, parent: 1-2
Oct 11 23:21:42 ryzen kernel: usb 1-2.4: PM: calling usb_dev_resume+0x0/0x20 @ 36863, parent: 1-2
Oct 11 23:21:42 ryzen kernel: usb 1-2.3: PM: calling usb_dev_resume+0x0/0x20 @ 36905, parent: 1-2
Oct 11 23:21:42 ryzen kernel: ata6: failed to resume link (SControl 0)
Oct 11 23:21:42 ryzen kernel: ata6: SATA link down (SStatus 0 SControl 0)
Oct 11 23:21:42 ryzen kernel: usb 1-10: reset full-speed USB device number 7 using xhci_hcd
Oct 11 23:21:42 ryzen kernel: usb 1-3: PM: usb_dev_resume+0x0/0x20 returned 0 after 1010252 usecs
Oct 11 23:21:42 ryzen kernel: usb 1-3.1: PM: calling usb_dev_resume+0x0/0x20 @ 36950, parent: 1-3
Oct 11 23:21:42 ryzen kernel: [drm] Fence fallback timer expired on ring sdma0
Oct 11 23:21:42 ryzen kernel: usb 1-10: PM: usb_dev_resume+0x0/0x20 returned 0 after 1200677 usecs
Oct 11 23:21:42 ryzen kernel: usb 1-7: reset full-speed USB device number 5 using xhci_hcd
Oct 11 23:21:42 ryzen kernel: usb 1-7: PM: usb_dev_resume+0x0/0x20 returned 0 after 1612809 usecs
Oct 11 23:21:42 ryzen kernel: [drm] Fence fallback timer expired on ring sdma0
Oct 11 23:21:42 ryzen kernel: usb 1-1: reset high-speed USB device number 10 using xhci_hcd
Oct 11 23:21:42 ryzen kernel: usb 1-1: PM: usb_dev_resume+0x0/0x20 returned 0 after 2103475 usecs
Oct 11 23:21:42 ryzen kernel: usb 1-1.1: PM: calling usb_dev_resume+0x0/0x20 @ 36937, parent: 1-1
Oct 11 23:21:42 ryzen kernel: usb 1-1.4: PM: calling usb_dev_resume+0x0/0x20 @ 36942, parent: 1-1
Oct 11 23:21:42 ryzen kernel: usb 1-5: reset low-speed USB device number 3 using xhci_hcd
Oct 11 23:21:42 ryzen kernel: [drm] Fence fallback timer expired on ring sdma0
Oct 11 23:21:42 ryzen kernel: usb 1-5: PM: usb_dev_resume+0x0/0x20 returned 0 after 2510721 usecs
Oct 11 23:21:42 ryzen kernel: input input4: PM: calling input_dev_resume+0x0/0x40 @ 36842, parent: 0003:05F3:00FF.0002
Oct 11 23:21:42 ryzen kernel: input input4: PM: input_dev_resume+0x0/0x40 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: usb 2-4: reset SuperSpeed USB device number 2 using xhci_hcd
Oct 11 23:21:42 ryzen kernel: usb 2-4: PM: usb_dev_resume+0x0/0x20 returned 0 after 2563590 usecs
Oct 11 23:21:42 ryzen kernel: scsi host6: PM: calling scsi_bus_resume+0x0/0x90 @ 36925, parent: 2-4:1.0
Oct 11 23:21:42 ryzen kernel: scsi host6: PM: scsi_bus_resume+0x0/0x90 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: scsi target6:0:0: PM: calling scsi_bus_resume+0x0/0x90 @ 36914, parent: host6
Oct 11 23:21:42 ryzen kernel: scsi target6:0:0: PM: scsi_bus_resume+0x0/0x90 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: sd 6:0:0:0: PM: calling scsi_bus_resume+0x0/0x90 @ 36921, parent: target6:0:0
Oct 11 23:21:42 ryzen kernel: sd 6:0:0:0: PM: scsi_bus_resume+0x0/0x90 returned 0 after 1 usecs
Oct 11 23:21:42 ryzen kernel: [drm] Fence fallback timer expired on ring sdma0
Oct 11 23:21:42 ryzen kernel: usb 1-2.1: reset full-speed USB device number 4 using xhci_hcd
Oct 11 23:21:42 ryzen kernel: [drm] Fence fallback timer expired on ring sdma0
Oct 11 23:21:42 ryzen kernel: [drm] Fence fallback timer expired on ring sdma0
Oct 11 23:21:42 ryzen kernel: [drm] Fence fallback timer expired on ring sdma0
Oct 11 23:21:42 ryzen kernel: [drm] Fence fallback timer expired on ring sdma0
Oct 11 23:21:42 ryzen kernel: [drm] UVD and UVD ENC initialized successfully.
Oct 11 23:21:42 ryzen kernel: [drm] VCE initialized successfully.
Oct 11 23:21:42 ryzen kernel: amdgpu 0000:05:00.0: PM: pci_pm_resume+0x0/0xf0 returned 0 after 5132839 usecs
Oct 11 23:21:42 ryzen kernel: snd_hda_intel 0000:05:00.1: PM: calling pci_pm_resume+0x0/0xf0 @ 36869, parent: 0000:00:03.1
Oct 11 23:21:42 ryzen kernel: snd_hda_intel 0000:05:00.1: PM: pci_pm_resume+0x0/0xf0 returned 0 after 2363 usecs
Oct 11 23:21:42 ryzen kernel: ata1: link is slow to respond, please be patient (ready=0)
Oct 11 23:21:42 ryzen kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Oct 11 23:21:42 ryzen kernel: ata1.00: configured for UDMA/133
Oct 11 23:21:42 ryzen kernel: usb 1-2.1: PM: usb_dev_resume+0x0/0x20 returned 0 after 7653423 usecs
Oct 11 23:21:42 ryzen kernel: input input5: PM: calling input_dev_resume+0x0/0x40 @ 36842, parent: 0003:0ECB:2057.0003
Oct 11 23:21:42 ryzen kernel: input input5: PM: input_dev_resume+0x0/0x40 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: usb 1-2.2: reset full-speed USB device number 6 using xhci_hcd
Oct 11 23:21:42 ryzen kernel: usb 1-2.2: PM: usb_dev_resume+0x0/0x20 returned 0 after 7976416 usecs
Oct 11 23:21:42 ryzen kernel: input input6: PM: calling input_dev_resume+0x0/0x40 @ 36842, parent: 0003:29EA:0102.0005
Oct 11 23:21:42 ryzen kernel: input input6: PM: input_dev_resume+0x0/0x40 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: input input7: PM: calling input_dev_resume+0x0/0x40 @ 36842, parent: 0003:29EA:0102.0006
Oct 11 23:21:42 ryzen kernel: input input7: PM: input_dev_resume+0x0/0x40 returned 0 after 8 usecs
Oct 11 23:21:42 ryzen kernel: leds input7::numlock: PM: calling led_resume+0x0/0x50 @ 36842, parent: input7
Oct 11 23:21:42 ryzen kernel: leds input7::numlock: PM: led_resume+0x0/0x50 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: leds input7::capslock: PM: calling led_resume+0x0/0x50 @ 36842, parent: input7
Oct 11 23:21:42 ryzen kernel: leds input7::capslock: PM: led_resume+0x0/0x50 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: leds input7::scrolllock: PM: calling led_resume+0x0/0x50 @ 36842, parent: input7
Oct 11 23:21:42 ryzen kernel: leds input7::scrolllock: PM: led_resume+0x0/0x50 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: leds input7::compose: PM: calling led_resume+0x0/0x50 @ 36842, parent: input7
Oct 11 23:21:42 ryzen kernel: leds input7::compose: PM: led_resume+0x0/0x50 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: leds input7::kana: PM: calling led_resume+0x0/0x50 @ 36842, parent: input7
Oct 11 23:21:42 ryzen kernel: leds input7::kana: PM: led_resume+0x0/0x50 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: input input8: PM: calling input_dev_resume+0x0/0x40 @ 36842, parent: 0003:29EA:0102.0007
Oct 11 23:21:42 ryzen kernel: input input8: PM: input_dev_resume+0x0/0x40 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: input input9: PM: calling input_dev_resume+0x0/0x40 @ 36842, parent: 0003:29EA:0102.0007
Oct 11 23:21:42 ryzen kernel: input input9: PM: input_dev_resume+0x0/0x40 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: usb 1-2.4: reset full-speed USB device number 9 using xhci_hcd
Oct 11 23:21:42 ryzen kernel: usb 1-2.4: PM: usb_dev_resume+0x0/0x20 returned 0 after 8258091 usecs
Oct 11 23:21:42 ryzen kernel: usb 1-2.3: reset full-speed USB device number 8 using xhci_hcd
Oct 11 23:21:42 ryzen kernel: usb 1-2.3: PM: usb_dev_resume+0x0/0x20 returned 0 after 8557381 usecs
Oct 11 23:21:42 ryzen kernel: input input10: PM: calling input_dev_resume+0x0/0x40 @ 36842, parent: 0003:046D:C092.0009
Oct 11 23:21:42 ryzen kernel: input input10: PM: input_dev_resume+0x0/0x40 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: input input11: PM: calling input_dev_resume+0x0/0x40 @ 36842, parent: 0003:046D:C092.000A
Oct 11 23:21:42 ryzen kernel: input input11: PM: input_dev_resume+0x0/0x40 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: sp5100-tco sp5100-tco: PM: calling platform_pm_resume+0x0/0x50 @ 36842, parent: platform
Oct 11 23:21:42 ryzen kernel: sp5100-tco sp5100-tco: PM: platform_pm_resume+0x0/0x50 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: input input14: PM: calling input_dev_resume+0x0/0x40 @ 36842, parent: pcspkr
Oct 11 23:21:42 ryzen kernel: input input14: PM: input_dev_resume+0x0/0x40 returned 0 after 11 usecs
Oct 11 23:21:42 ryzen kernel: input input15: PM: calling input_dev_resume+0x0/0x40 @ 36842, parent: card1
Oct 11 23:21:42 ryzen kernel: input input15: PM: input_dev_resume+0x0/0x40 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: input input16: PM: calling input_dev_resume+0x0/0x40 @ 36842, parent: card1
Oct 11 23:21:42 ryzen kernel: input input16: PM: input_dev_resume+0x0/0x40 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: input input17: PM: calling input_dev_resume+0x0/0x40 @ 36842, parent: card1
Oct 11 23:21:42 ryzen kernel: input input17: PM: input_dev_resume+0x0/0x40 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: input input18: PM: calling input_dev_resume+0x0/0x40 @ 36842, parent: card1
Oct 11 23:21:42 ryzen kernel: input input18: PM: input_dev_resume+0x0/0x40 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: input input19: PM: calling input_dev_resume+0x0/0x40 @ 36842, parent: card1
Oct 11 23:21:42 ryzen kernel: input input19: PM: input_dev_resume+0x0/0x40 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: input input20: PM: calling input_dev_resume+0x0/0x40 @ 36842, parent: card1
Oct 11 23:21:42 ryzen kernel: input input20: PM: input_dev_resume+0x0/0x40 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: input input21: PM: calling input_dev_resume+0x0/0x40 @ 36842, parent: card2
Oct 11 23:21:42 ryzen kernel: input input21: PM: input_dev_resume+0x0/0x40 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: input input22: PM: calling input_dev_resume+0x0/0x40 @ 36842, parent: card2
Oct 11 23:21:42 ryzen kernel: input input22: PM: input_dev_resume+0x0/0x40 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: input input23: PM: calling input_dev_resume+0x0/0x40 @ 36842, parent: card2
Oct 11 23:21:42 ryzen kernel: input input23: PM: input_dev_resume+0x0/0x40 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: input input24: PM: calling input_dev_resume+0x0/0x40 @ 36842, parent: card2
Oct 11 23:21:42 ryzen kernel: input input24: PM: input_dev_resume+0x0/0x40 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: input input25: PM: calling input_dev_resume+0x0/0x40 @ 36842, parent: card2
Oct 11 23:21:42 ryzen kernel: input input25: PM: input_dev_resume+0x0/0x40 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: Generic FE-GE Realtek PHY r8169-0-400:00: PM: calling mdio_bus_phy_resume+0x0/0x130 [libphy] @ 36842, parent: r8169-0-400
Oct 11 23:21:42 ryzen kernel: Generic FE-GE Realtek PHY r8169-0-400:00: PM: mdio_bus_phy_resume+0x0/0x130 [libphy] returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: intel_rapl_msr intel_rapl_msr.0: PM: calling platform_pm_resume+0x0/0x50 @ 36842, parent: platform
Oct 11 23:21:42 ryzen kernel: intel_rapl_msr intel_rapl_msr.0: PM: platform_pm_resume+0x0/0x50 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: usb 1-3.1: reset low-speed USB device number 14 using xhci_hcd
Oct 11 23:21:42 ryzen kernel: usb 1-3.1: PM: usb_dev_resume+0x0/0x20 returned 0 after 8793089 usecs
Oct 11 23:21:42 ryzen kernel: usb 1-1.1: reset low-speed USB device number 11 using xhci_hcd
Oct 11 23:21:42 ryzen kernel: usb 1-1.1: PM: usb_dev_resume+0x0/0x20 returned 0 after 8394523 usecs
Oct 11 23:21:42 ryzen kernel: input input26: PM: calling input_dev_resume+0x0/0x40 @ 36842, parent: 0003:09EB:0131.000C
Oct 11 23:21:42 ryzen kernel: input input26: PM: input_dev_resume+0x0/0x40 returned 0 after 8 usecs
Oct 11 23:21:42 ryzen kernel: leds input26::numlock: PM: calling led_resume+0x0/0x50 @ 36842, parent: input26
Oct 11 23:21:42 ryzen kernel: leds input26::numlock: PM: led_resume+0x0/0x50 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: leds input26::capslock: PM: calling led_resume+0x0/0x50 @ 36842, parent: input26
Oct 11 23:21:42 ryzen kernel: leds input26::capslock: PM: led_resume+0x0/0x50 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: leds input26::scrolllock: PM: calling led_resume+0x0/0x50 @ 36842, parent: input26
Oct 11 23:21:42 ryzen kernel: leds input26::scrolllock: PM: led_resume+0x0/0x50 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: leds input26::compose: PM: calling led_resume+0x0/0x50 @ 36842, parent: input26
Oct 11 23:21:42 ryzen kernel: leds input26::compose: PM: led_resume+0x0/0x50 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: leds input26::kana: PM: calling led_resume+0x0/0x50 @ 36842, parent: input26
Oct 11 23:21:42 ryzen kernel: leds input26::kana: PM: led_resume+0x0/0x50 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: input input27: PM: calling input_dev_resume+0x0/0x40 @ 36842, parent: 0003:09EB:0131.000D
Oct 11 23:21:42 ryzen kernel: input input27: PM: input_dev_resume+0x0/0x40 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: input input28: PM: calling input_dev_resume+0x0/0x40 @ 36842, parent: 0003:09EB:0131.000D
Oct 11 23:21:42 ryzen kernel: input input28: PM: input_dev_resume+0x0/0x40 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: input input29: PM: calling input_dev_resume+0x0/0x40 @ 36842, parent: 0003:09EB:0131.000D
Oct 11 23:21:42 ryzen kernel: input input29: PM: input_dev_resume+0x0/0x40 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: usb 1-1.4: reset low-speed USB device number 12 using xhci_hcd
Oct 11 23:21:42 ryzen kernel: usb 1-1.4: PM: usb_dev_resume+0x0/0x20 returned 0 after 9022377 usecs
Oct 11 23:21:42 ryzen kernel: input input30: PM: calling input_dev_resume+0x0/0x40 @ 36842, parent: 0003:046D:C016.000E
Oct 11 23:21:42 ryzen kernel: input input30: PM: input_dev_resume+0x0/0x40 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: input input31: PM: calling input_dev_resume+0x0/0x40 @ 36842, parent: 0003:413C:2006.000F
Oct 11 23:21:42 ryzen kernel: input input31: PM: input_dev_resume+0x0/0x40 returned 0 after 9 usecs
Oct 11 23:21:42 ryzen kernel: leds input31::numlock: PM: calling led_resume+0x0/0x50 @ 36842, parent: input31
Oct 11 23:21:42 ryzen kernel: leds input31::numlock: PM: led_resume+0x0/0x50 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: leds input31::capslock: PM: calling led_resume+0x0/0x50 @ 36842, parent: input31
Oct 11 23:21:42 ryzen kernel: leds input31::capslock: PM: led_resume+0x0/0x50 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: leds input31::scrolllock: PM: calling led_resume+0x0/0x50 @ 36842, parent: input31
Oct 11 23:21:42 ryzen kernel: leds input31::scrolllock: PM: led_resume+0x0/0x50 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: leds input31::compose: PM: calling led_resume+0x0/0x50 @ 36842, parent: input31
Oct 11 23:21:42 ryzen kernel: leds input31::compose: PM: led_resume+0x0/0x50 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: leds input31::kana: PM: calling led_resume+0x0/0x50 @ 36842, parent: input31
Oct 11 23:21:42 ryzen kernel: leds input31::kana: PM: led_resume+0x0/0x50 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: input input32: PM: calling input_dev_resume+0x0/0x40 @ 36842, parent: 0003:413C:2006.0010
Oct 11 23:21:42 ryzen kernel: input input32: PM: input_dev_resume+0x0/0x40 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: input input33: PM: calling input_dev_resume+0x0/0x40 @ 36842, parent: 0003:413C:2006.0010
Oct 11 23:21:42 ryzen kernel: input input33: PM: input_dev_resume+0x0/0x40 returned 0 after 0 usecs
Oct 11 23:21:42 ryzen kernel: PM: resume of devices complete after 11326.174 msecs
Oct 11 23:21:42 ryzen kernel: OOM killer enabled.
Oct 11 23:21:42 ryzen kernel: Restarting tasks ... done.
Oct 11 23:21:42 ryzen kernel: random: crng reseeded on system resumption
Oct 11 23:21:42 ryzen kernel: PM: suspend exit
Oct 11 23:21:42 ryzen rtkit-daemon[1365]: The canary thread is apparently starving. Taking action.
Oct 11 23:21:42 ryzen systemd-sleep[36842]: System returned from sleep state.
Oct 11 23:21:42 ryzen rtkit-daemon[1365]: Demoting known real-time threads.
Oct 11 23:21:42 ryzen systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
Oct 11 23:21:42 ryzen rtkit-daemon[1365]: Successfully demoted thread 27901 of process 27619.
Oct 11 23:21:42 ryzen systemd-udevd[364]: /etc/udev/rules.d/30-usbtmc.rules:5 Unknown group 'usbtmc', ignoring.
Oct 11 23:21:42 ryzen rtkit-daemon[1365]: Demoted 1 threads.
Oct 11 23:21:42 ryzen systemd-udevd[364]: /etc/udev/rules.d/30-usbtmc.rules:8 Unknown group 'usbtmc', ignoring.
Oct 11 23:21:42 ryzen /usr/bin/gpm[827]: *** info [mice.c(1990)]:
Oct 11 23:21:42 ryzen systemd-udevd[364]: /etc/udev/rules.d/30-usbtmc.rules:11 Unknown group 'usbtmc', ignoring.
Oct 11 23:21:42 ryzen /usr/bin/gpm[827]: imps2: Auto-detected intellimouse PS/2
Oct 11 23:21:42 ryzen systemd-udevd[364]: /etc/udev/rules.d/30-usbtmc.rules:14 Unknown group 'usbtmc', ignoring.
Oct 11 23:21:42 ryzen systemd-udevd[364]: /etc/udev/rules.d/30-usbtmc.rules:15 Unknown group 'usbtmc', ignoring.
Oct 11 23:21:42 ryzen systemd-udevd[364]: /usr/lib/udev/rules.d/51-footcontroller.rules:10 Invalid value for OPTIONS key, ignoring: 'last_rule'
Oct 11 23:21:42 ryzen systemd[1]: systemd-suspend.service: Deactivated successfully.
Oct 11 23:21:42 ryzen systemd[1]: Finished System Suspend.
Oct 11 23:21:42 ryzen systemd[1]: systemd-suspend.service: Consumed 3.067s CPU time.
Oct 11 23:21:42 ryzen systemd[1]: Stopped target Sleep.
Oct 11 23:21:42 ryzen systemd[1]: Reached target Suspend.
Oct 11 23:21:42 ryzen systemd[1]: Stopped target Suspend.
Oct 11 23:21:43 ryzen systemd-logind[830]: Operation 'sleep' finished.
Oct 11 23:21:43 ryzen NetworkManager[927]: <info> [1697091703.4130] manager: sleep: wake requested (sleeping: yes enabled: yes)
Oct 11 23:21:43 ryzen NetworkManager[927]: <info> [1697091703.4131] device (enp4s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Oct 11 23:21:43 ryzen kernel: Generic FE-GE Realtek PHY r8169-0-400:00: attached PHY driver (mii_bus:phy_addr=r8169-0-400:00, irq=MAC)
Oct 11 23:21:43 ryzen NetworkManager[927]: <info> [1697091703.6395] manager: NetworkManager state is now CONNECTED_LOCAL
Oct 11 23:21:43 ryzen kernel: r8169 0000:04:00.0 enp4s0: Link is Down
Oct 11 23:21:43 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 23:21:43 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 23:21:44 ryzen dbus-daemon[824]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.431' (uid=1001 pid=36690 comm="/usr/lib/kscreenlocker_greet --immediateLock --gra")
Oct 11 23:21:44 ryzen dbus-daemon[824]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.
Oct 11 23:21:46 ryzen NetworkManager[927]: <info> [1697091706.3242] device (enp4s0): carrier: link connected
Oct 11 23:21:46 ryzen NetworkManager[927]: <info> [1697091706.3244] device (enp4s0): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed')
Oct 11 23:21:46 ryzen NetworkManager[927]: <info> [1697091706.3249] policy: auto-activating connection 'Wired connection 1' (1a78b687-138e-3a66-9ca0-dc365ee4d000)
Oct 11 23:21:46 ryzen NetworkManager[927]: <info> [1697091706.3252] device (enp4s0): Activation: starting connection 'Wired connection 1' (1a78b687-138e-3a66-9ca0-dc365ee4d000)
Oct 11 23:21:46 ryzen NetworkManager[927]: <info> [1697091706.3252] device (enp4s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Oct 11 23:21:46 ryzen NetworkManager[927]: <info> [1697091706.3254] manager: NetworkManager state is now CONNECTING
Oct 11 23:21:46 ryzen NetworkManager[927]: <info> [1697091706.3254] device (enp4s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Oct 11 23:21:46 ryzen kernel: r8169 0000:04:00.0 enp4s0: Link is Up - 1Gbps/Full - flow control rx/tx
Oct 11 23:21:46 ryzen NetworkManager[927]: <info> [1697091706.3257] device (enp4s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Oct 11 23:21:46 ryzen NetworkManager[927]: <info> [1697091706.3261] dhcp4 (enp4s0): activation: beginning transaction (timeout in 45 seconds)
Oct 11 23:21:46 ryzen dnsmasq[1089]: reading /etc/resolv.conf
Oct 11 23:21:46 ryzen dnsmasq[1056]: reading /etc/resolv.conf
Oct 11 23:21:46 ryzen dnsmasq[1089]: using nameserver 1.1.1.1#53
Oct 11 23:21:46 ryzen dnsmasq[1056]: using nameserver 1.1.1.1#53
Oct 11 23:21:46 ryzen NetworkManager[927]: <info> [1697091706.3394] dhcp4 (enp4s0): state changed new lease, address=192.168.0.91
Oct 11 23:21:46 ryzen NetworkManager[927]: <info> [1697091706.3397] policy: set 'Wired connection 1' (enp4s0) as default for IPv4 routing and DNS
Oct 11 23:21:46 ryzen dnsmasq[1089]: reading /etc/resolv.conf
Oct 11 23:21:46 ryzen dnsmasq[1056]: reading /etc/resolv.conf
Oct 11 23:21:46 ryzen dnsmasq[1089]: using nameserver 1.1.1.1#53
Oct 11 23:21:46 ryzen dnsmasq[1089]: using nameserver 8.8.8.8#53
Oct 11 23:21:46 ryzen dnsmasq[1056]: using nameserver 1.1.1.1#53
Oct 11 23:21:46 ryzen dnsmasq[1056]: using nameserver 8.8.8.8#53
Oct 11 23:21:46 ryzen avahi-daemon[823]: Joining mDNS multicast group on interface enp4s0.IPv4 with address 192.168.0.91.
Oct 11 23:21:46 ryzen avahi-daemon[823]: New relevant interface enp4s0.IPv4 for mDNS.
Oct 11 23:21:46 ryzen avahi-daemon[823]: Registering new address record for 192.168.0.91 on enp4s0.IPv4.
Oct 11 23:21:46 ryzen avahi-daemon[823]: Joining mDNS multicast group on interface enp4s0.IPv6 with address fe80::1b36:1dd4:a5cf:3b8f.
Oct 11 23:21:46 ryzen avahi-daemon[823]: New relevant interface enp4s0.IPv6 for mDNS.
Oct 11 23:21:46 ryzen avahi-daemon[823]: Registering new address record for fe80::1b36:1dd4:a5cf:3b8f on enp4s0.*.
Oct 11 23:21:46 ryzen dbus-daemon[824]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.4' (uid=0 pid=927 comm="/usr/bin/NetworkManager --no-daemon")
Oct 11 23:21:46 ryzen NetworkManager[927]: <info> [1697091706.3519] device (enp4s0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Oct 11 23:21:46 ryzen systemd[1]: Starting Network Manager Script Dispatcher Service...
Oct 11 23:21:46 ryzen dbus-daemon[824]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Oct 11 23:21:46 ryzen systemd[1]: Started Network Manager Script Dispatcher Service.
Oct 11 23:21:46 ryzen NetworkManager[927]: <info> [1697091706.3856] device (enp4s0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Oct 11 23:21:46 ryzen NetworkManager[927]: <info> [1697091706.3857] device (enp4s0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Oct 11 23:21:46 ryzen NetworkManager[927]: <info> [1697091706.3858] manager: NetworkManager state is now CONNECTED_SITE
Oct 11 23:21:46 ryzen NetworkManager[927]: <info> [1697091706.3859] device (enp4s0): Activation: successful, device activated.
Oct 11 23:21:46 ryzen NetworkManager[927]: <info> [1697091706.7826] manager: NetworkManager state is now CONNECTED_GLOBAL
Oct 11 23:21:47 ryzen NetworkManager[927]: <info> [1697091707.9105] dhcp6 (enp4s0): activation: beginning transaction (timeout in 45 seconds)
Oct 11 23:21:47 ryzen dnsmasq[1089]: reading /etc/resolv.conf
Oct 11 23:21:47 ryzen dnsmasq[1056]: reading /etc/resolv.conf
Oct 11 23:21:47 ryzen dnsmasq[1056]: using nameserver 1.1.1.1#53
Oct 11 23:21:47 ryzen dnsmasq[1089]: using nameserver 1.1.1.1#53
Oct 11 23:21:47 ryzen dnsmasq[1056]: using nameserver 8.8.8.8#53
Oct 11 23:21:47 ryzen dnsmasq[1089]: using nameserver 8.8.8.8#53
Oct 11 23:21:47 ryzen dnsmasq[1056]: using nameserver fde3:5408:101c::1#53
Oct 11 23:21:47 ryzen dnsmasq[1089]: using nameserver fde3:5408:101c::1#53
Oct 11 23:21:47 ryzen NetworkManager[927]: <info> [1697091707.9173] dhcp6 (enp4s0): state changed new lease, address=fde3:5408:101c::566
Oct 11 23:21:47 ryzen avahi-daemon[823]: Leaving mDNS multicast group on interface enp4s0.IPv6 with address fe80::1b36:1dd4:a5cf:3b8f.
Oct 11 23:21:47 ryzen avahi-daemon[823]: Joining mDNS multicast group on interface enp4s0.IPv6 with address fde3:5408:101c:0:7441:9d56:d3c1:1a95.
Oct 11 23:21:47 ryzen avahi-daemon[823]: Registering new address record for fde3:5408:101c:0:7441:9d56:d3c1:1a95 on enp4s0.*.
Oct 11 23:21:47 ryzen avahi-daemon[823]: Withdrawing address record for fe80::1b36:1dd4:a5cf:3b8f on enp4s0.
Oct 11 23:21:47 ryzen avahi-daemon[823]: Registering new address record for fde3:5408:101c::566 on enp4s0.*.
Oct 11 23:21:51 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 23:21:51 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 23:21:53 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 23:21:53 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 23:21:56 ryzen systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
Oct 11 23:21:56 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 23:21:56 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 23:21:56 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 23:21:56 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 23:21:56 ryzen rtkit-daemon[1365]: Recovering from system lockup, not allowing further RT threads.
Oct 11 23:21:56 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 23:21:56 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 23:23:10 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 23:23:10 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 23:23:10 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 23:23:10 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 23:23:10 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 23:23:10 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 23:23:10 ryzen rtkit-daemon[1365]: Recovering from system lockup, not allowing further RT threads.
Oct 11 23:23:10 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 23:23:10 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 23:23:11 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 23:23:11 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 23:23:11 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 23:23:11 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 23:23:11 ryzen rtkit-daemon[1365]: Recovering from system lockup, not allowing further RT threads.
Oct 11 23:23:24 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 23:23:24 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 23:23:48 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 23:23:48 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 23:23:48 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 23:23:48 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 23:23:48 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 23:23:48 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 23:23:48 ryzen rtkit-daemon[1365]: Recovering from system lockup, not allowing further RT threads.
Oct 11 23:24:31 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 23:24:31 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 23:28:47 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 23:28:47 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 23:28:49 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 23:28:49 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 23:28:49 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 23:28:49 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 23:29:38 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 23:29:38 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 23:36:57 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 23:36:57 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 23:55:52 ryzen systemd-timesyncd[815]: Contacted time server 162.159.200.123:123 (0.arch.pool.ntp.org).
Oct 11 23:56:32 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 23:56:32 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 23:56:53 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 23:56:53 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 23:58:20 ryzen systemd-journald[309]: Suppressed 128346 messages from user@1001.service
Oct 11 23:59:42 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 11 23:59:42 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 12 00:00:37 ryzen systemd[1]: Started Verify integrity of password and group files.
Oct 12 00:00:37 ryzen systemd[1]: shadow.service: Deactivated successfully.
Oct 12 00:06:11 ryzen dbus-daemon[824]: [system] Activating service name='org.kde.filesharing.samba' requested by ':1.254' (uid=1001 pid=16778 comm="/usr/bin/dolphin /home/nyanpasu64/Downloads") (using servicehelper)
Oct 12 00:06:11 ryzen dbus-daemon[824]: [system] Successfully activated service 'org.kde.filesharing.samba'
Oct 12 00:09:23 ryzen dbus-daemon[824]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.471' (uid=1001 pid=40621 comm="/usr/lib/electron27/electron /usr/share/armcord/ap")
Oct 12 00:09:23 ryzen systemd[1]: Bluetooth service was skipped because of an unmet condition check (ConditionPathIsDirectory=/sys/class/bluetooth).
Oct 12 00:09:48 ryzen dbus-daemon[824]: [system] Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms)
Oct 12 00:13:47 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 12 00:13:47 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 12 00:16:24 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 12 00:16:24 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 12 00:16:27 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 12 00:16:27 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 12 00:16:43 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 12 00:16:43 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 12 00:16:52 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 12 00:16:52 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 12 00:17:08 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 12 00:17:08 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 12 00:17:08 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 12 00:17:08 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 12 00:21:34 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 12 00:21:34 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 12 00:21:36 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 12 00:21:36 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 12 00:26:16 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 12 00:26:16 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 12 00:27:11 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 12 00:27:11 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 12 00:27:11 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 12 00:27:11 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 12 00:27:11 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 12 00:27:11 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 12 00:27:11 ryzen rtkit-daemon[1365]: Successfully made thread 42600 of process 42540 owned by '1001' RT at priority 10.
Oct 12 00:27:11 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 12 00:36:16 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 12 00:36:16 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 12 00:36:54 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 12 00:36:54 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 12 00:36:54 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 12 00:36:54 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 12 00:36:54 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 12 00:36:54 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 12 00:36:54 ryzen rtkit-daemon[1365]: Successfully made thread 43339 of process 43282 owned by '1001' RT at priority 10.
Oct 12 00:36:54 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 12 00:39:56 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 12 00:39:56 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 12 00:40:03 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 12 00:40:03 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 12 00:40:41 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 12 00:40:41 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 12 00:40:41 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 12 00:40:41 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 12 00:45:19 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 12 00:45:19 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 12 00:54:34 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 12 00:54:34 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 12 00:54:36 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 12 00:54:36 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 12 01:03:38 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 12 01:03:38 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 12 01:03:44 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 12 01:03:44 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 12 01:04:28 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 12 01:04:28 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 12 01:04:33 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 12 01:04:33 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 12 01:04:33 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 12 01:04:33 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 12 01:04:33 ryzen rtkit-daemon[1365]: Successfully made thread 46105 of process 45362 owned by '1001' RT at priority 10.
Oct 12 01:04:33 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 12 01:05:05 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 12 01:05:05 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 12 01:05:29 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 12 01:05:29 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 12 01:05:32 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 12 01:05:32 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 12 01:05:32 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 12 01:05:32 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 12 01:06:11 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 12 01:06:11 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 12 01:06:14 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 12 01:06:14 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 12 01:06:17 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 12 01:06:17 ryzen rtkit-daemon[1365]: Supervising 1 threads of 1 processes of 1 users.
Oct 12 01:08:16 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 12 01:08:16 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 12 01:08:18 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 12 01:08:18 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 12 01:08:18 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 12 01:08:18 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 12 01:08:27 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 12 01:08:27 ryzen rtkit-daemon[1365]: Supervising 0 threads of 0 processes of 0 users.
Oct 12 01:11:15 ryzen systemd-logind[830]: The system will suspend now!
Oct 12 01:11:15 ryzen NetworkManager[927]: <info> [1697098275.8643] manager: sleep: sleep requested (sleeping: no enabled: yes)
Oct 12 01:11:15 ryzen NetworkManager[927]: <info> [1697098275.8644] manager: NetworkManager state is now ASLEEP
Oct 12 01:11:15 ryzen NetworkManager[927]: <info> [1697098275.8645] device (enp4s0): state change: activated -> deactivating (reason 'sleeping', sys-iface-state: 'managed')
Oct 12 01:11:15 ryzen dbus-daemon[824]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.4' (uid=0 pid=927 comm="/usr/bin/NetworkManager --no-daemon")
Oct 12 01:11:15 ryzen systemd[1]: Starting Network Manager Script Dispatcher Service...
Oct 12 01:11:15 ryzen dbus-daemon[824]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Oct 12 01:11:15 ryzen systemd[1]: Started Network Manager Script Dispatcher Service.
Oct 12 01:11:15 ryzen NetworkManager[927]: <info> [1697098275.9041] device (enp4s0): state change: deactivating -> disconnected (reason 'sleeping', sys-iface-state: 'managed')
Oct 12 01:11:15 ryzen avahi-daemon[823]: Withdrawing address record for fde3:5408:101c::566 on enp4s0.
Oct 12 01:11:15 ryzen avahi-daemon[823]: Withdrawing address record for fde3:5408:101c:0:7441:9d56:d3c1:1a95 on enp4s0.
Oct 12 01:11:15 ryzen NetworkManager[927]: <info> [1697098275.9054] dhcp4 (enp4s0): canceled DHCP transaction
Oct 12 01:11:15 ryzen avahi-daemon[823]: Leaving mDNS multicast group on interface enp4s0.IPv6 with address fde3:5408:101c:0:7441:9d56:d3c1:1a95.
Oct 12 01:11:15 ryzen NetworkManager[927]: <info> [1697098275.9054] dhcp4 (enp4s0): activation: beginning transaction (timeout in 45 seconds)
Oct 12 01:11:15 ryzen avahi-daemon[823]: Joining mDNS multicast group on interface enp4s0.IPv6 with address fe80::1b36:1dd4:a5cf:3b8f.
Oct 12 01:11:15 ryzen NetworkManager[927]: <info> [1697098275.9054] dhcp4 (enp4s0): state changed no lease
Oct 12 01:11:15 ryzen avahi-daemon[823]: Registering new address record for fe80::1b36:1dd4:a5cf:3b8f on enp4s0.*.
Oct 12 01:11:15 ryzen NetworkManager[927]: <info> [1697098275.9056] dhcp6 (enp4s0): canceled DHCP transaction
Oct 12 01:11:15 ryzen avahi-daemon[823]: Withdrawing address record for fe80::1b36:1dd4:a5cf:3b8f on enp4s0.
Oct 12 01:11:15 ryzen NetworkManager[927]: <info> [1697098275.9056] dhcp6 (enp4s0): activation: beginning transaction (timeout in 45 seconds)
Oct 12 01:11:15 ryzen avahi-daemon[823]: Leaving mDNS multicast group on interface enp4s0.IPv6 with address fe80::1b36:1dd4:a5cf:3b8f.
Oct 12 01:11:15 ryzen NetworkManager[927]: <info> [1697098275.9056] dhcp6 (enp4s0): state changed no lease
Oct 12 01:11:15 ryzen avahi-daemon[823]: Interface enp4s0.IPv6 no longer relevant for mDNS.
Oct 12 01:11:15 ryzen dnsmasq[1089]: no servers found in /etc/resolv.conf, will retry
Oct 12 01:11:15 ryzen dnsmasq[1056]: no servers found in /etc/resolv.conf, will retry
Oct 12 01:11:15 ryzen avahi-daemon[823]: Withdrawing address record for 192.168.0.91 on enp4s0.
Oct 12 01:11:15 ryzen avahi-daemon[823]: Leaving mDNS multicast group on interface enp4s0.IPv4 with address 192.168.0.91.
Oct 12 01:11:15 ryzen avahi-daemon[823]: Interface enp4s0.IPv4 no longer relevant for mDNS.
Oct 12 01:11:15 ryzen NetworkManager[927]: <info> [1697098275.9480] device (enp4s0): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Oct 12 01:11:15 ryzen kernel: r8169 0000:04:00.0 enp4s0: Link is Down
Oct 12 01:11:16 ryzen systemd[1]: Reached target Sleep.
Oct 12 01:11:16 ryzen systemd[1]: Starting System Suspend...
Oct 12 01:11:16 ryzen systemd-sleep[47526]: Entering sleep state 'suspend'...
Oct 12 01:11:16 ryzen kernel: PM: suspend entry (deep)
Oct 12 01:11:16 ryzen kernel: Filesystems sync: 0.049 seconds
Oct 12 13:14:18 ryzen kernel: Freezing user space processes
Oct 12 13:14:18 ryzen kernel: Freezing user space processes completed (elapsed 0.001 seconds)
Oct 12 13:14:18 ryzen kernel: OOM killer disabled.
Oct 12 13:14:18 ryzen kernel: Freezing remaining freezable tasks
Oct 12 13:14:18 ryzen kernel: Freezing remaining freezable tasks completed (elapsed 0.001 seconds)
Oct 12 13:14:18 ryzen kernel: input input33: PM: calling input_dev_suspend+0x0/0x70 @ 47526, parent: 0003:413C:2006.0010
Oct 12 13:14:18 ryzen kernel: input input33: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: input input32: PM: calling input_dev_suspend+0x0/0x70 @ 47526, parent: 0003:413C:2006.0010
Oct 12 13:14:18 ryzen kernel: input input32: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: leds input31::kana: PM: calling led_suspend+0x0/0x50 @ 47526, parent: input31
Oct 12 13:14:18 ryzen kernel: leds input31::kana: PM: led_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: leds input31::compose: PM: calling led_suspend+0x0/0x50 @ 47526, parent: input31
Oct 12 13:14:18 ryzen kernel: leds input31::compose: PM: led_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: leds input31::scrolllock: PM: calling led_suspend+0x0/0x50 @ 47526, parent: input31
Oct 12 13:14:18 ryzen kernel: leds input31::scrolllock: PM: led_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: leds input31::capslock: PM: calling led_suspend+0x0/0x50 @ 47526, parent: input31
Oct 12 13:14:18 ryzen kernel: leds input31::capslock: PM: led_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: leds input31::numlock: PM: calling led_suspend+0x0/0x50 @ 47526, parent: input31
Oct 12 13:14:18 ryzen kernel: leds input31::numlock: PM: led_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: input input31: PM: calling input_dev_suspend+0x0/0x70 @ 47526, parent: 0003:413C:2006.000F
Oct 12 13:14:18 ryzen kernel: input input31: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: input input30: PM: calling input_dev_suspend+0x0/0x70 @ 47526, parent: 0003:046D:C016.000E
Oct 12 13:14:18 ryzen kernel: input input30: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: usb 1-3.1: PM: calling usb_dev_suspend+0x0/0x20 @ 39439, parent: 1-3
Oct 12 13:14:18 ryzen kernel: input input29: PM: calling input_dev_suspend+0x0/0x70 @ 47526, parent: 0003:09EB:0131.000D
Oct 12 13:14:18 ryzen kernel: input input29: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: input input28: PM: calling input_dev_suspend+0x0/0x70 @ 47526, parent: 0003:09EB:0131.000D
Oct 12 13:14:18 ryzen kernel: usb 1-1.4: PM: calling usb_dev_suspend+0x0/0x20 @ 36953, parent: 1-1
Oct 12 13:14:18 ryzen kernel: input input28: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: input input27: PM: calling input_dev_suspend+0x0/0x70 @ 47526, parent: 0003:09EB:0131.000D
Oct 12 13:14:18 ryzen kernel: input input27: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: leds input26::kana: PM: calling led_suspend+0x0/0x50 @ 47526, parent: input26
Oct 12 13:14:18 ryzen kernel: leds input26::kana: PM: led_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: leds input26::compose: PM: calling led_suspend+0x0/0x50 @ 47526, parent: input26
Oct 12 13:14:18 ryzen kernel: leds input26::compose: PM: led_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: leds input26::scrolllock: PM: calling led_suspend+0x0/0x50 @ 47526, parent: input26
Oct 12 13:14:18 ryzen kernel: leds input26::scrolllock: PM: led_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: leds input26::capslock: PM: calling led_suspend+0x0/0x50 @ 47526, parent: input26
Oct 12 13:14:18 ryzen kernel: leds input26::capslock: PM: led_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: leds input26::numlock: PM: calling led_suspend+0x0/0x50 @ 47526, parent: input26
Oct 12 13:14:18 ryzen kernel: leds input26::numlock: PM: led_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: input input26: PM: calling input_dev_suspend+0x0/0x70 @ 47526, parent: 0003:09EB:0131.000C
Oct 12 13:14:18 ryzen kernel: input input26: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: usb 1-1.1: PM: calling usb_dev_suspend+0x0/0x20 @ 36943, parent: 1-1
Oct 12 13:14:18 ryzen kernel: intel_rapl_msr intel_rapl_msr.0: PM: calling platform_pm_suspend+0x0/0x50 @ 47526, parent: platform
Oct 12 13:14:18 ryzen kernel: intel_rapl_msr intel_rapl_msr.0: PM: platform_pm_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: Generic FE-GE Realtek PHY r8169-0-400:00: PM: calling mdio_bus_phy_suspend+0x0/0x120 [libphy] @ 47526, parent: r8169-0-400
Oct 12 13:14:18 ryzen kernel: Generic FE-GE Realtek PHY r8169-0-400:00: PM: mdio_bus_phy_suspend+0x0/0x120 [libphy] returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: sound pcmC3D0c: PM: calling do_pcm_suspend+0x0/0x30 [snd_pcm] @ 47526, parent: card3
Oct 12 13:14:18 ryzen kernel: sound pcmC3D0c: PM: do_pcm_suspend+0x0/0x30 [snd_pcm] returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: sound pcmC3D0p: PM: calling do_pcm_suspend+0x0/0x30 [snd_pcm] @ 47526, parent: card3
Oct 12 13:14:18 ryzen kernel: sound pcmC3D0p: PM: do_pcm_suspend+0x0/0x30 [snd_pcm] returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: sound pcmC0D1p: PM: calling do_pcm_suspend+0x0/0x30 [snd_pcm] @ 47526, parent: card0
Oct 12 13:14:18 ryzen kernel: sound pcmC0D1p: PM: do_pcm_suspend+0x0/0x30 [snd_pcm] returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: sound pcmC0D0c: PM: calling do_pcm_suspend+0x0/0x30 [snd_pcm] @ 47526, parent: card0
Oct 12 13:14:18 ryzen kernel: sound pcmC0D0c: PM: do_pcm_suspend+0x0/0x30 [snd_pcm] returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: sound pcmC0D0p: PM: calling do_pcm_suspend+0x0/0x30 [snd_pcm] @ 47526, parent: card0
Oct 12 13:14:18 ryzen kernel: sound pcmC0D0p: PM: do_pcm_suspend+0x0/0x30 [snd_pcm] returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: input input25: PM: calling input_dev_suspend+0x0/0x70 @ 47526, parent: card2
Oct 12 13:14:18 ryzen kernel: input input25: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: input input24: PM: calling input_dev_suspend+0x0/0x70 @ 47526, parent: card2
Oct 12 13:14:18 ryzen kernel: input input24: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: input input23: PM: calling input_dev_suspend+0x0/0x70 @ 47526, parent: card2
Oct 12 13:14:18 ryzen kernel: input input23: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: input input22: PM: calling input_dev_suspend+0x0/0x70 @ 47526, parent: card2
Oct 12 13:14:18 ryzen kernel: input input22: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: input input21: PM: calling input_dev_suspend+0x0/0x70 @ 47526, parent: card2
Oct 12 13:14:18 ryzen kernel: input input21: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: sound pcmC2D2c: PM: calling do_pcm_suspend+0x0/0x30 [snd_pcm] @ 47526, parent: card2
Oct 12 13:14:18 ryzen kernel: sound pcmC2D2c: PM: do_pcm_suspend+0x0/0x30 [snd_pcm] returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: sound pcmC2D0c: PM: calling do_pcm_suspend+0x0/0x30 [snd_pcm] @ 47526, parent: card2
Oct 12 13:14:18 ryzen kernel: sound pcmC2D0c: PM: do_pcm_suspend+0x0/0x30 [snd_pcm] returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: sound pcmC2D0p: PM: calling do_pcm_suspend+0x0/0x30 [snd_pcm] @ 47526, parent: card2
Oct 12 13:14:18 ryzen kernel: sound pcmC2D0p: PM: do_pcm_suspend+0x0/0x30 [snd_pcm] returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: input input20: PM: calling input_dev_suspend+0x0/0x70 @ 47526, parent: card1
Oct 12 13:14:18 ryzen kernel: input input20: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: input input19: PM: calling input_dev_suspend+0x0/0x70 @ 47526, parent: card1
Oct 12 13:14:18 ryzen kernel: input input19: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: snd_hda_codec_realtek hdaudioC2D0: PM: calling hda_codec_pm_suspend+0x0/0x20 [snd_hda_codec] @ 45914, parent: 0000:07:00.4
Oct 12 13:14:18 ryzen kernel: input input18: PM: calling input_dev_suspend+0x0/0x70 @ 47526, parent: card1
Oct 12 13:14:18 ryzen kernel: input input18: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: input input17: PM: calling input_dev_suspend+0x0/0x70 @ 47526, parent: card1
Oct 12 13:14:18 ryzen kernel: input input17: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: input input16: PM: calling input_dev_suspend+0x0/0x70 @ 47526, parent: card1
Oct 12 13:14:18 ryzen kernel: input input16: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: input input15: PM: calling input_dev_suspend+0x0/0x70 @ 47526, parent: card1
Oct 12 13:14:18 ryzen kernel: input input15: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: sound pcmC1D11p: PM: calling do_pcm_suspend+0x0/0x30 [snd_pcm] @ 47526, parent: card1
Oct 12 13:14:18 ryzen kernel: sound pcmC1D11p: PM: do_pcm_suspend+0x0/0x30 [snd_pcm] returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: sound pcmC1D10p: PM: calling do_pcm_suspend+0x0/0x30 [snd_pcm] @ 47526, parent: card1
Oct 12 13:14:18 ryzen kernel: sound pcmC1D10p: PM: do_pcm_suspend+0x0/0x30 [snd_pcm] returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: sound pcmC1D9p: PM: calling do_pcm_suspend+0x0/0x30 [snd_pcm] @ 47526, parent: card1
Oct 12 13:14:18 ryzen kernel: sound pcmC1D9p: PM: do_pcm_suspend+0x0/0x30 [snd_pcm] returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: sound pcmC1D8p: PM: calling do_pcm_suspend+0x0/0x30 [snd_pcm] @ 47526, parent: card1
Oct 12 13:14:18 ryzen kernel: sound pcmC1D8p: PM: do_pcm_suspend+0x0/0x30 [snd_pcm] returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: sound pcmC1D7p: PM: calling do_pcm_suspend+0x0/0x30 [snd_pcm] @ 47526, parent: card1
Oct 12 13:14:18 ryzen kernel: sound pcmC1D7p: PM: do_pcm_suspend+0x0/0x30 [snd_pcm] returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: sound pcmC1D3p: PM: calling do_pcm_suspend+0x0/0x30 [snd_pcm] @ 47526, parent: card1
Oct 12 13:14:18 ryzen kernel: sound pcmC1D3p: PM: do_pcm_suspend+0x0/0x30 [snd_pcm] returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: input input14: PM: calling input_dev_suspend+0x0/0x70 @ 47526, parent: pcspkr
Oct 12 13:14:18 ryzen kernel: input input14: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: sp5100-tco sp5100-tco: PM: calling platform_pm_suspend+0x0/0x50 @ 47526, parent: platform
Oct 12 13:14:18 ryzen kernel: sp5100-tco sp5100-tco: PM: platform_pm_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: input input11: PM: calling input_dev_suspend+0x0/0x70 @ 47526, parent: 0003:046D:C092.000A
Oct 12 13:14:18 ryzen kernel: input input11: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: usb 1-2.4: PM: calling usb_dev_suspend+0x0/0x20 @ 43650, parent: 1-2
Oct 12 13:14:18 ryzen kernel: usb 1-2.4: PM: usb_dev_suspend+0x0/0x20 returned 0 after 5 usecs
Oct 12 13:14:18 ryzen kernel: input input10: PM: calling input_dev_suspend+0x0/0x70 @ 47526, parent: 0003:046D:C092.0009
Oct 12 13:14:18 ryzen kernel: input input10: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: input input9: PM: calling input_dev_suspend+0x0/0x70 @ 47526, parent: 0003:29EA:0102.0007
Oct 12 13:14:18 ryzen kernel: usb 1-2.3: PM: calling usb_dev_suspend+0x0/0x20 @ 43650, parent: 1-2
Oct 12 13:14:18 ryzen kernel: input input9: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: usb 1-10: PM: calling usb_dev_suspend+0x0/0x20 @ 45728, parent: usb1
Oct 12 13:14:18 ryzen kernel: input input8: PM: calling input_dev_suspend+0x0/0x70 @ 47526, parent: 0003:29EA:0102.0007
Oct 12 13:14:18 ryzen kernel: input input8: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: usb 1-10: PM: usb_dev_suspend+0x0/0x20 returned 0 after 4 usecs
Oct 12 13:14:18 ryzen kernel: leds input7::kana: PM: calling led_suspend+0x0/0x50 @ 47526, parent: input7
Oct 12 13:14:18 ryzen kernel: leds input7::kana: PM: led_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: leds input7::compose: PM: calling led_suspend+0x0/0x50 @ 47526, parent: input7
Oct 12 13:14:18 ryzen kernel: leds input7::compose: PM: led_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: leds input7::scrolllock: PM: calling led_suspend+0x0/0x50 @ 47526, parent: input7
Oct 12 13:14:18 ryzen kernel: leds input7::scrolllock: PM: led_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: leds input7::capslock: PM: calling led_suspend+0x0/0x50 @ 47526, parent: input7
Oct 12 13:14:18 ryzen kernel: leds input7::capslock: PM: led_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: leds input7::numlock: PM: calling led_suspend+0x0/0x50 @ 47526, parent: input7
Oct 12 13:14:18 ryzen kernel: leds input7::numlock: PM: led_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: input input7: PM: calling input_dev_suspend+0x0/0x70 @ 47526, parent: 0003:29EA:0102.0006
Oct 12 13:14:18 ryzen kernel: input input7: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: input input6: PM: calling input_dev_suspend+0x0/0x70 @ 47526, parent: 0003:29EA:0102.0005
Oct 12 13:14:18 ryzen kernel: input input6: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: usb 1-2.2: PM: calling usb_dev_suspend+0x0/0x20 @ 40948, parent: 1-2
Oct 12 13:14:18 ryzen kernel: usb 1-7: PM: calling usb_dev_suspend+0x0/0x20 @ 45729, parent: usb1
Oct 12 13:14:18 ryzen kernel: input input5: PM: calling input_dev_suspend+0x0/0x70 @ 47526, parent: 0003:0ECB:2057.0003
Oct 12 13:14:18 ryzen kernel: sd 6:0:0:0: PM: calling scsi_bus_suspend+0x0/0xc0 @ 45728, parent: target6:0:0
Oct 12 13:14:18 ryzen kernel: input input5: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: usb 1-7: PM: usb_dev_suspend+0x0/0x20 returned 0 after 5 usecs
Oct 12 13:14:18 ryzen kernel: usb 1-2.1: PM: calling usb_dev_suspend+0x0/0x20 @ 45729, parent: 1-2
Oct 12 13:14:18 ryzen kernel: input input4: PM: calling input_dev_suspend+0x0/0x70 @ 47526, parent: 0003:05F3:00FF.0002
Oct 12 13:14:18 ryzen kernel: input input4: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: input input3: PM: calling input_dev_suspend+0x0/0x70 @ 47526, parent: 0003:1852:7022.0001
Oct 12 13:14:18 ryzen kernel: input input3: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: leds input2::scrolllock: PM: calling led_suspend+0x0/0x50 @ 47526, parent: input2
Oct 12 13:14:18 ryzen kernel: leds input2::scrolllock: PM: led_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: leds input2::capslock: PM: calling led_suspend+0x0/0x50 @ 47526, parent: input2
Oct 12 13:14:18 ryzen kernel: usb 1-5: PM: calling usb_dev_suspend+0x0/0x20 @ 36942, parent: usb1
Oct 12 13:14:18 ryzen kernel: leds input2::capslock: PM: led_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: leds input2::numlock: PM: calling led_suspend+0x0/0x50 @ 47526, parent: input2
Oct 12 13:14:18 ryzen kernel: leds input2::numlock: PM: led_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: input input2: PM: calling input_dev_suspend+0x0/0x70 @ 47526, parent: serio0
Oct 12 13:14:18 ryzen kernel: input input2: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: atkbd serio0: PM: calling serio_suspend+0x0/0x50 [serio] @ 47526, parent: i8042
Oct 12 13:14:18 ryzen kernel: usb 3-2: PM: calling usb_dev_suspend+0x0/0x20 @ 47559, parent: usb3
Oct 12 13:14:18 ryzen kernel: usb usb4: PM: calling usb_dev_suspend+0x0/0x20 @ 47561, parent: 0000:07:00.3
Oct 12 13:14:18 ryzen kernel: usb 1-1.4: PM: usb_dev_suspend+0x0/0x20 returned 0 after 796 usecs
Oct 12 13:14:18 ryzen kernel: usb 3-2: PM: usb_dev_suspend+0x0/0x20 returned 0 after 113 usecs
Oct 12 13:14:18 ryzen kernel: usb usb3: PM: calling usb_dev_suspend+0x0/0x20 @ 36953, parent: 0000:07:00.3
Oct 12 13:14:18 ryzen kernel: usb 1-5: PM: usb_dev_suspend+0x0/0x20 returned 0 after 1913 usecs
Oct 12 13:14:18 ryzen kernel: atkbd serio0: PM: serio_suspend+0x0/0x50 [serio] returned 0 after 2729 usecs
Oct 12 13:14:18 ryzen kernel: i8042 i8042: PM: calling platform_pm_suspend+0x0/0x50 @ 47526, parent: platform
Oct 12 13:14:18 ryzen kernel: usb 1-2.3: PM: usb_dev_suspend+0x0/0x20 returned 0 after 2995 usecs
Oct 12 13:14:18 ryzen kernel: i8042 i8042: PM: platform_pm_suspend+0x0/0x50 returned 0 after 74 usecs
Oct 12 13:14:18 ryzen kernel: platform microcode: PM: calling platform_pm_suspend+0x0/0x50 @ 47526, parent: platform
Oct 12 13:14:18 ryzen kernel: sr 1:0:0:0: PM: calling scsi_bus_suspend+0x0/0xc0 @ 43650, parent: target1:0:0
Oct 12 13:14:18 ryzen kernel: platform microcode: PM: platform_pm_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: sd 0:0:0:0: PM: calling scsi_bus_suspend+0x0/0xc0 @ 47559, parent: target0:0:0
Oct 12 13:14:18 ryzen kernel: alarmtimer alarmtimer.0.auto: PM: calling platform_pm_suspend+0x0/0x50 @ 47526, parent: rtc0
Oct 12 13:14:18 ryzen kernel: alarmtimer alarmtimer.0.auto: PM: platform_pm_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: rtc rtc0: PM: calling rtc_suspend+0x0/0x1f0 @ 47526, parent: 00:02
Oct 12 13:14:18 ryzen kernel: rtc rtc0: PM: rtc_suspend+0x0/0x1f0 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: port serial8250:0.31: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 47526, parent: serial8250:0
Oct 12 13:14:18 ryzen kernel: scsi host5: PM: calling scsi_bus_suspend+0x0/0xc0 @ 47564, parent: ata6
Oct 12 13:14:18 ryzen kernel: port serial8250:0.31: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: scsi host5: PM: scsi_bus_suspend+0x0/0xc0 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: port serial8250:0.30: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 47526, parent: serial8250:0
Oct 12 13:14:18 ryzen kernel: scsi host4: PM: calling scsi_bus_suspend+0x0/0xc0 @ 47564, parent: ata5
Oct 12 13:14:18 ryzen kernel: port serial8250:0.30: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: scsi host4: PM: scsi_bus_suspend+0x0/0xc0 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: port serial8250:0.29: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 47526, parent: serial8250:0
Oct 12 13:14:18 ryzen kernel: scsi host3: PM: calling scsi_bus_suspend+0x0/0xc0 @ 47564, parent: ata4
Oct 12 13:14:18 ryzen kernel: scsi host3: PM: scsi_bus_suspend+0x0/0xc0 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: port serial8250:0.29: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: scsi host2: PM: calling scsi_bus_suspend+0x0/0xc0 @ 47566, parent: ata3
Oct 12 13:14:18 ryzen kernel: port serial8250:0.28: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 47526, parent: serial8250:0
Oct 12 13:14:18 ryzen kernel: scsi host2: PM: scsi_bus_suspend+0x0/0xc0 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: port serial8250:0.28: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: port serial8250:0.27: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 47526, parent: serial8250:0
Oct 12 13:14:18 ryzen kernel: port serial8250:0.27: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: port serial8250:0.26: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 47526, parent: serial8250:0
Oct 12 13:14:18 ryzen kernel: port serial8250:0.26: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: ata6: PM: calling ata_port_pm_suspend+0x0/0x50 @ 47567, parent: 0000:02:00.1
Oct 12 13:14:18 ryzen kernel: port serial8250:0.25: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 47526, parent: serial8250:0
Oct 12 13:14:18 ryzen kernel: port serial8250:0.25: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: port serial8250:0.24: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 47526, parent: serial8250:0
Oct 12 13:14:18 ryzen kernel: port serial8250:0.24: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: port serial8250:0.23: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 47526, parent: serial8250:0
Oct 12 13:14:18 ryzen kernel: port serial8250:0.23: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: ata5: PM: calling ata_port_pm_suspend+0x0/0x50 @ 47568, parent: 0000:02:00.1
Oct 12 13:14:18 ryzen kernel: port serial8250:0.22: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 47526, parent: serial8250:0
Oct 12 13:14:18 ryzen kernel: port serial8250:0.22: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: port serial8250:0.21: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 47526, parent: serial8250:0
Oct 12 13:14:18 ryzen kernel: port serial8250:0.21: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: ata6: PM: ata_port_pm_suspend+0x0/0x50 returned 0 after 28 usecs
Oct 12 13:14:18 ryzen kernel: port serial8250:0.20: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 47526, parent: serial8250:0
Oct 12 13:14:18 ryzen kernel: ata4: PM: calling ata_port_pm_suspend+0x0/0x50 @ 47569, parent: 0000:02:00.1
Oct 12 13:14:18 ryzen kernel: ata3: PM: calling ata_port_pm_suspend+0x0/0x50 @ 47567, parent: 0000:02:00.1
Oct 12 13:14:18 ryzen kernel: port serial8250:0.20: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: port serial8250:0.19: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 47526, parent: serial8250:0
Oct 12 13:14:18 ryzen kernel: ata5: PM: ata_port_pm_suspend+0x0/0x50 returned 0 after 30 usecs
Oct 12 13:14:18 ryzen kernel: port serial8250:0.19: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: port serial8250:0.18: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 47526, parent: serial8250:0
Oct 12 13:14:18 ryzen kernel: port serial8250:0.18: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: port serial8250:0.17: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 47526, parent: serial8250:0
Oct 12 13:14:18 ryzen kernel: port serial8250:0.17: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: ata4: PM: ata_port_pm_suspend+0x0/0x50 returned 0 after 24 usecs
Oct 12 13:14:18 ryzen kernel: port serial8250:0.16: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 47526, parent: serial8250:0
Oct 12 13:14:18 ryzen kernel: port serial8250:0.16: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: port serial8250:0.15: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 47526, parent: serial8250:0
Oct 12 13:14:18 ryzen kernel: ata3: PM: ata_port_pm_suspend+0x0/0x50 returned 0 after 35 usecs
Oct 12 13:14:18 ryzen kernel: port serial8250:0.15: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: port serial8250:0.14: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 47526, parent: serial8250:0
Oct 12 13:14:18 ryzen kernel: port serial8250:0.14: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: port serial8250:0.13: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 47526, parent: serial8250:0
Oct 12 13:14:18 ryzen kernel: port serial8250:0.13: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: port serial8250:0.12: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 47526, parent: serial8250:0
Oct 12 13:14:18 ryzen kernel: port serial8250:0.12: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: port serial8250:0.11: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 47526, parent: serial8250:0
Oct 12 13:14:18 ryzen kernel: port serial8250:0.11: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: port serial8250:0.10: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 47526, parent: serial8250:0
Oct 12 13:14:18 ryzen kernel: port serial8250:0.10: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: port serial8250:0.9: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 47526, parent: serial8250:0
Oct 12 13:14:18 ryzen kernel: port serial8250:0.9: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: port serial8250:0.8: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 47526, parent: serial8250:0
Oct 12 13:14:18 ryzen kernel: port serial8250:0.8: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: port serial8250:0.7: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 47526, parent: serial8250:0
Oct 12 13:14:18 ryzen kernel: port serial8250:0.7: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: port serial8250:0.6: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 47526, parent: serial8250:0
Oct 12 13:14:18 ryzen kernel: port serial8250:0.6: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: port serial8250:0.5: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 47526, parent: serial8250:0
Oct 12 13:14:18 ryzen kernel: port serial8250:0.5: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: port serial8250:0.4: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 47526, parent: serial8250:0
Oct 12 13:14:18 ryzen kernel: port serial8250:0.4: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: port serial8250:0.3: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 47526, parent: serial8250:0
Oct 12 13:14:18 ryzen kernel: port serial8250:0.3: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: port serial8250:0.2: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 47526, parent: serial8250:0
Oct 12 13:14:18 ryzen kernel: port serial8250:0.2: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: port serial8250:0.1: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 47526, parent: serial8250:0
Oct 12 13:14:18 ryzen kernel: port serial8250:0.1: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: usb 1-2.1: PM: usb_dev_suspend+0x0/0x20 returned 0 after 3186 usecs
Oct 12 13:14:18 ryzen kernel: serial8250 serial8250: PM: calling platform_pm_suspend+0x0/0x50 @ 47526, parent: platform
Oct 12 13:14:18 ryzen kernel: serial8250 serial8250: PM: platform_pm_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: port 00:05:0.0: PM: calling pm_runtime_force_suspend+0x0/0x120 @ 47526, parent: 00:05:0
Oct 12 13:14:18 ryzen kernel: port 00:05:0.0: PM: pm_runtime_force_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: input input1: PM: calling input_dev_suspend+0x0/0x70 @ 47526, parent: LNXPWRBN:00
Oct 12 13:14:18 ryzen kernel: input input1: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: input input0: PM: calling input_dev_suspend+0x0/0x70 @ 47526, parent: PNP0C0C:00
Oct 12 13:14:18 ryzen kernel: input input0: PM: input_dev_suspend+0x0/0x70 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: pcspkr pcspkr: PM: calling platform_pm_suspend+0x0/0x50 @ 47526, parent: platform
Oct 12 13:14:18 ryzen kernel: pcspkr pcspkr: PM: platform_pm_suspend+0x0/0x50 returned 0 after 4 usecs
Oct 12 13:14:18 ryzen kernel: snd_hda_intel 0000:05:00.1: PM: calling pci_pm_suspend+0x0/0x170 @ 47572, parent: 0000:00:03.1
Oct 12 13:14:18 ryzen kernel: system 00:06: PM: calling pnp_bus_suspend+0x0/0x20 @ 47526, parent: pnp0
Oct 12 13:14:18 ryzen kernel: system 00:06: PM: pnp_bus_suspend+0x0/0x20 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: serial 00:05: PM: calling pnp_bus_suspend+0x0/0x20 @ 47526, parent: pnp0
Oct 12 13:14:18 ryzen kernel: serial 00:05: PM: pnp_bus_suspend+0x0/0x20 returned 0 after 4 usecs
Oct 12 13:14:18 ryzen kernel: i8042 kbd 00:04: PM: calling pnp_bus_suspend+0x0/0x20 @ 47526, parent: pnp0
Oct 12 13:14:18 ryzen kernel: i8042 kbd 00:04: PM: pnp_bus_suspend+0x0/0x20 returned 0 after 52 usecs
Oct 12 13:14:18 ryzen kernel: system 00:03: PM: calling pnp_bus_suspend+0x0/0x20 @ 47526, parent: pnp0
Oct 12 13:14:18 ryzen kernel: system 00:03: PM: pnp_bus_suspend+0x0/0x20 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: rtc_cmos 00:02: PM: calling pnp_bus_suspend+0x0/0x20 @ 47526, parent: pnp0
Oct 12 13:14:18 ryzen kernel: rtc_cmos 00:02: PM: pnp_bus_suspend+0x0/0x20 returned 0 after 23 usecs
Oct 12 13:14:18 ryzen kernel: system 00:01: PM: calling pnp_bus_suspend+0x0/0x20 @ 47526, parent: pnp0
Oct 12 13:14:18 ryzen kernel: system 00:01: PM: pnp_bus_suspend+0x0/0x20 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: system 00:00: PM: calling pnp_bus_suspend+0x0/0x20 @ 47526, parent: pnp0
Oct 12 13:14:18 ryzen kernel: system 00:00: PM: pnp_bus_suspend+0x0/0x20 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: platform efivars.0: PM: calling platform_pm_suspend+0x0/0x50 @ 47526, parent: platform
Oct 12 13:14:18 ryzen kernel: platform efivars.0: PM: platform_pm_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: platform rtc-efi.0: PM: calling platform_pm_suspend+0x0/0x50 @ 47526, parent: platform
Oct 12 13:14:18 ryzen kernel: platform rtc-efi.0: PM: platform_pm_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: button LNXPWRBN:00: PM: calling acpi_button_suspend+0x0/0x20 @ 47526, parent: LNXSYSTM:00
Oct 12 13:14:18 ryzen kernel: button LNXPWRBN:00: PM: acpi_button_suspend+0x0/0x20 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: acpi-wmi PNP0C14:01: PM: calling acpi_subsys_suspend+0x0/0x60 @ 47526, parent: platform
Oct 12 13:14:18 ryzen kernel: acpi-wmi PNP0C14:01: PM: acpi_subsys_suspend+0x0/0x60 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: acpi-wmi PNP0C14:00: PM: calling acpi_subsys_suspend+0x0/0x60 @ 47526, parent: platform
Oct 12 13:14:18 ryzen kernel: acpi-wmi PNP0C14:00: PM: acpi_subsys_suspend+0x0/0x60 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: platform PNP0103:00: PM: calling platform_pm_suspend+0x0/0x50 @ 47526, parent: platform
Oct 12 13:14:18 ryzen kernel: platform PNP0103:00: PM: platform_pm_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: pt-gpio AMDIF030:00: PM: calling acpi_subsys_suspend+0x0/0x60 @ 47526, parent: platform
Oct 12 13:14:18 ryzen kernel: pt-gpio AMDIF030:00: PM: acpi_subsys_suspend+0x0/0x60 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: acpi-cpufreq acpi-cpufreq: PM: calling platform_pm_suspend+0x0/0x50 @ 47526, parent: platform
Oct 12 13:14:18 ryzen kernel: acpi-cpufreq acpi-cpufreq: PM: platform_pm_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: platform MSFT0101:00: PM: calling platform_pm_suspend+0x0/0x50 @ 47526, parent: platform
Oct 12 13:14:18 ryzen kernel: platform MSFT0101:00: PM: platform_pm_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: amd_gpio AMDI0030:00: PM: calling acpi_subsys_suspend+0x0/0x60 @ 47526, parent: platform
Oct 12 13:14:18 ryzen kernel: amd_gpio AMDI0030:00: PM: acpi_subsys_suspend+0x0/0x60 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: platform PNP0C0C:00: PM: calling platform_pm_suspend+0x0/0x50 @ 47526, parent: platform
Oct 12 13:14:18 ryzen kernel: platform PNP0C0C:00: PM: platform_pm_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: platform PNP0800:00: PM: calling platform_pm_suspend+0x0/0x50 @ 47526, parent: 0000:00:14.3
Oct 12 13:14:18 ryzen kernel: platform PNP0800:00: PM: platform_pm_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: ccp 0000:07:00.1: PM: calling pci_pm_suspend+0x0/0x170 @ 45729, parent: 0000:00:08.1
Oct 12 13:14:18 ryzen kernel: ccp 0000:07:00.1: PM: pci_pm_suspend+0x0/0x170 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: thermal LNXTHERM:01: PM: calling acpi_thermal_suspend+0x0/0x20 @ 47526, parent: LNXSYBUS:01
Oct 12 13:14:18 ryzen kernel: pci 0000:07:00.0: PM: calling pci_pm_suspend+0x0/0x170 @ 45729, parent: 0000:00:08.1
Oct 12 13:14:18 ryzen kernel: thermal LNXTHERM:01: PM: acpi_thermal_suspend+0x0/0x20 returned 0 after 2 usecs
Oct 12 13:14:18 ryzen kernel: pci 0000:07:00.0: PM: pci_pm_suspend+0x0/0x170 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: thermal LNXTHERM:00: PM: calling acpi_thermal_suspend+0x0/0x20 @ 47526, parent: LNXSYBUS:01
Oct 12 13:14:18 ryzen kernel: pci 0000:06:00.0: PM: calling pci_pm_suspend+0x0/0x170 @ 45729, parent: 0000:00:07.1
Oct 12 13:14:18 ryzen kernel: thermal LNXTHERM:00: PM: acpi_thermal_suspend+0x0/0x20 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: pci 0000:06:00.0: PM: pci_pm_suspend+0x0/0x170 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: tpm_crb MSFT0101:00: PM: calling tpm_pm_suspend+0x0/0xd0 @ 47526, parent: LNXSYBUS:00
Oct 12 13:14:18 ryzen kernel: r8169 0000:04:00.0: PM: calling pci_pm_suspend+0x0/0x170 @ 47569, parent: 0000:03:09.0
Oct 12 13:14:18 ryzen kernel: r8169 0000:04:00.0: PM: pci_pm_suspend+0x0/0x170 returned 0 after 1 usecs
Oct 12 13:14:18 ryzen kernel: pcieport 0000:03:09.0: PM: calling pci_pm_suspend+0x0/0x170 @ 47569, parent: 0000:02:00.2
Oct 12 13:14:18 ryzen kernel: pcieport 0000:03:09.0: PM: pci_pm_suspend+0x0/0x170 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: pcieport 0000:02:00.2: PM: calling pci_pm_suspend+0x0/0x170 @ 47569, parent: 0000:00:01.2
Oct 12 13:14:18 ryzen kernel: pcieport 0000:02:00.2: PM: pci_pm_suspend+0x0/0x170 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: nvme 0000:01:00.0: PM: calling pci_pm_suspend+0x0/0x170 @ 47574, parent: 0000:00:01.1
Oct 12 13:14:18 ryzen kernel: pci 0000:00:18.7: PM: calling pci_pm_suspend+0x0/0x170 @ 47575, parent: pci0000:00
Oct 12 13:14:18 ryzen kernel: pci 0000:00:18.7: PM: pci_pm_suspend+0x0/0x170 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: pci 0000:00:18.6: PM: calling pci_pm_suspend+0x0/0x170 @ 47575, parent: pci0000:00
Oct 12 13:14:18 ryzen kernel: pci 0000:00:18.6: PM: pci_pm_suspend+0x0/0x170 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: pci 0000:00:18.5: PM: calling pci_pm_suspend+0x0/0x170 @ 47575, parent: pci0000:00
Oct 12 13:14:18 ryzen kernel: pci 0000:00:18.5: PM: pci_pm_suspend+0x0/0x170 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: pci 0000:00:18.4: PM: calling pci_pm_suspend+0x0/0x170 @ 47575, parent: pci0000:00
Oct 12 13:14:18 ryzen kernel: pci 0000:00:18.4: PM: pci_pm_suspend+0x0/0x170 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: k10temp 0000:00:18.3: PM: calling pci_pm_suspend+0x0/0x170 @ 47576, parent: pci0000:00
Oct 12 13:14:18 ryzen kernel: pci 0000:00:18.2: PM: calling pci_pm_suspend+0x0/0x170 @ 47575, parent: pci0000:00
Oct 12 13:14:18 ryzen kernel: pci 0000:00:18.2: PM: pci_pm_suspend+0x0/0x170 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: k10temp 0000:00:18.3: PM: pci_pm_suspend+0x0/0x170 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: pci 0000:00:18.1: PM: calling pci_pm_suspend+0x0/0x170 @ 47575, parent: pci0000:00
Oct 12 13:14:18 ryzen kernel: pci 0000:00:18.0: PM: calling pci_pm_suspend+0x0/0x170 @ 47576, parent: pci0000:00
Oct 12 13:14:18 ryzen kernel: pci 0000:00:18.1: PM: pci_pm_suspend+0x0/0x170 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: pci 0000:00:18.0: PM: pci_pm_suspend+0x0/0x170 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: pci 0000:00:14.3: PM: calling pci_pm_suspend+0x0/0x170 @ 47575, parent: pci0000:00
Oct 12 13:14:18 ryzen kernel: pci 0000:00:14.3: PM: pci_pm_suspend+0x0/0x170 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: piix4_smbus 0000:00:14.0: PM: calling pci_pm_suspend+0x0/0x170 @ 47576, parent: pci0000:00
Oct 12 13:14:18 ryzen kernel: piix4_smbus 0000:00:14.0: PM: pci_pm_suspend+0x0/0x170 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: pci 0000:00:08.0: PM: calling pci_pm_suspend+0x0/0x170 @ 47575, parent: pci0000:00
Oct 12 13:14:18 ryzen kernel: pci 0000:00:08.0: PM: pci_pm_suspend+0x0/0x170 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: pcieport 0000:00:07.1: PM: calling pci_pm_suspend+0x0/0x170 @ 47576, parent: pci0000:00
Oct 12 13:14:18 ryzen kernel: pci 0000:00:07.0: PM: calling pci_pm_suspend+0x0/0x170 @ 47575, parent: pci0000:00
Oct 12 13:14:18 ryzen kernel: pcieport 0000:00:07.1: PM: pci_pm_suspend+0x0/0x170 returned 0 after 2 usecs
Oct 12 13:14:18 ryzen kernel: pci 0000:00:07.0: PM: pci_pm_suspend+0x0/0x170 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: pci 0000:00:05.0: PM: calling pci_pm_suspend+0x0/0x170 @ 47575, parent: pci0000:00
Oct 12 13:14:18 ryzen kernel: pci 0000:00:04.0: PM: calling pci_pm_suspend+0x0/0x170 @ 47576, parent: pci0000:00
Oct 12 13:14:18 ryzen kernel: pci 0000:00:05.0: PM: pci_pm_suspend+0x0/0x170 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: pci 0000:00:04.0: PM: pci_pm_suspend+0x0/0x170 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: pci 0000:00:03.0: PM: calling pci_pm_suspend+0x0/0x170 @ 47576, parent: pci0000:00
Oct 12 13:14:18 ryzen kernel: pci 0000:00:03.0: PM: pci_pm_suspend+0x0/0x170 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: pci 0000:00:02.0: PM: calling pci_pm_suspend+0x0/0x170 @ 47576, parent: pci0000:00
Oct 12 13:14:18 ryzen kernel: pci 0000:00:02.0: PM: pci_pm_suspend+0x0/0x170 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: pci 0000:00:01.0: PM: calling pci_pm_suspend+0x0/0x170 @ 47579, parent: pci0000:00
Oct 12 13:14:18 ryzen kernel: pci 0000:00:01.0: PM: pci_pm_suspend+0x0/0x170 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: pci 0000:00:00.2: PM: calling pci_pm_suspend+0x0/0x170 @ 47579, parent: pci0000:00
Oct 12 13:14:18 ryzen kernel: pci 0000:00:00.2: PM: pci_pm_suspend+0x0/0x170 returned 0 after 1 usecs
Oct 12 13:14:18 ryzen kernel: pci 0000:00:00.0: PM: calling pci_pm_suspend+0x0/0x170 @ 47579, parent: pci0000:00
Oct 12 13:14:18 ryzen kernel: pci 0000:00:00.0: PM: pci_pm_suspend+0x0/0x170 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: usb usb3: PM: usb_dev_suspend+0x0/0x20 returned 0 after 9836 usecs
Oct 12 13:14:18 ryzen kernel: tpm_crb MSFT0101:00: PM: tpm_pm_suspend+0x0/0xd0 returned 0 after 9960 usecs
Oct 12 13:14:18 ryzen kernel: button PNP0C0C:00: PM: calling acpi_button_suspend+0x0/0x20 @ 47526, parent: LNXSYBUS:00
Oct 12 13:14:18 ryzen kernel: button PNP0C0C:00: PM: acpi_button_suspend+0x0/0x20 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: PCCT PCCT: PM: calling platform_pm_suspend+0x0/0x50 @ 47526, parent: platform
Oct 12 13:14:18 ryzen kernel: PCCT PCCT: PM: platform_pm_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: regulator regulator.0: PM: calling regulator_suspend+0x0/0x120 @ 47526, parent: reg-dummy
Oct 12 13:14:18 ryzen kernel: regulator regulator.0: PM: regulator_suspend+0x0/0x120 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: reg-dummy reg-dummy: PM: calling platform_pm_suspend+0x0/0x50 @ 47526, parent: platform
Oct 12 13:14:18 ryzen kernel: reg-dummy reg-dummy: PM: platform_pm_suspend+0x0/0x50 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: snd_hda_intel 0000:05:00.1: PM: pci_pm_suspend+0x0/0x170 returned 0 after 12505 usecs
Oct 12 13:14:18 ryzen kernel: amdgpu 0000:05:00.0: PM: calling pci_pm_suspend+0x0/0x170 @ 45729, parent: 0000:00:03.1
Oct 12 13:14:18 ryzen kernel: snd_hda_codec_realtek hdaudioC2D0: PM: hda_codec_pm_suspend+0x0/0x20 [snd_hda_codec] returned 0 after 18175 usecs
Oct 12 13:14:18 ryzen kernel: snd_hda_intel 0000:07:00.4: PM: calling pci_pm_suspend+0x0/0x170 @ 47571, parent: 0000:00:08.1
Oct 12 13:14:18 ryzen kernel: snd_hda_intel 0000:07:00.4: PM: pci_pm_suspend+0x0/0x170 returned 0 after 1065 usecs
Oct 12 13:14:18 ryzen kernel: usb 1-3.1: PM: usb_dev_suspend+0x0/0x20 returned 0 after 20706 usecs
Oct 12 13:14:18 ryzen kernel: sd 6:0:0:0: PM: scsi_bus_suspend+0x0/0xc0 returned 0 after 20137 usecs
Oct 12 13:14:18 ryzen kernel: usb 1-3: PM: calling usb_dev_suspend+0x0/0x20 @ 39442, parent: usb1
Oct 12 13:14:18 ryzen kernel: scsi target6:0:0: PM: calling scsi_bus_suspend+0x0/0xc0 @ 45915, parent: host6
Oct 12 13:14:18 ryzen kernel: scsi target6:0:0: PM: scsi_bus_suspend+0x0/0xc0 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: scsi host6: PM: calling scsi_bus_suspend+0x0/0xc0 @ 47556, parent: 2-4:1.0
Oct 12 13:14:18 ryzen kernel: scsi host6: PM: scsi_bus_suspend+0x0/0xc0 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: usb 2-4: PM: calling usb_dev_suspend+0x0/0x20 @ 47558, parent: usb2
Oct 12 13:14:18 ryzen kernel: sr 1:0:0:0: PM: scsi_bus_suspend+0x0/0xc0 returned 0 after 23879 usecs
Oct 12 13:14:18 ryzen kernel: scsi target1:0:0: PM: calling scsi_bus_suspend+0x0/0xc0 @ 36942, parent: host1
Oct 12 13:14:18 ryzen kernel: scsi target1:0:0: PM: scsi_bus_suspend+0x0/0xc0 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: usb usb4: PM: usb_dev_suspend+0x0/0x20 returned 0 after 26615 usecs
Oct 12 13:14:18 ryzen kernel: scsi host1: PM: calling scsi_bus_suspend+0x0/0xc0 @ 47564, parent: ata2
Oct 12 13:14:18 ryzen kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Oct 12 13:14:18 ryzen kernel: scsi host1: PM: scsi_bus_suspend+0x0/0xc0 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: xhci_hcd 0000:07:00.3: PM: calling pci_pm_suspend+0x0/0x170 @ 47567, parent: 0000:00:08.1
Oct 12 13:14:18 ryzen kernel: ata2: PM: calling ata_port_pm_suspend+0x0/0x50 @ 47568, parent: 0000:02:00.1
Oct 12 13:14:18 ryzen kernel: ata2: PM: ata_port_pm_suspend+0x0/0x50 returned 0 after 24 usecs
Oct 12 13:14:18 ryzen kernel: sd 0:0:0:0: [sda] Stopping disk
Oct 12 13:14:18 ryzen kernel: xhci_hcd 0000:07:00.3: PM: pci_pm_suspend+0x0/0x170 returned 0 after 158 usecs
Oct 12 13:14:18 ryzen kernel: pcieport 0000:00:08.1: PM: calling pci_pm_suspend+0x0/0x170 @ 47577, parent: pci0000:00
Oct 12 13:14:18 ryzen kernel: pcieport 0000:00:08.1: PM: pci_pm_suspend+0x0/0x170 returned 0 after 2 usecs
Oct 12 13:14:18 ryzen kernel: usb 1-2.2: PM: usb_dev_suspend+0x0/0x20 returned 0 after 33468 usecs
Oct 12 13:14:18 ryzen kernel: usb 1-1.1: PM: usb_dev_suspend+0x0/0x20 returned 0 after 33972 usecs
Oct 12 13:14:18 ryzen kernel: usb 1-2: PM: calling usb_dev_suspend+0x0/0x20 @ 47560, parent: usb1
Oct 12 13:14:18 ryzen kernel: usb 1-1: PM: calling usb_dev_suspend+0x0/0x20 @ 43033, parent: usb1
Oct 12 13:14:18 ryzen kernel: usb 2-4: PM: usb_dev_suspend+0x0/0x20 returned 0 after 23272 usecs
Oct 12 13:14:18 ryzen kernel: usb usb2: PM: calling usb_dev_suspend+0x0/0x20 @ 47562, parent: 0000:02:00.0
Oct 12 13:14:18 ryzen kernel: usb usb2: PM: usb_dev_suspend+0x0/0x20 returned 0 after 12 usecs
Oct 12 13:14:18 ryzen kernel: usb 1-3: PM: usb_dev_suspend+0x0/0x20 returned 0 after 33315 usecs
Oct 12 13:14:18 ryzen kernel: usb 1-2: PM: usb_dev_suspend+0x0/0x20 returned 0 after 33320 usecs
Oct 12 13:14:18 ryzen kernel: usb 1-1: PM: usb_dev_suspend+0x0/0x20 returned 0 after 33335 usecs
Oct 12 13:14:18 ryzen kernel: usb usb1: PM: calling usb_dev_suspend+0x0/0x20 @ 47563, parent: 0000:02:00.0
Oct 12 13:14:18 ryzen kernel: usb usb1: PM: usb_dev_suspend+0x0/0x20 returned 0 after 11063 usecs
Oct 12 13:14:18 ryzen kernel: xhci_hcd 0000:02:00.0: PM: calling pci_pm_suspend+0x0/0x170 @ 47573, parent: 0000:00:01.2
Oct 12 13:14:18 ryzen kernel: xhci_hcd 0000:02:00.0: PM: pci_pm_suspend+0x0/0x170 returned 0 after 1134 usecs
Oct 12 13:14:18 ryzen kernel: amdgpu 0000:05:00.0: PM: pci_pm_suspend+0x0/0x170 returned 0 after 242278 usecs
Oct 12 13:14:18 ryzen kernel: pcieport 0000:00:03.1: PM: calling pci_pm_suspend+0x0/0x170 @ 47575, parent: pci0000:00
Oct 12 13:14:18 ryzen kernel: pcieport 0000:00:03.1: PM: pci_pm_suspend+0x0/0x170 returned 0 after 2 usecs
Oct 12 13:14:18 ryzen kernel: sd 0:0:0:0: PM: scsi_bus_suspend+0x0/0xc0 returned 0 after 433772 usecs
Oct 12 13:14:18 ryzen kernel: scsi target0:0:0: PM: calling scsi_bus_suspend+0x0/0xc0 @ 47565, parent: host0
Oct 12 13:14:18 ryzen kernel: scsi target0:0:0: PM: scsi_bus_suspend+0x0/0xc0 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: scsi host0: PM: calling scsi_bus_suspend+0x0/0xc0 @ 47566, parent: ata1
Oct 12 13:14:18 ryzen kernel: scsi host0: PM: scsi_bus_suspend+0x0/0xc0 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: ata1: PM: calling ata_port_pm_suspend+0x0/0x50 @ 47570, parent: 0000:02:00.1
Oct 12 13:14:18 ryzen kernel: ata1: PM: ata_port_pm_suspend+0x0/0x50 returned 0 after 40 usecs
Oct 12 13:14:18 ryzen kernel: ahci 0000:02:00.1: PM: calling pci_pm_suspend+0x0/0x170 @ 47569, parent: 0000:00:01.2
Oct 12 13:14:18 ryzen kernel: ahci 0000:02:00.1: PM: pci_pm_suspend+0x0/0x170 returned 0 after 3 usecs
Oct 12 13:14:18 ryzen kernel: pcieport 0000:00:01.2: PM: calling pci_pm_suspend+0x0/0x170 @ 47578, parent: pci0000:00
Oct 12 13:14:18 ryzen kernel: pcieport 0000:00:01.2: PM: pci_pm_suspend+0x0/0x170 returned 0 after 2 usecs
Oct 12 13:14:18 ryzen kernel: nvme 0000:01:00.0: PM: pci_pm_suspend+0x0/0x170 returned 0 after 520458 usecs
Oct 12 13:14:18 ryzen kernel: pcieport 0000:00:01.1: PM: calling pci_pm_suspend+0x0/0x170 @ 47576, parent: pci0000:00
Oct 12 13:14:18 ryzen kernel: pcieport 0000:00:01.1: PM: pci_pm_suspend+0x0/0x170 returned 0 after 5 usecs
Oct 12 13:14:18 ryzen kernel: PM: suspend of devices complete after 524.844 msecs
Oct 12 13:14:18 ryzen kernel: PM: start suspend of devices complete after 1482.803 msecs
Oct 12 13:14:18 ryzen kernel: snd_hda_intel 0000:05:00.1: PM: calling pci_pm_suspend_late+0x0/0x40 @ 47576, parent: 0000:00:03.1
Oct 12 13:14:18 ryzen kernel: snd_hda_intel 0000:05:00.1: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: acpi-wmi PNP0C14:01: PM: calling acpi_subsys_suspend_late+0x0/0x50 @ 47526, parent: platform
Oct 12 13:14:18 ryzen kernel: acpi-wmi PNP0C14:01: PM: acpi_subsys_suspend_late+0x0/0x50 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: acpi-wmi PNP0C14:00: PM: calling acpi_subsys_suspend_late+0x0/0x50 @ 47526, parent: platform
Oct 12 13:14:18 ryzen kernel: acpi-wmi PNP0C14:00: PM: acpi_subsys_suspend_late+0x0/0x50 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: pt-gpio AMDIF030:00: PM: calling acpi_subsys_suspend_late+0x0/0x50 @ 47526, parent: platform
Oct 12 13:14:18 ryzen kernel: pt-gpio AMDIF030:00: PM: acpi_subsys_suspend_late+0x0/0x50 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: amd_gpio AMDI0030:00: PM: calling acpi_subsys_suspend_late+0x0/0x50 @ 47526, parent: platform
Oct 12 13:14:18 ryzen kernel: amd_gpio AMDI0030:00: PM: acpi_subsys_suspend_late+0x0/0x50 returned 0 after 8 usecs
Oct 12 13:14:18 ryzen kernel: snd_hda_intel 0000:07:00.4: PM: calling pci_pm_suspend_late+0x0/0x40 @ 47576, parent: 0000:00:08.1
Oct 12 13:14:18 ryzen kernel: snd_hda_intel 0000:07:00.4: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: xhci_hcd 0000:07:00.3: PM: calling pci_pm_suspend_late+0x0/0x40 @ 47576, parent: 0000:00:08.1
Oct 12 13:14:18 ryzen kernel: xhci_hcd 0000:07:00.3: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: ccp 0000:07:00.1: PM: calling pci_pm_suspend_late+0x0/0x40 @ 47576, parent: 0000:00:08.1
Oct 12 13:14:18 ryzen kernel: ccp 0000:07:00.1: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: pci 0000:06:00.0: PM: calling pci_pm_suspend_late+0x0/0x40 @ 47576, parent: 0000:00:07.1
Oct 12 13:14:18 ryzen kernel: pci 0000:07:00.0: PM: calling pci_pm_suspend_late+0x0/0x40 @ 47578, parent: 0000:00:08.1
Oct 12 13:14:18 ryzen kernel: pci 0000:06:00.0: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: amdgpu 0000:05:00.0: PM: calling pci_pm_suspend_late+0x0/0x40 @ 47576, parent: 0000:00:03.1
Oct 12 13:14:18 ryzen kernel: pci 0000:07:00.0: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: amdgpu 0000:05:00.0: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: r8169 0000:04:00.0: PM: calling pci_pm_suspend_late+0x0/0x40 @ 47576, parent: 0000:03:09.0
Oct 12 13:14:18 ryzen kernel: r8169 0000:04:00.0: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: xhci_hcd 0000:02:00.0: PM: calling pci_pm_suspend_late+0x0/0x40 @ 47576, parent: 0000:00:01.2
Oct 12 13:14:18 ryzen kernel: ahci 0000:02:00.1: PM: calling pci_pm_suspend_late+0x0/0x40 @ 47580, parent: 0000:00:01.2
Oct 12 13:14:18 ryzen kernel: pcieport 0000:03:09.0: PM: calling pci_pm_suspend_late+0x0/0x40 @ 47578, parent: 0000:02:00.2
Oct 12 13:14:18 ryzen kernel: xhci_hcd 0000:02:00.0: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: ahci 0000:02:00.1: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: nvme 0000:01:00.0: PM: calling pci_pm_suspend_late+0x0/0x40 @ 47576, parent: 0000:00:01.1
Oct 12 13:14:18 ryzen kernel: pcieport 0000:03:09.0: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: pci 0000:00:18.7: PM: calling pci_pm_suspend_late+0x0/0x40 @ 47580, parent: pci0000:00
Oct 12 13:14:18 ryzen kernel: nvme 0000:01:00.0: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: pci 0000:00:18.7: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: pci 0000:00:18.5: PM: calling pci_pm_suspend_late+0x0/0x40 @ 47576, parent: pci0000:00
Oct 12 13:14:18 ryzen kernel: pci 0000:00:18.6: PM: calling pci_pm_suspend_late+0x0/0x40 @ 47578, parent: pci0000:00
Oct 12 13:14:18 ryzen kernel: pci 0000:00:18.5: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: pci 0000:00:18.4: PM: calling pci_pm_suspend_late+0x0/0x40 @ 47580, parent: pci0000:00
Oct 12 13:14:18 ryzen kernel: pci 0000:00:18.6: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: pci 0000:00:18.4: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: pcieport 0000:02:00.2: PM: calling pci_pm_suspend_late+0x0/0x40 @ 47574, parent: 0000:00:01.2
Oct 12 13:14:18 ryzen kernel: pci 0000:00:18.2: PM: calling pci_pm_suspend_late+0x0/0x40 @ 47576, parent: pci0000:00
Oct 12 13:14:18 ryzen kernel: pci 0000:00:18.0: PM: calling pci_pm_suspend_late+0x0/0x40 @ 47580, parent: pci0000:00
Oct 12 13:14:18 ryzen kernel: pci 0000:00:18.1: PM: calling pci_pm_suspend_late+0x0/0x40 @ 47578, parent: pci0000:00
Oct 12 13:14:18 ryzen kernel: k10temp 0000:00:18.3: PM: calling pci_pm_suspend_late+0x0/0x40 @ 47569, parent: pci0000:00
Oct 12 13:14:18 ryzen kernel: pci 0000:00:18.0: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: pcieport 0000:02:00.2: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: pci 0000:00:18.1: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: pci 0000:00:18.2: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: pci 0000:00:14.3: PM: calling pci_pm_suspend_late+0x0/0x40 @ 47570, parent: pci0000:00
Oct 12 13:14:18 ryzen kernel: piix4_smbus 0000:00:14.0: PM: calling pci_pm_suspend_late+0x0/0x40 @ 47580, parent: pci0000:00
Oct 12 13:14:18 ryzen kernel: pci 0000:00:14.3: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: pcieport 0000:00:08.1: PM: calling pci_pm_suspend_late+0x0/0x40 @ 47578, parent: pci0000:00
Oct 12 13:14:18 ryzen kernel: piix4_smbus 0000:00:14.0: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: pci 0000:00:08.0: PM: calling pci_pm_suspend_late+0x0/0x40 @ 47574, parent: pci0000:00
Oct 12 13:14:18 ryzen kernel: pcieport 0000:00:07.1: PM: calling pci_pm_suspend_late+0x0/0x40 @ 47576, parent: pci0000:00
Oct 12 13:14:18 ryzen kernel: pcieport 0000:00:08.1: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: k10temp 0000:00:18.3: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: pcieport 0000:00:07.1: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: pci 0000:00:05.0: PM: calling pci_pm_suspend_late+0x0/0x40 @ 47580, parent: pci0000:00
Oct 12 13:14:18 ryzen kernel: pci 0000:00:08.0: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: pci 0000:00:07.0: PM: calling pci_pm_suspend_late+0x0/0x40 @ 47566, parent: pci0000:00
Oct 12 13:14:18 ryzen kernel: pci 0000:00:04.0: PM: calling pci_pm_suspend_late+0x0/0x40 @ 47570, parent: pci0000:00
Oct 12 13:14:18 ryzen kernel: pci 0000:00:05.0: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: pcieport 0000:00:03.1: PM: calling pci_pm_suspend_late+0x0/0x40 @ 47578, parent: pci0000:00
Oct 12 13:14:18 ryzen kernel: pci 0000:00:03.0: PM: calling pci_pm_suspend_late+0x0/0x40 @ 47576, parent: pci0000:00
Oct 12 13:14:18 ryzen kernel: pci 0000:00:04.0: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: pci 0000:00:07.0: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: pci 0000:00:02.0: PM: calling pci_pm_suspend_late+0x0/0x40 @ 47574, parent: pci0000:00
Oct 12 13:14:18 ryzen kernel: pcieport 0000:00:03.1: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: pci 0000:00:03.0: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: pci 0000:00:01.0: PM: calling pci_pm_suspend_late+0x0/0x40 @ 47570, parent: pci0000:00
Oct 12 13:14:18 ryzen kernel: pcieport 0000:00:01.1: PM: calling pci_pm_suspend_late+0x0/0x40 @ 47580, parent: pci0000:00
Oct 12 13:14:18 ryzen kernel: pcieport 0000:00:01.2: PM: calling pci_pm_suspend_late+0x0/0x40 @ 47565, parent: pci0000:00
Oct 12 13:14:18 ryzen kernel: pci 0000:00:02.0: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: pci 0000:00:00.0: PM: calling pci_pm_suspend_late+0x0/0x40 @ 47569, parent: pci0000:00
Oct 12 13:14:18 ryzen kernel: pci 0000:00:00.2: PM: calling pci_pm_suspend_late+0x0/0x40 @ 47566, parent: pci0000:00
Oct 12 13:14:18 ryzen kernel: pcieport 0000:00:01.1: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: pci 0000:00:01.0: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: pcieport 0000:00:01.2: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: pci 0000:00:00.2: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: pci 0000:00:00.0: PM: pci_pm_suspend_late+0x0/0x40 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: PM: late suspend of devices complete after 0.462 msecs
Oct 12 13:14:18 ryzen kernel: snd_hda_intel 0000:05:00.1: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 47565, parent: 0000:00:03.1
Oct 12 13:14:18 ryzen kernel: acpi-wmi PNP0C14:01: PM: calling acpi_subsys_suspend_noirq+0x0/0x50 @ 47526, parent: platform
Oct 12 13:14:18 ryzen kernel: acpi-wmi PNP0C14:01: PM: acpi_subsys_suspend_noirq+0x0/0x50 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: acpi-wmi PNP0C14:00: PM: calling acpi_subsys_suspend_noirq+0x0/0x50 @ 47526, parent: platform
Oct 12 13:14:18 ryzen kernel: acpi-wmi PNP0C14:00: PM: acpi_subsys_suspend_noirq+0x0/0x50 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: pt-gpio AMDIF030:00: PM: calling acpi_subsys_suspend_noirq+0x0/0x50 @ 47526, parent: platform
Oct 12 13:14:18 ryzen kernel: pt-gpio AMDIF030:00: PM: acpi_subsys_suspend_noirq+0x0/0x50 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: amd_gpio AMDI0030:00: PM: calling acpi_subsys_suspend_noirq+0x0/0x50 @ 47526, parent: platform
Oct 12 13:14:18 ryzen kernel: amd_gpio AMDI0030:00: PM: acpi_subsys_suspend_noirq+0x0/0x50 returned 0 after 0 usecs
Oct 12 13:14:18 ryzen kernel: snd_hda_intel 0000:07:00.4: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 47570, parent: 0000:00:08.1
Oct 12 13:14:18 ryzen kernel: xhci_hcd 0000:07:00.3: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 47580, parent: 0000:00:08.1
Oct 12 13:14:18 ryzen kernel: ccp 0000:07:00.1: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 47569, parent: 0000:00:08.1
Oct 12 13:14:18 ryzen kernel: pci 0000:07:00.0: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 47566, parent: 0000:00:08.1
Oct 12 13:14:18 ryzen kernel: pci 0000:06:00.0: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 47576, parent: 0000:00:07.1
Oct 12 13:14:18 ryzen kernel: r8169 0000:04:00.0: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 47559, parent: 0000:03:09.0
Oct 12 13:14:18 ryzen kernel: ahci 0000:02:00.1: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 45729, parent: 0000:00:01.2
Oct 12 13:14:18 ryzen kernel: xhci_hcd 0000:02:00.0: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 47573, parent: 0000:00:01.2
Oct 12 13:14:18 ryzen kernel: nvme 0000:01:00.0: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 47563, parent: 0000:00:01.1
Oct 12 13:14:18 ryzen kernel: pci 0000:00:18.7: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 43033, parent: pci0000:00
Oct 12 13:14:18 ryzen kernel: pci 0000:00:18.6: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 47560, parent: pci0000:00
Oct 12 13:14:18 ryzen kernel: pci 0000:00:18.5: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 39442, parent: pci0000:00
Oct 12 13:14:18 ryzen kernel: pci 0000:00:18.7: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 167 usecs
Oct 12 13:14:18 ryzen kernel: pci 0000:00:18.6: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 165 usecs
Oct 12 13:14:18 ryzen kernel: pci 0000:00:18.4: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 43033, parent: pci0000:00
Oct 12 13:14:18 ryzen kernel: k10temp 0000:00:18.3: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 47560, parent: pci0000:00
Oct 12 13:14:18 ryzen kernel: pci 0000:00:18.5: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 175 usecs
Oct 12 13:14:18 ryzen kernel: pci 0000:00:18.2: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 39442, parent: pci0000:00
Oct 12 13:14:18 ryzen kernel: pci 0000:07:00.0: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 316 usecs
Oct 12 13:14:18 ryzen kernel: pci 0000:00:18.1: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 47566, parent: pci0000:00
Oct 12 13:14:18 ryzen kernel: pci 0000:06:00.0: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 324 usecs
Oct 12 13:14:18 ryzen kernel: pci 0000:00:18.0: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 47576, parent: pci0000:00
Oct 12 13:14:18 ryzen kernel: pci 0000:00:14.3: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 47562, parent: pci0000:00
Oct 12 13:14:18 ryzen kernel: piix4_smbus 0000:00:14.0: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 47558, parent: pci0000:00
Oct 12 13:14:18 ryzen kernel: pci 0000:00:08.0: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 40948, parent: pci0000:00
Oct 12 13:14:18 ryzen kernel: pcieport 0000:00:07.1: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 47577, parent: pci0000:00
Oct 12 13:14:18 ryzen kernel: pci 0000:00:18.4: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 186 usecs
Oct 12 13:14:18 ryzen kernel: k10temp 0000:00:18.3: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 185 usecs
Oct 12 13:14:18 ryzen kernel: pci 0000:00:07.0: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 43033, parent: pci0000:00
Oct 12 13:14:18 ryzen kernel: pci 0000:00:05.0: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 47560, parent: pci0000:00
Oct 12 13:14:18 ryzen kernel: pci 0000:00:18.2: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 171 usecs
Oct 12 13:14:18 ryzen kernel: pci 0000:00:04.0: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 39442, parent: pci0000:00
Oct 12 13:14:18 ryzen kernel: pci 0000:00:18.1: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 129 usecs
Oct 12 13:14:18 ryzen kernel: pci 0000:00:18.0: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 128 usecs
Oct 12 13:14:18 ryzen kernel: pci 0000:00:03.0: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 47576, parent: pci0000:00
Oct 12 13:14:18 ryzen kernel: pci 0000:00:02.0: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 47567, parent: pci0000:00
Oct 12 13:14:18 ryzen kernel: pci 0000:00:01.0: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 47561, parent: pci0000:00
Oct 12 13:14:18 ryzen kernel: pci 0000:00:00.2: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 36942, parent: pci0000:00
Oct 12 13:14:18 ryzen kernel: pci 0000:00:00.0: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 43650, parent: pci0000:00
Oct 12 13:14:18 ryzen kernel: pci 0000:00:14.3: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 124 usecs
Oct 12 13:14:18 ryzen kernel: piix4_smbus 0000:00:14.0: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 123 usecs
Oct 12 13:14:18 ryzen kernel: pci 0000:00:08.0: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 121 usecs
Oct 12 13:14:18 ryzen kernel: pci 0000:00:07.0: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 98 usecs
Oct 12 13:14:18 ryzen kernel: pci 0000:00:05.0: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 98 usecs
Oct 12 13:14:18 ryzen kernel: pci 0000:00:04.0: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 90 usecs
Oct 12 13:14:18 ryzen kernel: pci 0000:00:03.0: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 80 usecs
Oct 12 13:14:18 ryzen kernel: pci 0000:00:02.0: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 79 usecs
Oct 12 13:14:18 ryzen kernel: pci 0000:00:01.0: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 74 usecs
Oct 12 13:14:18 ryzen kernel: pci 0000:00:00.0: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 73 usecs
Oct 12 13:14:18 ryzen kernel: pci 0000:00:00.2: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 76 usecs
Oct 12 13:14:18 ryzen kernel: ccp 0000:07:00.1: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 11885 usecs
Oct 12 13:14:18 ryzen kernel: snd_hda_intel 0000:07:00.4: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 11895 usecs
Oct 12 13:14:18 ryzen kernel: xhci_hcd 0000:02:00.0: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 11852 usecs
Oct 12 13:14:18 ryzen kernel: xhci_hcd 0000:07:00.3: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 11903 usecs
Oct 12 13:14:18 ryzen kernel: snd_hda_intel 0000:05:00.1: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 11944 usecs
Oct 12 13:14:18 ryzen kernel: pcieport 0000:00:08.1: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 36943, parent: pci0000:00
Oct 12 13:14:18 ryzen kernel: amdgpu 0000:05:00.0: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 47574, parent: 0000:00:03.1
Oct 12 13:14:18 ryzen kernel: amdgpu 0000:05:00.0: amdgpu: PCI CONFIG reset
Oct 12 13:14:18 ryzen kernel: r8169 0000:04:00.0: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 11969 usecs
Oct 12 13:14:18 ryzen kernel: pcieport 0000:03:09.0: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 47578, parent: 0000:02:00.2
Oct 12 13:14:18 ryzen kernel: nvme 0000:01:00.0: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 12191 usecs
Oct 12 13:14:18 ryzen kernel: pcieport 0000:00:07.1: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 11857 usecs
Oct 12 13:14:18 ryzen kernel: pcieport 0000:00:01.1: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 47564, parent: pci0000:00
Oct 12 13:14:18 ryzen kernel: ahci 0000:02:00.1: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 12342 usecs
Oct 12 13:14:18 ryzen kernel: pcieport 0000:03:09.0: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 12084 usecs
Oct 12 13:14:18 ryzen kernel: pcieport 0000:00:08.1: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 12170 usecs
Oct 12 13:14:18 ryzen kernel: pcieport 0000:02:00.2: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 47575, parent: 0000:00:01.2
Oct 12 13:14:18 ryzen kernel: amdgpu 0000:05:00.0: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 12435 usecs
Oct 12 13:14:18 ryzen kernel: pcieport 0000:00:01.1: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 12109 usecs
Oct 12 13:14:18 ryzen kernel: pcieport 0000:00:03.1: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 47566, parent: pci0000:00
Oct 12 13:14:18 ryzen kernel: pcieport 0000:02:00.2: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 12249 usecs
Oct 12 13:14:18 ryzen kernel: pcieport 0000:00:01.2: PM: calling pci_pm_suspend_noirq+0x0/0x2a0 @ 47568, parent: pci0000:00
Oct 12 13:14:18 ryzen kernel: pcieport 0000:00:03.1: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 12069 usecs
Oct 12 13:14:18 ryzen kernel: pcieport 0000:00:01.2: PM: pci_pm_suspend_noirq+0x0/0x2a0 returned 0 after 12428 usecs
Oct 12 13:14:18 ryzen kernel: PM: noirq suspend of devices complete after 49.098 msecs
Oct 12 13:14:18 ryzen kernel: ACPI: PM: Preparing to enter system sleep state S3
Oct 12 13:14:18 ryzen kernel: ACPI: PM: Saving platform NVS memory
Oct 12 13:14:18 ryzen kernel: Disabling non-boot CPUs ...
Oct 12 13:14:18 ryzen kernel: smpboot: CPU 1 is now offline
Oct 12 13:14:18 ryzen kernel: smpboot: CPU 2 is now offline
Oct 12 13:14:18 ryzen kernel: smpboot: CPU 3 is now offline
Oct 12 13:14:18 ryzen kernel: smpboot: CPU 4 is now offline
Oct 12 13:14:18 ryzen kernel: smpboot: CPU 5 is now offline
Oct 12 13:14:18 ryzen kernel: smpboot: CPU 6 is now offline
Oct 12 13:14:18 ryzen kernel: Spectre V2 : Update user space SMT mitigation: STIBP off
Oct 12 13:14:18 ryzen kernel: smpboot: CPU 7 is now offline
Oct 12 13:14:18 ryzen kernel: smpboot: CPU 8 is now offline
Oct 12 13:14:18 ryzen kernel: smpboot: CPU 9 is now offline
Oct 12 13:14:18 ryzen kernel: smpboot: CPU 10 is now offline
Oct 12 13:14:18 ryzen kernel: smpboot: CPU 11 is now offline
Oct 12 13:14:18 ryzen kernel: Checking wakeup interrupts
Oct 12 13:14:18 ryzen kernel: Calling mce_syscore_suspend+0x0/0x20
Oct 12 13:14:18 ryzen kernel: Calling ledtrig_cpu_syscore_suspend+0x0/0x20
Oct 12 13:14:18 ryzen kernel: Calling timekeeping_suspend+0x0/0x2f0
Oct 12 13:14:18 ryzen kernel: Calling irq_gc_suspend+0x0/0x80
Oct 12 13:14:18 ryzen kernel: Calling save_ioapic_entries+0x0/0xd0
Oct 12 13:14:18 ryzen kernel: Calling i8259A_suspend+0x0/0x30
Oct 12 13:14:18 ryzen kernel: Calling perf_ibs_suspend+0x0/0x40
Oct 12 13:14:18 ryzen kernel: Calling amd_iommu_suspend+0x0/0x50
Oct 12 13:14:18 ryzen kernel: Calling fw_suspend+0x0/0x20
Oct 12 13:14:18 ryzen kernel: Calling acpi_save_bm_rld+0x0/0x30
Oct 12 13:14:18 ryzen kernel: Calling lapic_suspend+0x0/0x210
Oct 12 13:14:18 ryzen kernel: ACPI: PM: Low-level resume complete
Oct 12 13:14:18 ryzen kernel: ACPI: PM: Restoring platform NVS memory
Oct 12 13:14:18 ryzen kernel: Calling lapic_resume+0x0/0x2e0
Oct 12 13:14:18 ryzen kernel: Calling acpi_restore_bm_rld+0x0/0x70
Oct 12 13:14:18 ryzen kernel: Calling irqrouter_resume+0x0/0x50
Oct 12 13:14:18 ryzen kernel: Calling amd_iommu_resume+0x0/0x50
Oct 12 13:14:18 ryzen kernel: Calling perf_ibs_resume+0x0/0x30
Oct 12 13:14:18 ryzen kernel: LVT offset 0 assigned for vector 0x400
Oct 12 13:14:18 ryzen kernel: Calling i8259A_resume+0x0/0x40
Oct 12 13:14:18 ryzen kernel: Calling i8237A_resume+0x0/0xb0
Oct 12 13:14:18 ryzen kernel: Calling ioapic_resume+0x0/0xc0
Oct 12 13:14:18 ryzen kernel: Calling irq_gc_resume+0x0/0x70
Oct 12 13:14:18 ryzen kernel: Calling irq_pm_syscore_resume+0x0/0x20
Oct 12 13:14:18 ryzen kernel: Calling timekeeping_resume+0x0/0x1e0
Oct 12 13:14:18 ryzen kernel: Timekeeping suspended for 43368.142 seconds
Oct 12 13:14:18 ryzen kernel: Calling init_counter_refs+0x0/0x40
Oct 12 13:14:18 ryzen kernel: Calling ledtrig_cpu_syscore_resume+0x0/0x20
Oct 12 13:14:18 ryzen kernel: Calling mce_syscore_resume+0x0/0x30
Oct 12 13:14:18 ryzen kernel: Calling microcode_bsp_resume+0x0/0x40
Oct 12 13:14:18 ryzen kernel: Enabling non-boot CPUs ...
Oct 12 13:14:18 ryzen kernel: smpboot: Booting Node 0 Processor 1 APIC 0x2
Oct 12 13:14:18 ryzen kernel: ACPI: \_SB_.PLTF.C002: Found 2 idle states
Oct 12 13:14:18 ryzen kernel: CPU1 is up
Oct 12 13:14:18 ryzen kernel: smpboot: Booting Node 0 Processor 2 APIC 0x4
Oct 12 13:14:18 ryzen kernel: ACPI: \_SB_.PLTF.C004: Found 2 idle states
Oct 12 13:14:18 ryzen kernel: CPU2 is up
Oct 12 13:14:18 ryzen kernel: smpboot: Booting Node 0 Processor 3 APIC 0x6
Oct 12 13:14:18 ryzen kernel: ACPI: \_SB_.PLTF.C006: Found 2 idle states
Oct 12 13:14:18 ryzen kernel: CPU3 is up
Oct 12 13:14:18 ryzen kernel: smpboot: Booting Node 0 Processor 4 APIC 0x8
Oct 12 13:14:18 ryzen kernel: ACPI: \_SB_.PLTF.C008: Found 2 idle states
Oct 12 13:14:18 ryzen kernel: CPU4 is up
Oct 12 13:14:18 ryzen kernel: smpboot: Booting Node 0 Processor 5 APIC 0xa
Oct 12 13:14:18 ryzen kernel: ACPI: \_SB_.PLTF.C00A: Found 2 idle states
Oct 12 13:14:18 ryzen kernel: CPU5 is up
Oct 12 13:14:18 ryzen kernel: smpboot: Booting Node 0 Processor 6 APIC 0x1
Oct 12 13:14:18 ryzen kernel: ACPI: \_SB_.PLTF.C001: Found 2 idle states
Oct 12 13:14:18 ryzen kernel: Spectre V2 : Update user space SMT mitigation: STIBP always-on
Oct 12 13:14:18 ryzen kernel: CPU6 is up
Oct 12 13:14:18 ryzen kernel: smpboot: Booting Node 0 Processor 7 APIC 0x3
Oct 12 13:14:18 ryzen kernel: ACPI: \_SB_.PLTF.C003: Found 2 idle states
Oct 12 13:14:18 ryzen kernel: CPU7 is up
Oct 12 13:14:18 ryzen kernel: smpboot: Booting Node 0 Processor 8 APIC 0x5
Oct 12 13:14:18 ryzen kernel: ACPI: \_SB_.PLTF.C005: Found 2 idle states
Oct 12 13:14:18 ryzen kernel: CPU8 is up
Oct 12 13:14:18 ryzen kernel: smpboot: Booting Node 0 Processor 9 APIC 0x7
Oct 12 13:14:18 ryzen kernel: ACPI: \_SB_.PLTF.C007: Found 2 idle states
Oct 12 13:14:18 ryzen kernel: CPU9 is up
Oct 12 13:14:18 ryzen kernel: smpboot: Booting Node 0 Processor 10 APIC 0x9
Oct 12 13:14:18 ryzen kernel: ACPI: \_SB_.PLTF.C009: Found 2 idle states
Oct 12 13:14:18 ryzen kernel: CPU10 is up
Oct 12 13:14:18 ryzen kernel: smpboot: Booting Node 0 Processor 11 APIC 0xb
Oct 12 13:14:18 ryzen kernel: ACPI: \_SB_.PLTF.C00B: Found 2 idle states
Oct 12 13:14:18 ryzen kernel: CPU11 is up
Oct 12 13:14:18 ryzen kernel: ACPI: PM: Waking up from system sleep state S3
Oct 12 13:14:18 ryzen kernel: pci 0000:00:00.0: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 47568, parent: pci0000:00
Oct 12 13:14:18 ryzen kernel: pci 0000:00:01.0: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 47575, parent: pci0000:00
Oct 12 13:14:18 ryzen kernel: pcieport 0000:00:01.1: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 47564, parent: pci0000:00
Oct 12 13:14:18 ryzen kernel: pci 0000:00:00.2: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 47566, parent: pci0000:00
Oct 12 13:14:18 ryzen kernel: pcieport 0000:00:01.2: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 47562, parent: pci0000:00
Oct 12 13:14:18 ryzen kernel: pci 0000:00:01.0: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 60 usecs
Oct 12 13:14:18 ryzen kernel: pci 0000:00:02.0: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 47575, parent: pci0000:00
Oct 12 13:14:18 ryzen kernel: pci 0000:00:00.0: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 105 usecs
Oct 12 13:14:18 ryzen kernel: pci 0000:00:03.0: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 47568, parent: pci0000:00
Oct 12 13:14:18 ryzen kernel: pci 0000:00:02.0: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 86 usecs
Oct 12 13:14:18 ryzen kernel: pcieport 0000:00:03.1: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 47575, parent: pci0000:00
Oct 12 13:14:18 ryzen kernel: pci 0000:00:00.2: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 170 usecs
Oct 12 13:14:18 ryzen kernel: pci 0000:00:04.0: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 47566, parent: pci0000:00
Oct 12 13:14:18 ryzen kernel: pci 0000:00:03.0: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 80 usecs
Oct 12 13:14:18 ryzen kernel: pci 0000:00:05.0: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 47568, parent: pci0000:00
Oct 12 13:14:18 ryzen kernel: pci 0000:00:04.0: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 83 usecs
Oct 12 13:14:18 ryzen kernel: pci 0000:00:07.0: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 47566, parent: pci0000:00
Oct 12 13:14:18 ryzen kernel: pci 0000:00:05.0: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 80 usecs
Oct 12 13:14:18 ryzen kernel: pcieport 0000:00:07.1: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 47568, parent: pci0000:00
Oct 12 13:14:18 ryzen kernel: pcieport 0000:00:01.1: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 314 usecs
Oct 12 13:14:18 ryzen kernel: pci 0000:00:08.0: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 47564, parent: pci0000:00
Oct 12 13:14:18 ryzen kernel: pcieport 0000:00:01.2: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 332 usecs
Oct 12 13:14:18 ryzen kernel: pcieport 0000:00:08.1: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 47562, parent: pci0000:00
Oct 12 13:14:18 ryzen kernel: piix4_smbus 0000:00:14.0: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 47574, parent: pci0000:00
Oct 12 13:14:18 ryzen kernel: pci 0000:00:07.0: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 77 usecs
Oct 12 13:14:18 ryzen kernel: pci 0000:00:14.3: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 36943, parent: pci0000:00
Oct 12 13:14:18 ryzen kernel: pci 0000:00:18.0: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 47566, parent: pci0000:00
Oct 12 13:14:18 ryzen kernel: pci 0000:00:18.1: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 47578, parent: pci0000:00
Oct 12 13:14:18 ryzen kernel: pci 0000:00:18.2: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 45729, parent: pci0000:00
Oct 12 13:14:18 ryzen kernel: k10temp 0000:00:18.3: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 47577, parent: pci0000:00
Oct 12 13:14:18 ryzen kernel: pci 0000:00:18.4: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 47563, parent: pci0000:00
Oct 12 13:14:18 ryzen kernel: pci 0000:00:18.6: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 47565, parent: pci0000:00
Oct 12 13:14:18 ryzen kernel: pci 0000:00:08.0: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 102 usecs
Oct 12 13:14:18 ryzen kernel: pci 0000:00:18.7: PM: calling pci_pm_resume_noirq+0x0/0x120 @ 47564, parent: pci0000:00
Oct 12 13:14:18 ryzen kernel: pci 0000:00:18.0: PM: pci_pm_resume_noirq+0x0/0x120 returned 0 after 126 usecs
Oct 12 13:14:18 ryzen kernel: piix4_smbus 0000:00:14.0: PM: pci_pm_resume_noirq+0x0/0x120 retur
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment