Created attachment 137158 [de=
tails]
Kernel serial log while firing up the Awesome WM
Hello-
I've been having (for a while now, and going back a bit in terms of AMD=
GPU
tree commit history) an issue whereby the framebuffer & graphics stack
(*usually* not the kernel writ large) will hang upon firing up XOrg's XServ=
er
or a Wayland compositor (in my case, GNOME-Shell).
What compounded my frustration was that I'd rarely (if ever) see any ou=
tput
from the Xorg server, the Wayland compositor, or the kernel indicating there
was any sort of problem, save for a trapped SIGQUIT (trap3) hitting
gnome-shell.
Finally, in firing up X11 directly w/ Awesome as the WM I obtained some
kernel output which will hopefully prove useful in diagnosing this issue. =
It's
below (and attached):
amdgpu 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x00500002
amdgpu 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0A088002
amdgpu 0000:01:00.0: VM fault (0x02, vmid 5, pasid 32768) at page 5242882, =
read
from 'TC6' (0x54433600) (136)
[drm:amdgpu_job_timedout] *ERROR* ring gfx timeout, last signaled seq=3D45,=
last
emitted seq=3D48
[drm] IP block:gfx_v8_0 is hung!
[drm] GPU recovery disabled.
Doubt it's tremendously useful, but kernel output with gnome-shell (in this
case acting as a Wayland compositor) is below and attached as well:
traps: gnome-shell[1260] trap int3 ip:7f6e4b956e01 sp:7ffe72a8aa50 error:0 =
in
libglib-2.0.so.0.5200.3[7f6e4b908000+10f000]
traps: gnome-shell[1336] trap int3 ip:7f0f89b3ee01 sp:7ffefd8d3df0 error:0 =
in
libglib-2.0.so.0.5200.3[7f0f89af0000+10f000]
traps: gnome-shell[1351] trap int3 ip:7f0984cb6e01 sp:7ffd3caa7650 error:0 =
in
libglib-2.0.so.0.5200.3[7f0984c68000+10f000]
Lastly, my Xorg.0.log is attached, but you'll find it's quite boring (no
complaints, which is good, but seemingly no useful debugging information,
either).