Immediate wake from suspend ONLY when manually locked (Super+L)

seventeen · 2026-01-16 18:35:50

am running Arch Linux with GNOME. I have a strange inconsistency with system suspend where the method of locking determines if suspend works or fails.

The Issue:

Idle Suspend (Works): If I let the PC sit idle, the screen turns off (5 min) and eventually suspends (15 min). It stays asleep perfectly.

Manual Lock (Fails): If I press Super + L to lock the screen, the screen turns off. When the 15-minute suspend timer hits, the system enters suspend but immediately wakes up (within 1 second). /sys/power/pm_wakeup_irq shows No data available

System Info:

Kernel: 6.18.5-arch1-1

DE: GNOME

GPU: NVIDIA (Driver Version: 590.48.01)

Logs (Manual Lock Scenario): The logs show the system entering S3 and waking up the same second.

Jan 17 02:09:32 my-pc systemd-logind[649]: The system will suspend now!
Jan 17 02:09:32 my-pc NetworkManager[647]: <info>  [1768586972.6329] manager: sleep: sleep requested (sleeping: no  enabled: yes)
Jan 17 02:09:32 my-pc chromium.desktop[5660]: [5660:5684:0117/020932.635087:ERROR:google_apis/gcm/engine/connection_factory_impl.cc:483] ConnectionHandler failed with net error: -2
Jan 17 02:09:32 my-pc rtkit-daemon[783]: Demoting known real-time threads.
Jan 17 02:09:32 my-pc NetworkManager[647]: <info>  [1768586972.6331] device (wlo1): state change: unavailable -> unmanaged (reason 'unmanaged-nm-disabled', managed-type: 'full')
Jan 17 02:09:32 my-pc rtkit-daemon[783]: Successfully demoted thread 3142 of process 3118.
Jan 17 02:09:32 my-pc NetworkManager[647]: <info>  [1768586972.6337] device (wlo1): set-hw-addr: reset MAC address to XX:XX:XX:XX:XX:XX (unmanage)
Jan 17 02:09:32 my-pc rtkit-daemon[783]: Successfully demoted thread 3118 of process 3118.
Jan 17 02:09:32 my-pc NetworkManager[647]: <info>  [1768586972.6342] manager: NetworkManager state is now DISABLED (ASLEEP)
Jan 17 02:09:32 my-pc rtkit-daemon[783]: Successfully demoted thread 3147 of process 3102.
Jan 17 02:09:32 my-pc NetworkManager[647]: <info>  [1768586972.6343] device (enp4s0): state change: activated -> deactivating (reason 'sleeping', managed-type: 'full')
Jan 17 02:09:32 my-pc rtkit-daemon[783]: Successfully demoted thread 3102 of process 3102.
Jan 17 02:09:32 my-pc systemd[1]: Starting Network Manager Script Dispatcher Service...
Jan 17 02:09:32 my-pc rtkit-daemon[783]: Successfully demoted thread 3133 of process 3100.
Jan 17 02:09:32 my-pc rtkit-daemon[783]: Successfully demoted thread 3100 of process 3100.
Jan 17 02:09:32 my-pc rtkit-daemon[783]: Successfully demoted thread 2831 of process 2801.
Jan 17 02:09:32 my-pc rtkit-daemon[783]: Demoted 7 threads.
Jan 17 02:09:32 my-pc systemd[1]: Started Network Manager Script Dispatcher Service.
Jan 17 02:09:32 my-pc NetworkManager[647]: <info>  [1768586972.6718] device (enp4s0): state change: deactivating -> disconnected (reason 'sleeping', managed-type: 'full')
Jan 17 02:09:32 my-pc NetworkManager[647]: <info>  [1768586972.6722] dhcp4 (enp4s0): canceled DHCP transaction
Jan 17 02:09:32 my-pc NetworkManager[647]: <info>  [1768586972.6722] dhcp4 (enp4s0): activation: beginning transaction (timeout in 45 seconds)
Jan 17 02:09:32 my-pc NetworkManager[647]: <info>  [1768586972.6723] dhcp4 (enp4s0): state changed no lease
Jan 17 02:09:32 my-pc NetworkManager[647]: <info>  [1768586972.7153] device (enp4s0): state change: disconnected -> unmanaged (reason 'unmanaged-nm-disabled', managed-type: 'full')
Jan 17 02:09:32 my-pc kernel: r8169 0000:04:00.0 enp4s0: Link is Down
Jan 17 02:09:32 my-pc gsd-sharing[2976]: Failed to stop rygel.service: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit rygel.service not loaded.
Jan 17 02:09:32 my-pc systemd[1]: Reached target Sleep.
Jan 17 02:09:32 my-pc systemd[1]: Starting NVIDIA system suspend actions...
Jan 17 02:09:32 my-pc suspend[17779]: nvidia-suspend.service
Jan 17 02:09:32 my-pc logger[17779]: <13>Jan 17 02:09:32 suspend: nvidia-suspend.service
Jan 17 02:09:32 my-pc kernel: rfkill: input handler enabled
Jan 17 02:09:32 my-pc bluetoothd[648]: Endpoint unregistered: sender=:1.165 path=/MediaEndpoint/A2DPSource/ldac
Jan 17 02:09:32 my-pc bluetoothd[648]: Endpoint unregistered: sender=:1.165 path=/MediaEndpoint/A2DPSink/aptx_hd
Jan 17 02:09:32 my-pc bluetoothd[648]: Endpoint unregistered: sender=:1.165 path=/MediaEndpoint/A2DPSource/aptx_hd
Jan 17 02:09:32 my-pc bluetoothd[648]: Endpoint unregistered: sender=:1.165 path=/MediaEndpoint/A2DPSink/aptx
Jan 17 02:09:32 my-pc bluetoothd[648]: Endpoint unregistered: sender=:1.165 path=/MediaEndpoint/A2DPSource/aptx
Jan 17 02:09:32 my-pc bluetoothd[648]: Endpoint unregistered: sender=:1.165 path=/MediaEndpoint/A2DPSink/aac
Jan 17 02:09:32 my-pc bluetoothd[648]: Endpoint unregistered: sender=:1.165 path=/MediaEndpoint/A2DPSource/aac
Jan 17 02:09:32 my-pc bluetoothd[648]: Endpoint unregistered: sender=:1.165 path=/MediaEndpoint/A2DPSink/opus_g
Jan 17 02:09:32 my-pc gsd-media-keys[2941]: Unable to get default sink
Jan 17 02:09:32 my-pc bluetoothd[648]: Endpoint unregistered: sender=:1.165 path=/MediaEndpoint/A2DPSource/opus_g
Jan 17 02:09:32 my-pc bluetoothd[648]: Endpoint unregistered: sender=:1.165 path=/MediaEndpoint/A2DPSink/sbc
Jan 17 02:09:32 my-pc bluetoothd[648]: Endpoint unregistered: sender=:1.165 path=/MediaEndpoint/A2DPSource/sbc
Jan 17 02:09:32 my-pc bluetoothd[648]: Endpoint unregistered: sender=:1.165 path=/MediaEndpoint/A2DPSource/aptx_ll_1
Jan 17 02:09:32 my-pc bluetoothd[648]: Endpoint unregistered: sender=:1.165 path=/MediaEndpoint/A2DPSource/aptx_ll_0
Jan 17 02:09:32 my-pc bluetoothd[648]: Endpoint unregistered: sender=:1.165 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_1
Jan 17 02:09:32 my-pc bluetoothd[648]: Endpoint unregistered: sender=:1.165 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_0
Jan 17 02:09:32 my-pc bluetoothd[648]: Endpoint unregistered: sender=:1.165 path=/MediaEndpoint/A2DPSource/faststream
Jan 17 02:09:32 my-pc bluetoothd[648]: Endpoint unregistered: sender=:1.165 path=/MediaEndpoint/A2DPSource/faststream_duplex
Jan 17 02:09:32 my-pc bluetoothd[648]: Endpoint unregistered: sender=:1.165 path=/MediaEndpoint/A2DPSink/opus_05
Jan 17 02:09:32 my-pc bluetoothd[648]: Endpoint unregistered: sender=:1.165 path=/MediaEndpoint/A2DPSource/opus_05
Jan 17 02:09:32 my-pc bluetoothd[648]: Endpoint unregistered: sender=:1.165 path=/MediaEndpoint/A2DPSink/opus_05_duplex
Jan 17 02:09:32 my-pc bluetoothd[648]: Endpoint unregistered: sender=:1.165 path=/MediaEndpoint/A2DPSource/opus_05_duplex
Jan 17 02:09:34 my-pc systemd[1]: nvidia-suspend.service: Deactivated successfully.
Jan 17 02:09:34 my-pc systemd[1]: Finished NVIDIA system suspend actions.
Jan 17 02:09:34 my-pc systemd[1]: nvidia-suspend.service: Consumed 1.647s CPU time, 1.4G memory peak.
Jan 17 02:09:34 my-pc systemd[1]: Starting System Suspend...
Jan 17 02:09:34 my-pc systemd-sleep[17810]: User sessions remain unfrozen on explicit request ($SYSTEMD_SLEEP_FREEZE_USER_SESSIONS=0).
Jan 17 02:09:34 my-pc systemd-sleep[17810]: This is not recommended, and might result in unexpected behavior, particularly
Jan 17 02:09:34 my-pc systemd-sleep[17810]: in suspend-then-hibernate operations or setups with encrypted home directories.
Jan 17 02:09:34 my-pc systemd-sleep[17810]: Performing sleep operation 'suspend'...
Jan 17 02:09:34 my-pc kernel: PM: suspend entry (deep)
Jan 17 02:09:34 my-pc kernel: Filesystems sync: 0.304 seconds
Jan 17 02:09:40 my-pc kernel: Freezing user space processes
Jan 17 02:09:40 my-pc kernel: Freezing user space processes completed (elapsed 0.001 seconds)
Jan 17 02:09:40 my-pc kernel: OOM killer disabled.
Jan 17 02:09:40 my-pc kernel: Freezing remaining freezable tasks
Jan 17 02:09:40 my-pc kernel: Freezing remaining freezable tasks completed (elapsed 0.001 seconds)
Jan 17 02:09:40 my-pc kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Jan 17 02:09:40 my-pc kernel: serial 00:03: disabled
Jan 17 02:09:40 my-pc kernel: ACPI: PM: Preparing to enter system sleep state S3
Jan 17 02:09:40 my-pc kernel: ACPI: PM: Saving platform NVS memory
Jan 17 02:09:40 my-pc kernel: Disabling non-boot CPUs ...
Jan 17 02:09:40 my-pc kernel: smpboot: CPU 19 is now offline
Jan 17 02:09:40 my-pc kernel: smpboot: CPU 18 is now offline
Jan 17 02:09:40 my-pc kernel: smpboot: CPU 17 is now offline
Jan 17 02:09:40 my-pc kernel: smpboot: CPU 16 is now offline
Jan 17 02:09:40 my-pc kernel: smpboot: CPU 15 is now offline
Jan 17 02:09:40 my-pc kernel: smpboot: CPU 14 is now offline
Jan 17 02:09:40 my-pc kernel: smpboot: CPU 13 is now offline
Jan 17 02:09:40 my-pc kernel: smpboot: CPU 12 is now offline
Jan 17 02:09:40 my-pc kernel: smpboot: CPU 11 is now offline
Jan 17 02:09:40 my-pc kernel: smpboot: CPU 10 is now offline
Jan 17 02:09:40 my-pc kernel: smpboot: CPU 9 is now offline
Jan 17 02:09:40 my-pc kernel: smpboot: CPU 8 is now offline
Jan 17 02:09:40 my-pc kernel: smpboot: CPU 7 is now offline
Jan 17 02:09:40 my-pc kernel: smpboot: CPU 6 is now offline
Jan 17 02:09:40 my-pc kernel: smpboot: CPU 5 is now offline
Jan 17 02:09:40 my-pc kernel: smpboot: CPU 4 is now offline
Jan 17 02:09:40 my-pc kernel: smpboot: CPU 3 is now offline
Jan 17 02:09:40 my-pc kernel: smpboot: CPU 2 is now offline
Jan 17 02:09:40 my-pc kernel: smpboot: CPU 1 is now offline
Jan 17 02:09:40 my-pc kernel: ACPI: PM: Low-level resume complete
Jan 17 02:09:40 my-pc kernel: ACPI: PM: Restoring platform NVS memory
Jan 17 02:09:40 my-pc kernel: Enabling non-boot CPUs ...
Jan 17 02:09:40 my-pc kernel: smpboot: Booting Node 0 Processor 1 APIC 0x1
Jan 17 02:09:40 my-pc kernel: CPU1 is up
Jan 17 02:09:40 my-pc kernel: smpboot: Booting Node 0 Processor 2 APIC 0x8
Jan 17 02:09:40 my-pc kernel: CPU2 is up
Jan 17 02:09:40 my-pc kernel: smpboot: Booting Node 0 Processor 3 APIC 0x9
Jan 17 02:09:40 my-pc kernel: CPU3 is up
Jan 17 02:09:40 my-pc kernel: smpboot: Booting Node 0 Processor 4 APIC 0x10
Jan 17 02:09:40 my-pc kernel: CPU4 is up
Jan 17 02:09:40 my-pc kernel: smpboot: Booting Node 0 Processor 5 APIC 0x11
Jan 17 02:09:40 my-pc kernel: CPU5 is up
Jan 17 02:09:40 my-pc kernel: smpboot: Booting Node 0 Processor 6 APIC 0x18
Jan 17 02:09:40 my-pc kernel: CPU6 is up
Jan 17 02:09:40 my-pc kernel: smpboot: Booting Node 0 Processor 7 APIC 0x19
Jan 17 02:09:40 my-pc kernel: CPU7 is up
Jan 17 02:09:40 my-pc kernel: smpboot: Booting Node 0 Processor 8 APIC 0x20
Jan 17 02:09:40 my-pc kernel: CPU8 is up
Jan 17 02:09:40 my-pc kernel: smpboot: Booting Node 0 Processor 9 APIC 0x21
Jan 17 02:09:40 my-pc kernel: CPU9 is up
Jan 17 02:09:40 my-pc kernel: smpboot: Booting Node 0 Processor 10 APIC 0x28
Jan 17 02:09:40 my-pc kernel: CPU10 is up
Jan 17 02:09:40 my-pc kernel: smpboot: Booting Node 0 Processor 11 APIC 0x29
Jan 17 02:09:40 my-pc kernel: CPU11 is up
Jan 17 02:09:40 my-pc kernel: smpboot: Booting Node 0 Processor 12 APIC 0x30
Jan 17 02:09:40 my-pc kernel: core: cpu_atom PMU driver: 
Jan 17 02:09:40 my-pc kernel: ... version:                   5
Jan 17 02:09:40 my-pc kernel: ... bit width:                 48
Jan 17 02:09:40 my-pc kernel: ... generic counters:          6
Jan 17 02:09:40 my-pc kernel: ... generic bitmap:            000000000000003f
Jan 17 02:09:40 my-pc kernel: ... fixed-purpose counters:    3
Jan 17 02:09:40 my-pc kernel: ... fixed-purpose bitmap:      0000000000000007
Jan 17 02:09:40 my-pc kernel: ... value mask:                0000ffffffffffff
Jan 17 02:09:40 my-pc kernel: ... max period:                00007fffffffffff
Jan 17 02:09:40 my-pc kernel: ... global_ctrl mask:          000000070000003f
Jan 17 02:09:40 my-pc kernel: CPU12 is up
Jan 17 02:09:40 my-pc kernel: smpboot: Booting Node 0 Processor 13 APIC 0x32
Jan 17 02:09:40 my-pc kernel: CPU13 is up
Jan 17 02:09:40 my-pc kernel: smpboot: Booting Node 0 Processor 14 APIC 0x34
Jan 17 02:09:40 my-pc kernel: CPU14 is up
Jan 17 02:09:40 my-pc kernel: smpboot: Booting Node 0 Processor 15 APIC 0x36
Jan 17 02:09:40 my-pc kernel: CPU15 is up
Jan 17 02:09:40 my-pc kernel: smpboot: Booting Node 0 Processor 16 APIC 0x38
Jan 17 02:09:40 my-pc kernel: CPU16 is up
Jan 17 02:09:40 my-pc kernel: smpboot: Booting Node 0 Processor 17 APIC 0x3a
Jan 17 02:09:40 my-pc kernel: CPU17 is up
Jan 17 02:09:40 my-pc kernel: smpboot: Booting Node 0 Processor 18 APIC 0x3c
Jan 17 02:09:40 my-pc kernel: CPU18 is up
Jan 17 02:09:40 my-pc kernel: smpboot: Booting Node 0 Processor 19 APIC 0x3e
Jan 17 02:09:40 my-pc kernel: CPU19 is up
Jan 17 02:09:40 my-pc kernel: ACPI: PM: Waking up from system sleep state S3
Jan 17 02:09:40 my-pc kernel: serial 00:03: activated
Jan 17 02:09:40 my-pc kernel: nvme nvme0: D3 entry latency set to 10 seconds
Jan 17 02:09:40 my-pc kernel: nvme nvme0: 16/0/0 default/read/poll queues
Jan 17 02:09:40 my-pc kernel: nvme nvme1: 8/0/0 default/read/poll queues
Jan 17 02:09:40 my-pc kernel: OOM killer enabled.
Jan 17 02:09:40 my-pc kernel: Restarting tasks: Starting
Jan 17 02:09:40 my-pc kernel: Restarting tasks: Done
Jan 17 02:09:40 my-pc kernel: efivarfs: resyncing variable state
Jan 17 02:09:40 my-pc kernel: efivarfs: finished resyncing variable state
Jan 17 02:09:40 my-pc kernel: random: crng reseeded on system resumption
Jan 17 02:09:40 my-pc systemd-sleep[17810]: System returned from sleep operation 'suspend'.
Jan 17 02:09:40 my-pc bluetoothd[648]: Controller resume with wake event 0x0
Jan 17 02:09:40 my-pc kernel: PM: suspend exit
Jan 17 02:09:40 my-pc kernel: ata7: SATA link down (SStatus 4 SControl 300)
Jan 17 02:09:40 my-pc kernel: ata6: SATA link down (SStatus 4 SControl 300)
Jan 17 02:09:40 my-pc kernel: ata8: SATA link down (SStatus 4 SControl 300)
Jan 17 02:09:40 my-pc kernel: ata5: SATA link down (SStatus 4 SControl 300)
Jan 17 02:09:41 my-pc gnome-shell[2801]: g_settings_get_value: assertion 'G_IS_SETTINGS (settings)' failed
Jan 17 02:09:41 my-pc gnome-shell[2801]: g_variant_get_type: assertion 'value != NULL' failed
Jan 17 02:09:41 my-pc gnome-shell[2801]: g_variant_type_is_subtype_of: assertion 'g_variant_type_check (type)' failed
Jan 17 02:09:41 my-pc gnome-shell[2801]: g_variant_get_uint32: assertion 'g_variant_is_of_type (value, G_VARIANT_TYPE_UINT32)' failed
Jan 17 02:09:41 my-pc gnome-shell[2801]: g_variant_unref: assertion 'value != NULL' failed
Jan 17 02:09:41 my-pc gnome-shell[2801]: g_settings_get_value: assertion 'G_IS_SETTINGS (settings)' failed
Jan 17 02:09:41 my-pc gnome-shell[2801]: g_variant_get_type: assertion 'value != NULL' failed
Jan 17 02:09:41 my-pc gnome-shell[2801]: g_variant_type_is_subtype_of: assertion 'g_variant_type_check (type)' failed
Jan 17 02:09:41 my-pc gnome-shell[2801]: g_variant_get_uint32: assertion 'g_variant_is_of_type (value, G_VARIANT_TYPE_UINT32)' failed
Jan 17 02:09:41 my-pc gnome-shell[2801]: g_variant_unref: assertion 'value != NULL' failed
Jan 17 02:09:41 my-pc gnome-shell[2801]: g_settings_get_value: assertion 'G_IS_SETTINGS (settings)' failed
Jan 17 02:09:41 my-pc gnome-shell[2801]: g_variant_get_type: assertion 'value != NULL' failed
Jan 17 02:09:41 my-pc gnome-shell[2801]: g_variant_type_is_subtype_of: assertion 'g_variant_type_check (type)' failed
Jan 17 02:09:41 my-pc gnome-shell[2801]: g_variant_get_boolean: assertion 'g_variant_is_of_type (value, G_VARIANT_TYPE_BOOLEAN)' failed
Jan 17 02:09:41 my-pc gnome-shell[2801]: g_variant_unref: assertion 'value != NULL' failed
Jan 17 02:09:41 my-pc gdm[692]: GLib: Source ID 140 was not found when attempting to remove it
Jan 17 02:09:41 my-pc systemd[1]: systemd-suspend.service: Deactivated successfully.
Jan 17 02:09:41 my-pc systemd[1]: Finished System Suspend.
Jan 17 02:09:41 my-pc systemd[1]: systemd-suspend.service: Consumed 1.312s CPU time, 3.2M memory peak.
Jan 17 02:09:41 my-pc systemd[1]: Stopped target Sleep.
Jan 17 02:09:41 my-pc systemd[1]: Reached target Suspend.
Jan 17 02:09:41 my-pc kernel: rfkill: input handler disabled
Jan 17 02:09:41 my-pc systemd-logind[649]: Operation 'suspend' finished.
Jan 17 02:09:41 my-pc NetworkManager[647]: <info>  [1768586981.4251] manager: sleep: wake requested (sleeping: yes  enabled: yes)
Jan 17 02:09:41 my-pc NetworkManager[647]: <info>  [1768586981.4252] device (enp4s0): state change: unmanaged -> unavailable (reason 'managed', managed-type: 'external')
Jan 17 02:09:41 my-pc systemd[1]: Starting NVIDIA system resume actions...
Jan 17 02:09:41 my-pc rtkit-daemon[783]: Resuming known real-time threads.
Jan 17 02:09:41 my-pc rtkit-daemon[783]: Successfully made thread 3142 of process 3118 owned by '1000' RT at priority 20.
Jan 17 02:09:41 my-pc systemd[1]: Stopped target Suspend.
Jan 17 02:09:41 my-pc rtkit-daemon[783]: Successfully made thread 3118 of process 3118 owned by '1000' high priority at nice level -11.
Jan 17 02:09:41 my-pc rtkit-daemon[783]: Successfully made thread 3147 of process 3102 owned by '1000' RT at priority 20.
Jan 17 02:09:41 my-pc rtkit-daemon[783]: Successfully made thread 3102 of process 3102 owned by '1000' high priority at nice level -11.
Jan 17 02:09:41 my-pc rtkit-daemon[783]: Successfully made thread 3133 of process 3100 owned by '1000' RT at priority 20.
Jan 17 02:09:41 my-pc rtkit-daemon[783]: Successfully made thread 3100 of process 3100 owned by '1000' high priority at nice level -11.
Jan 17 02:09:41 my-pc rtkit-daemon[783]: Successfully made thread 2831 of process 2801 owned by '1000' high priority at nice level -15.
Jan 17 02:09:41 my-pc rtkit-daemon[783]: Resumed scheduling 7 threads.
Jan 17 02:09:41 my-pc suspend[17890]: nvidia-resume.service
Jan 17 02:09:41 my-pc logger[17890]: <13>Jan 17 02:09:41 suspend: nvidia-resume.service
Jan 17 02:09:41 my-pc systemd[1]: nvidia-resume.service: Deactivated successfully.
Jan 17 02:09:41 my-pc systemd[1]: Finished NVIDIA system resume actions.
Jan 17 02:09:41 my-pc kernel: Realtek Internal NBASE-T PHY r8169-0-400:00: attached PHY driver (mii_bus:phy_addr=r8169-0-400:00, irq=MAC)
Jan 17 02:09:41 my-pc wireplumber[3102]: spa.bluez5.midi: org.bluez.GattManager1.RegisterApplication() failed: GDBus.Error:org.bluez.Error.AlreadyExists: Already Exists
Jan 17 02:09:41 my-pc bluetoothd[648]: Endpoint registered: sender=:1.174 path=/MediaEndpoint/A2DPSource/ldac
Jan 17 02:09:41 my-pc bluetoothd[648]: Endpoint registered: sender=:1.174 path=/MediaEndpoint/A2DPSink/aptx_hd
Jan 17 02:09:41 my-pc bluetoothd[648]: Endpoint registered: sender=:1.174 path=/MediaEndpoint/A2DPSource/aptx_hd
Jan 17 02:09:41 my-pc bluetoothd[648]: Endpoint registered: sender=:1.174 path=/MediaEndpoint/A2DPSink/aptx
Jan 17 02:09:41 my-pc bluetoothd[648]: Endpoint registered: sender=:1.174 path=/MediaEndpoint/A2DPSource/aptx
Jan 17 02:09:41 my-pc bluetoothd[648]: Endpoint registered: sender=:1.174 path=/MediaEndpoint/A2DPSink/aac
Jan 17 02:09:41 my-pc bluetoothd[648]: Endpoint registered: sender=:1.174 path=/MediaEndpoint/A2DPSource/aac
Jan 17 02:09:41 my-pc bluetoothd[648]: Endpoint registered: sender=:1.174 path=/MediaEndpoint/A2DPSink/opus_g
Jan 17 02:09:41 my-pc bluetoothd[648]: Endpoint registered: sender=:1.174 path=/MediaEndpoint/A2DPSource/opus_g
Jan 17 02:09:41 my-pc bluetoothd[648]: Endpoint registered: sender=:1.174 path=/MediaEndpoint/A2DPSink/sbc
Jan 17 02:09:41 my-pc bluetoothd[648]: Endpoint registered: sender=:1.174 path=/MediaEndpoint/A2DPSource/sbc
Jan 17 02:09:41 my-pc bluetoothd[648]: Endpoint registered: sender=:1.174 path=/MediaEndpoint/A2DPSource/aptx_ll_1
Jan 17 02:09:41 my-pc bluetoothd[648]: Endpoint registered: sender=:1.174 path=/MediaEndpoint/A2DPSource/aptx_ll_0
Jan 17 02:09:41 my-pc bluetoothd[648]: Endpoint registered: sender=:1.174 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_1
Jan 17 02:09:41 my-pc bluetoothd[648]: Endpoint registered: sender=:1.174 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_0
Jan 17 02:09:41 my-pc bluetoothd[648]: Endpoint registered: sender=:1.174 path=/MediaEndpoint/A2DPSource/faststream
Jan 17 02:09:41 my-pc bluetoothd[648]: Endpoint registered: sender=:1.174 path=/MediaEndpoint/A2DPSource/faststream_duplex
Jan 17 02:09:41 my-pc bluetoothd[648]: Endpoint registered: sender=:1.174 path=/MediaEndpoint/A2DPSink/opus_05
Jan 17 02:09:41 my-pc bluetoothd[648]: Endpoint registered: sender=:1.174 path=/MediaEndpoint/A2DPSource/opus_05
Jan 17 02:09:41 my-pc bluetoothd[648]: Endpoint registered: sender=:1.174 path=/MediaEndpoint/A2DPSink/opus_05_duplex
Jan 17 02:09:41 my-pc bluetoothd[648]: Endpoint registered: sender=:1.174 path=/MediaEndpoint/A2DPSource/opus_05_duplex
Jan 17 02:09:41 my-pc gsd-media-keys[2941]: Unable to get default sink
Jan 17 02:09:41 my-pc gsd-media-keys[2941]: Unable to get default source
Jan 17 02:09:41 my-pc NetworkManager[647]: <info>  [1768586981.6074] device (wlo1): state change: unmanaged -> unavailable (reason 'managed', managed-type: 'external')
Jan 17 02:09:41 my-pc NetworkManager[647]: <info>  [1768586981.6076] device (wlo1): set-hw-addr: set MAC address to XX:XX:XX:XX:XX:XX (scanning)
Jan 17 02:09:41 my-pc NetworkManager[647]: <info>  [1768586981.6077] manager: NetworkManager state is now DISCONNECTED
Jan 17 02:09:41 my-pc kernel: r8169 0000:04:00.0 enp4s0: Link is Down
Jan 17 02:09:41 my-pc gnome-shell[17919]: The XKEYBOARD keymap compiler (xkbcomp) reports:
Jan 17 02:09:41 my-pc gnome-shell[17919]: > Warning:          Unsupported maximum keycode 708, clipping.
Jan 17 02:09:41 my-pc gnome-shell[17919]: >                   X11 cannot support keycodes above 255.
Jan 17 02:09:41 my-pc gnome-shell[17919]: > Warning:          Virtual modifier Hyper multiply defined
Jan 17 02:09:41 my-pc gnome-shell[17919]: >                   Using 0, ignoring 0
Jan 17 02:09:41 my-pc gnome-shell[17919]: > Warning:          Virtual modifier ScrollLock multiply defined
Jan 17 02:09:41 my-pc gnome-shell[17919]: >                   Using 0, ignoring 0
Jan 17 02:09:41 my-pc gnome-shell[17919]: Errors from xkbcomp are not fatal to the X server
Jan 17 02:09:45 my-pc NetworkManager[647]: <info>  [1768586985.0627] device (enp4s0): carrier: link connected
Jan 17 02:09:45 my-pc kernel: r8169 0000:04:00.0 enp4s0: Link is Up - 2.5Gbps/Full - flow control rx/tx
Jan 17 02:09:45 my-pc NetworkManager[647]: <info>  [1768586985.0630] device (enp4s0): state change: unavailable -> disconnected (reason 'carrier-changed', managed-type: 'full')
Jan 17 02:09:45 my-pc NetworkManager[647]: <info>  [1768586985.0639] policy: auto-activating connection 'Wired connection 1' ([UUID-REDACTED])
Jan 17 02:09:45 my-pc NetworkManager[647]: <info>  [1768586985.0644] device (enp4s0): Activation: starting connection 'Wired connection 1' ([UUID-REDACTED])
Jan 17 02:09:45 my-pc NetworkManager[647]: <info>  [1768586985.0645] device (enp4s0): state change: disconnected -> prepare (reason 'none', managed-type: 'full')
Jan 17 02:09:45 my-pc NetworkManager[647]: <info>  [1768586985.0647] manager: NetworkManager state is now CONNECTING
Jan 17 02:09:45 my-pc NetworkManager[647]: <info>  [1768586985.0648] device (enp4s0): state change: prepare -> config (reason 'none', managed-type: 'full')
Jan 17 02:09:45 my-pc NetworkManager[647]: <info>  [1768586985.0653] device (enp4s0): state change: config -> ip-config (reason 'none', managed-type: 'full')
Jan 17 02:09:45 my-pc NetworkManager[647]: <info>  [1768586985.0656] dhcp4 (enp4s0): activation: beginning transaction (timeout in 45 seconds)
Jan 17 02:09:47 my-pc NetworkManager[647]: <info>  [1768586987.0680] dhcp4 (enp4s0): state changed new lease, address=192.168.x.x, acd pending
Jan 17 02:09:47 my-pc NetworkManager[647]: <info>  [1768586987.1911] dhcp4 (enp4s0): state changed new lease, address=192.168.x.x
Jan 17 02:09:47 my-pc NetworkManager[647]: <info>  [1768586987.1922] policy: set 'Wired connection 1' (enp4s0) as default for IPv4 routing and DNS
Jan 17 02:09:47 my-pc gsd-sharing[2976]: Failed to stop rygel.service: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit rygel.service not loaded.
Jan 17 02:09:47 my-pc NetworkManager[647]: <info>  [1768586987.2336] device (enp4s0): state change: ip-config -> ip-check (reason 'none', managed-type: 'full')
Jan 17 02:09:47 my-pc NetworkManager[647]: <info>  [1768586987.2357] device (enp4s0): state change: ip-check -> secondaries (reason 'none', managed-type: 'full')
Jan 17 02:09:47 my-pc NetworkManager[647]: <info>  [1768586987.2358] device (enp4s0): state change: secondaries -> activated (reason 'none', managed-type: 'full')
Jan 17 02:09:47 my-pc NetworkManager[647]: <info>  [1768586987.2361] manager: NetworkManager state is now CONNECTED_SITE
Jan 17 02:09:47 my-pc NetworkManager[647]: <info>  [1768586987.2364] device (enp4s0): Activation: successful, device activated.
Jan 17 02:09:47 my-pc systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
Jan 17 02:09:47 my-pc NetworkManager[647]: <info>  [1768586987.6669] manager: NetworkManager state is now CONNECTED_GLOBAL
Jan 17 02:09:47 my-pc systemd[1]: Starting Network Manager Script Dispatcher Service...
Jan 17 02:09:47 my-pc systemd[1]: Started Network Manager Script Dispatcher Service.
Jan 17 02:09:48 my-pc gdm-password][17922]: gkr-pam: unlocked login keyring
Jan 17 02:09:48 my-pc systemd[2661]: Started dbus-:1.2-org.gnome.Shell.CalendarServer@10.service.
Jan 17 02:09:48 my-pc gnome-shell-calendar-server[17939]: /usr/lib/gnome-shell-calendar-server: error while loading shared libraries: libecal-2.0.so.3: cannot open shared object file: No such file or directory
Jan 17 02:09:48 my-pc systemd[2661]: dbus-:1.2-org.gnome.Shell.CalendarServer@10.service: Main process exited, code=exited, status=127/n/a
Jan 17 02:09:48 my-pc systemd[2661]: dbus-:1.2-org.gnome.Shell.CalendarServer@10.service: Failed with result 'exit-code'.
Jan 17 02:09:48 my-pc gnome-shell[2801]: Called enable_unredirect_for_display while unredirection is enabled.
Jan 17 02:09:48 my-pc NetworkManager[647]: <info>  [1768586988.7000] agent-manager: agent[9ba6884a7d62a199,:1.62/org.gnome.Shell.NetworkAgent/1000]: agent registered
Jan 17 02:09:48 my-pc systemd[2661]: Started dbus-:1.2-org.gnome.Shell.CalendarServer@11.service.
Jan 17 02:09:48 my-pc gnome-shell-calendar-server[17950]: /usr/lib/gnome-shell-calendar-server: error while loading shared libraries: libecal-2.0.so.3: cannot open shared object file: No such file or directory
Jan 17 02:09:48 my-pc systemd[2661]: dbus-:1.2-org.gnome.Shell.CalendarServer@11.service: Main process exited, code=exited, status=127/n/a
Jan 17 02:09:48 my-pc systemd[2661]: dbus-:1.2-org.gnome.Shell.CalendarServer@11.service: Failed with result 'exit-code'.
Jan 17 02:09:48 my-pc gnome-shell[2801]: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not activate remote peer 'org.gnome.Shell.CalendarServer': unit failed
                                                 
                                                 Stack trace:
                                                   asyncCallback@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:115:23
                                                   @resource:///org/gnome/shell/ui/init.js:21:20
                                                   
Jan 17 02:09:48 my-pc gnome-shell[2801]: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not activate remote peer 'org.gnome.Shell.CalendarServer': unit failed
                                                 
                                                 Stack trace:
                                                   asyncCallback@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:115:23
                                                   @resource:///org/gnome/shell/ui/init.js:21:20
                                                   
Jan 17 02:09:57 my-pc systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
Jan 17 02:10:14 my-pc sudo[17963]:     user : TTY=pts/2 ; PWD=/home/user ; USER=root ; COMMAND=/usr/bin/journalctl '--since=-5 minutes'
Jan 17 02:10:14 my-pc sudo[17963]: pam_unix(sudo:session): session opened for user root(uid=0) by user(uid=1000)
Jan 17 02:10:21 my-pc sudo[17963]: pam_unix(sudo:session): session closed for user root
Jan 17 02:10:29 my-pc sudo[17971]:     user : TTY=pts/2 ; PWD=/home/user ; USER=root ; COMMAND=/usr/bin/journalctl '--since=-5 minutes'
Jan 17 02:10:29 my-pc sudo[17971]: pam_unix(sudo:session): session opened for user root(uid=0) by user(uid=1000)

Can anyone help to see what's going on and how to fix this issue? This is quite annoying.

Last edited by seventeen (2026-01-16 18:36:11)

seth · 2026-01-16 20:11:46

https://bbs.archlinux.org/viewtopic.php?id=308457 ?

seventeen · 2026-01-17 03:43:36

seth wrote:

https://bbs.archlinux.org/viewtopic.php?id=308457 ?

Hi, thanks for the reply!

Unfortunately this is not the case i am dealing with (I also encountered this and have temporarily solved with the provided workaround)

This post describes as wake up and then soon go suspend

My case is when entering suspend it wake up immediately and only happens with manual lock screen.

seth · 2026-01-17 09:48:24

Can you lock the screen w/

dbus-send --type=method_call --dest=org.gnome.ScreenSaver /org/gnome/ScreenSaver org.gnome.ScreenSaver.Lock

and does that cause the same behavior?
If yes, what if you run

sleep 5; dbus-send --type=method_call --dest=org.gnome.ScreenSaver /org/gnome/ScreenSaver org.gnome.ScreenSaver.Lock

and immediately stay away from keyboard and mouse until the system sleeps?

seventeen · 2026-01-17 16:20:22

Tried both commands and they all have the same behavior.

But this time in the log i see errors with PCI-E. Not sure whether they are related?

Jan 17 23:46:58 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:46:58 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:46:58 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:46:58 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:46:59 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:46:59 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:46:59 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:46:59 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:46:59 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:46:59 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:46:59 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:46:59 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:46:59 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:46:59 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:46:59 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:46:59 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:46:59 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:46:59 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:46:59 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:46:59 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:47:02 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:47:02 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:47:02 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:47:02 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:47:02 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:47:02 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:47:02 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:47:02 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:47:08 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:47:08 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:47:08 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:47:08 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:47:09 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:47:09 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:47:09 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:47:09 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:47:09 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:47:09 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:47:09 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:47:09 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:47:10 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:47:10 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:47:10 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:47:10 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:47:12 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:47:12 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:47:12 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:47:12 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:47:17 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:47:17 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:47:17 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:47:17 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:47:18 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:47:18 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:47:18 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:47:18 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:47:20 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:47:20 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:47:20 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:47:20 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:47:20 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:47:20 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:47:20 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:47:20 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:47:23 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:47:23 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:47:23 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:47:23 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:47:24 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:47:24 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:47:24 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:47:24 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:47:24 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:47:24 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:47:24 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:47:24 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:47:26 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:47:26 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:47:26 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:47:26 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:47:29 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:47:29 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:47:29 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:47:29 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:47:29 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:47:29 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:47:29 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:47:29 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:47:29 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:47:29 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:47:29 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:47:29 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:47:32 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:47:32 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:47:32 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:47:32 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:47:32 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:47:32 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:47:32 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:47:32 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:47:34 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:47:34 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:47:34 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:47:34 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:47:36 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:47:36 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:47:36 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:47:36 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:47:37 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:47:37 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:47:37 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:47:37 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:47:42 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:47:42 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:47:42 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:47:42 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:47:45 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:47:45 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:47:45 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:47:45 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:47:45 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:47:45 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:47:45 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:47:45 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:47:47 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:47:47 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:47:47 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:47:47 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:47:48 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:47:48 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:47:48 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:47:48 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:47:48 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:47:48 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:47:48 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:47:48 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:47:48 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:47:48 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:47:48 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:47:48 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:47:48 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:47:48 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:47:48 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:47:48 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:47:53 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:47:53 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:47:53 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:47:53 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:47:53 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:47:53 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:47:53 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:47:53 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:47:53 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:47:53 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:47:53 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:47:53 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:47:58 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:47:58 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:47:58 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:47:58 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:48:02 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:48:02 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:48:02 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:48:02 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:48:02 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:48:02 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:48:02 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:48:02 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:48:02 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:48:02 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:48:02 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:48:02 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:48:07 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:48:07 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:48:07 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:48:07 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:48:09 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:48:09 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:48:09 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:48:09 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:48:12 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:48:12 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:48:12 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:48:12 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:48:12 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:48:12 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:48:12 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:48:12 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:48:14 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:48:14 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:48:14 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:48:14 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:48:15 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:48:15 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:48:15 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:48:15 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:48:16 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:48:16 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:48:16 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:48:16 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:48:17 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:48:17 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:48:17 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:48:17 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:48:20 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:48:20 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:48:20 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:48:20 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:48:23 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:48:23 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:48:23 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:48:23 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:48:25 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:48:25 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:48:25 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:48:25 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:48:26 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:48:26 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:48:26 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:48:26 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:48:26 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:48:26 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:48:26 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:48:26 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:48:28 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:48:28 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:48:28 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:48:28 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:48:28 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:48:28 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:48:28 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:48:28 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:48:28 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:48:28 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:48:28 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:48:28 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:48:29 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:48:29 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:48:29 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:48:29 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:48:29 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:48:29 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:48:29 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:48:29 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:48:30 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:48:30 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:48:30 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:48:30 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:48:31 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:48:31 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:48:31 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:48:31 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:48:31 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:48:31 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:48:31 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:48:31 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:48:31 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:48:31 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:48:31 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:48:31 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:48:37 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:48:37 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:48:37 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:48:37 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:48:37 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:48:37 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:48:37 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:48:37 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:48:39 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:48:39 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:48:39 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:48:39 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:48:41 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:48:41 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:48:41 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:48:41 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:48:42 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:48:42 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:48:42 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:48:42 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:48:43 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:48:43 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:48:43 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:48:43 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:48:43 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:48:43 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:48:43 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:48:43 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:48:45 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:48:45 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:48:45 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:48:45 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:48:48 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:48:48 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:48:48 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:48:48 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:48:50 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:48:50 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:48:50 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:48:50 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:48:51 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:48:51 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:48:51 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:48:51 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:48:51 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:48:51 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:48:51 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:48:51 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:48:53 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:48:53 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:48:53 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:48:53 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:48:53 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:48:53 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:48:53 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:48:53 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:48:55 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:48:55 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:48:55 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:48:55 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:48:58 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:48:58 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:48:58 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:48:58 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:48:58 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:48:58 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:48:58 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:48:58 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:48:58 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:48:58 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:48:58 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:48:58 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:49:00 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:49:00 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:49:00 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:49:00 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:49:00 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:49:00 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:49:00 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:49:00 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:49:01 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:49:01 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:49:01 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:49:01 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:49:02 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:49:02 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:49:02 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:49:02 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:49:07 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:49:07 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:49:07 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:49:07 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:49:07 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:49:07 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:49:07 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:49:07 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:49:09 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:49:09 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:49:09 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:49:09 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:49:09 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:49:09 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:49:09 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:49:09 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:49:09 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:49:09 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:49:09 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:49:09 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:49:10 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:49:10 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:49:10 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:49:10 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:49:12 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:49:12 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:49:12 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:49:12 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:49:12 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:49:12 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:49:12 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:49:12 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:49:16 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:49:16 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:49:16 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:49:16 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:49:17 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:49:17 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:49:17 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:49:17 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:49:19 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:49:19 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:49:19 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:49:19 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:49:26 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:49:26 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:49:26 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:49:26 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:49:28 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:49:28 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:49:28 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:49:28 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:49:32 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:49:32 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:49:32 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:49:32 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:49:33 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:49:33 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:49:33 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:49:33 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:49:33 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:49:33 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:49:33 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:49:33 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:49:33 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:49:33 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:49:33 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:49:33 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:49:34 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:49:34 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:49:34 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:49:34 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:49:37 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:49:37 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:49:37 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:49:37 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:49:37 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:49:37 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:49:37 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:49:37 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:49:38 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:49:38 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:49:38 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:49:38 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:49:39 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:49:39 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:49:39 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:49:39 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:49:41 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:49:41 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:49:41 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:49:41 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:49:41 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:49:41 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:49:41 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:49:41 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:49:42 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:49:42 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:49:42 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:49:42 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:49:43 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:49:43 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:49:43 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:49:43 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:49:43 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:49:43 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:49:43 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:49:43 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:49:48 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:49:48 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:49:48 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:49:48 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:49:50 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:49:50 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:49:50 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:49:50 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:49:52 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:49:52 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:49:52 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:49:52 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:49:52 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:49:52 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:49:52 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:49:52 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:49:52 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:49:52 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:49:52 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:49:52 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:49:55 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:49:55 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:49:55 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:49:55 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:49:56 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:49:56 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:49:56 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:49:56 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:49:57 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:49:57 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:49:57 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:49:57 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:49:57 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:49:57 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:49:57 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:49:57 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:49:58 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:49:58 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:49:58 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:49:58 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:50:00 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:50:00 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:50:00 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:50:00 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:50:01 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:50:01 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:50:01 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:50:01 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:50:02 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:50:02 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:50:02 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:50:02 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:50:03 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:50:03 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:50:03 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:50:03 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:50:04 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:50:04 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:50:04 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:50:04 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:50:06 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:50:06 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:50:06 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:50:06 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:50:06 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:50:06 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:50:06 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:50:06 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:50:08 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:50:08 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:50:08 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:50:08 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:50:08 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:50:08 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:50:08 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:50:08 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:50:15 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:50:15 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:50:15 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:50:15 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:50:16 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:50:16 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:50:16 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:50:16 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:50:16 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:50:16 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:50:16 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:50:16 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:50:17 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:50:17 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:50:17 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:50:17 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:50:17 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:50:17 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:50:17 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:50:17 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:50:19 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:50:19 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:50:19 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:50:19 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:50:24 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:50:24 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:50:24 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:50:24 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:50:25 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:50:25 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:50:25 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:50:25 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:50:26 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:50:26 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:50:26 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:50:26 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:50:32 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:50:32 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:50:32 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:50:32 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:50:33 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:50:33 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:50:33 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:50:33 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:50:35 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:50:35 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:50:35 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:50:35 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:50:35 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:50:35 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:50:35 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:50:35 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:50:36 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:50:36 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:50:36 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:50:36 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:50:36 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:50:36 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:50:36 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:50:36 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:50:40 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:50:40 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:50:40 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:50:40 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:50:44 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:50:44 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:50:44 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:50:44 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:50:46 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:50:46 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:50:46 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:50:46 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:50:48 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:50:48 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:50:48 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:50:48 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:50:50 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:50:50 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:50:50 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:50:50 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:50:50 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:50:50 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:50:50 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:50:50 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:50:52 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:50:52 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:50:52 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:50:52 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:50:54 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:50:54 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:50:54 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:50:54 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:50:55 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:50:55 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:50:55 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:50:55 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:50:56 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:50:56 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:50:56 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:50:56 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:50:56 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:50:56 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:50:56 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:50:56 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:50:58 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:50:58 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:50:58 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:50:58 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:50:58 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:50:58 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:50:58 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:50:58 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:50:59 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:50:59 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:50:59 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:50:59 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:50:59 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:50:59 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:50:59 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:50:59 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:51:00 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:51:00 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:51:00 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:51:00 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:51:00 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:51:00 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:51:00 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:51:00 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:51:01 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:51:01 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:51:01 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:51:01 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:51:04 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:51:04 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:51:04 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:51:04 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:51:05 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:51:05 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:51:05 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:51:05 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:51:07 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:51:07 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:51:07 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:51:07 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:51:08 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:51:08 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:51:08 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:51:08 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:51:09 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:51:09 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:51:09 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:51:09 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:51:13 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:51:13 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:51:13 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:51:13 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:51:19 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:51:19 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:51:19 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:51:19 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:51:19 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:51:19 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:51:19 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:51:19 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:51:21 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:51:21 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:51:21 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:51:21 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:51:23 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:51:23 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:51:23 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:51:23 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:51:25 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:51:25 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:51:25 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:51:25 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:51:26 my-pc systemd-logind[651]: The system will suspend now!
Jan 17 23:51:26 my-pc NetworkManager[649]: <info>  [1768665086.7193] manager: sleep: sleep requested (sleeping: no  enabled: yes)
Jan 17 23:51:26 my-pc NetworkManager[649]: <info>  [1768665086.7195] device (wlo1): state change: unavailable -> unmanaged (reason 'unmanaged-nm-disabled', managed-type: 'full')
Jan 17 23:51:26 my-pc rtkit-daemon[781]: Demoting known real-time threads.
Jan 17 23:51:26 my-pc NetworkManager[649]: <info>  [1768665086.7199] device (wlo1): set-hw-addr: reset MAC address to XX:XX:XX:XX:XX (unmanage)
Jan 17 23:51:26 my-pc rtkit-daemon[781]: Successfully demoted thread 3395 of process 3346.
Jan 17 23:51:26 my-pc rtkit-daemon[781]: Successfully demoted thread 3346 of process 3346.
Jan 17 23:51:26 my-pc NetworkManager[649]: <info>  [1768665086.7205] manager: NetworkManager state is now DISABLED (ASLEEP)
Jan 17 23:51:26 my-pc rtkit-daemon[781]: Successfully demoted thread 3373 of process 3347.
Jan 17 23:51:26 my-pc NetworkManager[649]: <info>  [1768665086.7207] device (enp4s0): state change: activated -> deactivating (reason 'sleeping', managed-type: 'full')
Jan 17 23:51:26 my-pc rtkit-daemon[781]: Successfully demoted thread 3347 of process 3347.
Jan 17 23:51:26 my-pc rtkit-daemon[781]: Successfully demoted thread 3367 of process 3343.
Jan 17 23:51:26 my-pc rtkit-daemon[781]: Successfully demoted thread 3343 of process 3343.
Jan 17 23:51:26 my-pc chromium.desktop[9514]: [9514:9536:0117/235126.721151:ERROR:google_apis/gcm/engine/connection_factory_impl.cc:483] ConnectionHandler failed with net error: -2
Jan 17 23:51:26 my-pc rtkit-daemon[781]: Successfully demoted thread 3064 of process 3034.
Jan 17 23:51:26 my-pc systemd[1]: Starting Network Manager Script Dispatcher Service...
Jan 17 23:51:26 my-pc rtkit-daemon[781]: Demoted 7 threads.
Jan 17 23:51:26 my-pc systemd[1]: Started Network Manager Script Dispatcher Service.
Jan 17 23:51:26 my-pc NetworkManager[649]: <info>  [1768665086.7557] device (enp4s0): state change: deactivating -> disconnected (reason 'sleeping', managed-type: 'full')
Jan 17 23:51:26 my-pc NetworkManager[649]: <info>  [1768665086.7561] dhcp4 (enp4s0): canceled DHCP transaction
Jan 17 23:51:26 my-pc NetworkManager[649]: <info>  [1768665086.7561] dhcp4 (enp4s0): activation: beginning transaction (timeout in 45 seconds)
Jan 17 23:51:26 my-pc NetworkManager[649]: <info>  [1768665086.7561] dhcp4 (enp4s0): state changed no lease
Jan 17 23:51:26 my-pc NetworkManager[649]: <info>  [1768665086.8080] device (enp4s0): state change: disconnected -> unmanaged (reason 'unmanaged-nm-disabled', managed-type: 'full')
Jan 17 23:51:26 my-pc kernel: r8169 0000:04:00.0 enp4s0: Link is Down
Jan 17 23:51:26 my-pc gsd-sharing[3187]: Failed to stop rygel.service: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit rygel.service not loaded.
Jan 17 23:51:26 my-pc systemd[1]: Reached target Sleep.
Jan 17 23:51:26 my-pc systemd[1]: Starting NVIDIA system suspend actions...
Jan 17 23:51:26 my-pc suspend[10885]: nvidia-suspend.service
Jan 17 23:51:26 my-pc logger[10885]: <13>Jan 17 23:51:26 suspend: nvidia-suspend.service
Jan 17 23:51:26 my-pc kernel: rfkill: input handler enabled
Jan 17 23:51:26 my-pc bluetoothd[650]: Endpoint unregistered: sender=:1.122 path=/MediaEndpoint/A2DPSource/ldac
Jan 17 23:51:26 my-pc bluetoothd[650]: Endpoint unregistered: sender=:1.122 path=/MediaEndpoint/A2DPSink/aptx_hd
Jan 17 23:51:26 my-pc gsd-media-keys[3146]: Unable to get default sink
Jan 17 23:51:26 my-pc bluetoothd[650]: Endpoint unregistered: sender=:1.122 path=/MediaEndpoint/A2DPSource/aptx_hd
Jan 17 23:51:26 my-pc bluetoothd[650]: Endpoint unregistered: sender=:1.122 path=/MediaEndpoint/A2DPSink/aptx
Jan 17 23:51:26 my-pc bluetoothd[650]: Endpoint unregistered: sender=:1.122 path=/MediaEndpoint/A2DPSource/aptx
Jan 17 23:51:26 my-pc bluetoothd[650]: Endpoint unregistered: sender=:1.122 path=/MediaEndpoint/A2DPSink/aac
Jan 17 23:51:26 my-pc bluetoothd[650]: Endpoint unregistered: sender=:1.122 path=/MediaEndpoint/A2DPSource/aac
Jan 17 23:51:26 my-pc bluetoothd[650]: Endpoint unregistered: sender=:1.122 path=/MediaEndpoint/A2DPSink/opus_g
Jan 17 23:51:26 my-pc bluetoothd[650]: Endpoint unregistered: sender=:1.122 path=/MediaEndpoint/A2DPSource/opus_g
Jan 17 23:51:26 my-pc bluetoothd[650]: Endpoint unregistered: sender=:1.122 path=/MediaEndpoint/A2DPSink/sbc
Jan 17 23:51:26 my-pc bluetoothd[650]: Endpoint unregistered: sender=:1.122 path=/MediaEndpoint/A2DPSource/sbc
Jan 17 23:51:26 my-pc bluetoothd[650]: Endpoint unregistered: sender=:1.122 path=/MediaEndpoint/A2DPSource/aptx_ll_1
Jan 17 23:51:26 my-pc bluetoothd[650]: Endpoint unregistered: sender=:1.122 path=/MediaEndpoint/A2DPSource/aptx_ll_0
Jan 17 23:51:26 my-pc bluetoothd[650]: Endpoint unregistered: sender=:1.122 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_1
Jan 17 23:51:26 my-pc bluetoothd[650]: Endpoint unregistered: sender=:1.122 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_0
Jan 17 23:51:26 my-pc bluetoothd[650]: Endpoint unregistered: sender=:1.122 path=/MediaEndpoint/A2DPSource/faststream
Jan 17 23:51:26 my-pc bluetoothd[650]: Endpoint unregistered: sender=:1.122 path=/MediaEndpoint/A2DPSource/faststream_duplex
Jan 17 23:51:26 my-pc bluetoothd[650]: Endpoint unregistered: sender=:1.122 path=/MediaEndpoint/A2DPSink/opus_05
Jan 17 23:51:26 my-pc bluetoothd[650]: Endpoint unregistered: sender=:1.122 path=/MediaEndpoint/A2DPSource/opus_05
Jan 17 23:51:26 my-pc bluetoothd[650]: Endpoint unregistered: sender=:1.122 path=/MediaEndpoint/A2DPSink/opus_05_duplex
Jan 17 23:51:26 my-pc bluetoothd[650]: Endpoint unregistered: sender=:1.122 path=/MediaEndpoint/A2DPSource/opus_05_duplex
Jan 17 23:51:27 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:51:27 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:51:27 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:51:27 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:51:27 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:51:27 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:51:27 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:51:27 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:51:28 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:51:28 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:51:28 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:51:28 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:51:28 my-pc kernel: pcieport 0000:00:1a.0: AER: Correctable error message received from 0000:03:00.0
Jan 17 23:51:28 my-pc kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Jan 17 23:51:28 my-pc kernel: nvme 0000:03:00.0:   device [1e49:0071] error status/mask=00000001/0000e000
Jan 17 23:51:28 my-pc kernel: nvme 0000:03:00.0:    [ 0] RxErr                  (First)
Jan 17 23:51:28 my-pc systemd[1]: nvidia-suspend.service: Deactivated successfully.
Jan 17 23:51:28 my-pc systemd[1]: Finished NVIDIA system suspend actions.
Jan 17 23:51:28 my-pc systemd[1]: nvidia-suspend.service: Consumed 1.683s CPU time, 1.4G memory peak.
Jan 17 23:51:28 my-pc systemd[1]: Starting System Suspend...
Jan 17 23:51:28 my-pc systemd-sleep[10915]: User sessions remain unfrozen on explicit request ($SYSTEMD_SLEEP_FREEZE_USER_SESSIONS=0).
Jan 17 23:51:28 my-pc systemd-sleep[10915]: This is not recommended, and might result in unexpected behavior, particularly
Jan 17 23:51:28 my-pc systemd-sleep[10915]: in suspend-then-hibernate operations or setups with encrypted home directories.
Jan 17 23:51:28 my-pc systemd-sleep[10915]: Performing sleep operation 'suspend'...
Jan 17 23:51:28 my-pc kernel: PM: suspend entry (deep)
Jan 17 23:51:28 my-pc kernel: Filesystems sync: 0.305 seconds
Jan 17 23:51:34 my-pc kernel: Freezing user space processes
Jan 17 23:51:34 my-pc kernel: Freezing user space processes completed (elapsed 0.001 seconds)
Jan 17 23:51:34 my-pc kernel: OOM killer disabled.
Jan 17 23:51:34 my-pc kernel: Freezing remaining freezable tasks
Jan 17 23:51:34 my-pc kernel: Freezing remaining freezable tasks completed (elapsed 0.001 seconds)
Jan 17 23:51:34 my-pc kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Jan 17 23:51:34 my-pc kernel: serial 00:03: disabled
Jan 17 23:51:34 my-pc kernel: ACPI: PM: Preparing to enter system sleep state S3
Jan 17 23:51:34 my-pc kernel: ACPI: PM: Saving platform NVS memory
Jan 17 23:51:34 my-pc kernel: Disabling non-boot CPUs ...
Jan 17 23:51:34 my-pc kernel: smpboot: CPU 19 is now offline
Jan 17 23:51:34 my-pc kernel: smpboot: CPU 18 is now offline
Jan 17 23:51:34 my-pc kernel: smpboot: CPU 17 is now offline
Jan 17 23:51:34 my-pc kernel: smpboot: CPU 16 is now offline
Jan 17 23:51:34 my-pc kernel: smpboot: CPU 15 is now offline
Jan 17 23:51:34 my-pc kernel: smpboot: CPU 14 is now offline
Jan 17 23:51:34 my-pc kernel: smpboot: CPU 13 is now offline
Jan 17 23:51:34 my-pc kernel: smpboot: CPU 12 is now offline
Jan 17 23:51:34 my-pc kernel: smpboot: CPU 11 is now offline
Jan 17 23:51:34 my-pc kernel: smpboot: CPU 10 is now offline
Jan 17 23:51:34 my-pc kernel: smpboot: CPU 9 is now offline
Jan 17 23:51:34 my-pc kernel: smpboot: CPU 8 is now offline
Jan 17 23:51:34 my-pc kernel: smpboot: CPU 7 is now offline
Jan 17 23:51:34 my-pc kernel: smpboot: CPU 6 is now offline
Jan 17 23:51:34 my-pc kernel: smpboot: CPU 5 is now offline
Jan 17 23:51:34 my-pc kernel: smpboot: CPU 4 is now offline
Jan 17 23:51:34 my-pc kernel: smpboot: CPU 3 is now offline
Jan 17 23:51:34 my-pc kernel: smpboot: CPU 2 is now offline
Jan 17 23:51:34 my-pc kernel: smpboot: CPU 1 is now offline
Jan 17 23:51:34 my-pc kernel: ACPI: PM: Low-level resume complete
Jan 17 23:51:34 my-pc kernel: ACPI: PM: Restoring platform NVS memory
Jan 17 23:51:34 my-pc kernel: Enabling non-boot CPUs ...
Jan 17 23:51:34 my-pc kernel: smpboot: Booting Node 0 Processor 1 APIC 0x1
Jan 17 23:51:34 my-pc kernel: CPU1 is up
Jan 17 23:51:34 my-pc kernel: smpboot: Booting Node 0 Processor 2 APIC 0x8
Jan 17 23:51:34 my-pc kernel: CPU2 is up
Jan 17 23:51:34 my-pc kernel: smpboot: Booting Node 0 Processor 3 APIC 0x9
Jan 17 23:51:34 my-pc kernel: CPU3 is up
Jan 17 23:51:34 my-pc kernel: smpboot: Booting Node 0 Processor 4 APIC 0x10
Jan 17 23:51:34 my-pc kernel: CPU4 is up
Jan 17 23:51:34 my-pc kernel: smpboot: Booting Node 0 Processor 5 APIC 0x11
Jan 17 23:51:34 my-pc kernel: CPU5 is up
Jan 17 23:51:34 my-pc kernel: smpboot: Booting Node 0 Processor 6 APIC 0x18
Jan 17 23:51:34 my-pc kernel: CPU6 is up
Jan 17 23:51:34 my-pc kernel: smpboot: Booting Node 0 Processor 7 APIC 0x19
Jan 17 23:51:34 my-pc kernel: CPU7 is up
Jan 17 23:51:34 my-pc kernel: smpboot: Booting Node 0 Processor 8 APIC 0x20
Jan 17 23:51:34 my-pc kernel: CPU8 is up
Jan 17 23:51:34 my-pc kernel: smpboot: Booting Node 0 Processor 9 APIC 0x21
Jan 17 23:51:34 my-pc kernel: CPU9 is up
Jan 17 23:51:34 my-pc kernel: smpboot: Booting Node 0 Processor 10 APIC 0x28
Jan 17 23:51:34 my-pc kernel: CPU10 is up
Jan 17 23:51:34 my-pc kernel: smpboot: Booting Node 0 Processor 11 APIC 0x29
Jan 17 23:51:34 my-pc kernel: CPU11 is up
Jan 17 23:51:34 my-pc kernel: smpboot: Booting Node 0 Processor 12 APIC 0x30
Jan 17 23:51:34 my-pc kernel: core: cpu_atom PMU driver: 
Jan 17 23:51:34 my-pc kernel: ... version:                   5
Jan 17 23:51:34 my-pc kernel: ... bit width:                 48
Jan 17 23:51:34 my-pc kernel: ... generic counters:          6
Jan 17 23:51:34 my-pc kernel: ... generic bitmap:            000000000000003f
Jan 17 23:51:34 my-pc kernel: ... fixed-purpose counters:    3
Jan 17 23:51:34 my-pc kernel: ... fixed-purpose bitmap:      0000000000000007
Jan 17 23:51:34 my-pc kernel: ... value mask:                0000ffffffffffff
Jan 17 23:51:34 my-pc kernel: ... max period:                00007fffffffffff
Jan 17 23:51:34 my-pc kernel: ... global_ctrl mask:          000000070000003f
Jan 17 23:51:34 my-pc kernel: CPU12 is up
Jan 17 23:51:34 my-pc kernel: smpboot: Booting Node 0 Processor 13 APIC 0x32
Jan 17 23:51:34 my-pc kernel: CPU13 is up
Jan 17 23:51:34 my-pc kernel: smpboot: Booting Node 0 Processor 14 APIC 0x34
Jan 17 23:51:34 my-pc kernel: CPU14 is up
Jan 17 23:51:34 my-pc kernel: smpboot: Booting Node 0 Processor 15 APIC 0x36
Jan 17 23:51:34 my-pc kernel: CPU15 is up
Jan 17 23:51:34 my-pc kernel: smpboot: Booting Node 0 Processor 16 APIC 0x38
Jan 17 23:51:34 my-pc kernel: CPU16 is up
Jan 17 23:51:34 my-pc kernel: smpboot: Booting Node 0 Processor 17 APIC 0x3a
Jan 17 23:51:34 my-pc kernel: CPU17 is up
Jan 17 23:51:34 my-pc kernel: smpboot: Booting Node 0 Processor 18 APIC 0x3c
Jan 17 23:51:34 my-pc kernel: CPU18 is up
Jan 17 23:51:34 my-pc kernel: smpboot: Booting Node 0 Processor 19 APIC 0x3e
Jan 17 23:51:34 my-pc kernel: CPU19 is up
Jan 17 23:51:34 my-pc kernel: ACPI: PM: Waking up from system sleep state S3
Jan 17 23:51:34 my-pc kernel: serial 00:03: activated
Jan 17 23:51:34 my-pc kernel: nvme nvme0: D3 entry latency set to 10 seconds
Jan 17 23:51:34 my-pc kernel: nvme nvme0: 16/0/0 default/read/poll queues
Jan 17 23:51:34 my-pc kernel: nvme nvme1: 8/0/0 default/read/poll queues
Jan 17 23:51:34 my-pc kernel: OOM killer enabled.
Jan 17 23:51:34 my-pc kernel: Restarting tasks: Starting
Jan 17 23:51:34 my-pc kernel: Restarting tasks: Done
Jan 17 23:51:34 my-pc kernel: efivarfs: resyncing variable state
Jan 17 23:51:34 my-pc kernel: efivarfs: finished resyncing variable state
Jan 17 23:51:34 my-pc kernel: random: crng reseeded on system resumption
Jan 17 23:51:34 my-pc systemd-sleep[10915]: System returned from sleep operation 'suspend'.
Jan 17 23:51:34 my-pc bluetoothd[650]: Controller resume with wake event 0x0
Jan 17 23:51:34 my-pc kernel: PM: suspend exit
Jan 17 23:51:34 my-pc kernel: ata8: SATA link down (SStatus 4 SControl 300)
Jan 17 23:51:34 my-pc kernel: ata6: SATA link down (SStatus 4 SControl 300)
Jan 17 23:51:34 my-pc kernel: ata5: SATA link down (SStatus 4 SControl 300)
Jan 17 23:51:34 my-pc kernel: ata7: SATA link down (SStatus 4 SControl 300)
Jan 17 23:51:35 my-pc gnome-shell[3034]: g_settings_get_value: assertion 'G_IS_SETTINGS (settings)' failed
Jan 17 23:51:35 my-pc gnome-shell[3034]: g_variant_get_type: assertion 'value != NULL' failed
Jan 17 23:51:35 my-pc gnome-shell[3034]: g_variant_type_is_subtype_of: assertion 'g_variant_type_check (type)' failed
Jan 17 23:51:35 my-pc gnome-shell[3034]: g_variant_get_uint32: assertion 'g_variant_is_of_type (value, G_VARIANT_TYPE_UINT32)' failed
Jan 17 23:51:35 my-pc gnome-shell[3034]: g_variant_unref: assertion 'value != NULL' failed
Jan 17 23:51:35 my-pc gnome-shell[3034]: g_settings_get_value: assertion 'G_IS_SETTINGS (settings)' failed
Jan 17 23:51:35 my-pc gnome-shell[3034]: g_variant_get_type: assertion 'value != NULL' failed
Jan 17 23:51:35 my-pc gnome-shell[3034]: g_variant_type_is_subtype_of: assertion 'g_variant_type_check (type)' failed
Jan 17 23:51:35 my-pc gnome-shell[3034]: g_variant_get_uint32: assertion 'g_variant_is_of_type (value, G_VARIANT_TYPE_UINT32)' failed
Jan 17 23:51:35 my-pc gnome-shell[3034]: g_variant_unref: assertion 'value != NULL' failed
Jan 17 23:51:35 my-pc gnome-shell[3034]: g_settings_get_value: assertion 'G_IS_SETTINGS (settings)' failed
Jan 17 23:51:35 my-pc gnome-shell[3034]: g_variant_get_type: assertion 'value != NULL' failed
Jan 17 23:51:35 my-pc gnome-shell[3034]: g_variant_type_is_subtype_of: assertion 'g_variant_type_check (type)' failed
Jan 17 23:51:35 my-pc gnome-shell[3034]: g_variant_get_boolean: assertion 'g_variant_is_of_type (value, G_VARIANT_TYPE_BOOLEAN)' failed
Jan 17 23:51:35 my-pc gnome-shell[3034]: g_variant_unref: assertion 'value != NULL' failed
Jan 17 23:51:35 my-pc gdm[691]: GLib: Source ID 87 was not found when attempting to remove it
Jan 17 23:51:35 my-pc systemd[1]: systemd-suspend.service: Deactivated successfully.
Jan 17 23:51:35 my-pc systemd[1]: Finished System Suspend.
Jan 17 23:51:35 my-pc systemd[1]: systemd-suspend.service: Consumed 1.348s CPU time, 3.7M memory peak.
Jan 17 23:51:35 my-pc kernel: rfkill: input handler disabled
Jan 17 23:51:35 my-pc systemd[1]: Stopped target Sleep.
Jan 17 23:51:35 my-pc systemd[1]: Reached target Suspend.
Jan 17 23:51:35 my-pc systemd-logind[651]: Operation 'suspend' finished.
Jan 17 23:51:35 my-pc NetworkManager[649]: <info>  [1768665095.4432] manager: sleep: wake requested (sleeping: yes  enabled: yes)
Jan 17 23:51:35 my-pc NetworkManager[649]: <info>  [1768665095.4434] device (enp4s0): state change: unmanaged -> unavailable (reason 'managed', managed-type: 'external')
Jan 17 23:51:35 my-pc rtkit-daemon[781]: Resuming known real-time threads.
Jan 17 23:51:35 my-pc rtkit-daemon[781]: Successfully made thread 3395 of process 3346 owned by '1000' RT at priority 20.
Jan 17 23:51:35 my-pc rtkit-daemon[781]: Successfully made thread 3346 of process 3346 owned by '1000' high priority at nice level -11.
Jan 17 23:51:35 my-pc rtkit-daemon[781]: Successfully made thread 3373 of process 3347 owned by '1000' RT at priority 20.
Jan 17 23:51:35 my-pc rtkit-daemon[781]: Successfully made thread 3347 of process 3347 owned by '1000' high priority at nice level -11.
Jan 17 23:51:35 my-pc rtkit-daemon[781]: Successfully made thread 3367 of process 3343 owned by '1000' RT at priority 20.
Jan 17 23:51:35 my-pc rtkit-daemon[781]: Successfully made thread 3343 of process 3343 owned by '1000' high priority at nice level -11.
Jan 17 23:51:35 my-pc rtkit-daemon[781]: Successfully made thread 3064 of process 3034 owned by '1000' high priority at nice level -15.
Jan 17 23:51:35 my-pc systemd[1]: Starting NVIDIA system resume actions...
Jan 17 23:51:35 my-pc rtkit-daemon[781]: Resumed scheduling 7 threads.
Jan 17 23:51:35 my-pc systemd[1]: Stopped target Suspend.
Jan 17 23:51:35 my-pc suspend[10995]: nvidia-resume.service
Jan 17 23:51:35 my-pc logger[10995]: <13>Jan 17 23:51:35 suspend: nvidia-resume.service
Jan 17 23:51:35 my-pc systemd[1]: nvidia-resume.service: Deactivated successfully.
Jan 17 23:51:35 my-pc systemd[1]: Finished NVIDIA system resume actions.
Jan 17 23:51:35 my-pc kernel: Realtek Internal NBASE-T PHY r8169-0-400:00: attached PHY driver (mii_bus:phy_addr=r8169-0-400:00, irq=MAC)
Jan 17 23:51:35 my-pc wireplumber[3346]: spa.bluez5.midi: org.bluez.GattManager1.RegisterApplication() failed: GDBus.Error:org.bluez.Error.AlreadyExists: Already Exists
Jan 17 23:51:35 my-pc gsd-media-keys[3146]: Unable to get default sink
Jan 17 23:51:35 my-pc bluetoothd[650]: Endpoint registered: sender=:1.129 path=/MediaEndpoint/A2DPSource/ldac
Jan 17 23:51:35 my-pc bluetoothd[650]: Endpoint registered: sender=:1.129 path=/MediaEndpoint/A2DPSink/aptx_hd
Jan 17 23:51:35 my-pc bluetoothd[650]: Endpoint registered: sender=:1.129 path=/MediaEndpoint/A2DPSource/aptx_hd
Jan 17 23:51:35 my-pc bluetoothd[650]: Endpoint registered: sender=:1.129 path=/MediaEndpoint/A2DPSink/aptx
Jan 17 23:51:35 my-pc bluetoothd[650]: Endpoint registered: sender=:1.129 path=/MediaEndpoint/A2DPSource/aptx
Jan 17 23:51:35 my-pc bluetoothd[650]: Endpoint registered: sender=:1.129 path=/MediaEndpoint/A2DPSink/aac
Jan 17 23:51:35 my-pc bluetoothd[650]: Endpoint registered: sender=:1.129 path=/MediaEndpoint/A2DPSource/aac
Jan 17 23:51:35 my-pc bluetoothd[650]: Endpoint registered: sender=:1.129 path=/MediaEndpoint/A2DPSink/opus_g
Jan 17 23:51:35 my-pc bluetoothd[650]: Endpoint registered: sender=:1.129 path=/MediaEndpoint/A2DPSource/opus_g
Jan 17 23:51:35 my-pc bluetoothd[650]: Endpoint registered: sender=:1.129 path=/MediaEndpoint/A2DPSink/sbc
Jan 17 23:51:35 my-pc bluetoothd[650]: Endpoint registered: sender=:1.129 path=/MediaEndpoint/A2DPSource/sbc
Jan 17 23:51:35 my-pc bluetoothd[650]: Endpoint registered: sender=:1.129 path=/MediaEndpoint/A2DPSource/aptx_ll_1
Jan 17 23:51:35 my-pc bluetoothd[650]: Endpoint registered: sender=:1.129 path=/MediaEndpoint/A2DPSource/aptx_ll_0
Jan 17 23:51:35 my-pc bluetoothd[650]: Endpoint registered: sender=:1.129 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_1
Jan 17 23:51:35 my-pc bluetoothd[650]: Endpoint registered: sender=:1.129 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_0
Jan 17 23:51:35 my-pc bluetoothd[650]: Endpoint registered: sender=:1.129 path=/MediaEndpoint/A2DPSource/faststream
Jan 17 23:51:35 my-pc bluetoothd[650]: Endpoint registered: sender=:1.129 path=/MediaEndpoint/A2DPSource/faststream_duplex
Jan 17 23:51:35 my-pc bluetoothd[650]: Endpoint registered: sender=:1.129 path=/MediaEndpoint/A2DPSink/opus_05
Jan 17 23:51:35 my-pc bluetoothd[650]: Endpoint registered: sender=:1.129 path=/MediaEndpoint/A2DPSource/opus_05
Jan 17 23:51:35 my-pc bluetoothd[650]: Endpoint registered: sender=:1.129 path=/MediaEndpoint/A2DPSink/opus_05_duplex
Jan 17 23:51:35 my-pc bluetoothd[650]: Endpoint registered: sender=:1.129 path=/MediaEndpoint/A2DPSource/opus_05_duplex
Jan 17 23:51:35 my-pc gsd-media-keys[3146]: Unable to get default source
Jan 17 23:51:35 my-pc NetworkManager[649]: <info>  [1768665095.6253] device (wlo1): state change: unmanaged -> unavailable (reason 'managed', managed-type: 'external')
Jan 17 23:51:35 my-pc NetworkManager[649]: <info>  [1768665095.6255] device (wlo1): set-hw-addr: set MAC address to XX:XX:XX:XX:XX:XX (scanning)
Jan 17 23:51:35 my-pc NetworkManager[649]: <info>  [1768665095.6255] manager: NetworkManager state is now DISCONNECTED
Jan 17 23:51:35 my-pc kernel: r8169 0000:04:00.0 enp4s0: Link is Down
Jan 17 23:51:35 my-pc gnome-shell[11025]: The XKEYBOARD keymap compiler (xkbcomp) reports:
Jan 17 23:51:35 my-pc gnome-shell[11025]: > Warning:          Unsupported maximum keycode 708, clipping.
Jan 17 23:51:35 my-pc gnome-shell[11025]: >                   X11 cannot support keycodes above 255.
Jan 17 23:51:35 my-pc gnome-shell[11025]: > Warning:          Virtual modifier Hyper multiply defined
Jan 17 23:51:35 my-pc gnome-shell[11025]: >                   Using 0, ignoring 0
Jan 17 23:51:35 my-pc gnome-shell[11025]: > Warning:          Virtual modifier ScrollLock multiply defined
Jan 17 23:51:35 my-pc gnome-shell[11025]: >                   Using 0, ignoring 0
Jan 17 23:51:35 my-pc gnome-shell[11025]: Errors from xkbcomp are not fatal to the X server
Jan 17 23:51:39 my-pc kernel: r8169 0000:04:00.0 enp4s0: Link is Up - 2.5Gbps/Full - flow control rx/tx
Jan 17 23:51:39 my-pc NetworkManager[649]: <info>  [1768665099.0948] device (enp4s0): carrier: link connected
Jan 17 23:51:39 my-pc NetworkManager[649]: <info>  [1768665099.0950] device (enp4s0): state change: unavailable -> disconnected (reason 'carrier-changed', managed-type: 'full')
Jan 17 23:51:39 my-pc NetworkManager[649]: <info>  [1768665099.0956] policy: auto-activating connection 'Wired connection 1' (68d94244-8ad8-395e-ba31-e62dfe2c1ebf)
Jan 17 23:51:39 my-pc NetworkManager[649]: <info>  [1768665099.0961] device (enp4s0): Activation: starting connection 'Wired connection 1' (68d94244-8ad8-395e-ba31-e62dfe2c1ebf)
Jan 17 23:51:39 my-pc NetworkManager[649]: <info>  [1768665099.0962] device (enp4s0): state change: disconnected -> prepare (reason 'none', managed-type: 'full')
Jan 17 23:51:39 my-pc NetworkManager[649]: <info>  [1768665099.0964] manager: NetworkManager state is now CONNECTING
Jan 17 23:51:39 my-pc NetworkManager[649]: <info>  [1768665099.0965] device (enp4s0): state change: prepare -> config (reason 'none', managed-type: 'full')
Jan 17 23:51:39 my-pc NetworkManager[649]: <info>  [1768665099.0969] device (enp4s0): state change: config -> ip-config (reason 'none', managed-type: 'full')
Jan 17 23:51:39 my-pc NetworkManager[649]: <info>  [1768665099.0972] dhcp4 (enp4s0): activation: beginning transaction (timeout in 45 seconds)
Jan 17 23:51:41 my-pc NetworkManager[649]: <info>  [1768665101.0998] dhcp4 (enp4s0): state changed new lease, address=192.168.50.2, acd pending
Jan 17 23:51:41 my-pc NetworkManager[649]: <info>  [1768665101.2549] dhcp4 (enp4s0): state changed new lease, address=192.168.50.2
Jan 17 23:51:41 my-pc NetworkManager[649]: <info>  [1768665101.2561] policy: set 'Wired connection 1' (enp4s0) as default for IPv4 routing and DNS
Jan 17 23:51:41 my-pc gsd-sharing[3187]: Failed to stop rygel.service: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit rygel.service not loaded.
Jan 17 23:51:41 my-pc NetworkManager[649]: <info>  [1768665101.2881] device (enp4s0): state change: ip-config -> ip-check (reason 'none', managed-type: 'full')
Jan 17 23:51:41 my-pc NetworkManager[649]: <info>  [1768665101.2900] device (enp4s0): state change: ip-check -> secondaries (reason 'none', managed-type: 'full')
Jan 17 23:51:41 my-pc NetworkManager[649]: <info>  [1768665101.2902] device (enp4s0): state change: secondaries -> activated (reason 'none', managed-type: 'full')
Jan 17 23:51:41 my-pc NetworkManager[649]: <info>  [1768665101.2905] manager: NetworkManager state is now CONNECTED_SITE
Jan 17 23:51:41 my-pc NetworkManager[649]: <info>  [1768665101.2907] device (enp4s0): Activation: successful, device activated.
Jan 17 23:51:41 my-pc systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
Jan 17 23:51:41 my-pc NetworkManager[649]: <info>  [1768665101.6760] manager: NetworkManager state is now CONNECTED_GLOBAL
Jan 17 23:51:41 my-pc systemd[1]: Starting Network Manager Script Dispatcher Service...
Jan 17 23:51:41 my-pc systemd[1]: Started Network Manager Script Dispatcher Service.
Jan 17 23:51:49 my-pc gdm-password][11034]: gkr-pam: unlocked login keyring
Jan 17 23:51:50 my-pc systemd[2894]: Started dbus-:1.2-org.gnome.Shell.CalendarServer@4.service.
Jan 17 23:51:50 my-pc gnome-shell-calendar-server[11045]: /usr/lib/gnome-shell-calendar-server: error while loading shared libraries: libecal-2.0.so.3: cannot open shared object file: No such file or directory
Jan 17 23:51:50 my-pc systemd[2894]: dbus-:1.2-org.gnome.Shell.CalendarServer@4.service: Main process exited, code=exited, status=127/n/a
Jan 17 23:51:50 my-pc systemd[2894]: dbus-:1.2-org.gnome.Shell.CalendarServer@4.service: Failed with result 'exit-code'.
Jan 17 23:51:50 my-pc gnome-shell[3034]: Called enable_unredirect_for_display while unredirection is enabled.
Jan 17 23:51:50 my-pc NetworkManager[649]: <info>  [1768665110.0859] agent-manager: agent[b32dd999377b8082,:1.62/org.gnome.Shell.NetworkAgent/1000]: agent registered
Jan 17 23:51:50 my-pc systemd[2894]: Started dbus-:1.2-org.gnome.Shell.CalendarServer@5.service.
Jan 17 23:51:50 my-pc gnome-shell-calendar-server[11053]: /usr/lib/gnome-shell-calendar-server: error while loading shared libraries: libecal-2.0.so.3: cannot open shared object file: No such file or directory
Jan 17 23:51:50 my-pc systemd[2894]: dbus-:1.2-org.gnome.Shell.CalendarServer@5.service: Main process exited, code=exited, status=127/n/a
Jan 17 23:51:50 my-pc systemd[2894]: dbus-:1.2-org.gnome.Shell.CalendarServer@5.service: Failed with result 'exit-code'.
Jan 17 23:51:50 my-pc gnome-shell[3034]: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not activate remote peer 'org.gnome.Shell.CalendarServer': unit failed
                                                 
                                                 Stack trace:
                                                   asyncCallback@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:115:23
                                                   @resource:///org/gnome/shell/ui/init.js:21:20
                                                   
Jan 17 23:51:50 my-pc gnome-shell[3034]: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not activate remote peer 'org.gnome.Shell.CalendarServer': unit failed
                                                 
                                                 Stack trace:
                                                   asyncCallback@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:115:23
                                                   @resource:///org/gnome/shell/ui/init.js:21:20
                                                   
Jan 17 23:51:51 my-pc systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
Jan 17 23:51:56 my-pc sudo[11057]:     user : TTY=pts/1 ; PWD=/home/user ; USER=root ; COMMAND=/usr/bin/journalctl '--since=-5 minutes'
Jan 17 23:51:56 my-pc sudo[11057]: pam_unix(sudo:session): session opened for user root(uid=0) by user(uid=1000)

Last edited by seventeen (2026-01-17 16:21:53)

seventeen · 2026-01-17 16:59:29

seventeen wrote:

But this time in the log i see errors with PCI-E. Not sure whether they are related?

Update, i reboot my pc and tried again, now the PCI-E error is gone. but issue still exists for both command and super + L

seth · 2026-01-17 20:04:37

There's some noise on the PCI bus, related to the nvme, see https://wiki.archlinux.org/title/Solid_ … leshooting
Next to APST it also might be general ASPM, "pcie_aspm=off nvme_core.default_ps_max_latency_us=0 iommu=soft", https://wiki.archlinux.org/title/Kernel_parameters

For the original problem resp. if the above has no impact

cat /proc/acpi/wakeup

, there's probably some device that needs to be left alone for a while to power down before the system powers down.
Are you using any bluetooth IO (keyboard, mouse, headphones)?

seventeen · 2026-01-21 16:55:35

I don't have any bluetooth device connected, but my mouse / keyboard are usb wireless connected.

I tried disable usb wakeup, and it did fix the problem. But still it does not explain why it only get triggered when manual lock screen is applied. And I do need usb wake up.

Any suggestions how I can track this issue?

Device	S-state	  Status   Sysfs node
PEG1	  S4	*enabled   pci:0000:00:01.0
PEGP	  S4	*disabled  pci:0000:01:00.0
PEG2	  S4	*disabled
PEGP	  S4	*disabled
PEG0	  S4	*enabled   pci:0000:00:06.0
PEGP	  S4	*disabled  pci:0000:02:00.0
SIO1	  S3	*disabled  pnp:00:00
RP09	  S4	*disabled
PXSX	  S4	*disabled
RP10	  S4	*disabled
PXSX	  S4	*disabled
RP11	  S4	*disabled
PXSX	  S4	*disabled
RP12	  S4	*disabled
PXSX	  S4	*disabled
RP13	  S4	*disabled
PXSX	  S4	*disabled
RP14	  S4	*disabled
PXSX	  S4	*disabled
RP15	  S4	*disabled
PXSX	  S4	*disabled
RP16	  S4	*disabled
PXSX	  S4	*disabled
RP01	  S4	*disabled
PXSX	  S4	*disabled
RP02	  S4	*disabled
PXSX	  S4	*disabled
RP03	  S4	*disabled
PXSX	  S4	*disabled
RP04	  S4	*disabled
PXSX	  S4	*disabled
RP05	  S4	*disabled
PXSX	  S4	*disabled
RP06	  S4	*disabled
PXSX	  S4	*disabled
RP07	  S4	*enabled   pci:0000:00:1c.0
PXSX	  S4	*disabled  pci:0000:04:00.0
RP08	  S4	*disabled
PXSX	  S4	*disabled
RP17	  S4	*disabled
PXSX	  S4	*disabled
RP18	  S4	*disabled
PXSX	  S4	*disabled
RP19	  S4	*disabled
PXSX	  S4	*disabled
RP20	  S4	*disabled
PXSX	  S4	*disabled
RP21	  S4	*disabled
PXSX	  S4	*disabled
RP22	  S4	*disabled
PXSX	  S4	*disabled
RP23	  S4	*disabled
PXSX	  S4	*disabled
RP24	  S4	*disabled
PXSX	  S4	*disabled
RP25	  S4	*enabled   pci:0000:00:1a.0
PXSX	  S4	*disabled  pci:0000:03:00.0
RP26	  S4	*disabled
PXSX	  S4	*disabled
RP27	  S4	*disabled
PXSX	  S4	*disabled
RP28	  S4	*disabled
PXSX	  S4	*disabled
XHCI	  S4	*enabled   pci:0000:00:14.0
XDCI	  S4	*disabled
HDAS	  S4	*disabled  pci:0000:00:1f.3
CNVW	  S4	*disabled  pci:0000:00:14.3
AWAC	  S4	*enabled   platform:ACPI000E:00

Last edited by seventeen (2026-01-21 16:56:13)

seth · 2026-01-22 15:26:53

Any suggestions how I can track this issue?

re-enable the usb wakeup and replace the USB dongle (logitech unifying receiver?) w/ a wired mouse/keyboard.
Still a problem?

=> https://wiki.archlinux.org/title/Logite … from_sleep

Arch Linux

#1 2026-01-16 18:35:50

Immediate wake from suspend ONLY when manually locked (Super+L)

#2 2026-01-16 20:11:46

Re: Immediate wake from suspend ONLY when manually locked (Super+L)

#3 2026-01-17 03:43:36

Re: Immediate wake from suspend ONLY when manually locked (Super+L)

#4 2026-01-17 09:48:24

Re: Immediate wake from suspend ONLY when manually locked (Super+L)

#5 2026-01-17 16:20:22

Re: Immediate wake from suspend ONLY when manually locked (Super+L)

#6 2026-01-17 16:59:29

Re: Immediate wake from suspend ONLY when manually locked (Super+L)

#7 2026-01-17 20:04:37

Re: Immediate wake from suspend ONLY when manually locked (Super+L)

#8 2026-01-21 16:55:35

Re: Immediate wake from suspend ONLY when manually locked (Super+L)

#9 2026-01-22 15:26:53

Re: Immediate wake from suspend ONLY when manually locked (Super+L)

Board footer