[Bug 92774] New: [BSW] GPU reset fails after GPU HANG: *ERROR* Failed to reset chip: -5

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=92774

            Bug ID: 92774
           Summary: [BSW] GPU reset fails after GPU HANG: *ERROR* Failed
                    to reset chip: -5
           Product: DRI
           Version: DRI git
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: major
          Priority: medium
         Component: DRM/Intel
          Assignee: intel-gfx-bugs at lists.freedesktop.org
          Reporter: tomix.p.sarvela at intel.com
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
                CC: intel-gfx-bugs at lists.freedesktop.org

Created attachment 119335
  --> https://bugs.freedesktop.org/attachment.cgi?id=119335&action=edit
dmesg - [drm:i915_reset [i915]] *ERROR* Failed to reset chip: -5

We're tracking drm-intel-nightly from freedesktop.org and running IGT
(intel-gpu-tools/piglit) against each merge. Large amount of debug options is
turned on for this kernel.

On one machine the tests can cause GPU HANG, but the GPU reset fails, and rest
of the tests give the same error code. Below is the interesting part, full
dmesg attached.

Hardware is Intel NUC5CPYH (Braswell Celeron N3050)

Kuoppala, Mika <mika.kuoppala at intel.com> knows about this issue.





[  206.105691] kms_pipe_crc_basic: executing
[  206.368453] kms_pipe_crc_basic: starting subtest hang-read-crc-pipe-A
[  211.785045] [drm] stuck on render ring
[  211.798824] [drm] GPU HANG: ecode 8:0:0xfffffffe, in kms_pipe_crc_ba [5601],
reason: Ring hung, action: reset
[  211.799199] [drm] GPU hangs can indicate a bug anywhere in the entire gfx
stack, including userspace.
[  211.799209] [drm] Please file a _new_ bug report on bugs.freedesktop.org
against DRI -> DRM/Intel
[  211.799215] [drm] drm/i915 developers can then reassign to the right
component if it's not a kernel issue.
[  211.799221] [drm] The gpu crash dump is required to analyze gpu hangs, so
please always attach it.
[  211.799227] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[  211.799639] kobject: 'card0' (ffff88007906a530): kobject_uevent_env
[  211.799791] kobject: 'card0' (ffff88007906a530): fill_kobj_path: path =
'/devices/pci0000:00/0000:00:02.0/drm/card0'
[  211.802857] kobject: 'card0' (ffff88007906a530): kobject_uevent_env
[  211.803104] kobject: 'card0' (ffff88007906a530): fill_kobj_path: path =
'/devices/pci0000:00/0000:00:02.0/drm/card0'
[  212.509176] [drm:gen8_do_reset [i915]] *ERROR* render ring: reset request
timeout
[  212.509244] [drm] Simulated gpu hang, resetting stop_rings
[  212.509248] drm/i915: Resetting chip after gpu hang
[  212.509275] [drm:i915_reset [i915]] *ERROR* Failed to reset chip: -5
[  212.641248] kms_pipe_crc_basic: exiting, ret=0
[  212.656806] [drm:intel_lr_context_deferred_alloc [i915]] *ERROR* ring create
req: -5
[  212.853766] gem_ctx_param_basic: executing
[  212.857279] [drm:intel_lr_context_deferred_alloc [i915]] *ERROR* ring create
req: -5
[  212.861674] gem_ctx_param_basic: exiting, ret=99
[  213.050754] kms_addfb_basic: executing
[  213.053785] [drm:intel_lr_context_deferred_alloc [i915]] *ERROR* ring create
req: -5
[  213.061222] kms_addfb_basic: exiting, ret=99

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20151102/553e6972/attachment.html>