On Wed, Sep 04, 2019 at 09:17:16AM +0800, Hillf Danton wrote:
Daniel Vetter daniel@ffwll.ch
Now 11:01pm and "gnome shell stuck warning" not appear since 19:17. So looks like issue happens only when computer blocked and monitor in power save mode.
I'd bet on runtime pm or some other power saving feature in amdgpu shutting the interrupt handling down before we've handled all the interrupts. That would then result in a stuck fence.
Do we already know which fence is stuck?
It is welcomed to shed a thread of light on how to collect/print that info. Say line:xxx-yyy in path/to/amdgpu/zzz.c
Extend your backtrac warning slightly like
WARN(r, "we're stuck on fence %pS\n", fence->ops);
Also adding Harry and Alex, I'm not really working on amdgpu ... -Daniel