Summary: | [SKL execlists] WARN_ON(&target->list == &ring->request_list) from gem_reloc_vs_gpu/forked-interruptible-faulting-reloc-thrash-inactive-hang | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | DRI | Reporter: | Olivier Berthier <olivierx.berthier> | ||||||||||
Component: | DRM/Intel | Assignee: | Mika Kuoppala <mika.kuoppala> | ||||||||||
Status: | CLOSED FIXED | QA Contact: | Intel GFX Bugs mailing list <intel-gfx-bugs> | ||||||||||
Severity: | normal | ||||||||||||
Priority: | medium | CC: | intel-gfx-bugs, ramix.ben.hassine | ||||||||||
Version: | unspecified | ||||||||||||
Hardware: | x86-64 (AMD64) | ||||||||||||
OS: | Linux (All) | ||||||||||||
Whiteboard: | |||||||||||||
i915 platform: | SKL | i915 features: | GEM/execlists | ||||||||||
Attachments: |
|
Description
Olivier Berthier
2015-08-14 10:23:23 UTC
Created attachment 117678 [details]
kern.log file
Created attachment 117679 [details]
dmesg log file
Created attachment 117680 [details]
piglit results.json file
*** Bug 91640 has been marked as a duplicate of this bug. *** On SKL, following tests results are all crash: igt@gem_reloc_vs_gpu@faulting-reloc-interruptible-hang igt@gem_reloc_vs_gpu@forked-faulting-reloc-hang igt@gem_reloc_vs_gpu@forked-faulting-reloc-thrash-inactive-hang igt@gem_reloc_vs_gpu@forked-hang igt@gem_reloc_vs_gpu@forked-interruptible-faulting-reloc-hang igt@gem_reloc_vs_gpu@forked-interruptible-faulting-reloc-thrash-inactive-hang igt@gem_reloc_vs_gpu@forked-interruptible-hang igt@gem_reloc_vs_gpu@forked-interruptible-thrash-inactive-hang igt@gem_reloc_vs_gpu@forked-thrash-inactive-hang Bug scrub: Kimmo will discuss with VPG guys about this execlist related bug Created attachment 117813 [details] [review] drm/i915: Update ring space correctly on lrc context reset Should be handled by: commit 608c1a526c99d1858b02d035657e28c9837667a5 Author: Chris Wilson <chris@chris-wilson.co.uk> Date: Thu Sep 3 13:01:40 2015 +0100 drm/i915: Recover all available ringbuffer space following reset |
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.