Jan 23 02:47:00 vivobook kernel: wlp1s0: deauthenticating from c0:c9:e3:3a:4d:4c by local choice (Reason: 3=DEAUTH_LEAVING) Jan 23 02:47:00 vivobook kernel: PM: suspend entry (s2idle) Jan 23 02:47:00 vivobook kernel: Filesystems sync: 0.005 seconds Jan 23 10:35:36 vivobook kernel: Bluetooth: hci0: Timed out waiting for suspend events Jan 23 10:35:36 vivobook kernel: Bluetooth: hci0: Suspend timeout bit: 6 Jan 23 10:35:36 vivobook kernel: Bluetooth: hci0: Suspend notifier action (3) failed: -110 Jan 23 10:35:36 vivobook kernel: Freezing user space processes ... (elapsed 0.002 seconds) done. Jan 23 10:35:36 vivobook kernel: OOM killer disabled. Jan 23 10:35:36 vivobook kernel: Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. Jan 23 10:35:36 vivobook kernel: printk: Suspending console(s) (use no_console_suspend to debug) Jan 23 10:35:36 vivobook kernel: ACPI: EC: interrupt blocked Jan 23 10:35:36 vivobook kernel: ACPI: EC: interrupt unblocked Jan 23 10:35:36 vivobook kernel: pci 0000:00:00.2: can't derive routing for PCI INT A Jan 23 10:35:36 vivobook kernel: pci 0000:00:00.2: PCI INT A: no GSI Jan 23 10:35:36 vivobook kernel: [drm] PCIE GART of 1024M enabled. Jan 23 10:35:36 vivobook kernel: [drm] PTB located at 0x000000F400900000 Jan 23 10:35:36 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: SMU is resuming... Jan 23 10:35:36 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: dpm has been disabled Jan 23 10:35:36 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: SMU is resumed successfully! Jan 23 10:35:36 vivobook kernel: [drm] DMUB hardware initialized: version=0x0101001C Jan 23 10:35:36 vivobook kernel: nvme 0000:02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0009 address=0xce146000 flags=0x0000] Jan 23 10:35:36 vivobook kernel: nvme nvme0: 8/0/0 default/read/poll queues Jan 23 10:35:36 vivobook kernel: ata1: SATA link down (SStatus 0 SControl 300) Jan 23 10:35:36 vivobook kernel: ata2: SATA link down (SStatus 0 SControl 300) Jan 23 10:35:36 vivobook kernel: amdgpu 0000:03:00.0: [drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring sdma0 test failed (-110) Jan 23 10:35:36 vivobook kernel: [drm:amdgpu_device_ip_resume_phase2 [amdgpu]] *ERROR* resume of IP block failed -110 Jan 23 10:35:36 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: amdgpu_device_ip_resume failed (-110). Jan 23 10:35:36 vivobook kernel: PM: dpm_run_callback(): pci_pm_resume+0x0/0xe0 returns -110 Jan 23 10:35:36 vivobook kernel: amdgpu 0000:03:00.0: PM: failed to resume async: error -110 Jan 23 10:35:36 vivobook kernel: OOM killer enabled. Jan 23 10:35:36 vivobook kernel: Restarting tasks ... done. Jan 23 10:35:36 vivobook kernel: PM: suspend exit Jan 23 10:35:36 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: couldn't schedule ib on ring Jan 23 10:35:36 vivobook kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22) Jan 23 10:35:36 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: couldn't schedule ib on ring Jan 23 10:35:36 vivobook kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22) Jan 23 10:35:36 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:6 pasid:32793, for process kscreenlocker_g pid 6644 thread kscreenloc:cs0 pid 6655) Jan 23 10:35:36 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: couldn't schedule ib on ring Jan 23 10:35:36 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: in page starting at address 0x000080010bc80000 from IH client 0x1b (UTCL2) Jan 23 10:35:36 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00641051 Jan 23 10:35:36 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: Faulty UTCL2 client ID: TCP (0x8) Jan 23 10:35:36 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: MORE_FAULTS: 0x1 Jan 23 10:35:36 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: WALKER_ERROR: 0x0 Jan 23 10:35:36 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: PERMISSION_FAULTS: 0x5 Jan 23 10:35:36 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: MAPPING_ERROR: 0x0 Jan 23 10:35:36 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: RW: 0x1 Jan 23 10:35:36 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:6 pasid:32793, for process kscreenlocker_g pid 6644 thread kscreenloc:cs0 pid 6655) Jan 23 10:35:36 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: in page starting at address 0x000080010bc81000 from IH client 0x1b (UTCL2) Jan 23 10:35:36 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00641051 Jan 23 10:35:36 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: Faulty UTCL2 client ID: TCP (0x8) Jan 23 10:35:36 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: MORE_FAULTS: 0x1 Jan 23 10:35:36 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: WALKER_ERROR: 0x0 Jan 23 10:35:36 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: PERMISSION_FAULTS: 0x5 Jan 23 10:35:36 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: MAPPING_ERROR: 0x0 Jan 23 10:35:36 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: RW: 0x1 Jan 23 10:35:36 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:6 pasid:32793, for process kscreenlocker_g pid 6644 thread kscreenloc:cs0 pid 6655) Jan 23 10:35:36 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: in page starting at address 0x000080010bc82000 from IH client 0x1b (UTCL2) Jan 23 10:35:36 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00641051 Jan 23 10:35:36 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: Faulty UTCL2 client ID: TCP (0x8) Jan 23 10:35:36 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: MORE_FAULTS: 0x1 Jan 23 10:35:36 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: WALKER_ERROR: 0x0 Jan 23 10:35:36 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: PERMISSION_FAULTS: 0x5 Jan 23 10:35:36 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: MAPPING_ERROR: 0x0 Jan 23 10:35:36 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: RW: 0x1 Jan 23 10:35:36 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:6 pasid:32793, for process kscreenlocker_g pid 6644 thread kscreenloc:cs0 pid 6655) Jan 23 10:35:36 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: in page starting at address 0x000080010bc84000 from IH client 0x1b (UTCL2) Jan 23 10:35:36 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00641051 Jan 23 10:35:36 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: Faulty UTCL2 client ID: TCP (0x8) Jan 23 10:35:36 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: MORE_FAULTS: 0x1 Jan 23 10:35:36 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: WALKER_ERROR: 0x0 Jan 23 10:35:36 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: PERMISSION_FAULTS: 0x5 Jan 23 10:35:36 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: MAPPING_ERROR: 0x0 Jan 23 10:35:36 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: RW: 0x1 Jan 23 10:35:36 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:6 pasid:32793, for process kscreenlocker_g pid 6644 thread kscreenloc:cs0 pid 6655) Jan 23 10:35:36 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: in page starting at address 0x000080010bc83000 from IH client 0x1b (UTCL2) Jan 23 10:35:36 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00641051 Jan 23 10:35:36 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: Faulty UTCL2 client ID: TCP (0x8) Jan 23 10:35:36 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: MORE_FAULTS: 0x1 Jan 23 10:35:36 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: WALKER_ERROR: 0x0 Jan 23 10:35:36 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: PERMISSION_FAULTS: 0x5 Jan 23 10:35:36 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: MAPPING_ERROR: 0x0 Jan 23 10:35:36 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: RW: 0x1 Jan 23 10:35:36 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:6 pasid:32793, for process kscreenlocker_g pid 6644 thread kscreenloc:cs0 pid 6655) Jan 23 10:35:36 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: in page starting at address 0x000080010bc85000 from IH client 0x1b (UTCL2) Jan 23 10:35:36 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00641051 Jan 23 10:35:36 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: Faulty UTCL2 client ID: TCP (0x8) Jan 23 10:35:36 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: MORE_FAULTS: 0x1 Jan 23 10:35:36 vivobook kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22) Jan 23 10:35:36 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: WALKER_ERROR: 0x0 Jan 23 10:35:36 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: PERMISSION_FAULTS: 0x5 Jan 23 10:35:36 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: MAPPING_ERROR: 0x0 Jan 23 10:35:36 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: RW: 0x1 Jan 23 10:35:36 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:6 pasid:32793, for process kscreenlocker_g pid 6644 thread kscreenloc:cs0 pid 6655) Jan 23 10:35:36 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: in page starting at address 0x000080010bc86000 from IH client 0x1b (UTCL2) Jan 23 10:35:36 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00641051 Jan 23 10:35:36 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: Faulty UTCL2 client ID: TCP (0x8) Jan 23 10:35:36 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: MORE_FAULTS: 0x1 Jan 23 10:35:36 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: WALKER_ERROR: 0x0 Jan 23 10:35:36 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: PERMISSION_FAULTS: 0x5 Jan 23 10:35:36 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: MAPPING_ERROR: 0x0 Jan 23 10:35:36 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: RW: 0x1 Jan 23 10:35:36 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:6 pasid:32793, for process kscreenlocker_g pid 6644 thread kscreenloc:cs0 pid 6655) Jan 23 10:35:36 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: in page starting at address 0x000080010bc87000 from IH client 0x1b (UTCL2) Jan 23 10:35:36 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00641051 Jan 23 10:35:36 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: Faulty UTCL2 client ID: TCP (0x8) Jan 23 10:35:36 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: MORE_FAULTS: 0x1 Jan 23 10:35:36 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: WALKER_ERROR: 0x0 Jan 23 10:35:36 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: PERMISSION_FAULTS: 0x5 Jan 23 10:35:36 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: MAPPING_ERROR: 0x0 Jan 23 10:35:36 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: RW: 0x1 Jan 23 10:35:36 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:6 pasid:32793, for process kscreenlocker_g pid 6644 thread kscreenloc:cs0 pid 6655) Jan 23 10:35:36 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: in page starting at address 0x000080010bc88000 from IH client 0x1b (UTCL2) Jan 23 10:35:36 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00641051 Jan 23 10:35:36 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: Faulty UTCL2 client ID: TCP (0x8) Jan 23 10:35:36 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: MORE_FAULTS: 0x1 Jan 23 10:35:36 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: WALKER_ERROR: 0x0 Jan 23 10:35:36 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: PERMISSION_FAULTS: 0x5 Jan 23 10:35:36 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: MAPPING_ERROR: 0x0 Jan 23 10:35:36 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: RW: 0x1 Jan 23 10:35:36 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:6 pasid:32793, for process kscreenlocker_g pid 6644 thread kscreenloc:cs0 pid 6655) Jan 23 10:35:36 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: in page starting at address 0x000080010bc8a000 from IH client 0x1b (UTCL2) Jan 23 10:35:36 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00641051 Jan 23 10:35:36 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: Faulty UTCL2 client ID: TCP (0x8) Jan 23 10:35:36 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: MORE_FAULTS: 0x1 Jan 23 10:35:36 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: WALKER_ERROR: 0x0 Jan 23 10:35:36 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: PERMISSION_FAULTS: 0x5 Jan 23 10:35:36 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: MAPPING_ERROR: 0x0 Jan 23 10:35:36 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: RW: 0x1 Jan 23 10:35:36 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: couldn't schedule ib on ring Jan 23 10:35:36 vivobook kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22) Jan 23 10:35:36 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: couldn't schedule ib on ring Jan 23 10:35:36 vivobook kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22) Jan 23 10:35:36 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: couldn't schedule ib on ring Jan 23 10:35:36 vivobook kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22) Jan 23 10:35:36 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: couldn't schedule ib on ring Jan 23 10:35:36 vivobook kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22) Jan 23 10:35:36 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: couldn't schedule ib on ring Jan 23 10:35:36 vivobook kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22) Jan 23 10:35:36 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: couldn't schedule ib on ring Jan 23 10:35:36 vivobook kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22) Jan 23 10:35:36 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: couldn't schedule ib on ring Jan 23 10:35:36 vivobook kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22) Jan 23 10:35:36 vivobook kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22) Jan 23 10:35:41 vivobook kernel: [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* Waiting for fences timed out! Jan 23 10:35:41 vivobook kernel: wlp1s0: authenticate with c0:c9:e3:3a:4d:4c Jan 23 10:35:41 vivobook kernel: wlp1s0: send auth to c0:c9:e3:3a:4d:4c (try 1/3) Jan 23 10:35:42 vivobook kernel: wlp1s0: authenticated Jan 23 10:35:42 vivobook kernel: wlp1s0: associate with c0:c9:e3:3a:4d:4c (try 1/3) Jan 23 10:35:42 vivobook kernel: wlp1s0: RX AssocResp from c0:c9:e3:3a:4d:4c (capab=0x11 status=0 aid=2) Jan 23 10:35:42 vivobook kernel: wlp1s0: associated Jan 23 10:35:42 vivobook kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlp1s0: link becomes ready Jan 23 10:35:46 vivobook kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, but soft recovered Jan 23 10:35:47 vivobook kernel: [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* Waiting for fences timed out! Jan 23 10:35:47 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: couldn't schedule ib on ring Jan 23 10:35:47 vivobook kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22) Jan 23 10:36:07 vivobook kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=202547, emitted seq=202550 Jan 23 10:36:07 vivobook kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process kscreenlocker_g pid 6644 thread kscreenloc:cs0 pid 6655 Jan 23 10:36:07 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: GPU reset begin! Jan 23 10:36:07 vivobook kernel: [drm] free PSP TMR buffer Jan 23 10:36:07 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: MODE2 reset Jan 23 10:36:07 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: GPU reset succeeded, trying to resume Jan 23 10:36:07 vivobook kernel: [drm] PCIE GART of 1024M enabled. Jan 23 10:36:07 vivobook kernel: [drm] PTB located at 0x000000F400900000 Jan 23 10:36:07 vivobook kernel: [drm] PSP is resuming... Jan 23 10:36:07 vivobook kernel: [drm] reserve 0x400000 from 0xf41f800000 for PSP TMR Jan 23 10:36:07 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: RAS: optional ras ta ucode is not available Jan 23 10:36:07 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: RAP: optional rap ta ucode is not available Jan 23 10:36:07 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: SECUREDISPLAY: securedisplay ta ucode is not available Jan 23 10:36:07 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: SMU is resuming... Jan 23 10:36:07 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: dpm has been disabled Jan 23 10:36:07 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: SMU is resumed successfully! Jan 23 10:36:07 vivobook kernel: [drm] DMUB hardware initialized: version=0x0101001C Jan 23 10:36:08 vivobook kernel: [drm] kiq ring mec 2 pipe 1 q 0 Jan 23 10:36:08 vivobook kernel: [drm] VCN decode and encode initialized successfully(under DPG Mode). Jan 23 10:36:08 vivobook kernel: [drm] JPEG decode initialized successfully. Jan 23 10:36:08 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: ring gfx uses VM inv eng 0 on hub 0 Jan 23 10:36:08 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0 Jan 23 10:36:08 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0 Jan 23 10:36:08 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 5 on hub 0 Jan 23 10:36:08 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 6 on hub 0 Jan 23 10:36:08 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 7 on hub 0 Jan 23 10:36:08 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 8 on hub 0 Jan 23 10:36:08 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 9 on hub 0 Jan 23 10:36:08 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 10 on hub 0 Jan 23 10:36:08 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: ring kiq_2.1.0 uses VM inv eng 11 on hub 0 Jan 23 10:36:08 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: ring sdma0 uses VM inv eng 0 on hub 1 Jan 23 10:36:08 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: ring vcn_dec uses VM inv eng 1 on hub 1 Jan 23 10:36:08 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: ring vcn_enc0 uses VM inv eng 4 on hub 1 Jan 23 10:36:08 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: ring vcn_enc1 uses VM inv eng 5 on hub 1 Jan 23 10:36:08 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: ring jpeg_dec uses VM inv eng 6 on hub 1 Jan 23 10:36:08 vivobook kernel: [drm] Fence fallback timer expired on ring gfx Jan 23 10:36:09 vivobook kernel: [drm] Fence fallback timer expired on ring comp_1.0.0 Jan 23 10:36:09 vivobook kernel: [drm] Fence fallback timer expired on ring comp_1.1.0 Jan 23 10:36:10 vivobook kernel: [drm] Fence fallback timer expired on ring comp_1.2.0 Jan 23 10:36:10 vivobook kernel: [drm] Fence fallback timer expired on ring comp_1.3.0 Jan 23 10:36:11 vivobook kernel: [drm] Fence fallback timer expired on ring comp_1.0.1 Jan 23 10:36:11 vivobook kernel: [drm] Fence fallback timer expired on ring comp_1.1.1 Jan 23 10:36:12 vivobook kernel: [drm] Fence fallback timer expired on ring comp_1.2.1 Jan 23 10:36:12 vivobook kernel: [drm] Fence fallback timer expired on ring comp_1.3.1 Jan 23 10:36:13 vivobook kernel: [drm] Fence fallback timer expired on ring sdma0 Jan 23 10:36:13 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: recover vram bo from shadow start Jan 23 10:36:13 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: recover vram bo from shadow done Jan 23 10:36:13 vivobook kernel: [drm] Skip scheduling IBs! Jan 23 10:36:13 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: GPU reset(4) succeeded! Jan 23 10:36:13 vivobook kernel: [drm] Fence fallback timer expired on ring gfx Jan 23 10:36:13 vivobook kernel: [drm] Fence fallback timer expired on ring sdma0 Jan 23 10:36:14 vivobook kernel: [drm] Fence fallback timer expired on ring sdma0 Jan 23 10:36:23 vivobook kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=202552, emitted seq=202555 Jan 23 10:36:23 vivobook kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process spotify pid 6803 thread debug.log :cs0 pid 6807 Jan 23 10:36:23 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: GPU reset begin! Jan 23 10:36:23 vivobook kernel: [drm] free PSP TMR buffer Jan 23 10:36:23 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: MODE2 reset Jan 23 10:36:23 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: GPU reset succeeded, trying to resume Jan 23 10:36:23 vivobook kernel: [drm] PCIE GART of 1024M enabled. Jan 23 10:36:23 vivobook kernel: [drm] PTB located at 0x000000F400900000 Jan 23 10:36:23 vivobook kernel: [drm] PSP is resuming... Jan 23 10:36:23 vivobook kernel: [drm] reserve 0x400000 from 0xf41f800000 for PSP TMR Jan 23 10:36:23 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: RAS: optional ras ta ucode is not available Jan 23 10:36:23 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: RAP: optional rap ta ucode is not available Jan 23 10:36:23 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: SECUREDISPLAY: securedisplay ta ucode is not available Jan 23 10:36:23 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: SMU is resuming... Jan 23 10:36:23 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: dpm has been disabled Jan 23 10:36:23 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: SMU is resumed successfully! Jan 23 10:36:23 vivobook kernel: [drm] DMUB hardware initialized: version=0x0101001C Jan 23 10:36:24 vivobook kernel: [drm] kiq ring mec 2 pipe 1 q 0 Jan 23 10:36:24 vivobook kernel: [drm] VCN decode and encode initialized successfully(under DPG Mode). Jan 23 10:36:24 vivobook kernel: [drm] JPEG decode initialized successfully. Jan 23 10:36:24 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: ring gfx uses VM inv eng 0 on hub 0 Jan 23 10:36:24 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0 Jan 23 10:36:24 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0 Jan 23 10:36:24 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 5 on hub 0 Jan 23 10:36:24 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 6 on hub 0 Jan 23 10:36:24 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 7 on hub 0 Jan 23 10:36:24 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 8 on hub 0 Jan 23 10:36:24 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 9 on hub 0 Jan 23 10:36:24 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 10 on hub 0 Jan 23 10:36:24 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: ring kiq_2.1.0 uses VM inv eng 11 on hub 0 Jan 23 10:36:24 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: ring sdma0 uses VM inv eng 0 on hub 1 Jan 23 10:36:24 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: ring vcn_dec uses VM inv eng 1 on hub 1 Jan 23 10:36:24 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: ring vcn_enc0 uses VM inv eng 4 on hub 1 Jan 23 10:36:24 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: ring vcn_enc1 uses VM inv eng 5 on hub 1 Jan 23 10:36:24 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: ring jpeg_dec uses VM inv eng 6 on hub 1 Jan 23 10:36:24 vivobook kernel: [drm] Fence fallback timer expired on ring gfx Jan 23 10:36:25 vivobook kernel: [drm] Fence fallback timer expired on ring comp_1.0.0 Jan 23 10:36:25 vivobook kernel: [drm] Fence fallback timer expired on ring comp_1.1.0 Jan 23 10:36:26 vivobook kernel: [drm] Fence fallback timer expired on ring comp_1.2.0 Jan 23 10:36:26 vivobook kernel: [drm] Fence fallback timer expired on ring comp_1.3.0 Jan 23 10:36:27 vivobook kernel: [drm] Fence fallback timer expired on ring comp_1.0.1 Jan 23 10:36:27 vivobook kernel: [drm] Fence fallback timer expired on ring comp_1.1.1 Jan 23 10:36:28 vivobook kernel: [drm] Fence fallback timer expired on ring comp_1.2.1 Jan 23 10:36:28 vivobook kernel: [drm] Fence fallback timer expired on ring comp_1.3.1 Jan 23 10:36:29 vivobook kernel: [drm] Fence fallback timer expired on ring sdma0 Jan 23 10:36:29 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: recover vram bo from shadow start Jan 23 10:36:29 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: recover vram bo from shadow done Jan 23 10:36:29 vivobook kernel: [drm] Skip scheduling IBs! Jan 23 10:36:29 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: GPU reset(6) succeeded! Jan 23 10:36:29 vivobook kernel: [drm] Fence fallback timer expired on ring sdma0 Jan 23 10:36:29 vivobook kernel: [drm] Fence fallback timer expired on ring gfx Jan 23 10:36:29 vivobook kernel: gmc_v9_0_process_interrupt: 21 callbacks suppressed Jan 23 10:36:29 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:6 pasid:32793, for process kscreenlocker_g pid 6644 thread kscreenloc:cs0 pid 6655) Jan 23 10:36:29 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: in page starting at address 0x000080010bc8f000 from IH client 0x1b (UTCL2) Jan 23 10:36:29 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x004C0071 Jan 23 10:36:29 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: Faulty UTCL2 client ID: CB (0x0) Jan 23 10:36:29 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: MORE_FAULTS: 0x1 Jan 23 10:36:29 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: WALKER_ERROR: 0x0 Jan 23 10:36:29 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: PERMISSION_FAULTS: 0x7 Jan 23 10:36:29 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: MAPPING_ERROR: 0x0 Jan 23 10:36:29 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: RW: 0x1 Jan 23 10:36:29 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:6 pasid:32793, for process kscreenlocker_g pid 6644 thread kscreenloc:cs0 pid 6655) Jan 23 10:36:29 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: in page starting at address 0x000080010bc81000 from IH client 0x1b (UTCL2) Jan 23 10:36:29 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x004C0071 Jan 23 10:36:29 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: Faulty UTCL2 client ID: CB (0x0) Jan 23 10:36:29 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: MORE_FAULTS: 0x1 Jan 23 10:36:29 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: WALKER_ERROR: 0x0 Jan 23 10:36:29 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: PERMISSION_FAULTS: 0x7 Jan 23 10:36:29 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: MAPPING_ERROR: 0x0 Jan 23 10:36:29 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: RW: 0x1 Jan 23 10:36:29 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:6 pasid:32793, for process kscreenlocker_g pid 6644 thread kscreenloc:cs0 pid 6655) Jan 23 10:36:29 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: in page starting at address 0x000080010bc84000 from IH client 0x1b (UTCL2) Jan 23 10:36:29 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x004C0071 Jan 23 10:36:29 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: Faulty UTCL2 client ID: CB (0x0) Jan 23 10:36:29 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: MORE_FAULTS: 0x1 Jan 23 10:36:29 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: WALKER_ERROR: 0x0 Jan 23 10:36:29 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: PERMISSION_FAULTS: 0x7 Jan 23 10:36:29 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: MAPPING_ERROR: 0x0 Jan 23 10:36:29 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: RW: 0x1 Jan 23 10:36:29 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:6 pasid:32793, for process kscreenlocker_g pid 6644 thread kscreenloc:cs0 pid 6655) Jan 23 10:36:29 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: in page starting at address 0x000080010bc85000 from IH client 0x1b (UTCL2) Jan 23 10:36:29 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x004C0071 Jan 23 10:36:29 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: Faulty UTCL2 client ID: CB (0x0) Jan 23 10:36:29 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: MORE_FAULTS: 0x1 Jan 23 10:36:29 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: WALKER_ERROR: 0x0 Jan 23 10:36:29 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: PERMISSION_FAULTS: 0x7 Jan 23 10:36:29 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: MAPPING_ERROR: 0x0 Jan 23 10:36:29 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: RW: 0x1 Jan 23 10:36:29 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:6 pasid:32793, for process kscreenlocker_g pid 6644 thread kscreenloc:cs0 pid 6655) Jan 23 10:36:29 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: in page starting at address 0x000080010bc82000 from IH client 0x1b (UTCL2) Jan 23 10:36:29 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x004C0071 Jan 23 10:36:29 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: Faulty UTCL2 client ID: CB (0x0) Jan 23 10:36:29 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: MORE_FAULTS: 0x1 Jan 23 10:36:29 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: WALKER_ERROR: 0x0 Jan 23 10:36:29 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: PERMISSION_FAULTS: 0x7 Jan 23 10:36:29 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: MAPPING_ERROR: 0x0 Jan 23 10:36:29 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: RW: 0x1 Jan 23 10:36:30 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:6 pasid:32793, for process kscreenlocker_g pid 6644 thread kscreenloc:cs0 pid 6655) Jan 23 10:36:30 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: in page starting at address 0x000080010bc87000 from IH client 0x1b (UTCL2) Jan 23 10:36:30 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x004C0071 Jan 23 10:36:30 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: Faulty UTCL2 client ID: CB (0x0) Jan 23 10:36:30 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: MORE_FAULTS: 0x1 Jan 23 10:36:30 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: WALKER_ERROR: 0x0 Jan 23 10:36:30 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: PERMISSION_FAULTS: 0x7 Jan 23 10:36:30 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: MAPPING_ERROR: 0x0 Jan 23 10:36:30 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: RW: 0x1 Jan 23 10:36:30 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:6 pasid:32793, for process kscreenlocker_g pid 6644 thread kscreenloc:cs0 pid 6655) Jan 23 10:36:30 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: in page starting at address 0x000080010bc8a000 from IH client 0x1b (UTCL2) Jan 23 10:36:30 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x004C0071 Jan 23 10:36:30 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: Faulty UTCL2 client ID: CB (0x0) Jan 23 10:36:30 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: MORE_FAULTS: 0x1 Jan 23 10:36:30 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: WALKER_ERROR: 0x0 Jan 23 10:36:30 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: PERMISSION_FAULTS: 0x7 Jan 23 10:36:30 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: MAPPING_ERROR: 0x0 Jan 23 10:36:30 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: RW: 0x1 Jan 23 10:36:30 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:6 pasid:32793, for process kscreenlocker_g pid 6644 thread kscreenloc:cs0 pid 6655) Jan 23 10:36:30 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: in page starting at address 0x000080010bc80000 from IH client 0x1b (UTCL2) Jan 23 10:36:30 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x004C0071 Jan 23 10:36:30 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: Faulty UTCL2 client ID: CB (0x0) Jan 23 10:36:30 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: MORE_FAULTS: 0x1 Jan 23 10:36:30 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: WALKER_ERROR: 0x0 Jan 23 10:36:30 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: PERMISSION_FAULTS: 0x7 Jan 23 10:36:30 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: MAPPING_ERROR: 0x0 Jan 23 10:36:30 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: RW: 0x1 Jan 23 10:36:30 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:6 pasid:32793, for process kscreenlocker_g pid 6644 thread kscreenloc:cs0 pid 6655) Jan 23 10:36:30 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: in page starting at address 0x000080010bc8b000 from IH client 0x1b (UTCL2) Jan 23 10:36:30 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x004C0071 Jan 23 10:36:30 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: Faulty UTCL2 client ID: CB (0x0) Jan 23 10:36:30 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: MORE_FAULTS: 0x1 Jan 23 10:36:30 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: WALKER_ERROR: 0x0 Jan 23 10:36:30 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: PERMISSION_FAULTS: 0x7 Jan 23 10:36:30 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: MAPPING_ERROR: 0x0 Jan 23 10:36:30 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: RW: 0x1 Jan 23 10:36:30 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:6 pasid:32793, for process kscreenlocker_g pid 6644 thread kscreenloc:cs0 pid 6655) Jan 23 10:36:30 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: in page starting at address 0x000080010bc88000 from IH client 0x1b (UTCL2) Jan 23 10:36:30 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x004C0071 Jan 23 10:36:30 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: Faulty UTCL2 client ID: CB (0x0) Jan 23 10:36:30 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: MORE_FAULTS: 0x1 Jan 23 10:36:30 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: WALKER_ERROR: 0x0 Jan 23 10:36:30 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: PERMISSION_FAULTS: 0x7 Jan 23 10:36:30 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: MAPPING_ERROR: 0x0 Jan 23 10:36:30 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: RW: 0x1 Jan 23 10:36:30 vivobook kernel: [drm] Fence fallback timer expired on ring gfx Jan 23 10:36:30 vivobook kernel: [drm] Fence fallback timer expired on ring sdma0 Jan 23 10:36:30 vivobook kernel: [drm] Fence fallback timer expired on ring sdma0 Jan 23 10:36:31 vivobook kernel: [drm] Fence fallback timer expired on ring sdma0 Jan 23 10:36:31 vivobook kernel: [drm] Fence fallback timer expired on ring sdma0 Jan 23 10:36:32 vivobook kernel: [drm] Fence fallback timer expired on ring sdma0 Jan 23 10:36:32 vivobook kernel: [drm] Fence fallback timer expired on ring sdma0 Jan 23 10:36:33 vivobook kernel: [drm] Fence fallback timer expired on ring sdma0 Jan 23 10:36:33 vivobook kernel: [drm] Fence fallback timer expired on ring sdma0 Jan 23 10:36:34 vivobook kernel: [drm] Fence fallback timer expired on ring sdma0 Jan 23 10:36:34 vivobook kernel: [drm] Fence fallback timer expired on ring sdma0 Jan 23 10:36:35 vivobook kernel: [drm] Fence fallback timer expired on ring sdma0 Jan 23 10:36:35 vivobook kernel: [drm] Fence fallback timer expired on ring sdma0 Jan 23 10:36:36 vivobook kernel: [drm] Fence fallback timer expired on ring sdma0 Jan 23 10:36:36 vivobook kernel: [drm] Fence fallback timer expired on ring sdma0 Jan 23 10:36:37 vivobook kernel: [drm] Fence fallback timer expired on ring sdma0 Jan 23 10:36:37 vivobook kernel: [drm] Fence fallback timer expired on ring sdma0 Jan 23 10:36:38 vivobook kernel: [drm] Fence fallback timer expired on ring sdma0 Jan 23 10:36:39 vivobook kernel: [drm] Fence fallback timer expired on ring sdma0 Jan 23 10:36:40 vivobook kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=202561, emitted seq=202564 Jan 23 10:36:40 vivobook kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process kscreenlocker_g pid 6644 thread kscreenloc:cs0 pid 6655 Jan 23 10:36:40 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: GPU reset begin! Jan 23 10:36:40 vivobook kernel: [drm] free PSP TMR buffer Jan 23 10:36:40 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: MODE2 reset Jan 23 10:36:40 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: GPU reset succeeded, trying to resume Jan 23 10:36:40 vivobook kernel: [drm] PCIE GART of 1024M enabled. Jan 23 10:36:40 vivobook kernel: [drm] PTB located at 0x000000F400900000 Jan 23 10:36:40 vivobook kernel: [drm] PSP is resuming... Jan 23 10:36:40 vivobook kernel: [drm] reserve 0x400000 from 0xf41f800000 for PSP TMR Jan 23 10:36:40 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: RAS: optional ras ta ucode is not available Jan 23 10:36:40 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: RAP: optional rap ta ucode is not available Jan 23 10:36:40 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: SECUREDISPLAY: securedisplay ta ucode is not available Jan 23 10:36:40 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: SMU is resuming... Jan 23 10:36:40 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: dpm has been disabled Jan 23 10:36:40 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: SMU is resumed successfully! Jan 23 10:36:40 vivobook kernel: [drm] DMUB hardware initialized: version=0x0101001C Jan 23 10:36:41 vivobook kernel: [drm] kiq ring mec 2 pipe 1 q 0 Jan 23 10:36:41 vivobook kernel: [drm] VCN decode and encode initialized successfully(under DPG Mode). Jan 23 10:36:41 vivobook kernel: [drm] JPEG decode initialized successfully. Jan 23 10:36:41 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: ring gfx uses VM inv eng 0 on hub 0 Jan 23 10:36:41 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0 Jan 23 10:36:41 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0 Jan 23 10:36:41 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 5 on hub 0 Jan 23 10:36:41 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 6 on hub 0 Jan 23 10:36:41 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 7 on hub 0 Jan 23 10:36:41 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 8 on hub 0 Jan 23 10:36:41 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 9 on hub 0 Jan 23 10:36:41 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 10 on hub 0 Jan 23 10:36:41 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: ring kiq_2.1.0 uses VM inv eng 11 on hub 0 Jan 23 10:36:41 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: ring sdma0 uses VM inv eng 0 on hub 1 Jan 23 10:36:41 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: ring vcn_dec uses VM inv eng 1 on hub 1 Jan 23 10:36:41 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: ring vcn_enc0 uses VM inv eng 4 on hub 1 Jan 23 10:36:41 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: ring vcn_enc1 uses VM inv eng 5 on hub 1 Jan 23 10:36:41 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: ring jpeg_dec uses VM inv eng 6 on hub 1 Jan 23 10:36:41 vivobook kernel: [drm] Fence fallback timer expired on ring gfx Jan 23 10:36:42 vivobook kernel: [drm] Fence fallback timer expired on ring comp_1.0.0 Jan 23 10:36:42 vivobook kernel: [drm] Fence fallback timer expired on ring comp_1.1.0 Jan 23 10:36:43 vivobook kernel: [drm] Fence fallback timer expired on ring comp_1.2.0 Jan 23 10:36:43 vivobook kernel: [drm] Fence fallback timer expired on ring comp_1.3.0 Jan 23 10:36:44 vivobook kernel: [drm] Fence fallback timer expired on ring comp_1.0.1 Jan 23 10:36:44 vivobook kernel: [drm] Fence fallback timer expired on ring comp_1.1.1 Jan 23 10:36:45 vivobook kernel: [drm] Fence fallback timer expired on ring comp_1.2.1 Jan 23 10:36:45 vivobook kernel: [drm] Fence fallback timer expired on ring comp_1.3.1 Jan 23 10:36:46 vivobook kernel: [drm] Fence fallback timer expired on ring sdma0 Jan 23 10:36:46 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: recover vram bo from shadow start Jan 23 10:36:46 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: recover vram bo from shadow done Jan 23 10:36:46 vivobook kernel: [drm] Skip scheduling IBs! Jan 23 10:36:46 vivobook kernel: amdgpu 0000:03:00.0: amdgpu: GPU reset(8) succeeded! Jan 23 10:36:46 vivobook kernel: [drm] Fence fallback timer expired on ring gfx Jan 23 10:36:46 vivobook kernel: [drm] Skip scheduling IBs! Jan 23 10:36:46 vivobook kernel: [drm] Skip scheduling IBs! Jan 23 10:36:46 vivobook kernel: show_signal_msg: 21 callbacks suppressed Jan 23 10:36:46 vivobook kernel: Discord[1867]: segfault at 0 ip 00007f306964e0d6 sp 00007f306962dd10 error 4 in discord_utils.node[7f3069630000+8d000] Jan 23 10:36:46 vivobook kernel: Code: 38 48 83 ff 01 77 09 49 8d 70 ff 48 21 ce eb 13 48 89 ce 4c 39 c1 72 0b 48 89 c8 31 d2 49 f7 f0 48 89 d6 48 8b 05 5a 47 27 00 <48> 8b 04 f0 48 85 c0 74 76 48 8b 18 48 85 db 74 6e 4d 8d 48 ff eb Jan 23 10:36:46 vivobook kernel: wlp1s0: deauthenticating from c0:c9:e3:3a:4d:4c by local choice (Reason: 3=DEAUTH_LEAVING) Jan 23 10:36:47 vivobook kernel: [drm] Fence fallback timer expired on ring gfx Jan 23 10:36:47 vivobook kernel: [drm] Fence fallback timer expired on ring sdma0 Jan 23 10:36:47 vivobook kernel: [drm] Fence fallback timer expired on ring gfx Jan 23 10:36:47 vivobook kernel: [drm] Fence fallback timer expired on ring sdma0 Jan 23 10:36:48 vivobook kernel: [drm] Fence fallback timer expired on ring sdma0 Jan 23 10:36:48 vivobook kernel: [drm] Fence fallback timer expired on ring gfx Jan 23 10:36:48 vivobook kernel: [drm] Fence fallback timer expired on ring gfx Jan 23 10:36:48 vivobook kernel: [drm] Fence fallback timer expired on ring sdma0 Jan 23 10:36:49 vivobook kernel: [drm] Fence fallback timer expired on ring sdma0 Jan 23 10:36:49 vivobook kernel: [drm] Fence fallback timer expired on ring gfx Jan 23 10:36:49 vivobook kernel: [drm] Fence fallback timer expired on ring sdma0 Jan 23 10:36:49 vivobook kernel: [drm] Fence fallback timer expired on ring gfx Jan 23 10:36:50 vivobook kernel: [drm] Fence fallback timer expired on ring gfx Jan 23 10:36:50 vivobook kernel: [drm] Fence fallback timer expired on ring sdma0 Jan 23 10:36:50 vivobook kernel: [drm] Fence fallback timer expired on ring gfx Jan 23 10:36:50 vivobook kernel: [drm] Fence fallback timer expired on ring sdma0 Jan 23 10:36:51 vivobook kernel: [drm] Fence fallback timer expired on ring sdma0 Jan 23 10:36:51 vivobook kernel: [drm] Fence fallback timer expired on ring sdma0 Jan 23 10:36:52 vivobook kernel: [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* Waiting for fences timed out! Jan 23 10:36:52 vivobook kernel: [drm] Fence fallback timer expired on ring sdma0 Jan 23 10:36:52 vivobook kernel: [drm] Fence fallback timer expired on ring gfx Jan 23 10:36:52 vivobook kernel: [drm] Fence fallback timer expired on ring sdma0 Jan 23 10:36:53 vivobook kernel: [drm] Fence fallback timer expired on ring gfx Jan 23 10:36:53 vivobook kernel: [drm] Fence fallback timer expired on ring sdma0 Jan 23 10:36:53 vivobook kernel: [drm] Fence fallback timer expired on ring sdma0 Jan 23 10:36:54 vivobook kernel: [drm] Fence fallback timer expired on ring sdma0 Jan 23 10:36:54 vivobook kernel: [drm] Fence fallback timer expired on ring sdma0 Jan 23 10:36:55 vivobook kernel: [drm] Fence fallback timer expired on ring sdma0 Jan 23 10:36:55 vivobook kernel: [drm] Fence fallback timer expired on ring sdma0 Jan 23 10:36:56 vivobook kernel: [drm] Fence fallback timer expired on ring sdma0 Jan 23 10:36:56 vivobook kernel: [drm] Fence fallback timer expired on ring sdma0 Jan 23 10:36:57 vivobook kernel: [drm] Fence fallback timer expired on ring sdma0 Jan 23 10:36:57 vivobook kernel: [drm] Fence fallback timer expired on ring sdma0 Jan 23 10:36:58 vivobook kernel: [drm] Fence fallback timer expired on ring sdma0 Jan 23 10:36:58 vivobook kernel: [drm] Fence fallback timer expired on ring sdma0 Jan 23 10:36:59 vivobook kernel: [drm] Fence fallback timer expired on ring sdma0 Jan 23 10:36:59 vivobook kernel: [drm] Fence fallback timer expired on ring sdma0 Jan 23 10:37:00 vivobook kernel: [drm] Fence fallback timer expired on ring sdma0 Jan 23 10:37:00 vivobook kernel: [drm] Fence fallback timer expired on ring sdma0 Jan 23 10:37:01 vivobook kernel: [drm] Fence fallback timer expired on ring sdma0 Jan 23 10:37:01 vivobook kernel: [drm] Fence fallback timer expired on ring sdma0 Jan 23 10:37:02 vivobook kernel: [drm] Fence fallback timer expired on ring sdma0 Jan 23 10:37:34 vivobook kernel: Linux version 5.16.2-arch1-1 (linux@archlinux) (gcc (GCC) 11.1.0, GNU ld (GNU Binutils) 2.36.1) #1 SMP PREEMPT Thu, 20 Jan 2022 16:18:29 +0000 Jan 23 10:37:34 vivobook kernel: Command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=d21e63b3-ad15-4401-8f4f-72b53ba870ec rw loglevel=3 quiet acpi_backlight=vendor audit=0 Jan 23 10:37:34 vivobook kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers' Jan 23 10:37:34 vivobook kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers' Jan 23 10:37:34 vivobook kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers' Jan 23 10:37:34 vivobook kernel: x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256 Jan 23 10:37:34 vivobook kernel: x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'compacted' format. Jan 23 10:37:34 vivobook kernel: signal: max sigframe size: 1776 Jan 23 10:37:34 vivobook kernel: BIOS-provided physical RAM map: Jan 23 10:37:34 vivobook kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009ffff] usable Jan 23 10:37:34 vivobook kernel: BIOS-e820: [mem 0x00000000000a0000-0x00000000000fffff] reserved Jan 23 10:37:34 vivobook kernel: BIOS-e820: [mem 0x0000000000100000-0x0000000009d01fff] usable Jan 23 10:37:34 vivobook kernel: BIOS-e820: [mem 0x0000000009d02000-0x0000000009ffffff] reserved Jan 23 10:37:34 vivobook kernel: BIOS-e820: [mem 0x000000000a000000-0x000000000a1fffff] usable Jan 23 10:37:34 vivobook kernel: BIOS-e820: [mem 0x000000000a200000-0x000000000a20ffff] ACPI NVS Jan 23 10:37:34 vivobook kernel: BIOS-e820: [mem 0x000000000a210000-0x00000000cb275fff] usable Jan 23 10:37:34 vivobook kernel: BIOS-e820: [mem 0x00000000cb276000-0x00000000cc758fff] reserved Jan 23 10:37:34 vivobook kernel: BIOS-e820: [mem 0x00000000cc759000-0x00000000cc7aafff] ACPI data Jan 23 10:37:34 vivobook kernel: BIOS-e820: [mem 0x00000000cc7ab000-0x00000000cc950fff] ACPI NVS Jan 23 10:37:34 vivobook kernel: BIOS-e820: [mem 0x00000000cc951000-0x00000000cd12afff] reserved Jan 23 10:37:34 vivobook kernel: BIOS-e820: [mem 0x00000000cd12b000-0x00000000cd13cfff] type 20 Jan 23 10:37:34 vivobook kernel: BIOS-e820: [mem 0x00000000cd13d000-0x00000000cd13dfff] reserved Jan 23 10:37:34 vivobook kernel: BIOS-e820: [mem 0x00000000cd13e000-0x00000000cd1fefff] type 20 Jan 23 10:37:34 vivobook kernel: BIOS-e820: [mem 0x00000000cd1ff000-0x00000000cdffffff] usable Jan 23 10:37:34 vivobook kernel: BIOS-e820: [mem 0x00000000ce000000-0x00000000cfffffff] reserved Jan 23 10:37:34 vivobook kernel: BIOS-e820: [mem 0x00000000f0000000-0x00000000f7ffffff] reserved Jan 23 10:37:34 vivobook kernel: BIOS-e820: [mem 0x00000000fd000000-0x00000000ffffffff] reserved Jan 23 10:37:34 vivobook kernel: BIOS-e820: [mem 0x0000000100000000-0x000000040f33ffff] usable Jan 23 10:37:34 vivobook kernel: BIOS-e820: [mem 0x000000040f340000-0x00000004501fffff] reserved Jan 23 10:37:34 vivobook kernel: NX (Execute Disable) protection: active Jan 23 10:37:34 vivobook kernel: efi: EFI v2.70 by American Megatrends Jan 23 10:37:34 vivobook kernel: efi: ACPI=0xcc7aa000 ACPI 2.0=0xcc7aa014 TPMFinalLog=0xcc90a000 SMBIOS=0xccfcb000 SMBIOS 3.0=0xccfca000 ESRT=0xca18ce98 Jan 23 10:37:34 vivobook kernel: SMBIOS 3.2.0 present. Jan 23 10:37:34 vivobook kernel: DMI: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X421IA_M433IA/X421IA, BIOS X421IA.305 07/27/2020 Jan 23 10:37:34 vivobook kernel: tsc: Fast TSC calibration using PIT Jan 23 10:37:34 vivobook kernel: tsc: Detected 2370.599 MHz processor Jan 23 10:37:34 vivobook kernel: e820: update [mem 0x00000000-0x00000fff] usable ==> reserved Jan 23 10:37:34 vivobook kernel: e820: remove [mem 0x000a0000-0x000fffff] usable Jan 23 10:37:34 vivobook kernel: last_pfn = 0x40f340 max_arch_pfn = 0x400000000 Jan 23 10:37:34 vivobook kernel: x86/PAT: Configuration [0-7]: WB WC UC- UC WB WP UC- WT Jan 23 10:37:34 vivobook kernel: e820: update [mem 0xd0000000-0xffffffff] usable ==> reserved Jan 23 10:37:34 vivobook kernel: last_pfn = 0xce000 max_arch_pfn = 0x400000000 Jan 23 10:37:34 vivobook kernel: esrt: Reserving ESRT space from 0x00000000ca18ce98 to 0x00000000ca18ced0. Jan 23 10:37:34 vivobook kernel: e820: update [mem 0xca18c000-0xca18cfff] usable ==> reserved Jan 23 10:37:34 vivobook kernel: Using GB pages for direct mapping Jan 23 10:37:34 vivobook kernel: Secure boot could not be determined