View previous topic :: View next topic |
Author |
Message |
grubber33 n00b
Joined: 27 Aug 2003 Posts: 62
|
Posted: Sun Nov 13, 2022 10:13 am Post subject: KDE Plasma on Wayland - Hardware Acceleration Lock Ups |
|
|
Hi all,
Having an issue that seems specifically related to applications using hardware acceleration on my discrete GPU in Wayland. Here are some of my observations so far:
Prints all information fine
Code: | DRI_PRIME=1 glxinfo |
Prints
Quote: | name of display: :1 |
Then the display locks up.
Works fine.
Code: | DRI_PRIME=1 glxgears |
Works fine until exiting. As soon as I press escape, the display locks up.
Locks up the display when a web page that would use hardware acceleration is loaded.
Code: | chromium --disable-gpu |
Works fine.
From all of these, I haven't gotten any log messages relating to graphics that I can find. The only related log messages I found were from Microsoft Teams in syslog before I disabled GPU acceleration in Teams:
Quote: | Nov 12 20:48:57 laptop kernel: GpuWatchdog[6609]: segfault at 0 ip 0000558c93edf376 sp 00007f346e74e7f0 error 6 in teams[558c90432000+5fcb000]
Nov 12 20:48:57 laptop kernel: Code: 89 de e8 7d 01 71 ff 80 7d cf 00 79 09 48 8b 7d b8 e8 1e 3e bd fe 41 8b 84 24 e0 00 00 00 89 45 b8 48 8d 7d b8 e8 fa 80 55 fc <c7> 04 25 00 00 00 00 37 13 00 00 48 83 c4 38 5b 41 5c 41 5d 41 5e
Nov 12 20:49:27 laptop kernel: GpuWatchdog[7877]: segfault at 0 ip 0000558c93edf376 sp 00007f346e74e7f0 error 6 in teams[558c90432000+5fcb000]
Nov 12 20:49:27 laptop kernel: Code: 89 de e8 7d 01 71 ff 80 7d cf 00 79 09 48 8b 7d b8 e8 1e 3e bd fe 41 8b 84 24 e0 00 00 00 89 45 b8 48 8d 7d b8 e8 fa 80 55 fc <c7> 04 25 00 00 00 00 37 13 00 00 48 83 c4 38 5b 41 5c 41 5d 41 5e |
Other than that, nothing else in syslog, kernel logs, sddm logs or Xorg logs.
My setup is a laptop with the laptop screen running from the integrated graphics in 1080p and an external monitor running from the discrete graphics over HDMI in 1440p. The discrete graphics card is a Radeon RX 5500M using the AMDGPU drivers. To clarify, all of the above work fine when I'm not using Wayland (was previously using Cinnamon), but I would really like to figure this issue out as Plasma on Wayland is the only way I've been able to get both monitors working at the same time so far.
It may also be helpful to note that this isn't a full-system lock up. For example, after the display locks up, if I close the lid on my laptop, it gets logged in syslog, or if I turn on my bluetooth speaker it connects automatically while locked up. However, I'm not able to switch to a terminal using ctrl+alt+f1 and I always have to hard-reset my laptop when this happens.
Any suggestions are highly appreciated! |
|
Back to top |
|
|
grubber33 n00b
Joined: 27 Aug 2003 Posts: 62
|
Posted: Sun Nov 13, 2022 12:31 pm Post subject: |
|
|
Found some related information via Google:
https://community.spotify.com/t5/Desktop-Linux/Spotify-segfaults-and-freezes-graphical-session/td-p/4916797
The disassembled code from the Teams segfault contains that same instruction:
Code: | 0: 89 de mov esi,ebx
2: e8 7d 01 71 ff call 0xffffffffff710184
7: 80 7d cf 00 cmp BYTE PTR [rbp-0x31],0x0
b: 79 09 jns 0x16
d: 48 8b 7d b8 mov rdi,QWORD PTR [rbp-0x48]
11: e8 1e 3e bd fe call 0xfffffffffebd3e34
16: 41 8b 84 24 e0 00 00 mov eax,DWORD PTR [r12+0xe0]
1d: 00
1e: 89 45 b8 mov DWORD PTR [rbp-0x48],eax
21: 48 8d 7d b8 lea rdi,[rbp-0x48]
25: e8 fa 80 55 fc call 0xfffffffffc558124
2a: c7 04 25 00 00 00 00 mov DWORD PTR ds:0x0,0x1337
31: 37 13 00 00
35: 48 83 c4 38 add rsp,0x38
39: 5b pop rbx
3a: 41 5c pop r12
3c: 41 5d pop r13
3e: 41 5e pop r14 |
But I don't have the technical knowledge to do anything with this information. |
|
Back to top |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|