Created attachment 134575 [details] xorg.log I am using plasma 5 with compositing enabled for a long time. Since kernel upgrade to 4.13, I see occasional hangs of the graphics on VT7. It happened 3 times already and always during switch of the desktops. The animation just hangs after the switch, still showing what desktop I ended at. After that I still can move with the mouse pointer, but nothing else. No traces in dmesg or Xorg.log -- the GPU is not hung. I can change to VT1 and reboot. I am not sure what states should I provide?
That xorg.log says -modesetting, fwiw. No error messages anywhere, suggests that it is just a bad pageflip request. If you are stuck, either enable DebugPresent in xorg, or --enable-debug=full in sna, and we can go over the logs looking for the needle.
My bad, I wanted to write ivb, not sna :/. So with modesetting as you correctly deduced, is there anything to trap? Will DebugPresent still help?
I think DebugPresent is the avenue we want to persue, it will at least give us clue as to the sequence that lead up to the hang. On top of that, drm.debug=0x1e may help, but if it is bad userspace timing not so much.
(In reply to Chris Wilson from comment #3) > I think DebugPresent is the avenue we want to persue, it will at least give > us clue as to the sequence that lead up to the hang. On top of that, > drm.debug=0x1e may help, but if it is bad userspace timing not so much. Changing to NEEDINFO.
First of all. Sorry about spam. This is mass update for our bugs. Sorry if you feel this annoying but with this trying to understand if bug still valid or not. If bug investigation still in progress, please ignore this and I apologize! If you think this is not anymore valid, please comment to the bug that can be closed. If you haven't tested with our latest pre-upstream tree(drm-tip), can you do that also to see if issue is valid there still and if you cannot see issue there, please comment to the bug.
Closing, please re-open if still occurs.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.