[Bug 100046] [BAT][HSW] igt at gem_busy@basic-hang-default

[bugzilla-daemon at freedesktop.org]

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

--- Comment #1 from Marta Löfstedt <marta.lofstedt at intel.com> ---
In above run I dmesg has:
[   84.105787] [IGT] gem_busy: starting subtest basic-hang-default
[  150.099693] INFO: rcu_preempt detected stalls on CPUs/tasks:
[  150.099743]  0-...: (1 GPs behind) idle=c4c/0/0 softirq=6778/6778 fqs=0 
[  150.099797]  1-...: (1 GPs behind) idle=ffc/0/0 softirq=6688/6688 fqs=0 
[  150.099810]  2-...: (0 ticks this GP) idle=264/0/0 softirq=7681/7681 fqs=0 
[  150.099823]  3-...: (1 GPs behind) idle=7e4/0/0 softirq=6616/6616 fqs=0 
[  150.099836]  4-...: (11 GPs behind) idle=018/0/0 softirq=6439/6439 fqs=0 
[  150.099848]  7-...: (0 ticks this GP) idle=864/0/0 softirq=6884/6884 fqs=0 
[  150.099861]  (detected by 6, t=65002 jiffies, g=3493, c=3492, q=1)

However, in passing runs we typically see:
[   80.657663] [IGT] gem_busy: starting subtest basic-hang-default
[   98.721063] [drm] GPU HANG: ecode 7:0:0xe757feff, in gem_busy [7019],
reason: No progress on render ring, action: reset
[   98.721313] [drm:i915_reset_and_wakeup [i915]] resetting chip
[   98.721386] drm/i915: Resetting chip after gpu hang
[   98.722371] [drm:i915_gem_reset [i915]] context gem_busy[7019]/0 marked
guilty (score 10) banned? no
[   98.722402] [drm:i915_gem_reset [i915]] resetting render ring to restart
from tail of request 0x168
[   98.722566] [drm:intel_print_rc6_info [i915]] Enabling RC6 states: RC6 on
[   98.730562] [drm:init_workarounds_ring [i915]] render ring: Number of
context specific w/a: 0
[   98.730648] [drm:intel_guc_setup [i915]] GuC fw status: path (null), fetch
NONE, load NONE
[   98.730894] [IGT] gem_busy: exiting, ret=0

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