| What | Removed | Added |
|---|---|---|
| QA Contact | intel-gfx-bugs@lists.freedesktop.org | |
| Component | DRM/Intel | IGT |
| Assignee | intel-gfx-bugs@lists.freedesktop.org | dri-devel@lists.freedesktop.org |
*** Bug 102620 has been marked as a du= plicate of this bug. ***
Related igt commit 4f082c35d2df545f81d202ae1a08463f6c123552 (u= pstream/master) Author: Chris Wilson <ch= ris@chris-wilson.co.uk> Date: Fri Sep 8 13:48:05 2017 +0100 igt/gem_eio: Install an exithandler to unwedge the device after failure Under normal conditions, we try to repair the damage we inflict to the GPU, but if we fail we don't. Make sure that if the test does die, we do try to restore normal operation by using an atexit handler. Bugzilla: https://bugs.freedesktop.org/show_bug.= cgi?id=3D102616 Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk> Reviewed-by: Arkadiusz Hiler <arkadiusz.hiler@intel.com>
*** Bug 102652 has been marked as a du= plicate of this bug. ***
| What | Removed | Added |
|---|---|---|
| Status | NEW | RESOLVED |
| Resolution | --- | FIXED |
commit 92e457d0ffe930369d09bc83d3d3ed90c9bd6cb1 Author: Chris Wilson <ch= ris@chris-wilson.co.uk> Date: Fri Sep 8 11:33:15 2017 +0100 igt/gem_eio: inflight wedged requires long plugging As our hangcheck may exceed 10s to declare the device wedged, we need to hold the plugging fence indefinitely. This makes using vgem as our input fence unusable, so resort to using sw_sync. At the same time, we can then check that the async result is also -EIO. Bugzilla: https://bugs.freedesktop.org/show_bug.= cgi?id=3D102616 Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk> Reviewed-by: Micha=C5=82 Winiarski <michal.winiarski@intel.com>
| What | Removed | Added |
|---|---|---|
| i915 platform | APL | BXT |
igt@gem_eio@in-flight with "Failed assertion"= ; was not seen recently and there are no open bugs related to failed assertion. So closing this bug.
| What | Removed | Added |
|---|---|---|
| Status | RESOLVED | CLOSED |
(In reply to Lakshmi from comment #8) > igt@gem_eio@in-flight test failure with = "Failed assertion" was not seen recently and there are no open bu= gs related to failed assertion. So closing this bug.