You are not logged in.

#1 2023-03-07 00:58:49

mearkat7
Member
Registered: 2023-03-07
Posts: 22

Random GPU crashes amdgpu across 2 different GPUs

Kernel: 6.2.2
xf86-video-amdgpu: 23.0.0-1
GPU: Sapphire RX 6800 XT followed by ASUS RX 6400
WM: i3

This has been going on for about a week now, I've done everything I can to try and solve it but haven't made any progress, some days this will happen multiple times to the point of the system not being usable, other times it'll go days without a crash.

Last Wednesday I came home to find both my screens black and unable to wake. I powered the system off via the power button and when I rebooted I found a bunch of messges in a row like this:

Mar 01 21:32:34 revan kernel: amdgpu 0000:0a:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:1 pasid:32769, for process Xorg pid 737 thread Xorg:cs0 pid 738)
Mar 01 21:32:34 revan kernel: amdgpu 0000:0a:00.0: amdgpu:   in page starting at address 0x000080010078a000 from client 0x1b (UTCL2)
Mar 01 21:32:34 revan kernel: amdgpu 0000:0a:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000000
Mar 01 21:32:34 revan kernel: amdgpu 0000:0a:00.0: amdgpu:          Faulty UTCL2 client ID: CB/DB (0x0)
Mar 01 21:32:34 revan kernel: amdgpu 0000:0a:00.0: amdgpu:          MORE_FAULTS: 0x0
Mar 01 21:32:34 revan kernel: amdgpu 0000:0a:00.0: amdgpu:          WALKER_ERROR: 0x0
Mar 01 21:32:34 revan kernel: amdgpu 0000:0a:00.0: amdgpu:          PERMISSION_FAULTS: 0x0
Mar 01 21:32:34 revan kernel: amdgpu 0000:0a:00.0: amdgpu:          MAPPING_ERROR: 0x0
Mar 01 21:32:34 revan kernel: amdgpu 0000:0a:00.0: amdgpu:          RW: 0x0
Mar 01 21:32:34 revan kernel: amdgpu 0000:0a:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:1 pasid:32769, for process Xorg pid 737 thread Xorg:cs0 pid 738)
Mar 01 21:32:34 revan kernel: amdgpu 0000:0a:00.0: amdgpu:   in page starting at address 0x0000800100788000 from client 0x1b (UTCL2)
Mar 01 21:32:34 revan kernel: amdgpu 0000:0a:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000000
Mar 01 21:32:34 revan kernel: amdgpu 0000:0a:00.0: amdgpu:          Faulty UTCL2 client ID: CB/DB (0x0)
Mar 01 21:32:34 revan kernel: amdgpu 0000:0a:00.0: amdgpu:          MORE_FAULTS: 0x0
Mar 01 21:32:34 revan kernel: amdgpu 0000:0a:00.0: amdgpu:          WALKER_ERROR: 0x0
Mar 01 21:32:34 revan kernel: amdgpu 0000:0a:00.0: amdgpu:          PERMISSION_FAULTS: 0x0
Mar 01 21:32:34 revan kernel: amdgpu 0000:0a:00.0: amdgpu:          MAPPING_ERROR: 0x0
Mar 01 21:32:34 revan kernel: amdgpu 0000:0a:00.0: amdgpu:          RW: 0x0
Mar 01 21:32:34 revan kernel: amdgpu 0000:0a:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:1 pasid:32769, for process Xorg pid 737 thread Xorg:cs0 pid 738)
Mar 01 21:32:34 revan kernel: amdgpu 0000:0a:00.0: amdgpu:   in page starting at address 0x0000800100784000 from client 0x1b (UTCL2)
Mar 01 21:32:34 revan kernel: amdgpu 0000:0a:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000000
Mar 01 21:32:34 revan kernel: amdgpu 0000:0a:00.0: amdgpu:          Faulty UTCL2 client ID: CB/DB (0x0)
Mar 01 21:32:34 revan kernel: amdgpu 0000:0a:00.0: amdgpu:          MORE_FAULTS: 0x0
Mar 01 21:32:34 revan kernel: amdgpu 0000:0a:00.0: amdgpu:          WALKER_ERROR: 0x0
Mar 01 21:32:34 revan kernel: amdgpu 0000:0a:00.0: amdgpu:          PERMISSION_FAULTS: 0x0
Mar 01 21:32:34 revan kernel: amdgpu 0000:0a:00.0: amdgpu:          MAPPING_ERROR: 0x0
Mar 01 21:32:34 revan kernel: amdgpu 0000:0a:00.0: amdgpu:          RW: 0x0
Mar 01 21:32:44 revan kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, but soft recovered
Mar 01 21:32:54 revan kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, signaled seq=7298877, emitted seq=7298880
Mar 01 21:32:54 revan kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Xorg pid 737 thread Xorg:cs0 pid 738
Mar 01 21:32:54 revan kernel: [drm] psp gfx command DESTROY_TMR(0x7) failed and response status is (0x32)
Mar 01 21:33:02 revan kernel: [drm:psp_v11_0_memory_training [amdgpu]] *ERROR* send training msg failed.
Mar 01 21:33:02 revan kernel: [drm:psp_resume [amdgpu]] *ERROR* Failed to process memory training!
Mar 01 21:33:02 revan kernel: [drm:amdgpu_device_fw_loading [amdgpu]] *ERROR* resume of IP block <psp> failed -62
Mar 01 21:33:02 revan kernel: amdgpu_cs_ioctl: 124 callbacks suppressed
Mar 01 21:33:02 revan kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
Mar 01 21:33:02 revan kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* GPU Recovery Failed: -62
Mar 01 21:33:12 revan kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdma1 timeout, signaled seq=13975, emitted seq=13977
Mar 01 21:33:12 revan kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process  pid 0 thread  pid 0
Mar 01 21:33:12 revan kernel: amdgpu 0000:0a:00.0: amdgpu: Failed to disallow df cstate

I have a 6800xt that has been having hardware issues so I just assumed it was the culprit and switched it out to a brand new rx 6400 that I had as a backup while the 6800xt gets RMA'd. I install the RX 6400 and boot up only to find the same crash messages. Sometimes it would occur as a slight pause while typing (often in firefox) and it would recover but sometimes it would pause for longer periods of time and end up rebooting the system.

My first step was to downgraded the recently upgraded amdgpu driver from 23 to 22, after the crashes still occured after a reboot I then tried downgrading the kernal to 6.1.12 from 6.2.2 but also still got the crashes. The system randomly seemed stable from Thursday -> Sunday with regular use so i'm unable to recreate the issue on demand.

Output of lspci -k:

00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Root Complex
	Subsystem: ASUSTeK Computer Inc. Device 8808
lspci: Unable to load libkmod resources: error -2
00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Starship/Matisse IOMMU
	Subsystem: ASUSTeK Computer Inc. Device 8808
00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge
00:01.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge
	Subsystem: ASUSTeK Computer Inc. Device 8808
	Kernel driver in use: pcieport
00:01.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge
	Subsystem: ASUSTeK Computer Inc. Device 8808
	Kernel driver in use: pcieport
00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge
	DeviceName:  Onboard IGD
00:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge
00:03.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge
	Subsystem: ASUSTeK Computer Inc. Device 8808
	Kernel driver in use: pcieport
00:04.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge
00:05.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge
00:07.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge
00:07.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B]
	Subsystem: ASUSTeK Computer Inc. Device 8808
	Kernel driver in use: pcieport
00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge
00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B]
	Subsystem: ASUSTeK Computer Inc. Device 8808
	Kernel driver in use: pcieport
00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 61)
	Subsystem: ASUSTeK Computer Inc. Device 87c0
	Kernel driver in use: piix4_smbus
00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 51)
	Subsystem: ASUSTeK Computer Inc. Device 87c0
00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 0
00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 1
00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 2
00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 3
	Kernel driver in use: k10temp
00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 4
00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 5
00:18.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 6
00:18.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 7
01:00.0 Non-Volatile memory controller: Phison Electronics Corporation E16 PCIe4 NVMe Controller (rev 01)
	Subsystem: Phison Electronics Corporation E16 PCIe4 NVMe Controller
	Kernel driver in use: nvme
02:00.0 USB controller: Advanced Micro Devices, Inc. [AMD] 500 Series Chipset USB 3.1 XHCI Controller
	Subsystem: ASMedia Technology Inc. ASM1042A USB 3.0 Host Controller
	Kernel driver in use: xhci_hcd
02:00.1 SATA controller: Advanced Micro Devices, Inc. [AMD] 500 Series Chipset SATA Controller
	Subsystem: ASMedia Technology Inc. ASM1062 Serial ATA Controller
	Kernel driver in use: ahci
02:00.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] 500 Series Chipset Switch Upstream Port
	Subsystem: ASMedia Technology Inc. Device 0201
	Kernel driver in use: pcieport
03:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 43ea
	Subsystem: ASMedia Technology Inc. Device 3308
	Kernel driver in use: pcieport
03:04.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 43ea
	Subsystem: ASMedia Technology Inc. Device 3308
	Kernel driver in use: pcieport
03:08.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 43ea
	Subsystem: ASMedia Technology Inc. Device 3308
	Kernel driver in use: pcieport
03:09.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 43ea
	Subsystem: ASMedia Technology Inc. Device 3308
	Kernel driver in use: pcieport
05:00.0 Non-Volatile memory controller: Phison Electronics Corporation E12 NVMe Controller (rev 01)
	Subsystem: Phison Electronics Corporation E12 NVMe Controller
	Kernel driver in use: nvme
06:00.0 Network controller: Intel Corporation Wi-Fi 6 AX200 (rev 1a)
	Subsystem: Intel Corporation Wi-Fi 6 AX200NGW
	Kernel driver in use: iwlwifi
07:00.0 Ethernet controller: Intel Corporation Ethernet Controller I225-V (rev 02)
	Subsystem: ASUSTeK Computer Inc. Device 87d2
	Kernel driver in use: igc
08:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 XL Upstream Port of PCI Express Switch (rev c7)
	Kernel driver in use: pcieport
09:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 XL Downstream Port of PCI Express Switch
	Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 XL Downstream Port of PCI Express Switch
	Kernel driver in use: pcieport
0a:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 24 [Radeon RX 6400/6500 XT/6500M] (rev c7)
	Subsystem: ASUSTeK Computer Inc. Device 0502
	Kernel driver in use: amdgpu
0a:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Navi 21/23 HDMI/DP Audio Controller
	Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Navi 21/23 HDMI/DP Audio Controller
	Kernel driver in use: snd_hda_intel
0b:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Function
	Subsystem: ASUSTeK Computer Inc. Device 8808
0c:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP
	Subsystem: ASUSTeK Computer Inc. Device 8808
0c:00.1 Encryption controller: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Cryptographic Coprocessor PSPCPP
	Subsystem: ASUSTeK Computer Inc. Device 8808
	Kernel driver in use: ccp
0c:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller
	Subsystem: ASUSTeK Computer Inc. Device 87c0
	Kernel driver in use: xhci_hcd
0c:00.4 Audio device: Advanced Micro Devices, Inc. [AMD] Starship/Matisse HD Audio Controller
	Subsystem: ASUSTeK Computer Inc. Device 87e9
	Kernel driver in use: snd_hda_intel

A longer boot log of the issue from yesterday morning:

Mar 06 06:28:12 revan systemd-timesyncd[433]: Contacted time server 194.195.254.254:123 (2.arch.pool.ntp.org).
Mar 06 06:28:12 revan systemd-timesyncd[433]: Initial clock synchronization to Mon 2023-03-06 06:28:12.673448 AEDT.
Mar 06 06:28:12 revan systemd[1]: Started Verify integrity of password and group files.
Mar 06 06:28:12 revan systemd[1]: shadow.service: Deactivated successfully.
Mar 06 06:42:43 revan systemd[1]: Starting Cleanup of Temporary Directories...
Mar 06 06:42:43 revan systemd[1]: systemd-tmpfiles-clean.service: Deactivated successfully.
Mar 06 06:42:43 revan systemd[1]: Finished Cleanup of Temporary Directories.
Mar 06 06:42:43 revan systemd[1]: run-credentials-systemd\x2dtmpfiles\x2dclean.service.mount: Deactivated successfully.
Mar 06 06:48:07 revan dbus-daemon[443]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.9' (uid=0 pid=470 comm="/bin/login -p --     ")
Mar 06 06:48:07 revan dbus-daemon[443]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.
Mar 06 06:48:07 revan login[470]: pam_systemd_home(login:auth): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found.
Mar 06 06:48:09 revan login[470]: pam_unix(login:session): session opened for user mearkat7(uid=1000) by LOGIN(uid=0)
Mar 06 06:48:09 revan systemd[1]: Created slice User Slice of UID 1000.
Mar 06 06:48:09 revan systemd[1]: Starting User Runtime Directory /run/user/1000...
Mar 06 06:48:09 revan systemd-logind[445]: New session 1 of user mearkat7.
Mar 06 06:48:09 revan systemd[1]: Finished User Runtime Directory /run/user/1000.
Mar 06 06:48:09 revan systemd[1]: Starting User Manager for UID 1000...
Mar 06 06:48:09 revan dbus-daemon[443]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.11' (uid=0 pid=721 comm="(systemd)")
Mar 06 06:48:09 revan dbus-daemon[443]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.
Mar 06 06:48:09 revan (systemd)[721]: pam_systemd_home(systemd-user:account): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found.
Mar 06 06:48:09 revan (systemd)[721]: pam_warn(systemd-user:setcred): function=[pam_sm_setcred] flags=0x8002 service=[systemd-user] terminal=[] user=[mearkat7] ruser=[<unknown>] rhost=[<unknown>]
Mar 06 06:48:09 revan (systemd)[721]: pam_unix(systemd-user:session): session opened for user mearkat7(uid=1000) by (uid=0)
Mar 06 06:48:09 revan systemd[721]: Queued start job for default target Main User Target.
Mar 06 06:48:09 revan systemd-journald[296]: /var/log/journal/68a93eebf67943688105155727f3161b/user-1000.journal: Monotonic clock jumped backwards relative to last journal entry, rotating.
Mar 06 06:48:09 revan systemd[721]: Created slice User Application Slice.
Mar 06 06:48:09 revan systemd[721]: Reached target Paths.
Mar 06 06:48:09 revan systemd[721]: Reached target Timers.
Mar 06 06:48:09 revan systemd[721]: Starting D-Bus User Message Bus Socket...
Mar 06 06:48:09 revan systemd[721]: Listening on GnuPG network certificate management daemon.
Mar 06 06:48:09 revan systemd[721]: Listening on GCR ssh-agent wrapper.
Mar 06 06:48:09 revan systemd[721]: Listening on GNOME Keyring daemon.
Mar 06 06:48:09 revan systemd[721]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers).
Mar 06 06:48:09 revan systemd[721]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
Mar 06 06:48:09 revan systemd[721]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
Mar 06 06:48:09 revan systemd[721]: Listening on GnuPG cryptographic agent and passphrase cache.
Mar 06 06:48:09 revan systemd[721]: Listening on p11-kit server.
Mar 06 06:48:09 revan systemd[721]: Listening on PipeWire Multimedia System Socket.
Mar 06 06:48:09 revan systemd[721]: Listening on Sound System.
Mar 06 06:48:09 revan systemd[721]: Listening on D-Bus User Message Bus Socket.
Mar 06 06:48:09 revan systemd[721]: Reached target Sockets.
Mar 06 06:48:09 revan systemd[721]: Reached target Basic System.
Mar 06 06:48:09 revan systemd[721]: Reached target Main User Target.
Mar 06 06:48:09 revan systemd[721]: Startup finished in 80ms.
Mar 06 06:48:09 revan systemd[1]: Started User Manager for UID 1000.
Mar 06 06:48:09 revan systemd[1]: Started Session 1 of User mearkat7.
Mar 06 06:48:09 revan login[470]: LOGIN ON tty1 BY mearkat7
Mar 06 06:48:10 revan systemd[721]: Created slice User Core Session Slice.
Mar 06 06:48:10 revan systemd[721]: Starting D-Bus User Message Bus...
Mar 06 06:48:10 revan systemd[721]: Started D-Bus User Message Bus.
Mar 06 06:48:10 revan dbus-daemon[767]: [session uid=1000 pid=767] Successfully activated service 'org.freedesktop.systemd1'
Mar 06 06:48:10 revan dbus-daemon[767]: [session uid=1000 pid=767] Activating via systemd: service name='org.gtk.vfs.Daemon' unit='gvfs-daemon.service' requested by ':1.2' (uid=1000 pid=780 comm="pasystray")
Mar 06 06:48:10 revan dbus-daemon[443]: [system] Activating via systemd: service name='org.freedesktop.UDisks2' unit='udisks2.service' requested by ':1.14' (uid=1000 pid=788 comm="/usr/bin/python /usr/bin/udiskie")
Mar 06 06:48:10 revan systemd[721]: Starting Virtual filesystem service...
Mar 06 06:48:10 revan dbus-daemon[767]: [session uid=1000 pid=767] Successfully activated service 'org.gtk.vfs.Daemon'
Mar 06 06:48:10 revan systemd[721]: Started Virtual filesystem service.
Mar 06 06:48:10 revan dbus-daemon[767]: [session uid=1000 pid=767] Activating via systemd: service name='org.a11y.Bus' unit='at-spi-dbus-bus.service' requested by ':1.9' (uid=1000 pid=786 comm="termite")
Mar 06 06:48:10 revan systemd[721]: Starting Accessibility services bus...
Mar 06 06:48:10 revan systemd[1]: Starting Disk Manager...
Mar 06 06:48:10 revan udisksd[906]: udisks daemon version 2.9.4 starting
Mar 06 06:48:10 revan dbus-daemon[767]: [session uid=1000 pid=767] Successfully activated service 'org.a11y.Bus'
Mar 06 06:48:10 revan systemd[721]: Started Accessibility services bus.
Mar 06 06:48:10 revan dbus-daemon[443]: [system] Activating via systemd: service name='org.freedesktop.Avahi' unit='dbus-org.freedesktop.Avahi.service' requested by ':1.16' (uid=1000 pid=780 comm="pasystray")
Mar 06 06:48:10 revan dbus-daemon[443]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.Avahi.service': Unit dbus-org.freedesktop.Avahi.service not found.
Mar 06 06:48:10 revan dbus-daemon[443]: [system] Activating via systemd: service name='org.freedesktop.PolicyKit1' unit='polkit.service' requested by ':1.3' (uid=0 pid=446 comm="/usr/bin/NetworkManager --no-daemon")
Mar 06 06:48:10 revan systemd[1]: Starting Authorization Manager...
Mar 06 06:48:10 revan polkitd[922]: Started polkitd version 122
Mar 06 06:48:10 revan polkitd[922]: Loading rules from directory /etc/polkit-1/rules.d
Mar 06 06:48:10 revan polkitd[922]: Loading rules from directory /usr/share/polkit-1/rules.d
Mar 06 06:48:10 revan polkitd[922]: Finished loading, compiling and executing 3 rules
Mar 06 06:48:10 revan dbus-daemon[443]: [system] Successfully activated service 'org.freedesktop.PolicyKit1'
Mar 06 06:48:10 revan polkitd[922]: Acquired the name org.freedesktop.PolicyKit1 on the system bus
Mar 06 06:48:10 revan systemd[1]: Started Authorization Manager.
Mar 06 06:48:10 revan at-spi-bus-launcher[916]: dbus-daemon[916]: Activating service name='org.a11y.atspi.Registry' requested by ':1.3' (uid=1000 pid=780 comm="pasystray")
Mar 06 06:48:10 revan systemd[721]: Starting Sound Service...
Mar 06 06:48:10 revan at-spi-bus-launcher[916]: dbus-daemon[916]: Successfully activated service 'org.a11y.atspi.Registry'
Mar 06 06:48:10 revan at-spi-bus-launcher[980]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
Mar 06 06:48:10 revan NetworkManager[446]: <info>  [1678045690.3371] agent-manager: agent[bddc7f16c8b5dafc,:1.17/org.freedesktop.nm-applet/1000]: agent registered
Mar 06 06:48:10 revan dbus-daemon[767]: [session uid=1000 pid=767] Activating via systemd: service name='org.freedesktop.Notifications' unit='dunst.service' requested by ':1.5' (uid=1000 pid=776 comm="nm-applet")
Mar 06 06:48:10 revan systemd[721]: Starting Dunst notification daemon...
Mar 06 06:48:10 revan dbus-daemon[443]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.21' (uid=1000 pid=981 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo")
Mar 06 06:48:10 revan dunst[995]: WARNING: Could not find theme breeze
Mar 06 06:48:10 revan dbus-daemon[767]: [session uid=1000 pid=767] Successfully activated service 'org.freedesktop.Notifications'
Mar 06 06:48:10 revan systemd[721]: Started Dunst notification daemon.
Mar 06 06:48:10 revan systemd[1]: Starting RealtimeKit Scheduling Policy Service...
Mar 06 06:48:10 revan dbus-daemon[443]: [system] Successfully activated service 'org.freedesktop.RealtimeKit1'
Mar 06 06:48:10 revan systemd[1]: Started RealtimeKit Scheduling Policy Service.
Mar 06 06:48:10 revan rtkit-daemon[1010]: Successfully called chroot.
Mar 06 06:48:10 revan rtkit-daemon[1010]: Successfully dropped privileges.
Mar 06 06:48:10 revan rtkit-daemon[1010]: Successfully limited resources.
Mar 06 06:48:10 revan rtkit-daemon[1010]: Canary thread running.
Mar 06 06:48:10 revan rtkit-daemon[1010]: Running.
Mar 06 06:48:10 revan rtkit-daemon[1010]: Watchdog thread running.
Mar 06 06:48:10 revan dbus-daemon[443]: [system] Successfully activated service 'org.freedesktop.UDisks2'
Mar 06 06:48:10 revan systemd[1]: Started Disk Manager.
Mar 06 06:48:10 revan rtkit-daemon[1010]: Successfully made thread 981 of process 981 owned by '1000' high priority at nice level -11.
Mar 06 06:48:10 revan rtkit-daemon[1010]: Supervising 1 threads of 1 processes of 1 users.
Mar 06 06:48:10 revan udisksd[906]: Acquired the name org.freedesktop.UDisks2 on the system message bus
Mar 06 06:48:10 revan dbus-daemon[443]: [system] Activating via systemd: service name='org.blueman.Mechanism' unit='blueman-mechanism.service' requested by ':1.19' (uid=1000 pid=778 comm="/usr/bin/python /usr/bin/blueman-applet")
Mar 06 06:48:10 revan systemd[1]: Starting Bluetooth management mechanism...
Mar 06 06:48:10 revan dbus-daemon[443]: [system] Successfully activated service 'org.blueman.Mechanism'
Mar 06 06:48:10 revan systemd[1]: Started Bluetooth management mechanism.
Mar 06 06:48:10 revan dbus-daemon[767]: [session uid=1000 pid=767] Activating via systemd: service name='org.bluez.obex' unit='dbus-org.bluez.obex.service' requested by ':1.6' (uid=1000 pid=778 comm="/usr/bin/python /usr/bin/blueman-applet")
Mar 06 06:48:10 revan dbus-daemon[443]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.19' (uid=1000 pid=778 comm="/usr/bin/python /usr/bin/blueman-applet")
Mar 06 06:48:10 revan dbus-daemon[443]: [system] Activation via systemd failed for unit 'dbus-org.bluez.service': Unit dbus-org.bluez.service not found.
Mar 06 06:48:10 revan systemd[721]: Starting Bluetooth OBEX service...
Mar 06 06:48:10 revan obexd[1088]: OBEX daemon 5.66
Mar 06 06:48:10 revan dbus-daemon[767]: [session uid=1000 pid=767] Successfully activated service 'org.bluez.obex'
Mar 06 06:48:10 revan systemd[721]: Started Bluetooth OBEX service.
Mar 06 06:48:10 revan rtkit-daemon[1010]: Supervising 1 threads of 1 processes of 1 users.
Mar 06 06:48:10 revan rtkit-daemon[1010]: Supervising 1 threads of 1 processes of 1 users.
Mar 06 06:48:10 revan kernel: usb 2-2.1: reset high-speed USB device number 4 using xhci_hcd
Mar 06 06:48:10 revan rtkit-daemon[1010]: Supervising 1 threads of 1 processes of 1 users.
Mar 06 06:48:10 revan rtkit-daemon[1010]: Supervising 1 threads of 1 processes of 1 users.
Mar 06 06:48:10 revan rtkit-daemon[1010]: Supervising 1 threads of 1 processes of 1 users.
Mar 06 06:48:10 revan rtkit-daemon[1010]: Supervising 1 threads of 1 processes of 1 users.
Mar 06 06:48:10 revan rtkit-daemon[1010]: Successfully made thread 1445 of process 784 owned by '1000' RT at priority 10.
Mar 06 06:48:10 revan rtkit-daemon[1010]: Supervising 2 threads of 2 processes of 1 users.
Mar 06 06:48:11 revan rtkit-daemon[1010]: Supervising 2 threads of 2 processes of 1 users.
Mar 06 06:48:11 revan rtkit-daemon[1010]: Successfully made thread 1491 of process 981 owned by '1000' RT at priority 5.
Mar 06 06:48:11 revan rtkit-daemon[1010]: Supervising 3 threads of 2 processes of 1 users.
Mar 06 06:48:11 revan rtkit-daemon[1010]: Supervising 3 threads of 2 processes of 1 users.
Mar 06 06:48:11 revan rtkit-daemon[1010]: Successfully made thread 1493 of process 981 owned by '1000' RT at priority 5.
Mar 06 06:48:11 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 06:48:11 revan systemd[721]: Started Sound Service.
Mar 06 06:48:11 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 06:48:11 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 06:48:11 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 06:48:11 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 06:48:12 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 06:48:12 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 06:48:12 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 06:48:12 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 06:48:12 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 06:48:12 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 06:48:13 revan systemd[1]: proc-sys-fs-binfmt_misc.automount: Got automount request for /proc/sys/fs/binfmt_misc, triggered by 1796 (AUTHENTICATE)
Mar 06 06:48:13 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 06:48:13 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 06:48:13 revan systemd[1]: Mounting Arbitrary Executable File Formats File System...
Mar 06 06:48:13 revan systemd[1]: Mounted Arbitrary Executable File Formats File System.
Mar 06 06:48:14 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 06:48:14 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 06:48:26 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 06:48:26 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 06:48:26 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 06:48:26 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 06:48:28 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 06:48:28 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 06:48:31 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 06:48:31 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 06:48:31 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 06:48:31 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 06:48:31 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 06:48:31 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 06:48:38 revan dbus-daemon[443]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.44' (uid=0 pid=2701 comm="sudo pacman -Syu")
Mar 06 06:48:38 revan dbus-daemon[443]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.
Mar 06 06:48:38 revan sudo[2701]: pam_systemd_home(sudo:account): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found.
Mar 06 06:48:38 revan sudo[2701]:     mearkat7 : TTY=pts/0 ; PWD=/home/mearkat7 ; USER=root ; COMMAND=/usr/bin/pacman -Syu
Mar 06 06:48:38 revan sudo[2701]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000)
Mar 06 06:48:40 revan systemd[1]: blueman-mechanism.service: Deactivated successfully.
Mar 06 06:48:41 revan sudo[2701]: pam_unix(sudo:session): session closed for user root
Mar 06 06:48:41 revan dbus-daemon[443]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.45' (uid=0 pid=2774 comm="sudo pacman -S -u -y --config /etc/pacman.conf --")
Mar 06 06:48:41 revan dbus-daemon[443]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.
Mar 06 06:48:41 revan sudo[2774]: pam_systemd_home(sudo:account): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found.
Mar 06 06:48:41 revan sudo[2774]:     mearkat7 : TTY=pts/0 ; PWD=/home/mearkat7 ; USER=root ; COMMAND=/usr/bin/pacman -S -u -y --config /etc/pacman.conf --
Mar 06 06:48:41 revan sudo[2774]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000)
Mar 06 06:48:42 revan sudo[2774]: pam_unix(sudo:session): session closed for user root
Mar 06 06:50:01 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 06:50:01 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 06:50:36 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 06:50:36 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 06:52:37 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 06:52:37 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 06:53:36 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 06:53:36 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 06:54:37 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 06:54:37 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 06:56:38 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 06:56:38 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 06:58:36 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 06:58:36 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 06:59:10 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 06:59:10 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:00:39 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:00:39 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:01:16 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:01:16 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:02:40 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:02:40 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:03:36 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:03:36 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:04:41 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:04:41 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:06:16 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:06:16 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:08:36 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:08:36 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:10:43 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:10:43 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:11:16 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:11:16 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:12:44 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:12:44 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:13:36 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:13:36 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:14:44 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:14:44 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:16:16 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:16:16 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:18:36 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:18:36 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:19:17 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:19:17 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:20:46 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:20:46 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:22:47 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:22:47 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:23:36 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:23:36 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:24:48 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:24:48 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:26:16 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:26:16 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:26:49 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:26:49 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:28:36 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:28:36 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:30:50 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:30:50 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:32:51 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:32:51 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:33:36 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:33:36 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:34:51 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:34:51 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:36:16 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:36:16 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:36:52 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:36:52 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:38:03 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:38:03 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:38:20 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:38:20 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:38:20 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:38:20 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:38:21 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:38:21 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:38:30 revan dbus-daemon[443]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.86' (uid=1000 pid=45111 comm="/usr/lib/slack/slack -s --enable-crashpad")
Mar 06 07:38:30 revan dbus-daemon[443]: [system] Activation via systemd failed for unit 'dbus-org.bluez.service': Unit dbus-org.bluez.service not found.
Mar 06 07:38:31 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:38:31 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:38:33 revan dbus-daemon[443]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.88' (uid=1000 pid=45388 comm="/usr/lib/signal-desktop/signal-desktop --")
Mar 06 07:38:33 revan dbus-daemon[443]: [system] Activation via systemd failed for unit 'dbus-org.bluez.service': Unit dbus-org.bluez.service not found.
Mar 06 07:38:36 revan dbus-daemon[443]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.89' (uid=1000 pid=45589 comm="/opt/discord/Discord")
Mar 06 07:38:36 revan dbus-daemon[443]: [system] Activation via systemd failed for unit 'dbus-org.bluez.service': Unit dbus-org.bluez.service not found.
Mar 06 07:38:54 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:38:54 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:38:56 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:38:56 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:38:56 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:38:56 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:38:58 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:38:58 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:39:09 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:39:09 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:39:23 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:39:23 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:39:26 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:39:26 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:39:28 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:39:28 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:39:40 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:39:40 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:40:54 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:40:54 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:42:42 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:42:42 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:42:42 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:42:42 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:42:46 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:42:46 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:42:46 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:42:46 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:42:48 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:42:48 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:42:48 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:42:48 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:42:53 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:42:53 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:42:53 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:42:53 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:42:53 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:42:53 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:43:29 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:43:29 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:43:36 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:43:36 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:43:55 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:43:55 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:44:23 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:44:23 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:44:37 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:44:37 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:44:42 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:44:42 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:45:04 revan dbus-daemon[443]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.115' (uid=1000 pid=52680 comm="/opt/visual-studio-code/code --unity-launch --enab")
Mar 06 07:45:04 revan dbus-daemon[443]: [system] Activation via systemd failed for unit 'dbus-org.bluez.service': Unit dbus-org.bluez.service not found.
Mar 06 07:45:06 revan dbus-daemon[767]: [session uid=1000 pid=767] Activating service name='org.freedesktop.secrets' requested by ':1.55' (uid=1000 pid=52680 comm="/opt/visual-studio-code/code --unity-launch --enab")
Mar 06 07:45:07 revan systemd[721]: Started GNOME Keyring daemon.
Mar 06 07:45:07 revan gnome-keyring-daemon[53103]: GNOME_KEYRING_CONTROL=/run/user/1000/keyring
Mar 06 07:45:07 revan dbus-daemon[767]: [session uid=1000 pid=767] Successfully activated service 'org.freedesktop.secrets'
Mar 06 07:45:07 revan gnome-keyring-daemon[53103]: The Secret Service was already initialized
Mar 06 07:45:07 revan gnome-keyring-d[53103]: The Secret Service was already initialized
Mar 06 07:45:07 revan gnome-keyring-daemon[53094]: discover_other_daemon: 1
Mar 06 07:45:07 revan org.freedesktop.secrets[53094]: GNOME_KEYRING_CONTROL=/run/user/1000/keyring
Mar 06 07:45:09 revan dbus-daemon[443]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.117' (uid=0 pid=54566 comm="sudo ctop")
Mar 06 07:45:09 revan dbus-daemon[443]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.
Mar 06 07:45:09 revan sudo[54566]: pam_systemd_home(sudo:account): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found.
Mar 06 07:45:09 revan sudo[54566]:     mearkat7 : TTY=pts/3 ; PWD=/home/mearkat7 ; USER=root ; COMMAND=/usr/bin/ctop
Mar 06 07:45:09 revan sudo[54566]: pam_unix(sudo:session): session opened for user root(uid=0) by mearkat7(uid=1000)
Mar 06 07:45:09 revan dbus-daemon[443]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.118' (uid=0 pid=54576 comm="sudo docker compose up")
Mar 06 07:45:09 revan dbus-daemon[443]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.
Mar 06 07:45:09 revan sudo[54576]: pam_systemd_home(sudo:account): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found.
Mar 06 07:45:09 revan sudo[54576]:     mearkat7 : TTY=pts/2 ; PWD=/home/mearkat7/docker/lp ; USER=root ; COMMAND=/usr/bin/docker compose up
Mar 06 07:45:09 revan sudo[54576]: pam_unix(sudo:session): session opened for user root(uid=0) by mearkat7(uid=1000)
Mar 06 07:45:09 revan NetworkManager[446]: <info>  [1678049109.9828] manager: (vethe67c850): new Veth device (/org/freedesktop/NetworkManager/Devices/7)
Mar 06 07:45:09 revan NetworkManager[446]: <info>  [1678049109.9836] manager: (vethc72fb5e): new Veth device (/org/freedesktop/NetworkManager/Devices/8)
Mar 06 07:45:09 revan kernel: br-e5f0a2a8c742: port 1(vethc72fb5e) entered blocking state
Mar 06 07:45:09 revan kernel: br-e5f0a2a8c742: port 1(vethc72fb5e) entered disabled state
Mar 06 07:45:09 revan kernel: device vethc72fb5e entered promiscuous mode
Mar 06 07:45:09 revan kernel: br-e5f0a2a8c742: port 2(veth1d47f2d) entered blocking state
Mar 06 07:45:09 revan kernel: br-e5f0a2a8c742: port 2(veth1d47f2d) entered disabled state
Mar 06 07:45:10 revan NetworkManager[446]: <info>  [1678049110.0204] manager: (veth76fc017): new Veth device (/org/freedesktop/NetworkManager/Devices/9)
Mar 06 07:45:10 revan kernel: device veth1d47f2d entered promiscuous mode
Mar 06 07:45:10 revan kernel: br-e5f0a2a8c742: port 2(veth1d47f2d) entered blocking state
Mar 06 07:45:10 revan kernel: br-e5f0a2a8c742: port 2(veth1d47f2d) entered forwarding state
Mar 06 07:45:10 revan NetworkManager[446]: <info>  [1678049110.0220] manager: (veth1d47f2d): new Veth device (/org/freedesktop/NetworkManager/Devices/10)
Mar 06 07:45:10 revan kernel: br-e5f0a2a8c742: port 2(veth1d47f2d) entered disabled state
Mar 06 07:45:10 revan NetworkManager[446]: <info>  [1678049110.0295] manager: (veth8029967): new Veth device (/org/freedesktop/NetworkManager/Devices/11)
Mar 06 07:45:10 revan NetworkManager[446]: <info>  [1678049110.0301] manager: (veth667d7cb): new Veth device (/org/freedesktop/NetworkManager/Devices/12)
Mar 06 07:45:10 revan kernel: br-e5f0a2a8c742: port 3(veth667d7cb) entered blocking state
Mar 06 07:45:10 revan kernel: br-e5f0a2a8c742: port 3(veth667d7cb) entered disabled state
Mar 06 07:45:10 revan kernel: device veth667d7cb entered promiscuous mode
Mar 06 07:45:10 revan kernel: br-e5f0a2a8c742: port 3(veth667d7cb) entered blocking state
Mar 06 07:45:10 revan kernel: br-e5f0a2a8c742: port 3(veth667d7cb) entered forwarding state
Mar 06 07:45:10 revan kernel: IPv6: ADDRCONF(NETDEV_CHANGE): br-e5f0a2a8c742: link becomes ready
Mar 06 07:45:10 revan kernel: br-e5f0a2a8c742: port 3(veth667d7cb) entered disabled state
Mar 06 07:45:10 revan containerd[468]: time="2023-03-06T07:45:10.173934661+11:00" level=info msg="loading plugin \"io.containerd.event.v1.publisher\"..." runtime=io.containerd.runc.v2 type=io.containerd.event.v1
Mar 06 07:45:10 revan containerd[468]: time="2023-03-06T07:45:10.174443231+11:00" level=info msg="loading plugin \"io.containerd.internal.v1.shutdown\"..." runtime=io.containerd.runc.v2 type=io.containerd.internal.v1
Mar 06 07:45:10 revan containerd[468]: time="2023-03-06T07:45:10.174455091+11:00" level=info msg="loading plugin \"io.containerd.ttrpc.v1.task\"..." runtime=io.containerd.runc.v2 type=io.containerd.ttrpc.v1
Mar 06 07:45:10 revan containerd[468]: time="2023-03-06T07:45:10.174600811+11:00" level=info msg="starting signal loop" namespace=moby path=/run/containerd/io.containerd.runtime.v2.task/moby/f78cec8596d00e8b71b95c6ad38875dfed0dbb5df591344dad8ff398df34f752 pid=54861 runtime=io.containerd.runc.v2
Mar 06 07:45:10 revan containerd[468]: time="2023-03-06T07:45:10.180410832+11:00" level=info msg="loading plugin \"io.containerd.event.v1.publisher\"..." runtime=io.containerd.runc.v2 type=io.containerd.event.v1
Mar 06 07:45:10 revan containerd[468]: time="2023-03-06T07:45:10.180513652+11:00" level=info msg="loading plugin \"io.containerd.internal.v1.shutdown\"..." runtime=io.containerd.runc.v2 type=io.containerd.internal.v1
Mar 06 07:45:10 revan containerd[468]: time="2023-03-06T07:45:10.180533602+11:00" level=info msg="loading plugin \"io.containerd.ttrpc.v1.task\"..." runtime=io.containerd.runc.v2 type=io.containerd.ttrpc.v1
Mar 06 07:45:10 revan containerd[468]: time="2023-03-06T07:45:10.180697872+11:00" level=info msg="starting signal loop" namespace=moby path=/run/containerd/io.containerd.runtime.v2.task/moby/44595fb9090bb46f2f30c4ada1694fe9d782c259a6bc0b2d8fce9ccc8c434f92 pid=54879 runtime=io.containerd.runc.v2
Mar 06 07:45:10 revan systemd[1]: run-docker-runtime\x2drunc-moby-f78cec8596d00e8b71b95c6ad38875dfed0dbb5df591344dad8ff398df34f752-runc.3vTyaa.mount: Deactivated successfully.
Mar 06 07:45:10 revan containerd[468]: time="2023-03-06T07:45:10.205447602+11:00" level=info msg="loading plugin \"io.containerd.event.v1.publisher\"..." runtime=io.containerd.runc.v2 type=io.containerd.event.v1
Mar 06 07:45:10 revan containerd[468]: time="2023-03-06T07:45:10.205493592+11:00" level=info msg="loading plugin \"io.containerd.internal.v1.shutdown\"..." runtime=io.containerd.runc.v2 type=io.containerd.internal.v1
Mar 06 07:45:10 revan containerd[468]: time="2023-03-06T07:45:10.205499882+11:00" level=info msg="loading plugin \"io.containerd.ttrpc.v1.task\"..." runtime=io.containerd.runc.v2 type=io.containerd.ttrpc.v1
Mar 06 07:45:10 revan containerd[468]: time="2023-03-06T07:45:10.205553342+11:00" level=info msg="starting signal loop" namespace=moby path=/run/containerd/io.containerd.runtime.v2.task/moby/095147ef0261988c9314ed9225af5f70f2d9f1f04de0c7a9da32d1f36e0bde0b pid=54911 runtime=io.containerd.runc.v2
Mar 06 07:45:10 revan systemd[1]: Started libcontainer container 095147ef0261988c9314ed9225af5f70f2d9f1f04de0c7a9da32d1f36e0bde0b.
Mar 06 07:45:10 revan systemd[1]: Started libcontainer container 44595fb9090bb46f2f30c4ada1694fe9d782c259a6bc0b2d8fce9ccc8c434f92.
Mar 06 07:45:10 revan systemd[1]: Started libcontainer container f78cec8596d00e8b71b95c6ad38875dfed0dbb5df591344dad8ff398df34f752.
Mar 06 07:45:10 revan kernel: eth0: renamed from veth76fc017
Mar 06 07:45:10 revan kernel: eth0: renamed from vethe67c850
Mar 06 07:45:10 revan kernel: eth0: renamed from veth8029967
Mar 06 07:45:10 revan NetworkManager[446]: <info>  [1678049110.6235] device (vethc72fb5e): carrier: link connected
Mar 06 07:45:10 revan NetworkManager[446]: <info>  [1678049110.6236] device (veth1d47f2d): carrier: link connected
Mar 06 07:45:10 revan NetworkManager[446]: <info>  [1678049110.6237] device (veth667d7cb): carrier: link connected
Mar 06 07:45:10 revan NetworkManager[446]: <info>  [1678049110.6238] device (br-e5f0a2a8c742): carrier: link connected
Mar 06 07:45:10 revan kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethc72fb5e: link becomes ready
Mar 06 07:45:10 revan kernel: br-e5f0a2a8c742: port 1(vethc72fb5e) entered blocking state
Mar 06 07:45:10 revan kernel: br-e5f0a2a8c742: port 1(vethc72fb5e) entered forwarding state
Mar 06 07:45:10 revan kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth1d47f2d: link becomes ready
Mar 06 07:45:10 revan kernel: br-e5f0a2a8c742: port 2(veth1d47f2d) entered blocking state
Mar 06 07:45:10 revan kernel: br-e5f0a2a8c742: port 2(veth1d47f2d) entered forwarding state
Mar 06 07:45:10 revan kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth667d7cb: link becomes ready
Mar 06 07:45:10 revan kernel: br-e5f0a2a8c742: port 3(veth667d7cb) entered blocking state
Mar 06 07:45:10 revan kernel: br-e5f0a2a8c742: port 3(veth667d7cb) entered forwarding state
Mar 06 07:45:10 revan NetworkManager[446]: <info>  [1678049110.6604] manager: (veth1232c76): new Veth device (/org/freedesktop/NetworkManager/Devices/13)
Mar 06 07:45:10 revan NetworkManager[446]: <info>  [1678049110.6609] manager: (veth8ebcd51): new Veth device (/org/freedesktop/NetworkManager/Devices/14)
Mar 06 07:45:10 revan kernel: br-e5f0a2a8c742: port 4(veth8ebcd51) entered blocking state
Mar 06 07:45:10 revan kernel: br-e5f0a2a8c742: port 4(veth8ebcd51) entered disabled state
Mar 06 07:45:10 revan kernel: device veth8ebcd51 entered promiscuous mode
Mar 06 07:45:10 revan kernel: br-e5f0a2a8c742: port 4(veth8ebcd51) entered blocking state
Mar 06 07:45:10 revan kernel: br-e5f0a2a8c742: port 4(veth8ebcd51) entered forwarding state
Mar 06 07:45:10 revan containerd[468]: time="2023-03-06T07:45:10.701909712+11:00" level=info msg="loading plugin \"io.containerd.event.v1.publisher\"..." runtime=io.containerd.runc.v2 type=io.containerd.event.v1
Mar 06 07:45:10 revan containerd[468]: time="2023-03-06T07:45:10.701959452+11:00" level=info msg="loading plugin \"io.containerd.internal.v1.shutdown\"..." runtime=io.containerd.runc.v2 type=io.containerd.internal.v1
Mar 06 07:45:10 revan containerd[468]: time="2023-03-06T07:45:10.701976412+11:00" level=info msg="loading plugin \"io.containerd.ttrpc.v1.task\"..." runtime=io.containerd.runc.v2 type=io.containerd.ttrpc.v1
Mar 06 07:45:10 revan containerd[468]: time="2023-03-06T07:45:10.702035732+11:00" level=info msg="starting signal loop" namespace=moby path=/run/containerd/io.containerd.runtime.v2.task/moby/50cc28e71d4730ce125b543aa8270068dc16bfa1a4a21b5a9d86874be9fbb616 pid=55200 runtime=io.containerd.runc.v2
Mar 06 07:45:10 revan systemd[1]: Started libcontainer container 50cc28e71d4730ce125b543aa8270068dc16bfa1a4a21b5a9d86874be9fbb616.
Mar 06 07:45:10 revan kernel: hugetlbfs: java (55287): Using mlock ulimits for SHM_HUGETLB is obsolete
Mar 06 07:45:10 revan kernel: eth0: renamed from veth1232c76
Mar 06 07:45:10 revan NetworkManager[446]: <info>  [1678049110.9353] device (veth8ebcd51): carrier: link connected
Mar 06 07:45:10 revan kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth8ebcd51: link becomes ready
Mar 06 07:45:26 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:45:26 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:46:09 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:46:09 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:46:16 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:46:16 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:46:22 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:46:22 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:46:42 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:46:42 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:46:42 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:46:42 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:46:45 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:46:45 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:46:47 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:46:47 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:46:47 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:46:47 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:46:47 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:46:47 revan rtkit-daemon[1010]: Supervising 4 threads of 2 processes of 1 users.
Mar 06 07:46:47 revan rtkit-daemon[1010]: Successfully made thread 57445 of process 57217 owned by '1000' RT at priority 10.
Mar 06 07:46:47 revan rtkit-daemon[1010]: Supervising 5 threads of 3 processes of 1 users.
Mar 06 07:46:58 revan rtkit-daemon[1010]: Supervising 5 threads of 3 processes of 1 users.
Mar 06 07:46:58 revan rtkit-daemon[1010]: Supervising 5 threads of 3 processes of 1 users.
Mar 06 07:47:00 revan rtkit-daemon[1010]: Supervising 5 threads of 3 processes of 1 users.
Mar 06 07:47:00 revan rtkit-daemon[1010]: Supervising 5 threads of 3 processes of 1 users.
Mar 06 07:48:00 revan kernel: amdgpu 0000:0a:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:2 pasid:32773, for process firefox pid 784 thread firefox:cs0 pid 1086)
Mar 06 07:48:00 revan kernel: amdgpu 0000:0a:00.0: amdgpu:   in page starting at address 0x0000800168d0d000 from client 0x1b (UTCL2)
Mar 06 07:48:00 revan kernel: amdgpu 0000:0a:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00201031
Mar 06 07:48:00 revan kernel: amdgpu 0000:0a:00.0: amdgpu:          Faulty UTCL2 client ID: TCP (0x8)
Mar 06 07:48:00 revan kernel: amdgpu 0000:0a:00.0: amdgpu:          MORE_FAULTS: 0x1
Mar 06 07:48:00 revan kernel: amdgpu 0000:0a:00.0: amdgpu:          WALKER_ERROR: 0x0
Mar 06 07:48:00 revan kernel: amdgpu 0000:0a:00.0: amdgpu:          PERMISSION_FAULTS: 0x3
Mar 06 07:48:00 revan kernel: amdgpu 0000:0a:00.0: amdgpu:          MAPPING_ERROR: 0x0
Mar 06 07:48:00 revan kernel: amdgpu 0000:0a:00.0: amdgpu:          RW: 0x0
Mar 06 07:48:00 revan kernel: amdgpu 0000:0a:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:2 pasid:32773, for process firefox pid 784 thread firefox:cs0 pid 1086)
Mar 06 07:48:00 revan kernel: amdgpu 0000:0a:00.0: amdgpu:   in page starting at address 0x0000800168d0c000 from client 0x1b (UTCL2)
Mar 06 07:48:00 revan kernel: amdgpu 0000:0a:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000000
Mar 06 07:48:00 revan kernel: amdgpu 0000:0a:00.0: amdgpu:          Faulty UTCL2 client ID: CB/DB (0x0)
Mar 06 07:48:00 revan kernel: amdgpu 0000:0a:00.0: amdgpu:          MORE_FAULTS: 0x0
Mar 06 07:48:00 revan kernel: amdgpu 0000:0a:00.0: amdgpu:          WALKER_ERROR: 0x0
Mar 06 07:48:00 revan kernel: amdgpu 0000:0a:00.0: amdgpu:          PERMISSION_FAULTS: 0x0
Mar 06 07:48:00 revan kernel: amdgpu 0000:0a:00.0: amdgpu:          MAPPING_ERROR: 0x0
Mar 06 07:48:00 revan kernel: amdgpu 0000:0a:00.0: amdgpu:          RW: 0x0
Mar 06 07:48:10 revan kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, but soft recovered
Mar 06 07:48:28 revan rtkit-daemon[1010]: Supervising 5 threads of 3 processes of 1 users.
Mar 06 07:48:28 revan rtkit-daemon[1010]: Supervising 5 threads of 3 processes of 1 users.
Mar 06 07:50:04 revan rtkit-daemon[1010]: Supervising 5 threads of 3 processes of 1 users.
Mar 06 07:50:04 revan rtkit-daemon[1010]: Supervising 5 threads of 3 processes of 1 users.
Mar 06 07:51:00 revan rtkit-daemon[1010]: Supervising 5 threads of 3 processes of 1 users.
Mar 06 07:51:00 revan rtkit-daemon[1010]: Supervising 5 threads of 3 processes of 1 users.
Mar 06 07:52:11 revan rtkit-daemon[1010]: Supervising 5 threads of 3 processes of 1 users.
Mar 06 07:52:11 revan rtkit-daemon[1010]: Supervising 5 threads of 3 processes of 1 users.
Mar 06 07:53:01 revan rtkit-daemon[1010]: Supervising 5 threads of 3 processes of 1 users.
Mar 06 07:53:01 revan rtkit-daemon[1010]: Supervising 5 threads of 3 processes of 1 users.
Mar 06 07:55:03 revan rtkit-daemon[1010]: Supervising 5 threads of 3 processes of 1 users.
Mar 06 07:55:03 revan rtkit-daemon[1010]: Supervising 5 threads of 3 processes of 1 users.
Mar 06 07:56:17 revan rtkit-daemon[1010]: Supervising 5 threads of 3 processes of 1 users.
Mar 06 07:56:17 revan rtkit-daemon[1010]: Supervising 5 threads of 3 processes of 1 users.
Mar 06 07:57:05 revan rtkit-daemon[1010]: Supervising 5 threads of 3 processes of 1 users.
Mar 06 07:57:05 revan rtkit-daemon[1010]: Supervising 5 threads of 3 processes of 1 users.
Mar 06 07:58:37 revan rtkit-daemon[1010]: Supervising 5 threads of 3 processes of 1 users.
Mar 06 07:58:37 revan rtkit-daemon[1010]: Supervising 5 threads of 3 processes of 1 users.
Mar 06 08:00:44 revan rtkit-daemon[1010]: Supervising 5 threads of 3 processes of 1 users.
Mar 06 08:00:44 revan rtkit-daemon[1010]: Supervising 5 threads of 3 processes of 1 users.
Mar 06 08:03:10 revan rtkit-daemon[1010]: Supervising 5 threads of 3 processes of 1 users.
Mar 06 08:03:10 revan rtkit-daemon[1010]: Supervising 5 threads of 3 processes of 1 users.
Mar 06 08:05:08 revan rtkit-daemon[1010]: Supervising 5 threads of 3 processes of 1 users.
Mar 06 08:05:08 revan rtkit-daemon[1010]: Supervising 5 threads of 3 processes of 1 users.
Mar 06 08:06:18 revan rtkit-daemon[1010]: Supervising 5 threads of 3 processes of 1 users.
Mar 06 08:06:18 revan rtkit-daemon[1010]: Supervising 5 threads of 3 processes of 1 users.
Mar 06 08:07:12 revan rtkit-daemon[1010]: Supervising 5 threads of 3 processes of 1 users.
Mar 06 08:07:12 revan rtkit-daemon[1010]: Supervising 5 threads of 3 processes of 1 users.
Mar 06 08:08:38 revan rtkit-daemon[1010]: Supervising 5 threads of 3 processes of 1 users.
Mar 06 08:08:38 revan rtkit-daemon[1010]: Supervising 5 threads of 3 processes of 1 users.
Mar 06 08:09:14 revan rtkit-daemon[1010]: Supervising 5 threads of 3 processes of 1 users.
Mar 06 08:09:14 revan rtkit-daemon[1010]: Supervising 5 threads of 3 processes of 1 users.
Mar 06 08:10:30 revan rtkit-daemon[1010]: Supervising 5 threads of 3 processes of 1 users.
Mar 06 08:10:30 revan rtkit-daemon[1010]: Supervising 5 threads of 3 processes of 1 users.
Mar 06 08:11:15 revan rtkit-daemon[1010]: Supervising 5 threads of 3 processes of 1 users.
Mar 06 08:11:15 revan rtkit-daemon[1010]: Supervising 5 threads of 3 processes of 1 users.
Mar 06 08:13:03 revan rtkit-daemon[1010]: Supervising 5 threads of 3 processes of 1 users.
Mar 06 08:13:03 revan rtkit-daemon[1010]: Supervising 5 threads of 3 processes of 1 users.
Mar 06 08:13:30 revan rtkit-daemon[1010]: Supervising 5 threads of 3 processes of 1 users.
Mar 06 08:13:30 revan rtkit-daemon[1010]: Supervising 5 threads of 3 processes of 1 users.
Mar 06 08:13:30 revan rtkit-daemon[1010]: Supervising 5 threads of 3 processes of 1 users.
Mar 06 08:13:30 revan rtkit-daemon[1010]: Supervising 5 threads of 3 processes of 1 users.
Mar 06 08:13:37 revan rtkit-daemon[1010]: Supervising 5 threads of 3 processes of 1 users.
Mar 06 08:13:37 revan rtkit-daemon[1010]: Supervising 5 threads of 3 processes of 1 users.
Mar 06 08:13:37 revan rtkit-daemon[1010]: Supervising 5 threads of 3 processes of 1 users.
Mar 06 08:13:37 revan rtkit-daemon[1010]: Supervising 5 threads of 3 processes of 1 users.
Mar 06 08:13:37 revan rtkit-daemon[1010]: Supervising 5 threads of 3 processes of 1 users.
Mar 06 08:13:37 revan rtkit-daemon[1010]: Supervising 5 threads of 3 processes of 1 users.
Mar 06 08:13:37 revan rtkit-daemon[1010]: Successfully made thread 81000 of process 80266 owned by '1000' RT at priority 10.
Mar 06 08:13:37 revan rtkit-daemon[1010]: Supervising 6 threads of 4 processes of 1 users.
Mar 06 08:14:04 revan rtkit-daemon[1010]: Supervising 6 threads of 4 processes of 1 users.
Mar 06 08:14:04 revan rtkit-daemon[1010]: Supervising 6 threads of 4 processes of 1 users.
Mar 06 08:14:16 revan rtkit-daemon[1010]: Supervising 6 threads of 4 processes of 1 users.
Mar 06 08:14:16 revan rtkit-daemon[1010]: Supervising 6 threads of 4 processes of 1 users.
Mar 06 08:14:21 revan rtkit-daemon[1010]: Supervising 6 threads of 4 processes of 1 users.
Mar 06 08:14:21 revan rtkit-daemon[1010]: Supervising 6 threads of 4 processes of 1 users.
Mar 06 08:14:45 revan rtkit-daemon[1010]: Supervising 6 threads of 4 processes of 1 users.
Mar 06 08:14:45 revan rtkit-daemon[1010]: Supervising 6 threads of 4 processes of 1 users.
Mar 06 08:15:13 revan rtkit-daemon[1010]: Supervising 6 threads of 4 processes of 1 users.
Mar 06 08:15:13 revan rtkit-daemon[1010]: Supervising 6 threads of 4 processes of 1 users.
Mar 06 08:15:15 revan rtkit-daemon[1010]: Supervising 6 threads of 4 processes of 1 users.
Mar 06 08:15:15 revan rtkit-daemon[1010]: Supervising 6 threads of 4 processes of 1 users.
Mar 06 08:15:44 revan rtkit-daemon[1010]: Supervising 6 threads of 4 processes of 1 users.
Mar 06 08:15:44 revan rtkit-daemon[1010]: Supervising 6 threads of 4 processes of 1 users.
Mar 06 08:15:45 revan rtkit-daemon[1010]: Supervising 6 threads of 4 processes of 1 users.
Mar 06 08:15:45 revan rtkit-daemon[1010]: Supervising 6 threads of 4 processes of 1 users.
Mar 06 08:15:53 revan rtkit-daemon[1010]: Supervising 6 threads of 4 processes of 1 users.
Mar 06 08:15:53 revan rtkit-daemon[1010]: Supervising 6 threads of 4 processes of 1 users.
Mar 06 08:16:35 revan rtkit-daemon[1010]: Supervising 6 threads of 4 processes of 1 users.
Mar 06 08:16:35 revan rtkit-daemon[1010]: Supervising 6 threads of 4 processes of 1 users.
Mar 06 08:16:35 revan rtkit-daemon[1010]: Supervising 6 threads of 4 processes of 1 users.
Mar 06 08:16:35 revan rtkit-daemon[1010]: Supervising 6 threads of 4 processes of 1 users.
Mar 06 08:16:40 revan pulseaudio[981]: ALSA woke us up to write new data to the device, but there was actually nothing to write.
Mar 06 08:16:40 revan pulseaudio[981]: Most likely this is a bug in the ALSA driver 'snd_usb_audio'. Please report this issue to the ALSA developers.
Mar 06 08:16:40 revan pulseaudio[981]: We were woken up with POLLOUT set -- however a subsequent snd_pcm_avail() returned 0 or another value < min_avail.
Mar 06 08:17:00 revan rtkit-daemon[1010]: Supervising 6 threads of 4 processes of 1 users.
Mar 06 08:17:00 revan rtkit-daemon[1010]: Supervising 6 threads of 4 processes of 1 users.
Mar 06 08:17:00 revan rtkit-daemon[1010]: Supervising 6 threads of 4 processes of 1 users.
Mar 06 08:17:00 revan rtkit-daemon[1010]: Supervising 6 threads of 4 processes of 1 users.
Mar 06 08:17:45 revan rtkit-daemon[1010]: Supervising 6 threads of 4 processes of 1 users.
Mar 06 08:17:45 revan rtkit-daemon[1010]: Supervising 6 threads of 4 processes of 1 users.
Mar 06 08:17:46 revan rtkit-daemon[1010]: Supervising 6 threads of 4 processes of 1 users.
Mar 06 08:17:46 revan rtkit-daemon[1010]: Supervising 6 threads of 4 processes of 1 users.
Mar 06 08:18:11 revan rtkit-daemon[1010]: Supervising 6 threads of 4 processes of 1 users.
Mar 06 08:18:11 revan rtkit-daemon[1010]: Supervising 6 threads of 4 processes of 1 users.
Mar 06 08:18:23 revan rtkit-daemon[1010]: Supervising 6 threads of 4 processes of 1 users.
Mar 06 08:18:23 revan rtkit-daemon[1010]: Supervising 6 threads of 4 processes of 1 users.
Mar 06 08:18:23 revan rtkit-daemon[1010]: Supervising 6 threads of 4 processes of 1 users.
Mar 06 08:18:23 revan rtkit-daemon[1010]: Supervising 6 threads of 4 processes of 1 users.
Mar 06 08:18:27 revan rtkit-daemon[1010]: Supervising 6 threads of 4 processes of 1 users.
Mar 06 08:18:27 revan rtkit-daemon[1010]: Supervising 6 threads of 4 processes of 1 users.
Mar 06 08:18:27 revan rtkit-daemon[1010]: Supervising 6 threads of 4 processes of 1 users.
Mar 06 08:18:27 revan rtkit-daemon[1010]: Supervising 6 threads of 4 processes of 1 users.
Mar 06 08:18:27 revan rtkit-daemon[1010]: Supervising 6 threads of 4 processes of 1 users.
Mar 06 08:18:27 revan rtkit-daemon[1010]: Supervising 6 threads of 4 processes of 1 users.
Mar 06 08:18:30 revan rtkit-daemon[1010]: Supervising 6 threads of 4 processes of 1 users.
Mar 06 08:18:30 revan rtkit-daemon[1010]: Supervising 6 threads of 4 processes of 1 users.
Mar 06 08:19:06 revan rtkit-daemon[1010]: Supervising 6 threads of 4 processes of 1 users.
Mar 06 08:19:06 revan rtkit-daemon[1010]: Supervising 6 threads of 4 processes of 1 users.
Mar 06 08:20:16 revan rtkit-daemon[1010]: Supervising 6 threads of 4 processes of 1 users.
Mar 06 08:20:16 revan rtkit-daemon[1010]: Supervising 6 threads of 4 processes of 1 users.
Mar 06 08:20:16 revan rtkit-daemon[1010]: Supervising 6 threads of 4 processes of 1 users.
Mar 06 08:20:16 revan rtkit-daemon[1010]: Supervising 6 threads of 4 processes of 1 users.
Mar 06 08:20:31 revan rtkit-daemon[1010]: Supervising 6 threads of 4 processes of 1 users.
Mar 06 08:20:31 revan rtkit-daemon[1010]: Supervising 6 threads of 4 processes of 1 users.
Mar 06 08:20:59 revan rtkit-daemon[1010]: Supervising 6 threads of 4 processes of 1 users.
Mar 06 08:20:59 revan rtkit-daemon[1010]: Supervising 6 threads of 4 processes of 1 users.
Mar 06 08:21:03 revan rtkit-daemon[1010]: Supervising 6 threads of 4 processes of 1 users.
Mar 06 08:21:03 revan rtkit-daemon[1010]: Supervising 6 threads of 4 processes of 1 users.
Mar 06 08:21:03 revan rtkit-daemon[1010]: Supervising 6 threads of 4 processes of 1 users.
Mar 06 08:21:03 revan rtkit-daemon[1010]: Supervising 6 threads of 4 processes of 1 users.
Mar 06 08:21:03 revan rtkit-daemon[1010]: Supervising 6 threads of 4 processes of 1 users.
Mar 06 08:21:03 revan rtkit-daemon[1010]: Supervising 6 threads of 4 processes of 1 users.
Mar 06 08:21:55 revan rtkit-daemon[1010]: Supervising 6 threads of 4 processes of 1 users.
Mar 06 08:21:55 revan rtkit-daemon[1010]: Supervising 6 threads of 4 processes of 1 users.
Mar 06 08:23:08 revan rtkit-daemon[1010]: Supervising 6 threads of 4 processes of 1 users.
Mar 06 08:23:08 revan rtkit-daemon[1010]: Supervising 6 threads of 4 processes of 1 users.
Mar 06 08:23:56 revan rtkit-daemon[1010]: Supervising 6 threads of 4 processes of 1 users.
Mar 06 08:23:56 revan rtkit-daemon[1010]: Supervising 6 threads of 4 processes of 1 users.
Mar 06 08:23:58 revan rtkit-daemon[1010]: Supervising 6 threads of 4 processes of 1 users.
Mar 06 08:23:58 revan rtkit-daemon[1010]: Supervising 6 threads of 4 processes of 1 users.
Mar 06 08:24:01 revan rtkit-daemon[1010]: Supervising 6 threads of 4 processes of 1 users.
Mar 06 08:24:01 revan rtkit-daemon[1010]: Supervising 6 threads of 4 processes of 1 users.
Mar 06 08:24:27 revan rtkit-daemon[1010]: Supervising 6 threads of 4 processes of 1 users.
Mar 06 08:24:27 revan rtkit-daemon[1010]: Supervising 6 threads of 4 processes of 1 users.
Mar 06 08:24:27 revan rtkit-daemon[1010]: Supervising 6 threads of 4 processes of 1 users.
Mar 06 08:24:27 revan rtkit-daemon[1010]: Supervising 6 threads of 4 processes of 1 users.
Mar 06 08:24:30 revan rtkit-daemon[1010]: Supervising 6 threads of 4 processes of 1 users.
Mar 06 08:24:30 revan rtkit-daemon[1010]: Supervising 6 threads of 4 processes of 1 users.
Mar 06 08:24:56 revan rtkit-daemon[1010]: Supervising 6 threads of 4 processes of 1 users.
Mar 06 08:24:56 revan rtkit-daemon[1010]: Supervising 6 threads of 4 processes of 1 users.
Mar 06 08:24:56 revan rtkit-daemon[1010]: Supervising 6 threads of 4 processes of 1 users.
Mar 06 08:24:56 revan rtkit-daemon[1010]: Supervising 6 threads of 4 processes of 1 users.
Mar 06 08:25:01 revan rtkit-daemon[1010]: Supervising 6 threads of 4 processes of 1 users.
Mar 06 08:25:01 revan rtkit-daemon[1010]: Supervising 6 threads of 4 processes of 1 users.
Mar 06 08:25:17 revan rtkit-daemon[1010]: Supervising 6 threads of 4 processes of 1 users.
Mar 06 08:25:17 revan rtkit-daemon[1010]: Supervising 6 threads of 4 processes of 1 users.
Mar 06 08:25:31 revan kernel: amdgpu 0000:0a:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:2 pasid:32773, for process firefox pid 784 thread firefox:cs0 pid 1086)
Mar 06 08:25:31 revan kernel: amdgpu 0000:0a:00.0: amdgpu:   in page starting at address 0x000080058650c000 from client 0x1b (UTCL2)
Mar 06 08:25:31 revan kernel: amdgpu 0000:0a:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00201031
Mar 06 08:25:31 revan kernel: amdgpu 0000:0a:00.0: amdgpu:          Faulty UTCL2 client ID: TCP (0x8)
Mar 06 08:25:31 revan kernel: amdgpu 0000:0a:00.0: amdgpu:          MORE_FAULTS: 0x1
Mar 06 08:25:31 revan kernel: amdgpu 0000:0a:00.0: amdgpu:          WALKER_ERROR: 0x0
Mar 06 08:25:31 revan kernel: amdgpu 0000:0a:00.0: amdgpu:          PERMISSION_FAULTS: 0x3
Mar 06 08:25:31 revan kernel: amdgpu 0000:0a:00.0: amdgpu:          MAPPING_ERROR: 0x0
Mar 06 08:25:31 revan kernel: amdgpu 0000:0a:00.0: amdgpu:          RW: 0x0
Mar 06 08:25:31 revan kernel: amdgpu 0000:0a:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:2 pasid:32773, for process firefox pid 784 thread firefox:cs0 pid 1086)
Mar 06 08:25:31 revan kernel: amdgpu 0000:0a:00.0: amdgpu:   in page starting at address 0x000080058650c000 from client 0x1b (UTCL2)
Mar 06 08:25:31 revan kernel: amdgpu 0000:0a:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000000
Mar 06 08:25:31 revan kernel: amdgpu 0000:0a:00.0: amdgpu:          Faulty UTCL2 client ID: CB/DB (0x0)
Mar 06 08:25:31 revan kernel: amdgpu 0000:0a:00.0: amdgpu:          MORE_FAULTS: 0x0
Mar 06 08:25:31 revan kernel: amdgpu 0000:0a:00.0: amdgpu:          WALKER_ERROR: 0x0
Mar 06 08:25:31 revan kernel: amdgpu 0000:0a:00.0: amdgpu:          PERMISSION_FAULTS: 0x0
Mar 06 08:25:31 revan kernel: amdgpu 0000:0a:00.0: amdgpu:          MAPPING_ERROR: 0x0
Mar 06 08:25:31 revan kernel: amdgpu 0000:0a:00.0: amdgpu:          RW: 0x0
Mar 06 08:25:31 revan kernel: amdgpu 0000:0a:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:2 pasid:32773, for process firefox pid 784 thread firefox:cs0 pid 1086)
Mar 06 08:25:31 revan kernel: amdgpu 0000:0a:00.0: amdgpu:   in page starting at address 0x000080058650e000 from client 0x1b (UTCL2)
Mar 06 08:25:31 revan kernel: amdgpu 0000:0a:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000000
Mar 06 08:25:31 revan kernel: amdgpu 0000:0a:00.0: amdgpu:          Faulty UTCL2 client ID: CB/DB (0x0)
Mar 06 08:25:31 revan kernel: amdgpu 0000:0a:00.0: amdgpu:          MORE_FAULTS: 0x0
Mar 06 08:25:31 revan kernel: amdgpu 0000:0a:00.0: amdgpu:          WALKER_ERROR: 0x0
Mar 06 08:25:31 revan kernel: amdgpu 0000:0a:00.0: amdgpu:          PERMISSION_FAULTS: 0x0
Mar 06 08:25:31 revan kernel: amdgpu 0000:0a:00.0: amdgpu:          MAPPING_ERROR: 0x0
Mar 06 08:25:31 revan kernel: amdgpu 0000:0a:00.0: amdgpu:          RW: 0x0
Mar 06 08:25:31 revan kernel: amdgpu 0000:0a:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:2 pasid:32773, for process firefox pid 784 thread firefox:cs0 pid 1086)
Mar 06 08:25:31 revan kernel: amdgpu 0000:0a:00.0: amdgpu:   in page starting at address 0x0000800586504000 from client 0x1b (UTCL2)
Mar 06 08:25:31 revan kernel: amdgpu 0000:0a:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000000
Mar 06 08:25:31 revan kernel: amdgpu 0000:0a:00.0: amdgpu:          Faulty UTCL2 client ID: CB/DB (0x0)
Mar 06 08:25:31 revan kernel: amdgpu 0000:0a:00.0: amdgpu:          MORE_FAULTS: 0x0
Mar 06 08:25:31 revan kernel: amdgpu 0000:0a:00.0: amdgpu:          WALKER_ERROR: 0x0
Mar 06 08:25:31 revan kernel: amdgpu 0000:0a:00.0: amdgpu:          PERMISSION_FAULTS: 0x0
Mar 06 08:25:31 revan kernel: amdgpu 0000:0a:00.0: amdgpu:          MAPPING_ERROR: 0x0
Mar 06 08:25:31 revan kernel: amdgpu 0000:0a:00.0: amdgpu:          RW: 0x0
Mar 06 08:25:31 revan kernel: amdgpu 0000:0a:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:2 pasid:32773, for process firefox pid 784 thread firefox:cs0 pid 1086)
Mar 06 08:25:31 revan kernel: amdgpu 0000:0a:00.0: amdgpu:   in page starting at address 0x000080058650c000 from client 0x1b (UTCL2)
Mar 06 08:25:31 revan kernel: amdgpu 0000:0a:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000000
Mar 06 08:25:31 revan kernel: amdgpu 0000:0a:00.0: amdgpu:          Faulty UTCL2 client ID: CB/DB (0x0)
Mar 06 08:25:31 revan kernel: amdgpu 0000:0a:00.0: amdgpu:          MORE_FAULTS: 0x0
Mar 06 08:25:31 revan kernel: amdgpu 0000:0a:00.0: amdgpu:          WALKER_ERROR: 0x0
Mar 06 08:25:31 revan kernel: amdgpu 0000:0a:00.0: amdgpu:          PERMISSION_FAULTS: 0x0
Mar 06 08:25:31 revan kernel: amdgpu 0000:0a:00.0: amdgpu:          MAPPING_ERROR: 0x0
Mar 06 08:25:31 revan kernel: amdgpu 0000:0a:00.0: amdgpu:          RW: 0x0
Mar 06 08:25:31 revan kernel: amdgpu 0000:0a:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:2 pasid:32773, for process firefox pid 784 thread firefox:cs0 pid 1086)
Mar 06 08:25:31 revan kernel: amdgpu 0000:0a:00.0: amdgpu:   in page starting at address 0x0000800586504000 from client 0x1b (UTCL2)
Mar 06 08:25:31 revan kernel: amdgpu 0000:0a:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000000
Mar 06 08:25:31 revan kernel: amdgpu 0000:0a:00.0: amdgpu:          Faulty UTCL2 client ID: CB/DB (0x0)
Mar 06 08:25:31 revan kernel: amdgpu 0000:0a:00.0: amdgpu:          MORE_FAULTS: 0x0
Mar 06 08:25:31 revan kernel: amdgpu 0000:0a:00.0: amdgpu:          WALKER_ERROR: 0x0
Mar 06 08:25:31 revan kernel: amdgpu 0000:0a:00.0: amdgpu:          PERMISSION_FAULTS: 0x0
Mar 06 08:25:31 revan kernel: amdgpu 0000:0a:00.0: amdgpu:          MAPPING_ERROR: 0x0
Mar 06 08:25:31 revan kernel: amdgpu 0000:0a:00.0: amdgpu:          RW: 0x0
Mar 06 08:25:31 revan kernel: amdgpu 0000:0a:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:2 pasid:32773, for process firefox pid 784 thread firefox:cs0 pid 1086)
Mar 06 08:25:31 revan kernel: amdgpu 0000:0a:00.0: amdgpu:   in page starting at address 0x0000800586504000 from client 0x1b (UTCL2)
Mar 06 08:25:31 revan kernel: amdgpu 0000:0a:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000000
Mar 06 08:25:31 revan kernel: amdgpu 0000:0a:00.0: amdgpu:          Faulty UTCL2 client ID: CB/DB (0x0)
Mar 06 08:25:31 revan kernel: amdgpu 0000:0a:00.0: amdgpu:          MORE_FAULTS: 0x0
Mar 06 08:25:31 revan kernel: amdgpu 0000:0a:00.0: amdgpu:          WALKER_ERROR: 0x0
Mar 06 08:25:31 revan kernel: amdgpu 0000:0a:00.0: amdgpu:          PERMISSION_FAULTS: 0x0
Mar 06 08:25:31 revan kernel: amdgpu 0000:0a:00.0: amdgpu:          MAPPING_ERROR: 0x0
Mar 06 08:25:31 revan kernel: amdgpu 0000:0a:00.0: amdgpu:          RW: 0x0
Mar 06 08:25:31 revan kernel: amdgpu 0000:0a:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:2 pasid:32773, for process firefox pid 784 thread firefox:cs0 pid 1086)
Mar 06 08:25:31 revan kernel: amdgpu 0000:0a:00.0: amdgpu:   in page starting at address 0x000080058650e000 from client 0x1b (UTCL2)
Mar 06 08:25:31 revan kernel: amdgpu 0000:0a:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000000
Mar 06 08:25:31 revan kernel: amdgpu 0000:0a:00.0: amdgpu:          Faulty UTCL2 client ID: CB/DB (0x0)
Mar 06 08:25:31 revan kernel: amdgpu 0000:0a:00.0: amdgpu:          MORE_FAULTS: 0x0
Mar 06 08:25:31 revan kernel: amdgpu 0000:0a:00.0: amdgpu:          WALKER_ERROR: 0x0
Mar 06 08:25:31 revan kernel: amdgpu 0000:0a:00.0: amdgpu:          PERMISSION_FAULTS: 0x0
Mar 06 08:25:31 revan kernel: amdgpu 0000:0a:00.0: amdgpu:          MAPPING_ERROR: 0x0
Mar 06 08:25:31 revan kernel: amdgpu 0000:0a:00.0: amdgpu:          RW: 0x0
Mar 06 08:25:41 revan kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, but soft recovered
Mar 06 08:25:51 revan kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, signaled seq=643164, emitted seq=643167
Mar 06 08:25:51 revan kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process firefox pid 784 thread firefox:cs0 pid 1086
Mar 06 08:25:51 revan kernel: amdgpu 0000:0a:00.0: amdgpu: GPU reset begin!
Mar 06 08:25:51 revan kernel: amdgpu 0000:0a:00.0: amdgpu: MODE1 reset
Mar 06 08:25:51 revan kernel: amdgpu 0000:0a:00.0: amdgpu: GPU mode1 reset
Mar 06 08:25:51 revan kernel: amdgpu 0000:0a:00.0: amdgpu: GPU smu mode1 reset
Mar 06 08:25:52 revan kernel: amdgpu 0000:0a:00.0: amdgpu: GPU reset succeeded, trying to resume
Mar 06 08:25:52 revan kernel: [drm] PCIE GART of 512M enabled (table at 0x00000080FEB00000).
Mar 06 08:25:52 revan kernel: [drm] VRAM is lost due to GPU reset!
Mar 06 08:25:52 revan kernel: [drm] PSP is resuming...
Mar 06 08:25:52 revan kernel: [drm] reserve 0xa00000 from 0x80fd000000 for PSP TMR
Mar 06 08:25:52 revan kernel: amdgpu 0000:0a:00.0: amdgpu: RAS: optional ras ta ucode is not available
Mar 06 08:25:52 revan kernel: amdgpu 0000:0a:00.0: amdgpu: SECUREDISPLAY: securedisplay ta ucode is not available
Mar 06 08:25:52 revan kernel: amdgpu 0000:0a:00.0: amdgpu: SMU is resuming...
Mar 06 08:25:52 revan kernel: amdgpu 0000:0a:00.0: amdgpu: smu driver if version = 0x0000000d, smu fw if version = 0x0000000f, smu fw program = 0, version = 0x00491f00 (73.31.0)
Mar 06 08:25:52 revan kernel: amdgpu 0000:0a:00.0: amdgpu: SMU driver if version not matched
Mar 06 08:25:52 revan kernel: amdgpu 0000:0a:00.0: amdgpu: use vbios provided pptable
Mar 06 08:25:52 revan kernel: amdgpu 0000:0a:00.0: amdgpu: SMU is resumed successfully!
Mar 06 08:25:52 revan kernel: [drm] DMUB hardware initialized: version=0x02020017
Mar 06 08:25:52 revan kernel: [drm] kiq ring mec 2 pipe 1 q 0
Mar 06 08:25:52 revan kernel: [drm] VCN decode and encode initialized successfully(under DPG Mode).
Mar 06 08:25:52 revan kernel: amdgpu 0000:0a:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0 on hub 0
Mar 06 08:25:52 revan kernel: amdgpu 0000:0a:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0
Mar 06 08:25:52 revan kernel: amdgpu 0000:0a:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0
Mar 06 08:25:52 revan kernel: amdgpu 0000:0a:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 5 on hub 0
Mar 06 08:25:52 revan kernel: amdgpu 0000:0a:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 6 on hub 0
Mar 06 08:25:52 revan kernel: amdgpu 0000:0a:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 7 on hub 0
Mar 06 08:25:52 revan kernel: amdgpu 0000:0a:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 8 on hub 0
Mar 06 08:25:52 revan kernel: amdgpu 0000:0a:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 9 on hub 0
Mar 06 08:25:52 revan kernel: amdgpu 0000:0a:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 10 on hub 0
Mar 06 08:25:52 revan kernel: amdgpu 0000:0a:00.0: amdgpu: ring kiq_2.1.0 uses VM inv eng 11 on hub 0
Mar 06 08:25:52 revan kernel: amdgpu 0000:0a:00.0: amdgpu: ring sdma0 uses VM inv eng 12 on hub 0
Mar 06 08:25:52 revan kernel: amdgpu 0000:0a:00.0: amdgpu: ring vcn_dec_0 uses VM inv eng 0 on hub 1
Mar 06 08:25:52 revan kernel: amdgpu 0000:0a:00.0: amdgpu: recover vram bo from shadow start
Mar 06 08:25:52 revan kernel: amdgpu 0000:0a:00.0: amdgpu: recover vram bo from shadow done
Mar 06 08:25:52 revan kernel: amdgpu 0000:0a:00.0: amdgpu: GPU reset(4) succeeded!
Mar 06 08:25:52 revan kernel: [drm] Skip scheduling IBs!
Mar 06 08:25:52 revan kernel: [drm] Skip scheduling IBs!
Mar 06 08:25:52 revan kernel: [drm] Skip scheduling IBs!
Mar 06 08:25:52 revan kernel: [drm] Skip scheduling IBs!
Mar 06 08:25:52 revan kernel: [drm] Skip scheduling IBs!
Mar 06 08:25:52 revan kernel: [drm] Skip scheduling IBs!
Mar 06 08:25:52 revan kernel: [drm] Skip scheduling IBs!
Mar 06 08:25:52 revan kernel: [drm] Skip scheduling IBs!
Mar 06 08:25:52 revan kernel: [drm] Skip scheduling IBs!
Mar 06 08:25:52 revan kernel: [drm] Skip scheduling IBs!
Mar 06 08:25:52 revan kernel: [drm] Skip scheduling IBs!
Mar 06 08:25:52 revan kernel: [drm] Skip scheduling IBs!
Mar 06 08:25:52 revan kernel: [drm] Skip scheduling IBs!
Mar 06 08:25:52 revan kernel: [drm] Skip scheduling IBs!
Mar 06 08:25:52 revan kernel: [drm] Skip scheduling IBs!
Mar 06 08:25:52 revan kernel: [drm] Skip scheduling IBs!
Mar 06 08:25:52 revan kernel: [drm] Skip scheduling IBs!
Mar 06 08:25:52 revan kernel: [drm] Skip scheduling IBs!
Mar 06 08:25:52 revan kernel: [drm] Skip scheduling IBs!
Mar 06 08:25:52 revan kernel: [drm] Skip scheduling IBs!
Mar 06 08:25:52 revan kernel: [drm] Skip scheduling IBs!
Mar 06 08:25:52 revan kernel: [drm] Skip scheduling IBs!
Mar 06 08:25:52 revan kernel: [drm] Skip scheduling IBs!
Mar 06 08:25:52 revan kernel: [drm] Skip scheduling IBs!
Mar 06 08:25:52 revan kernel: [drm] Skip scheduling IBs!
Mar 06 08:25:52 revan kernel: [drm] Skip scheduling IBs!
Mar 06 08:25:52 revan kernel: [drm] Skip scheduling IBs!
Mar 06 08:25:52 revan kernel: [drm] Skip scheduling IBs!
Mar 06 08:25:52 revan kernel: [drm] Skip scheduling IBs!
Mar 06 08:25:52 revan kernel: [drm] Skip scheduling IBs!
Mar 06 08:25:52 revan kernel: [drm] Skip scheduling IBs!
Mar 06 08:25:52 revan kernel: [drm] Skip scheduling IBs!
Mar 06 08:25:52 revan kernel: [drm] Skip scheduling IBs!
Mar 06 08:25:52 revan kernel: [drm] Skip scheduling IBs!
Mar 06 08:25:52 revan kernel: [drm] Skip scheduling IBs!
Mar 06 08:25:52 revan kernel: [drm] Skip scheduling IBs!
Mar 06 08:25:52 revan kernel: [drm] Skip scheduling IBs!
Mar 06 08:25:52 revan kernel: [drm] Skip scheduling IBs!
Mar 06 08:25:52 revan kernel: [drm] Skip scheduling IBs!
Mar 06 08:25:52 revan kernel: [drm] Skip scheduling IBs!
Mar 06 08:25:52 revan kernel: [drm] Skip scheduling IBs!
Mar 06 08:25:52 revan kernel: [drm] Skip scheduling IBs!
Mar 06 08:25:52 revan kernel: [drm] Skip scheduling IBs!
Mar 06 08:25:52 revan kernel: [drm] Skip scheduling IBs!
Mar 06 08:25:52 revan kernel: [drm] Skip scheduling IBs!
Mar 06 08:25:52 revan kernel: [drm] Skip scheduling IBs!
Mar 06 08:25:52 revan kernel: [drm] Skip scheduling IBs!
Mar 06 08:25:52 revan kernel: [drm] Skip scheduling IBs!
Mar 06 08:25:52 revan kernel: [drm] Skip scheduling IBs!
Mar 06 08:25:52 revan kernel: [drm] Skip scheduling IBs!
Mar 06 08:25:52 revan kernel: [drm] Skip scheduling IBs!
Mar 06 08:25:52 revan kernel: [drm] Skip scheduling IBs!
Mar 06 08:25:52 revan kernel: [drm] Skip scheduling IBs!
Mar 06 08:25:52 revan kernel: [drm] Skip scheduling IBs!
Mar 06 08:25:52 revan kernel: [drm] Skip scheduling IBs!
Mar 06 08:25:52 revan kernel: [drm] Skip scheduling IBs!
Mar 06 08:25:52 revan kernel: [drm] Skip scheduling IBs!
Mar 06 08:25:52 revan kernel: [drm] Skip scheduling IBs!
Mar 06 08:25:52 revan dunst[995]: X connection to :0 broken (explicit kill or server shutdown).
Mar 06 08:25:52 revan systemd[721]: dunst.service: Main process exited, code=exited, status=1/FAILURE
Mar 06 08:25:52 revan at-spi-bus-launcher[980]: X connection to :0 broken (explicit kill or server shutdown).
Mar 06 08:25:52 revan systemd[721]: dunst.service: Failed with result 'exit-code'.

On Monday morning the crashes returned so I switched to a different device to work but am struggling to find any more things to try or any more info, would love any help if people know of anything to try!

Last edited by mearkat7 (2023-03-08 06:41:50)

Offline

#2 2023-03-07 11:22:23

Lone_Wolf
Forum Moderator
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 12,048

Re: Random GPU crashes amdgpu across 2 different GPUs

lspci: Unable to load libkmod resources: error -2

Don't like that, though I have no clue what it means.

The page faults in the log at the bottom of your post all come from firefox, can you switch to a different browser for testing if that is involved ?

What WM/DE are you using ?

Welcome to archlinux forums .


Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.


(A works at time B)  && (time C > time B ) ≠  (A works at time C)

Offline

#3 2023-03-07 12:56:12

seth
Member
Registered: 2012-09-03
Posts: 52,545

Re: Random GPU crashes amdgpu across 2 different GPUs

ENOENT / "404 file not found"

downgraded the recently upgraded amdgpu driver from 23 to 22

How about just removing xf86-video-amdgpu?

And please post your complete system journal for a boot:

sudo journalctl -b | curl -F 'file=@-' 0x0.st

Offline

#4 2023-03-08 06:47:21

mearkat7
Member
Registered: 2023-03-07
Posts: 22

Re: Random GPU crashes amdgpu across 2 different GPUs

Lone_Wolf wrote:
lspci: Unable to load libkmod resources: error -2

Don't like that, though I have no clue what it means.

The page faults in the log at the bottom of your post all come from firefox, can you switch to a different browser for testing if that is involved ?

What WM/DE are you using ?

Welcome to archlinux forums .

That error seemed to go away when I ran as root so maybe a permission issue?

I've moved to chromium now as a backup and it's crashed within the first few minutes of being up so will see if the issue occurs more/less than with firefox, i'm using i3. I will note though most of the page faults come from Xorg but firefox has also been the culprit a few times.

seth wrote:

ENOENT / "404 file not found"

downgraded the recently upgraded amdgpu driver from 23 to 22

How about just removing xf86-video-amdgpu?

And please post your complete system journal for a boot:

sudo journalctl -b | curl -F 'file=@-' 0x0.st

I'll try removing and see how I go.

Complete system journal: http://0x0.st/HiXc.txt

Last edited by mearkat7 (2023-03-08 06:48:56)

Offline

#5 2023-03-08 20:41:44

mearkat7
Member
Registered: 2023-03-07
Posts: 22

Re: Random GPU crashes amdgpu across 2 different GPUs

seth wrote:

ENOENT / "404 file not found"

downgraded the recently upgraded amdgpu driver from 23 to 22

How about just removing xf86-video-amdgpu?

And please post your complete system journal for a boot:

sudo journalctl -b | curl -F 'file=@-' 0x0.st

Looks like xf86-video-amdgpu isn't the issue, I removed it and rebooted and in no time at all after booting I got the error:

Mar 09 06:49:05 revan kernel: amdgpu 0000:0a:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:1 pasid:32769, for process Xorg pid 707 thread Xorg:cs0 pid 708)
Mar 09 06:49:05 revan kernel: amdgpu 0000:0a:00.0: amdgpu:   in page starting at address 0x00008001824af000 from client 0x1b (UTCL2)
Mar 09 06:49:05 revan kernel: amdgpu 0000:0a:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00101031
Mar 09 06:49:05 revan kernel: amdgpu 0000:0a:00.0: amdgpu:          Faulty UTCL2 client ID: TCP (0x8)
Mar 09 06:49:05 revan kernel: amdgpu 0000:0a:00.0: amdgpu:          MORE_FAULTS: 0x1
Mar 09 06:49:05 revan kernel: amdgpu 0000:0a:00.0: amdgpu:          WALKER_ERROR: 0x0
Mar 09 06:49:05 revan kernel: amdgpu 0000:0a:00.0: amdgpu:          PERMISSION_FAULTS: 0x3
Mar 09 06:49:05 revan kernel: amdgpu 0000:0a:00.0: amdgpu:          MAPPING_ERROR: 0x0
Mar 09 06:49:05 revan kernel: amdgpu 0000:0a:00.0: amdgpu:          RW: 0x0
Mar 09 06:49:05 revan kernel: amdgpu 0000:0a:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:1 pasid:32769, for process Xorg pid 707 thread Xorg:cs0 pid 708)
Mar 09 06:49:05 revan kernel: amdgpu 0000:0a:00.0: amdgpu:   in page starting at address 0x00008001824ae000 from client 0x1b (UTCL2)
Mar 09 06:49:05 revan kernel: amdgpu 0000:0a:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000000
Mar 09 06:49:05 revan kernel: amdgpu 0000:0a:00.0: amdgpu:          Faulty UTCL2 client ID: CB/DB (0x0)
Mar 09 06:49:05 revan kernel: amdgpu 0000:0a:00.0: amdgpu:          MORE_FAULTS: 0x0
Mar 09 06:49:05 revan kernel: amdgpu 0000:0a:00.0: amdgpu:          WALKER_ERROR: 0x0
Mar 09 06:49:05 revan kernel: amdgpu 0000:0a:00.0: amdgpu:          PERMISSION_FAULTS: 0x0
Mar 09 06:49:05 revan kernel: amdgpu 0000:0a:00.0: amdgpu:          MAPPING_ERROR: 0x0
Mar 09 06:49:05 revan kernel: amdgpu 0000:0a:00.0: amdgpu:          RW: 0x0
Mar 09 06:49:15 revan kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, but soft recovered

Offline

#6 2023-03-08 21:24:31

seth
Member
Registered: 2012-09-03
Posts: 52,545

Re: Random GPU crashes amdgpu across 2 different GPUs

This leaves us in the ballpark of https://bbs.archlinux.org/viewtopic.php?id=282511&p=5
https://gitlab.freedesktop.org/drm/amd/-/issues/2113 looks similar, but was apparently fixed in 6.1
Do you get this w/ linux-lts?

Offline

#7 2023-03-08 21:47:33

mearkat7
Member
Registered: 2023-03-07
Posts: 22

Re: Random GPU crashes amdgpu across 2 different GPUs

seth wrote:

This leaves us in the ballpark of https://bbs.archlinux.org/viewtopic.php?id=282511&p=5
https://gitlab.freedesktop.org/drm/amd/-/issues/2113 looks similar, but was apparently fixed in 6.1
Do you get this w/ linux-lts?

Those look quite similar. I'd not tried linux-lts up until this point but have switched back to it now and will report back any issues.

Update: linux-lts crashes too, started off doing a few soft crashes that were recovered but eventually led to a hard crash that restarted the computer.

Last edited by mearkat7 (2023-03-09 00:00:43)

Offline

#8 2023-03-08 23:12:10

mearkat7
Member
Registered: 2023-03-07
Posts: 22

Re: Random GPU crashes amdgpu across 2 different GPUs

It may not be relevant but I also noticed when looking through logs one weird thing with the GTT memory.

Mar 08 06:35:52 revan kernel: [drm] amdgpu: 4080M of VRAM memory ready
Mar 08 06:35:52 revan kernel: [drm] amdgpu: 15999M of GTT memory ready.

Most resources I could find on the GTT memory seem to suggest that GTT would be normally less than the VRAM amount.

Offline

#9 2023-03-09 07:31:08

seth
Member
Registered: 2012-09-03
Posts: 52,545

Re: Random GPU crashes amdgpu across 2 different GPUs

amdgpu.gttsize=2048

but it seems to simply default to half your RAM
You could stress it w/ memtest86+, though (you need it to run multiple cycles, probably 24h at least)
However, the problems seem to be a little bit too un-random from faulty RAM.

Offline

#10 2023-03-09 12:07:47

mearkat7
Member
Registered: 2023-03-07
Posts: 22

Re: Random GPU crashes amdgpu across 2 different GPUs

seth wrote:
amdgpu.gttsize=2048

but it seems to simply default to half your RAM
You could stress it w/ memtest86+, though (you need it to run multiple cycles, probably 24h at least)
However, the problems seem to be a little bit too un-random from faulty RAM.

I tried setting the gttsize which I checked worked correctly with /sys/class/drm/card0/device/mem_info_gtt_total but sadly still got a crash quite quickly after the boot.

If I get the chance i'll run memtest86+ when I can, I was curious so tried booting into windows where i'd usually play games and the system had no issues over there so my assumption is that it's a software issue.

That said on the weekend i'll try to take a look at other hardware causes, it occurred to me that the GPU is on a riser and maybe that has gone bad but i'd assume that would occur across any OS the pc is using.

Offline

#11 2023-03-15 15:52:19

UndeadLeech
Member
Registered: 2016-03-07
Posts: 6

Re: Random GPU crashes amdgpu across 2 different GPUs

Unfortunately I can't be of much help, but I have encountered similar issues with the 6900XT:

[ 7729.263070] amdgpu 0000:03:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:2 pasid:32779, for process RelicCardinal.e pid 11164 thread RelicCardinal.e pid 11164)
[ 7729.263077] amdgpu 0000:03:00.0: amdgpu:   in page starting at address 0x00008041c6dff000 from client 0x1b (UTCL2)
[ 7729.263080] amdgpu 0000:03:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00201030
[ 7729.263081] amdgpu 0000:03:00.0: amdgpu: 	 Faulty UTCL2 client ID: TCP (0x8)
[ 7729.263082] amdgpu 0000:03:00.0: amdgpu: 	 MORE_FAULTS: 0x0
[ 7729.263084] amdgpu 0000:03:00.0: amdgpu: 	 WALKER_ERROR: 0x0
[ 7729.263084] amdgpu 0000:03:00.0: amdgpu: 	 PERMISSION_FAULTS: 0x3
[ 7729.263085] amdgpu 0000:03:00.0: amdgpu: 	 MAPPING_ERROR: 0x0
[ 7729.263086] amdgpu 0000:03:00.0: amdgpu: 	 RW: 0x0
[ 7739.415401] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, but soft recovered
[ 7739.423578] amdgpu 0000:03:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:2 pasid:32779, for process RelicCardinal.e pid 11164 thread RelicCardinal.e pid 11164)
[ 7739.423584] amdgpu 0000:03:00.0: amdgpu:   in page starting at address 0x00008041c95ff000 from client 0x1b (UTCL2)
[ 7739.423587] amdgpu 0000:03:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00201030
[ 7739.423588] amdgpu 0000:03:00.0: amdgpu: 	 Faulty UTCL2 client ID: TCP (0x8)
[ 7739.423590] amdgpu 0000:03:00.0: amdgpu: 	 MORE_FAULTS: 0x0
[ 7739.423591] amdgpu 0000:03:00.0: amdgpu: 	 WALKER_ERROR: 0x0
[ 7739.423592] amdgpu 0000:03:00.0: amdgpu: 	 PERMISSION_FAULTS: 0x3
[ 7739.423592] amdgpu 0000:03:00.0: amdgpu: 	 MAPPING_ERROR: 0x0
[ 7739.423593] amdgpu 0000:03:00.0: amdgpu: 	 RW: 0x0
[ 7749.442304] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, but soft recovered
[ 7749.443279] amdgpu 0000:03:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:2 pasid:32779, for process RelicCardinal.e pid 11164 thread RelicCardinal.e pid 11164)
[ 7749.443284] amdgpu 0000:03:00.0: amdgpu:   in page starting at address 0x00008041c95ff000 from client 0x1b (UTCL2)
[ 7749.443286] amdgpu 0000:03:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00201030
[ 7749.443288] amdgpu 0000:03:00.0: amdgpu: 	 Faulty UTCL2 client ID: TCP (0x8)
[ 7749.443289] amdgpu 0000:03:00.0: amdgpu: 	 MORE_FAULTS: 0x0
[ 7749.443290] amdgpu 0000:03:00.0: amdgpu: 	 WALKER_ERROR: 0x0
[ 7749.443290] amdgpu 0000:03:00.0: amdgpu: 	 PERMISSION_FAULTS: 0x3
[ 7749.443291] amdgpu 0000:03:00.0: amdgpu: 	 MAPPING_ERROR: 0x0
[ 7749.443292] amdgpu 0000:03:00.0: amdgpu: 	 RW: 0x0
[ 7754.775365] [drm:amdgpu_dm_atomic_check [amdgpu]] *ERROR* [CRTC:77:crtc-0] hw_done or flip_done timed out
[ 7759.468932] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, but soft recovered

I don't think this has ever happened in Xorg for me, but I can reproduce it reliably in some games.

So I feel like this probably isn't a hardware issue? I don't remember the last time I've played these games but I've run this GPU for about a year without any issues.

Offline

#12 2023-03-16 10:56:00

Lone_Wolf
Forum Moderator
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 12,048

Re: Random GPU crashes amdgpu across 2 different GPUs

That makes atleast 3 people with GCVM_L2_PROTECTION_FAULT_STATUS errrors with videocards in the rx6000 series.
It smells like a kernel module issue, but sofar no one has been able to reproduce the error or pin down what exactly causes this.


UndeadLeech wrote:

but I can reproduce it reliably in some games.

please elaborate.

Last edited by Lone_Wolf (2023-03-16 10:57:40)


Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.


(A works at time B)  && (time C > time B ) ≠  (A works at time C)

Offline

#13 2023-03-16 11:15:20

mearkat7
Member
Registered: 2023-03-07
Posts: 22

Re: Random GPU crashes amdgpu across 2 different GPUs

I've not had time to pull the pc apart to test my riser cable theory but I did go back onto my old arch SSD which was rock solid stable and I've now installed the exact same kernel(6.1.6-3) + kernel api headers(5.18.15-1) to see if that makes any difference as most other kernels have still crashed on me. I played around with a few older linux-firmware versions too with no luck.

Offline

#14 2023-03-17 06:41:24

mearkat7
Member
Registered: 2023-03-07
Posts: 22

Re: Random GPU crashes amdgpu across 2 different GPUs

mearkat7 wrote:

I've not had time to pull the pc apart to test my riser cable theory but I did go back onto my old arch SSD which was rock solid stable and I've now installed the exact same kernel(6.1.6-3) + kernel api headers(5.18.15-1) to see if that makes any difference as most other kernels have still crashed on me. I played around with a few older linux-firmware versions too with no luck.

Update on the older kernel and kernel api headers, seemed great for a few hours but then sadly encountered the freeze again. Hoping to have some time this weekend to test the riser.

Offline

#15 2023-03-18 12:21:26

mearkat7
Member
Registered: 2023-03-07
Posts: 22

Re: Random GPU crashes amdgpu across 2 different GPUs

I apologise for 3 posts in a row but just trying to add as much info as possible.

Firstly I have now tried a different riser cable just to be sure and still getting the same freezes.

Prior to March 1st I never ever got these crashes/freezes despite running an amd gpu for the past 2.5 years. I've compiled a list below of a few of my pacman logs in the days leading up to the first crash. The main 2 packages that were upgraded in the days prior were xf86-video-amdgpu (22.0.0-1 -> 23.0.0-1) and linux (6.1.12.arch1-1 -> 6.2.1.arch1-1). Despite me reverting to these packages the freezes still occur which seems very strange.

Logs:

Packages changed on Feb 27th(2 days before first crash):
    3564 [2023-02-27T06:48:14+1100] [PACMAN] Running 'pacman -Syu'
    3565 [2023-02-27T06:48:14+1100] [PACMAN] synchronizing package lists
    3566 [2023-02-27T06:48:16+1100] [PACMAN] starting full system upgrade
    3567 [2023-02-27T06:48:23+1100] [ALPM] transaction started
    3568 [2023-02-27T06:48:23+1100] [ALPM] warning: /etc/pacman.d/mirrorlist installed as /etc/pacman.d/mirrorlist.pacnew
    3569 [2023-02-27T06:48:23+1100] [ALPM] upgraded pacman-mirrorlist (20221204-1 -> 20230226-1)
    3570 [2023-02-27T06:48:23+1100] [ALPM] upgraded zstd (1.5.2-8 -> 1.5.4-1)
    3571 [2023-02-27T06:48:23+1100] [ALPM] upgraded sqlite (3.40.1-1 -> 3.41.0-1)
    3572 [2023-02-27T06:48:23+1100] [ALPM] upgraded archlinux-keyring (20230130-1 -> 20230225-1)
    3573 [2023-02-27T06:48:23+1100] [ALPM-SCRIPTLET] ==> Appending keys from archlinux.gpg...
    3574 [2023-02-27T06:48:24+1100] [ALPM-SCRIPTLET] ==> Updating trust database...
    3575 [2023-02-27T06:48:24+1100] [ALPM-SCRIPTLET] gpg: next trustdb check due at 2023-07-12
    3576 [2023-02-27T06:48:24+1100] [ALPM-SCRIPTLET] ==> Updating trust database...
    3577 [2023-02-27T06:48:24+1100] [ALPM-SCRIPTLET] gpg: next trustdb check due at 2023-07-12
    3578 [2023-02-27T06:48:24+1100] [ALPM] upgraded dav1d (1.0.0-1 -> 1.1.0-1)
    3579 [2023-02-27T06:48:24+1100] [ALPM] upgraded file (5.44-2 -> 5.44-3)
    3580 [2023-02-27T06:48:24+1100] [ALPM] upgraded libcups (1:2.4.2-5 -> 1:2.4.2-6)
    3581 [2023-02-27T06:48:24+1100] [ALPM] upgraded hicolor-icon-theme (0.17-2 -> 0.17-3)
    3582 [2023-02-27T06:48:24+1100] [ALPM] upgraded galculator (2.1.4-7 -> 2.1.4-8)
    3583 [2023-02-27T06:48:25+1100] [ALPM] upgraded gegl (0.4.42-1 -> 0.4.42-2)
    3584 [2023-02-27T06:48:25+1100] [ALPM] upgraded libpaper (1.1.28-2 -> 2.0.10-1)
    3585 [2023-02-27T06:48:25+1100] [ALPM] upgraded ghostscript (10.0.0-4 -> 10.0.0-5)
    3586 [2023-02-27T06:48:25+1100] [ALPM] upgraded hwloc (2.8.0-1 -> 2.9.0-1)
    3587 [2023-02-27T06:48:25+1100] [ALPM] upgraded iproute2 (6.2.0-1 -> 6.2.0-2)
    3588 [2023-02-27T06:48:25+1100] [ALPM] upgraded l-smash (2.14.5-2 -> 2.14.5-3)
    3589 [2023-02-27T06:48:25+1100] [ALPM] upgraded libavc1394 (0.5.4-4 -> 0.5.4-5)
    3590 [2023-02-27T06:48:25+1100] [ALPM] upgraded shaderc (2022.4-1 -> 2023.2-1)
    3591 [2023-02-27T06:48:25+1100] [ALPM] upgraded libplacebo (5.229.1-2 -> 5.229.2-1)
    3592 [2023-02-27T06:48:25+1100] [ALPM] upgraded xf86-video-amdgpu (22.0.0-1 -> 23.0.0-1)

Packages changed on Feb 28th(day before the first crash):
    3607 [2023-02-28T07:25:44+1100] [PACMAN] Running 'pacman -Syu'
    3608 [2023-02-28T07:25:44+1100] [PACMAN] synchronizing package lists
    3609 [2023-02-28T07:25:47+1100] [PACMAN] starting full system upgrade
    3610 [2023-02-28T07:26:05+1100] [ALPM] running '60-mkinitcpio-remove.hook'...
    3611 [2023-02-28T07:26:05+1100] [ALPM] transaction started
    3612 [2023-02-28T07:26:05+1100] [ALPM] upgraded audit (3.0.9-2 -> 3.1-1)
    3613 [2023-02-28T07:26:05+1100] [ALPM] upgraded glib2 (2.74.5-1 -> 2.74.6-1)
    3614 [2023-02-28T07:26:05+1100] [ALPM] upgraded libjpeg-turbo (2.1.5-2 -> 2.1.5.1-1)
    3615 [2023-02-28T07:26:05+1100] [ALPM] upgraded libwacom (2.6.0-1 -> 2.6.0-2)
    3616 [2023-02-28T07:26:06+1100] [ALPM] upgraded linux (6.1.12.arch1-1 -> 6.2.1.arch1-1)
    3617 [2023-02-28T07:26:06+1100] [ALPM] upgraded openmpi (4.1.4-4 -> 4.1.5-1)
    3618 [2023-02-28T07:26:06+1100] [ALPM] upgraded sudo (1.9.13-1 -> 1.9.13.p1-1)

    - installed and then removed rust, dotnet, dotnetsdk xwinwrap, xwinwrap-bin and gifsicle
    - installed rustup, aws-session-manager-plugin

Packages changed on March 1st(day of the crash):
    3728 [2023-03-01T06:39:02+1100] [PACMAN] Running 'pacman -Syu'
    3729 [2023-03-01T06:39:02+1100] [PACMAN] synchronizing package lists
    3730 [2023-03-01T06:39:05+1100] [PACMAN] starting full system upgrade
    3731 [2023-03-01T06:39:10+1100] [ALPM] transaction started
    3732 [2023-03-01T06:39:10+1100] [ALPM] upgraded fuse-common (3.13.1-1 -> 3.14.0-1)
    3733 [2023-03-01T06:39:10+1100] [ALPM] upgraded fuse3 (3.13.1-1 -> 3.14.0-1)
    3734 [2023-03-01T06:39:10+1100] [ALPM] upgraded iso-codes (4.12.0-1 -> 4.13.0-1)
    3735 [2023-03-01T06:39:10+1100] [ALPM] upgraded libass (0.17.0-1 -> 0.17.1-1)
    3736 [2023-03-01T06:39:10+1100] [ALPM] upgraded make (4.4-1 -> 4.4.1-1)
    3744 [2023-03-01T12:46:24+1100] [PACMAN] Running 'pacman -U --noconfirm --config /etc/pacman.conf -- /home/luke/.cache/yay/aws-sam-cli-bin/     aws-sam-cli-bin-1.75.0-1-x86_64.pkg.tar.zst'
    3749 [2023-03-01T12:46:35+1100] [PACMAN] Running 'pacman -U --noconfirm --config /etc/pacman.conf -- /home/luke/.cache/yay/postman-bin/post     man-bin-10.11.1-1-x86_64.pkg.tar.zst'
    3756 [2023-03-01T17:07:21+1100] [PACMAN] Running 'pacman -S solaar'
    3757 [2023-03-01T17:07:23+1100] [ALPM] transaction started
    3758 [2023-03-01T17:07:23+1100] [ALPM] installed dbus-python (1.2.18-4)
    3759 [2023-03-01T17:07:23+1100] [ALPM] installed python-evdev (1.6.1-1)
    3760 [2023-03-01T17:07:23+1100] [ALPM] installed python-typing_extensions (4.5.0-1)
    3761 [2023-03-01T17:07:23+1100] [ALPM] installed python-hid-parser (0.0.3-1)
    3762 [2023-03-01T17:07:23+1100] [ALPM] installed python-pyudev (0.24.0-2)
    3763 [2023-03-01T17:07:23+1100] [ALPM] installed python-xlib (0.33-1)
    3764 [2023-03-01T17:07:23+1100] [ALPM] installed solaar (1.1.8-1)

Offline

#16 2023-03-18 13:00:21

seth
Member
Registered: 2012-09-03
Posts: 52,545

Re: Random GPU crashes amdgpu across 2 different GPUs

When did you update linux-firmware and amd-ucode (both updated in the repos 2023-02-17)

Offline

#17 2023-03-18 19:29:47

mearkat7
Member
Registered: 2023-03-07
Posts: 22

Re: Random GPU crashes amdgpu across 2 different GPUs

seth wrote:

When did you update linux-firmware and amd-ucode (both updated in the repos 2023-02-17)

Both were upgraded on the 19th of Feb for me:

[2023-02-19T21:12:44+1100] [ALPM] upgraded amd-ucode (20230117.7e4f0ed-1 -> 20230210.bf4115c-1)
[2023-02-19T21:12:46+1100] [ALPM] upgraded linux-firmware (20230117.7e4f0ed-1 -> 20230210.bf4115c-1)

Offline

#18 2023-03-18 20:24:37

seth
Member
Registered: 2012-09-03
Posts: 52,545

Re: Random GPU crashes amdgpu across 2 different GPUs

Did you reboot between those updates and March 1st?
Next to those packages and the kernel, I'd look at mesa.
Unless the crash is always triggered by some gegl client (gimp?)…

Offline

#19 2023-03-18 20:38:38

mearkat7
Member
Registered: 2023-03-07
Posts: 22

Re: Random GPU crashes amdgpu across 2 different GPUs

seth wrote:

Did you reboot between those updates and March 1st?
Next to those packages and the kernel, I'd look at mesa.
Unless the crash is always triggered by some gegl client (gimp?)…

I would have, I normally shutdown every night unless I forget. I do use gimp maybe a few times a week but wouldn't normally be open.

On boot I have firefox, nm-applet, udiskie, feh, firefox, picom, termite, dropbox and pasystray run.

Last night I tried reverting mesa, linux and xf86-video-amdgpu to the previous versions listed in the pacman update above but sadly still seemed to happen fairly quickly.

EDIT: come to think of it termite is the only application I really always have running, seems unlikely but I will try something else for now.

Last edited by mearkat7 (2023-03-18 20:40:57)

Offline

#20 2023-03-18 20:53:51

seth
Member
Registered: 2012-09-03
Posts: 52,545

Re: Random GPU crashes amdgpu across 2 different GPUs

Also, you did try w/o xf86--video-amdgpu, did you?
You should cut that out as well, just to eliminate an unnecessary variable.

Offline

#21 2023-03-18 20:56:04

mearkat7
Member
Registered: 2023-03-07
Posts: 22

Re: Random GPU crashes amdgpu across 2 different GPUs

seth wrote:

Also, you did try w/o xf86--video-amdgpu, did you?
You should cut that out as well, just to eliminate an unnecessary variable.

I did earlier on, did the exact same crash unfortunately.

Offline

#22 2023-03-20 04:06:00

UndeadLeech
Member
Registered: 2016-03-07
Posts: 6

Re: Random GPU crashes amdgpu across 2 different GPUs

>> but I can reproduce it reliably in some games.
> please elaborate.

Sorry for the delay, I haven't been following this thread. But I reliably get these errors every time I load into a game in AoE IV.
Right when the match loads up everything freezes, these errors pop up in dmesg, then it recovers.

Offline

#23 2023-03-20 05:42:16

mearkat7
Member
Registered: 2023-03-07
Posts: 22

Re: Random GPU crashes amdgpu across 2 different GPUs

UndeadLeech wrote:

>> but I can reproduce it reliably in some games.
> please elaborate.

Sorry for the delay, I haven't been following this thread. But I reliably get these errors every time I load into a game in AoE IV.
Right when the match loads up everything freezes, these errors pop up in dmesg, then it recovers.

Have you tried the latest kernel (6.2.7, came out earlier today)? It appears to have some amd fixes, i've been stable since upgrading but will see how it goes over the next few days.

Offline

#24 2023-03-22 21:42:53

mearkat7
Member
Registered: 2023-03-07
Posts: 22

Re: Random GPU crashes amdgpu across 2 different GPUs

Update:
I hesitate to say this is "solved" because it is not a real fix but after nothing seemed to be working I've switched over to wayland/hyprland and the system has been stable ever since.

After it has been a full 7 days of stablility i'll update again but I doubt i'll be back on i3/Xorg unless I encounter more breaking issues like the above freezes/crashes.

Offline

#25 2023-03-27 03:56:57

mearkat7
Member
Registered: 2023-03-07
Posts: 22

Re: Random GPU crashes amdgpu across 2 different GPUs

mearkat7 wrote:

Update:
I hesitate to say this is "solved" because it is not a real fix but after nothing seemed to be working I've switched over to wayland/hyprland and the system has been stable ever since.

After it has been a full 7 days of stablility i'll update again but I doubt i'll be back on i3/Xorg unless I encounter more breaking issues like the above freezes/crashes.

Not solved at all. Strangely it was stable for about a week but now i'm getting the same crashes in hyprland but it appears wayland is less able to recover from the crashes so end up being worse.

Mar 27 14:52:14 revan kernel: amdgpu 0000:0a:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:1 pasid:32770, for process Hyprland pid 1029 thread Hyprland:cs0 pid 1044)
Mar 27 14:52:14 revan kernel: amdgpu 0000:0a:00.0: amdgpu:   in page starting at address 0x0000800132803000 from client 0x1b (UTCL2)
Mar 27 14:52:14 revan kernel: amdgpu 0000:0a:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00101030
Mar 27 14:52:14 revan kernel: amdgpu 0000:0a:00.0: amdgpu:          Faulty UTCL2 client ID: TCP (0x8)
Mar 27 14:52:14 revan kernel: amdgpu 0000:0a:00.0: amdgpu:          MORE_FAULTS: 0x0
Mar 27 14:52:14 revan kernel: amdgpu 0000:0a:00.0: amdgpu:          WALKER_ERROR: 0x0
Mar 27 14:52:14 revan kernel: amdgpu 0000:0a:00.0: amdgpu:          PERMISSION_FAULTS: 0x3
Mar 27 14:52:14 revan kernel: amdgpu 0000:0a:00.0: amdgpu:          MAPPING_ERROR: 0x0
Mar 27 14:52:14 revan kernel: amdgpu 0000:0a:00.0: amdgpu:          RW: 0x0
Mar 27 14:52:24 revan kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, signaled seq=135723, emitted seq=135725
Mar 27 14:52:24 revan kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Hyprland pid 1029 thread Hyprland:cs0 pid 1044
Mar 27 14:52:25 revan kernel: amdgpu 0000:0a:00.0: amdgpu: SMU driver if version not matched
Mar 27 14:52:25 revan kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!

Offline

Board footer

Powered by FluxBB