https://bugs.kde.org/show_bug.cgi?id=523824
--- Comment #3 from [email protected] --- Shortened Journalctl output at time of crash, starting from the moment the tablet is disconnected --- Aug 02 23:10:55 archrur kernel: usb 5-1: USB disconnect, device number 5 Aug 02 23:10:55 archrur kernel: usb 5-1.3: USB disconnect, device number 6 Aug 02 23:10:55 archrur kernel: usb 5-1.3.1: USB disconnect, device number 11 Aug 02 23:10:55 archrur org_kde_powerdevil[50040]: [ 50102][47207.379913] Udev event detected Aug 02 23:10:55 archrur org_kde_powerdevil[50040]: [ 50102][47207.380894] Udev_Event_Detail Aug 02 23:10:55 archrur org_kde_powerdevil[50040]: [ 50102][47207.380894] prop_subsystem: drm Aug 02 23:10:55 archrur org_kde_powerdevil[50040]: [ 50102][47207.380894] prop_action: change Aug 02 23:10:55 archrur org_kde_powerdevil[50040]: [ 50102][47207.380894] prop_connector: 93 Aug 02 23:10:55 archrur org_kde_powerdevil[50040]: [ 50102][47207.380894] prop_devname: /dev/dri/card1 Aug 02 23:10:55 archrur org_kde_powerdevil[50040]: [ 50102][47207.380894] prop_devmode: (null) Aug 02 23:10:55 archrur org_kde_powerdevil[50040]: [ 50102][47207.380894] prop_hotplug: 1 Aug 02 23:10:55 archrur org_kde_powerdevil[50040]: [ 50102][47207.380894] prop_major: 226 Aug 02 23:10:55 archrur org_kde_powerdevil[50040]: [ 50102][47207.380894] prop_minor: 1 Aug 02 23:10:55 archrur org_kde_powerdevil[50040]: [ 50102][47207.380894] sysname: card1 Aug 02 23:10:55 archrur org_kde_powerdevil[50040]: [ 50102][47207.380894] syspath: /sys/devices/pci0000:00/0000:00:03.1/0000:08:00.0/0000:09:00.0/0000:0a:00.0/drm/card1 Aug 02 23:10:55 archrur org_kde_powerdevil[50040]: [ 50102][47207.380894] attr_name: (null) Aug 02 23:10:55 archrur org_kde_powerdevil[50040]: [ 50102][47207.380894] prop_connector = 93 -> /dev/i2c-4 Aug 02 23:10:55 archrur org_kde_powerdevil[50040]: [ 50102][47207.380894] prop_connector = 93 -> card1-DP-1 Aug 02 23:10:55 archrur org_kde_powerdevil[50040]: [ 50102][47207.380952] (dw_watch_display_connections) Time since last return from sleep = 47207307868280 ns = 47207308 ms Aug 02 23:10:55 archrur systemd[1]: iio-sensor-proxy.service: Deactivated successfully. Aug 02 23:10:55 archrur systemd[1024]: Started dbus-:[email protected]. Aug 02 23:10:55 archrur kernel: usb 5-1.3.2: USB disconnect, device number 10 Aug 02 23:10:55 archrur kernel: usb 5-1.3.3: USB disconnect, device number 28 Aug 02 23:10:55 archrur kernel: usb 5-1.3.4: USB disconnect, device number 9 Aug 02 23:10:55 archrur kernel: usb 5-1.4: USB disconnect, device number 7 Aug 02 23:10:55 archrur Vesktop-1.6.5.AppImage[75879]: [75879:0802/231055.343614:ERROR:services/video_capture/video_capture_service_impl.cc:187] Bind context provider failed. Aug 02 23:10:55 archrur org_kde_powerdevil[50040]: [ 50102] Removing connected display on bus 4 Aug 02 23:10:55 archrur org_kde_powerdevil[50040]: [ 50102] (dw_remove_display_by_businfo) No Display_Ref found for i2c bus: 4 Aug 02 23:11:03 archrur kdeconnectd[1512]: No Primary Battery detected on this system. This may be a bug. Aug 02 23:11:03 archrur kdeconnectd[1512]: Total quantity of batteries found: 0 Aug 02 23:11:03 archrur kdeconnectd[1512]: Primary Battery seems to have been removed. Suspending packets until it is reconnected. Aug 02 23:11:03 archrur kdeconnectd[1512]: discarding unsupported packet "kdeconnect.notification.request" for "wacomrur" Aug 02 23:11:03 archrur kdeconnectd[1512]: Ignoring clipboard without timestamp Aug 02 23:11:06 archrur kernel: [UFW BLOCK] IN=enp6s0 OUT= MAC=40:b0:76:dd:8c:84:f4:96:34:19:79:fe:08:00 SRC=192.168.1.189 DST=192.168.1.64 LEN=325 TOS=0x00 PREC=0x00 TTL=64 ID=3471 DF PROTO=TCP SPT=22000 DPT=60494 WINDOW=63 RES=0x00 ACK PSH URGP=0 Aug 02 23:11:10 archrur syncthing[1034]: Established secure connection (device=WTDAXJB connection.local=192.168.1.64:22000 connection.remote=192.168.1.189:22000 connection.type=tcp-server connection.lan=true connection.crypto=TLS1.3-TLS_AES_128_GCM_SHA256 connection.prio=10 connection.id=6686R25UPUU5AK97GK5NC3UUNK log.pkg=connections) Aug 02 23:11:10 archrur syncthing[1034]: New device connection (device=WTDAXJB address=192.168.1.189:22000 remote.name=wacomrur remote.client=syncthing remote.version=v2.1.2 log.pkg=model) Aug 02 23:11:10 archrur syncthing[1034]: Failed to exchange Hello messages (device=WTDAXJB address="[fe80::1f6d:fd95:1647:5441%enp6s0]:22000" error="read tcp [fe80::f3ca:2275:df67:b5e3%enp6s0]:22000->[fe80::1f6d:fd95:1647:5441%enp6s0]:22000: read: connection reset by peer" log.pkg=connections) Aug 02 23:11:19 archrur kernel: [UFW BLOCK] IN=enp6s0 OUT= MAC=40:b0:76:dd:8c:84:f4:96:34:19:79:fe:08:00 SRC=192.168.1.189 DST=192.168.1.64 LEN=325 TOS=0x00 PREC=0x00 TTL=64 ID=3472 DF PROTO=TCP SPT=22000 DPT=60494 WINDOW=63 RES=0x00 ACK PSH URGP=0 Aug 02 23:11:33 archrur syncthing[1034]: Failed to exchange Hello messages (device=WTDAXJB address=192.168.1.189:22000 error=EOF log.pkg=connections) Aug 02 23:11:36 archrur syncthing[1034]: Established secure connection (device=WTDAXJB connection.local=192.168.1.64:22000 connection.remote=192.168.1.189:44848 connection.type=tcp-server connection.lan=true connection.crypto=TLS1.3-TLS_AES_128_GCM_SHA256 connection.prio=10 connection.id=6686R56TUMBE0RFA38FL8V1QN0 log.pkg=connections) Aug 02 23:11:36 archrur syncthing[1034]: Additional device connection (device=WTDAXJB address=192.168.1.189:44848 count=1 log.pkg=model) Aug 02 23:11:43 archrur syncthing[1034]: Failed TLS handshake (address="[fe80::1f6d:fd95:1647:5441%enp6s0]:59722" error=EOF log.pkg=connections) Aug 02 23:11:43 archrur syncthing[1034]: Failed to exchange Hello messages (device=WTDAXJB address="[fe80::1f6d:fd95:1647:5441%enp6s0]:22000" error="read tcp [fe80::f3ca:2275:df67:b5e3%enp6s0]:22000->[fe80::1f6d:fd95:1647:5441%enp6s0]:22000: read: connection reset by peer" log.pkg=connections) Aug 02 23:11:47 archrur kernel: [UFW BLOCK] IN=enp6s0 OUT= MAC=40:b0:76:dd:8c:84:f4:96:34:19:79:fe:08:00 SRC=192.168.1.189 DST=192.168.1.64 LEN=325 TOS=0x00 PREC=0x00 TTL=64 ID=3473 DF PROTO=TCP SPT=22000 DPT=60494 WINDOW=63 RES=0x00 ACK PSH URGP=0 Aug 02 23:11:54 archrur plasma_waitforname[75870]: WaitForName: Service was not registered within timeout Aug 02 23:11:54 archrur systemd[1024]: dbus-:[email protected]: Main process exited, code=exited, status=1/FAILURE Aug 02 23:11:54 archrur systemd[1024]: dbus-:[email protected]: Failed with result 'exit-code'. Aug 02 23:12:03 archrur syncthing[1034]: Failed to exchange Hello messages (device=WTDAXJB address=192.168.1.189:22000 error=EOF log.pkg=connections) Aug 02 23:12:34 archrur syncthing[1034]: Failed to exchange Hello messages (device=WTDAXJB address=192.168.1.189:22000 error=EOF log.pkg=connections) Aug 02 23:12:44 archrur kernel: [UFW BLOCK] IN=enp6s0 OUT= MAC=40:b0:76:dd:8c:84:f4:96:34:19:79:fe:08:00 SRC=192.168.1.189 DST=192.168.1.64 LEN=325 TOS=0x00 PREC=0x00 TTL=64 ID=3474 DF PROTO=TCP SPT=22000 DPT=60494 WINDOW=63 RES=0x00 ACK PSH URGP=0 Aug 02 23:12:50 archrur syncthing[1034]: Established secure connection (device=WTDAXJB connection.local="[fe80::f3ca:2275:df67:b5e3%enp6s0]:22000" connection.remote="[fe80::1f6d:fd95:1647:5441%enp6s0]:22000" connection.type=tcp-server connection.lan=true connection.crypto=TLS1.3-TLS_AES_128_GCM_SHA256 connection.prio=10 connection.id=6686RDRDM0OJK81QHHPLT3D3DS log.pkg=connections) Aug 02 23:12:50 archrur syncthing[1034]: Additional device connection (device=WTDAXJB address="[fe80::1f6d:fd95:1647:5441%enp6s0]:22000" count=2 log.pkg=model) Aug 02 23:25:21 archrur syncthing[1034]: Lost device connection (kind=secondary device=WTDAXJB connection="[fe80::f3ca:2275:df67:b5e3%enp6s0]:22000-[fe80::1f6d:fd95:1647:5441%enp6s0]:22000/tcp-server/TLS1.3-TLS_AES_128_GCM_SHA256/LAN-P10-6686RDRDM0OJK81QHHPLT3D3DS" error="read timeout" remaining=2 log.pkg=model) Aug 02 23:26:11 archrur syncthing[1034]: Lost device connection (kind=primary device=WTDAXJB connection=192.168.1.64:22000-192.168.1.189:22000/tcp-server/TLS1.3-TLS_AES_128_GCM_SHA256/LAN-P10-6686R25UPUU5AK97GK5NC3UUNK error="read timeout" remaining=1 log.pkg=model) Aug 02 23:26:37 archrur syncthing[1034]: Lost device connection (kind=primary device=WTDAXJB connection=192.168.1.64:22000-192.168.1.189:44848/tcp-server/TLS1.3-TLS_AES_128_GCM_SHA256/LAN-P10-6686R56TUMBE0RFA38FL8V1QN0 error="read timeout" remaining=0 log.pkg=model) Aug 02 23:26:37 archrur syncthing[1034]: Connection closed (device=WTDAXJB connection=192.168.1.64:22000-192.168.1.189:44848/tcp-server/TLS1.3-TLS_AES_128_GCM_SHA256/LAN-P10-6686R56TUMBE0RFA38FL8V1QN0 error="read timeout" log.pkg=model) Aug 02 23:40:52 archrur kscreenlocker_greet[75995]: The theme "Sweet" uses the legacy metadata.desktop. Consider contacting the author and asking them update it to use the newer JSON format. Aug 02 23:40:52 archrur kscreenlocker_greet[75995]: The theme "Sweet" uses the legacy metadata.desktop. Consider contacting the author and asking them update it to use the newer JSON format. Aug 02 23:40:52 archrur kscreenlocker_greet[75995]: The theme "Sweet" uses the legacy metadata.desktop. Consider contacting the author and asking them update it to use the newer JSON format. Aug 02 23:40:52 archrur kscreenlocker_greet[75995]: The theme "Sweet" uses the legacy metadata.desktop. Consider contacting the author and asking them update it to use the newer JSON format. Aug 02 23:40:52 archrur kscreenlocker_greet[75995]: Data set on unsupported clipboard mode. QMimeData object will be deleted. Aug 02 23:40:53 archrur kwin_wayland[1148]: Pageflip timed out! This is a bug in the amdgpu kernel driver Aug 02 23:40:53 archrur kwin_wayland[1148]: Please report this at https://gitlab.freedesktop.org/drm/amd/-/issues Aug 02 23:40:53 archrur kwin_wayland[1148]: With the output of 'sudo dmesg' and 'journalctl --user-unit plasma-kwin_wayland --boot 0' Aug 02 23:40:54 archrur kwin_wayland[1148]: Pageflip timed out! This is a bug in the amdgpu kernel driver Aug 02 23:40:54 archrur kwin_wayland[1148]: Please report this at https://gitlab.freedesktop.org/drm/amd/-/issues Aug 02 23:40:54 archrur kwin_wayland[1148]: With the output of 'sudo dmesg' and 'journalctl --user-unit plasma-kwin_wayland --boot 0' Aug 02 23:40:54 archrur kernel: amdgpu 0000:0a:00.0: Dumping IP State Aug 02 23:40:54 archrur kernel: amdgpu 0000:0a:00.0: Dumping IP State Completed Aug 02 23:40:54 archrur kernel: amdgpu 0000:0a:00.0: [drm] AMDGPU device coredump file has been created Aug 02 23:40:54 archrur kernel: amdgpu 0000:0a:00.0: [drm] Check your /sys/class/drm/card1/device/devcoredump/data Aug 02 23:40:54 archrur kernel: amdgpu 0000:0a:00.0: ring page0 timeout, signaled seq=2829503, emitted seq=2829527 Aug 02 23:40:54 archrur kernel: amdgpu 0000:0a:00.0: GPU reset begin!. Source: 1 Aug 02 23:40:54 archrur kernel: amdgpu 0000:0a:00.0: [drm] REG_WAIT timeout 10us * 3500 tries - dce_mi_free_dmif line:804 Aug 02 23:40:54 archrur kernel: amdgpu 0000:0a:00.0: psp gfx command UNLOAD_TA(0x2) failed and response status is (0x117) Aug 02 23:40:54 archrur kernel: amdgpu 0000:0a:00.0: BACO reset Aug 02 23:40:55 archrur kernel: amdgpu 0000:0a:00.0: GPU reset succeeded, trying to resume Aug 02 23:40:55 archrur kernel: amdgpu 0000:0a:00.0: [drm] PCIE GART of 512M enabled. Aug 02 23:40:55 archrur kernel: amdgpu 0000:0a:00.0: [drm] PTB located at 0x000000F400000000 Aug 02 23:40:55 archrur kernel: amdgpu 0000:0a:00.0: VRAM is lost due to GPU reset! Aug 02 23:40:55 archrur kernel: amdgpu 0000:0a:00.0: PSP is resuming... Aug 02 23:40:55 archrur kernel: amdgpu 0000:0a:00.0: reserve 0x400000 from 0xf5fec00000 for PSP TMR Aug 02 23:40:55 archrur kernel: amdgpu 0000:0a:00.0: kiq ring mec 2 pipe 1 q 0 Aug 02 23:40:55 archrur kwin_wayland[1148]: Pageflip timed out! This is a bug in the amdgpu kernel driver Aug 02 23:40:55 archrur kwin_wayland[1148]: Please report this at https://gitlab.freedesktop.org/drm/amd/-/issues Aug 02 23:40:55 archrur kwin_wayland[1148]: With the output of 'sudo dmesg' and 'journalctl --user-unit plasma-kwin_wayland --boot 0' Aug 02 23:40:55 archrur kernel: amdgpu 0000:0a:00.0: [drm] UVD and UVD ENC initialized successfully. Aug 02 23:40:55 archrur kernel: amdgpu 0000:0a:00.0: [drm] VCE initialized successfully. Aug 02 23:40:55 archrur kernel: amdgpu 0000:0a:00.0: ring gfx uses VM inv eng 0 on hub 0 Aug 02 23:40:55 archrur kernel: amdgpu 0000:0a:00.0: ring comp_1.0.0 uses VM inv eng 1 on hub 0 Aug 02 23:40:55 archrur kernel: amdgpu 0000:0a:00.0: ring comp_1.1.0 uses VM inv eng 4 on hub 0 Aug 02 23:40:55 archrur kernel: amdgpu 0000:0a:00.0: ring comp_1.2.0 uses VM inv eng 5 on hub 0 Aug 02 23:40:55 archrur kernel: amdgpu 0000:0a:00.0: ring comp_1.3.0 uses VM inv eng 6 on hub 0 Aug 02 23:40:55 archrur kernel: amdgpu 0000:0a:00.0: ring comp_1.0.1 uses VM inv eng 7 on hub 0 Aug 02 23:40:55 archrur kernel: amdgpu 0000:0a:00.0: ring comp_1.1.1 uses VM inv eng 8 on hub 0 Aug 02 23:40:55 archrur kernel: amdgpu 0000:0a:00.0: ring comp_1.2.1 uses VM inv eng 9 on hub 0 Aug 02 23:40:55 archrur kernel: amdgpu 0000:0a:00.0: ring comp_1.3.1 uses VM inv eng 10 on hub 0 Aug 02 23:40:55 archrur kernel: amdgpu 0000:0a:00.0: ring kiq_0.2.1.0 uses VM inv eng 11 on hub 0 Aug 02 23:40:55 archrur kernel: amdgpu 0000:0a:00.0: ring sdma0 uses VM inv eng 0 on hub 8 Aug 02 23:40:55 archrur kernel: amdgpu 0000:0a:00.0: ring sdma0 shares VM invalidation engine 0 with ring page0 on hub 8 Aug 02 23:40:55 archrur kernel: amdgpu 0000:0a:00.0: ring page0 uses VM inv eng 1 on hub 8 Aug 02 23:40:55 archrur kernel: amdgpu 0000:0a:00.0: ring sdma1 uses VM inv eng 4 on hub 8 Aug 02 23:40:55 archrur kernel: amdgpu 0000:0a:00.0: ring sdma1 shares VM invalidation engine 4 with ring page1 on hub 8 Aug 02 23:40:55 archrur kernel: amdgpu 0000:0a:00.0: ring page1 uses VM inv eng 5 on hub 8 Aug 02 23:40:55 archrur kernel: amdgpu 0000:0a:00.0: ring uvd_0 uses VM inv eng 6 on hub 8 Aug 02 23:40:55 archrur kernel: amdgpu 0000:0a:00.0: ring uvd_enc_0.0 uses VM inv eng 7 on hub 8 Aug 02 23:40:55 archrur kernel: amdgpu 0000:0a:00.0: ring uvd_enc_0.1 uses VM inv eng 8 on hub 8 Aug 02 23:40:55 archrur kernel: amdgpu 0000:0a:00.0: ring vce0 uses VM inv eng 9 on hub 8 Aug 02 23:40:55 archrur kernel: amdgpu 0000:0a:00.0: ring vce1 uses VM inv eng 10 on hub 8 Aug 02 23:40:55 archrur kernel: amdgpu 0000:0a:00.0: ring vce2 uses VM inv eng 11 on hub 8 Aug 02 23:40:55 archrur kernel: amdgpu 0000:0a:00.0: GPU reset(1) succeeded! Aug 02 23:40:55 archrur kwin_wayland[1148]: Pageflip arrived after all, 3162ms after the commit Aug 02 23:40:55 archrur kernel: amdgpu 0000:0a:00.0: [drm] device wedged, but no recovery needed Aug 02 23:40:55 archrur org_kde_powerdevil[50040]: [ 50102][49007.771312] Udev event detected Aug 02 23:40:55 archrur kwin_wayland[1148]: 0x3: GL_CONTEXT_LOST in context lost Aug 02 23:40:55 archrur org_kde_powerdevil[50040]: [ 50102][49007.771391] Udev_Event_Detail Aug 02 23:40:55 archrur kwin_wayland[1148]: 0x3: GL_CONTEXT_LOST in context lost Aug 02 23:40:55 archrur org_kde_powerdevil[50040]: [ 50102][49007.771391] prop_subsystem: drm Aug 02 23:40:55 archrur kwin_wayland[1148]: 0x3: GL_CONTEXT_LOST in context lost Aug 02 23:40:55 archrur org_kde_powerdevil[50040]: [ 50102][49007.771391] prop_action: change Aug 02 23:40:55 archrur kwin_wayland[1148]: 0x3: GL_CONTEXT_LOST in context lost Aug 02 23:40:55 archrur org_kde_powerdevil[50040]: [ 50102][49007.771391] prop_connector: (null) Aug 02 23:40:55 archrur kwin_wayland[1148]: 0x3: GL_CONTEXT_LOST in context lost Aug 02 23:40:55 archrur org_kde_powerdevil[50040]: [ 50102][49007.771391] prop_devname: /dev/dri/card1 Aug 02 23:40:55 archrur kwin_wayland[1148]: 0x3: GL_CONTEXT_LOST in context lost Aug 02 23:40:55 archrur org_kde_powerdevil[50040]: [ 50102][49007.771391] prop_devmode: (null) Aug 02 23:40:55 archrur kwin_wayland[1148]: 0x3: GL_CONTEXT_LOST in context lost Aug 02 23:40:55 archrur org_kde_powerdevil[50040]: [ 50102][49007.771391] prop_hotplug: (null) Aug 02 23:40:55 archrur kwin_wayland[1148]: 0x3: GL_CONTEXT_LOST in context lost Aug 02 23:40:55 archrur org_kde_powerdevil[50040]: [ 50102][49007.771391] prop_major: 226 Aug 02 23:40:55 archrur kwin_wayland[1148]: A graphics reset not attributable to the current GL context occurred. Aug 02 23:40:55 archrur org_kde_powerdevil[50040]: [ 50102][49007.771391] prop_minor: 1 Aug 02 23:40:55 archrur kwin_wayland[1148]: 0x3: GL_CONTEXT_LOST in context lost Aug 02 23:40:55 archrur org_kde_powerdevil[50040]: [ 50102][49007.771391] sysname: card1 Aug 02 23:40:55 archrur kwin_wayland[1148]: 0x3: GL_CONTEXT_LOST in context lost Aug 02 23:40:55 archrur org_kde_powerdevil[50040]: [ 50102][49007.771391] syspath: /sys/devices/pci0000:00/0000:00:03.1/0000:08:00.0/0000:09:00.0/0000:0a:00.0/drm/card1 Aug 02 23:40:55 archrur kwin_wayland[1148]: 0x3: GL_CONTEXT_LOST in context lost Aug 02 23:40:55 archrur org_kde_powerdevil[50040]: [ 50102][49007.771391] attr_name: (null) Aug 02 23:40:55 archrur kwin_wayland[1148]: 0x3: GL_CONTEXT_LOST in context lost Aug 02 23:40:55 archrur org_kde_powerdevil[50040]: [ 50102][49007.771438] (dw_watch_display_connections) Time since last return from sleep = 49007698354741 ns = 49007698 ms Aug 02 23:40:55 archrur kwin_wayland[1148]: 0x3: GL_CONTEXT_LOST in context lost Aug 02 23:40:55 archrur kwin_wayland[1148]: 0x3: GL_CONTEXT_LOST in context lost Aug 02 23:40:55 archrur kwin_wayland[1148]: 0x3: GL_CONTEXT_LOST in context lost ... (and so on for several lines) Aug 02 23:40:55 archrur kwin_wayland[1148]: 0x3: GL_CONTEXT_LOST in context lost Aug 02 23:40:55 archrur kwin_wayland[1148]: 0x3: GL_CONTEXT_LOST in context lost Aug 02 23:40:55 archrur kwin_wayland[1148]: 0x3: GL_CONTEXT_LOST in context lost Aug 02 23:40:55 archrur kwin_wayland[1148]: BlurConfig::instance called after the first use - ignoring Aug 02 23:40:55 archrur kwin_wayland[1148]: KscreenConfig::instance called after the first use - ignoring Aug 02 23:40:55 archrur kwin_wayland[1148]: OverviewConfig::instance called after the first use - ignoring Aug 02 23:40:55 archrur kwin_wayland[1148]: ShakeCursorConfig::instance called after the first use - ignoring Aug 02 23:40:55 archrur kwin_wayland[1148]: SlideConfig::instance called after the first use - ignoring Aug 02 23:40:55 archrur kwin_wayland[1148]: SlidingPopupsConfig::instance called after the first use - ignoring Aug 02 23:40:55 archrur kwin_wayland[1148]: WindowViewConfig::instance called after the first use - ignoring Aug 02 23:40:55 archrur kwin_wayland[1148]: ZoomConfig::instance called after the first use - ignoring Aug 02 23:40:55 archrur kwin_wayland[1148]: Could not delete render time query because no context is current Aug 02 23:40:55 archrur plasmashell[1298]: QRhiGles2: Context is lost. Aug 02 23:40:55 archrur plasmashell[1298]: Graphics device lost, cleaning up scenegraph and releasing RHI Aug 02 23:40:55 archrur plasmashell[1298]: QRhiGles2: Context is lost. Aug 02 23:40:55 archrur plasmashell[1298]: Graphics device lost, cleaning up scenegraph and releasing RHI Aug 02 23:40:55 archrur kscreenlocker_greet[75995]: QRhiGles2: Context is lost. Aug 02 23:40:55 archrur kscreenlocker_greet[75995]: Graphics device lost, cleaning up scenegraph and releasing RHI Aug 02 23:40:55 archrur kscreenlocker_greet[75995]: The Wayland connection broke. Did the Wayland compositor die? Aug 02 23:40:57 archrur kernel: amdgpu 0000:0a:00.0: Dumping IP State Aug 02 23:40:57 archrur kernel: amdgpu 0000:0a:00.0: Dumping IP State Completed Aug 02 23:40:57 archrur kernel: amdgpu 0000:0a:00.0: [drm] AMDGPU device coredump file has been created Aug 02 23:40:57 archrur kernel: amdgpu 0000:0a:00.0: [drm] Check your /sys/class/drm/card1/device/devcoredump/data Aug 02 23:40:57 archrur kernel: amdgpu 0000:0a:00.0: ring comp_1.2.0 timeout, signaled seq=27641, emitted seq=27644 Aug 02 23:40:57 archrur kernel: amdgpu 0000:0a:00.0: Process kwin_wayland pid 1148 thread kwin_wayla:cs0 pid 1165 Aug 02 23:40:57 archrur kernel: amdgpu 0000:0a:00.0: Starting comp_1.2.0 ring reset Aug 02 23:40:57 archrur kernel: amdgpu 0000:0a:00.0: fail to wait on hqd deactive Aug 02 23:40:57 archrur kernel: amdgpu 0000:0a:00.0: Ring comp_1.2.0 reset failed Aug 02 23:40:57 archrur kernel: amdgpu 0000:0a:00.0: GPU reset begin!. Source: 1 Aug 02 23:40:57 archrur kernel: amdgpu 0000:0a:00.0: psp gfx command UNLOAD_TA(0x2) failed and response status is (0x117) Aug 02 23:40:57 archrur kernel: amdgpu 0000:0a:00.0: BACO reset Aug 02 23:40:58 archrur kernel: amdgpu 0000:0a:00.0: GPU reset succeeded, trying to resume Aug 02 23:40:58 archrur kernel: amdgpu 0000:0a:00.0: [drm] PCIE GART of 512M enabled. Aug 02 23:40:58 archrur kernel: amdgpu 0000:0a:00.0: [drm] PTB located at 0x000000F400000000 Aug 02 23:40:58 archrur kernel: amdgpu 0000:0a:00.0: VRAM is lost due to GPU reset! Aug 02 23:40:58 archrur kernel: amdgpu 0000:0a:00.0: PSP is resuming... Aug 02 23:40:58 archrur kernel: amdgpu 0000:0a:00.0: reserve 0x400000 from 0xf5fec00000 for PSP TMR Aug 02 23:40:58 archrur kernel: amdgpu 0000:0a:00.0: kiq ring mec 2 pipe 1 q 0 Aug 02 23:40:58 archrur kernel: amdgpu 0000:0a:00.0: [drm] UVD and UVD ENC initialized successfully. Aug 02 23:40:58 archrur kernel: amdgpu 0000:0a:00.0: [drm] VCE initialized successfully. Aug 02 23:40:58 archrur kernel: amdgpu 0000:0a:00.0: ring gfx uses VM inv eng 0 on hub 0 Aug 02 23:40:58 archrur kernel: amdgpu 0000:0a:00.0: ring comp_1.0.0 uses VM inv eng 1 on hub 0 Aug 02 23:40:58 archrur kernel: amdgpu 0000:0a:00.0: ring comp_1.1.0 uses VM inv eng 4 on hub 0 Aug 02 23:40:58 archrur kernel: amdgpu 0000:0a:00.0: ring comp_1.2.0 uses VM inv eng 5 on hub 0 Aug 02 23:40:58 archrur kernel: amdgpu 0000:0a:00.0: ring comp_1.3.0 uses VM inv eng 6 on hub 0 Aug 02 23:40:58 archrur kernel: amdgpu 0000:0a:00.0: ring comp_1.0.1 uses VM inv eng 7 on hub 0 Aug 02 23:40:58 archrur kernel: amdgpu 0000:0a:00.0: ring comp_1.1.1 uses VM inv eng 8 on hub 0 Aug 02 23:40:58 archrur kernel: amdgpu 0000:0a:00.0: ring comp_1.2.1 uses VM inv eng 9 on hub 0 Aug 02 23:40:58 archrur kernel: amdgpu 0000:0a:00.0: ring comp_1.3.1 uses VM inv eng 10 on hub 0 Aug 02 23:40:58 archrur kernel: amdgpu 0000:0a:00.0: ring kiq_0.2.1.0 uses VM inv eng 11 on hub 0 Aug 02 23:40:58 archrur kernel: amdgpu 0000:0a:00.0: ring sdma0 uses VM inv eng 0 on hub 8 Aug 02 23:40:58 archrur kernel: amdgpu 0000:0a:00.0: ring sdma0 shares VM invalidation engine 0 with ring page0 on hub 8 Aug 02 23:40:58 archrur kernel: amdgpu 0000:0a:00.0: ring page0 uses VM inv eng 1 on hub 8 Aug 02 23:40:58 archrur kernel: amdgpu 0000:0a:00.0: ring sdma1 uses VM inv eng 4 on hub 8 Aug 02 23:40:58 archrur kernel: amdgpu 0000:0a:00.0: ring sdma1 shares VM invalidation engine 4 with ring page1 on hub 8 Aug 02 23:40:58 archrur kernel: amdgpu 0000:0a:00.0: ring page1 uses VM inv eng 5 on hub 8 Aug 02 23:40:58 archrur kernel: amdgpu 0000:0a:00.0: ring uvd_0 uses VM inv eng 6 on hub 8 Aug 02 23:40:58 archrur kernel: amdgpu 0000:0a:00.0: ring uvd_enc_0.0 uses VM inv eng 7 on hub 8 Aug 02 23:40:58 archrur kernel: amdgpu 0000:0a:00.0: ring uvd_enc_0.1 uses VM inv eng 8 on hub 8 Aug 02 23:40:58 archrur kernel: amdgpu 0000:0a:00.0: ring vce0 uses VM inv eng 9 on hub 8 Aug 02 23:40:58 archrur kernel: amdgpu 0000:0a:00.0: ring vce1 uses VM inv eng 10 on hub 8 Aug 02 23:40:58 archrur kernel: amdgpu 0000:0a:00.0: ring vce2 uses VM inv eng 11 on hub 8 Aug 02 23:40:58 archrur kernel: amdgpu 0000:0a:00.0: GPU reset(2) succeeded! Aug 02 23:40:58 archrur kwin_wayland[1148]: 0x3: GL_CONTEXT_LOST in context lost Aug 02 23:40:58 archrur kwin_wayland[1148]: 0x3: GL_CONTEXT_LOST in context lost Aug 02 23:40:58 archrur kernel: amdgpu 0000:0a:00.0: [drm] device wedged, but no recovery needed Aug 02 23:40:58 archrur org_kde_powerdevil[50040]: [ 50102][49011.149156] Udev event detected Aug 02 23:40:58 archrur org_kde_powerdevil[50040]: [ 50102][49011.149262] Udev_Event_Detail Aug 02 23:40:58 archrur org_kde_powerdevil[50040]: [ 50102][49011.149262] prop_subsystem: drm Aug 02 23:40:58 archrur org_kde_powerdevil[50040]: [ 50102][49011.149262] prop_action: change Aug 02 23:40:58 archrur org_kde_powerdevil[50040]: [ 50102][49011.149262] prop_connector: (null) Aug 02 23:40:58 archrur org_kde_powerdevil[50040]: [ 50102][49011.149262] prop_devname: /dev/dri/card1 Aug 02 23:40:58 archrur org_kde_powerdevil[50040]: [ 50102][49011.149262] prop_devmode: (null) Aug 02 23:40:58 archrur org_kde_powerdevil[50040]: [ 50102][49011.149262] prop_hotplug: (null) Aug 02 23:40:58 archrur org_kde_powerdevil[50040]: [ 50102][49011.149262] prop_major: 226 Aug 02 23:40:58 archrur org_kde_powerdevil[50040]: [ 50102][49011.149262] prop_minor: 1 Aug 02 23:40:58 archrur org_kde_powerdevil[50040]: [ 50102][49011.149262] sysname: card1 Aug 02 23:40:58 archrur org_kde_powerdevil[50040]: [ 50102][49011.149262] syspath: /sys/devices/pci0000:00/0000:00:03.1/0000:08:00.0/0000:09:00.0/0000:0a:00.0/drm/card1 Aug 02 23:40:58 archrur org_kde_powerdevil[50040]: [ 50102][49011.149262] attr_name: (null) Aug 02 23:40:58 archrur org_kde_powerdevil[50040]: [ 50102][49011.149335] (dw_watch_display_connections) Time since last return from sleep = 49011076251613 ns = 49011076 ms Aug 02 23:40:58 archrur org_kde_powerdevil[50040]: [ 50102][49011.149343] (recently_resumed_from_sleep_by_clocktime) Resume from sleep detected by BOOTTIME/MONOTONIC Aug 02 23:40:58 archrur org_kde_powerdevil[50040]: [ 50102][49011.149349] (dw_watch_display_connections) Recently resumed from sleep detected Aug 02 23:40:58 archrur org_kde_powerdevil[50040]: [ 50102][49011.149355] (dw_watch_display_connections) Pausing for 1000 millisec Aug 02 23:40:58 archrur kwin_wayland[1148]: 0x3: GL_CONTEXT_LOST in context lost Aug 02 23:40:58 archrur kwin_wayland[1148]: 0x3: GL_CONTEXT_LOST in context lost Aug 02 23:40:58 archrur kwin_wayland[1148]: 0x3: GL_CONTEXT_LOST in context lost ... (and so on. This pattern essentially repeats until system was shutdown via power button) -- You are receiving this mail because: You are watching all bug changes.
