All bdw/skl machines have random gpu hangs when running gem_storedw_loop/basic-render.
Strangely other engines are all fine, and this testcasee only uses CS instructions (so doesn't even load a full render workload).
This is kinda PO-exit criteria of fail, while bdw/skl are PV ready :(
Long-term history to make this clear can be found on the CI server under /archive/results/CI_IGT_test/igt@email@example.com
Wow, it's telling that the render ring is so slow! :)
I can run this in a loop until I get bored (>10minutes) on -nightly and haven't encountered an issue yet. I'd like to see the error state to see if there are any clues there.
I suspect Daniel got confused by the error message. For what I can see, the
gem_store_dwloop triggers the hangcheck timer elapsed, rander ring idle errors.
Created attachment 121002 [details] [review]
drm/i915: Force ordering on request submission and hangcheck
(In reply to Mika Kuoppala from comment #3)
> Created attachment 121002 [details] [review] [review]
> drm/i915: Force ordering on request submission and hangcheck
You can't move the list manipulation just like that! It's time we eliminated that list_empty() check, but this does nothing to paper over the race.
(In reply to Mika Kuoppala from comment #2)
> I suspect Daniel got confused by the error message. For what I can see, the
> gem_store_dwloop triggers the hangcheck timer elapsed, rander ring idle
Yeah I screwed up the title, it's "just" that the sw tracking got out of whack with reality, the gpu is actually perfectly fine. After all the testcase does succeed (and it checks that all the CS dw stores did land).
Same bug most likely in gem_sync/basic-render.
Author: Chris Wilson <firstname.lastname@example.org>
Date: Wed Jan 20 15:43:35 2016 +0200
drm/i915: Use ordered seqno write interrupt generation on gen8+ execlists
For the record, this only happens for me when I have an output connected - suggests some interesting hilarity with memory bw/latency.