Created attachment 134088 [details] /sys/class/drm/card0/error Whenever I run into a 360 degree photo or video, my laptop stalls for seconds and I get the below dump in my dmesg. This is very reproducible, happens every time. Let me know what other information you need. [10166.900764] [drm] GPU HANG: ecode 9:0:0x86dffffd, in chrome [2283], reason: Hang on rcs0, action: reset [10166.900766] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. [10166.900766] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel [10166.900767] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. [10166.900767] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. [10166.900767] [drm] GPU crash dump saved to /sys/class/drm/card0/error [10166.900773] i915 0000:00:02.0: Resetting rcs0 after gpu hang [10182.892356] i915 0000:00:02.0: Resetting rcs0 after gpu hang [10193.052222] asynchronous wait on fence i915:Xorg[1101]/0:3ee4c timed out [10193.052321] i915 0000:00:02.0: Resetting rcs0 after gpu hang Laptop is a Lenovo X1, generation 4. Issue happened on 4.13, and also happens on current -git as of yesterday.
I updated the DRI driver and Mesa components to the newest available from ubuntu-x-swat, but that didn't change anything. The laptop is running Mint 18.2, fwiw.
(In reply to Jens Axboe from comment #1) > I updated the DRI driver and Mesa components to the newest available from > ubuntu-x-swat, but that didn't change anything. The laptop is running Mint > 18.2, fwiw. Hello Jens, Could you share the Mesa and Kernel that you're actually using? Also, if this is still reproducible with latest, could you share a 360 photo to try to reproduce? What desktop are you using, also X version? Thanks.
It no longer reproduces... Let me know if you still want some info, otherwise feel free to close this bug report.
Thanks for your time Jens. Closing issue.
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.