Created attachment 123216 [details] /sys/class/drm/card0/error [drm:i915_hangcheck_elapsed [i915]] *ERROR* Hangcheck timer elapsed... render ring idle [drm] no progress on render ring [drm] GPU HANG: ecode 7:-1:0x00000000, reason: Ring hung, action: reset [drm:intel_rcs_ctx_init [i915]] *ERROR* init render state: -11 [drm:i915_switch_context [i915]] *ERROR* ring init context: -11 drm/i915: Resetting chip after gpu hang [drm] stuck on render ring [drm] GPU HANG: ecode 7:0:0xf3cffffe, in chromium [28393], reason: Ring hung, action: reset drm/i915: Resetting chip after gpu hang 4.5.0-1-ARCH x86_64 It happened only once and never before. The system froze and recovered. Audio playback from youtube in chromium continued uninterrupted during the freeze.
Created attachment 123217 [details] intel_reg dump --all
(In reply to bugreport from comment #0) > Created attachment 123216 [details] > /sys/class/drm/card0/error > > [drm:i915_hangcheck_elapsed [i915]] *ERROR* Hangcheck timer elapsed... > render ring idle > [drm] no progress on render ring > [drm] GPU HANG: ecode 7:-1:0x00000000, reason: Ring hung, action: reset > [drm:intel_rcs_ctx_init [i915]] *ERROR* init render state: -11 > [drm:i915_switch_context [i915]] *ERROR* ring init context: -11 > drm/i915: Resetting chip after gpu hang > [drm] stuck on render ring > [drm] GPU HANG: ecode 7:0:0xf3cffffe, in chromium [28393], reason: Ring > hung, action: reset > drm/i915: Resetting chip after gpu hang > > 4.5.0-1-ARCH x86_64 > > It happened only once and never before. The system froze and recovered. > > Audio playback from youtube in chromium continued uninterrupted during the > freeze. Is it still occuring? If so, can you attached your kernel log (ie dmesg)? You may add drm.debug=0xe to your boot command line.
Created attachment 126225 [details] dmesg2
Created attachment 126226 [details] /sys/class/drm/card0/error2
this happened again yesterday. that was the second time it ever happened.
information provided, removing needinfo status
(In reply to bugreport from comment #5) > this happened again yesterday. that was the second time it ever happened. Hello, This seems too hard to replicate, and last update on this case is with kernel 4.7. A lot of changes have been made since that version, could you please confirm is it still is happening on latest kernel versions https://www.kernel.org/? Thank you.
Closing as no new occurrences of this problem have been reported since September 2016. If problem arise with latest kernel versions, please file a new bug with HW and SW information and relevant logs. Thank you.
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.