| Summary: | [CI][HSW] igt@drv_selftest@live_hangcheck - SW HANG - Incomplete | ||
|---|---|---|---|
| Product: | DRI | Reporter: | Marta Löfstedt <marta.lofstedt> |
| Component: | DRM/Intel | Assignee: | Intel GFX Bugs mailing list <intel-gfx-bugs> |
| Status: | CLOSED FIXED | QA Contact: | Intel GFX Bugs mailing list <intel-gfx-bugs> |
| Severity: | normal | ||
| Priority: | high | CC: | intel-gfx-bugs |
| Version: | DRI git | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | ReadyForDev | ||
| i915 platform: | HSW | i915 features: | |
|
Description
Marta Löfstedt
2017-09-25 12:24:43 UTC
NOTE: the referred pstore file is identical to the one in BUG 102974. *** Bug 102974 has been marked as a duplicate of this bug. *** <marta_> Adrinael, you mentioned something about being wrong testlist for shards on CI_DRM_3026, could you elaborate. I have already filed bugs for this run... <Adrinael> CI_DRM_3126 <Adrinael> It was running everything ever on accident <Adrinael> ivyl, ^ right? <marta_> but it was only 3 new drv_selftests and 3 new gem tests, for sure we have more than that blacklisted <ivyl> yep, due to elaborated nature of deployment method, and streamilining it to use just "make install" an inevitable error occured on the human-Jenkins boundary. <ivyl> marta_: it run with ALL ALL, but it got cancelled pretty quickly <ivyl> and then rerun properly <ivyl> what you see is the merge of both <Adrinael> tools_test@* got "broken" by make install -deployment btw * Weine (~dweineha@134.134.139.76) has joined <ivyl> as jenkins haven't cleaned staging area for results <Adrinael> marta_, if you file a bug on igt@tools_test@tools_test, make it an IGT bug <ivyl> so sorry about confusion, it wasn't intended and I hoped the rerun will fix it <ivyl> but as you can see we have the few leftovers <marta_> OK, I will archive if needed when I results from the next run. * Ahuj (Thunderbir@nat/intel/x-ngcmqbhsvahecvri) has joined <ivyl> results from -27 already came in and they look clean, we also should have results for -28 in half an hour or so *** Bug 102970 has been marked as a duplicate of this bug. *** commit 87dc03ad268f285065cdd2e2ac75701a1f04d0b8 Author: Chris Wilson <chris@chris-wilson.co.uk> Date: Fri Sep 15 14:09:29 2017 +0100 drm/i915/selftests: Try to recover from a wedged GPU during reset tests If we see the seqno stop progressing, we abandon the test for fear that the GPU died following the reset. However, during test teardown we still wait for the GPU to idle before continuing, but we have already confirmed that the GPU is dead. Furthermore, since we are inside a reset test, we have disabled the hangchecker, and so there is no safety net and we wait indefinitely. Detect the stuck GPU and declare it wedged as a state of emergency so we can escape. Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk> Cc: Jari Tahvanainen <jari.tahvanainen@intel.com> Cc: Mika Kuoppala <mika.kuoppala@linux.intel.com> Link: https://patchwork.freedesktop.org/patch/msgid/20170915130929.18892-1-chris@chris-wilson.co.uk Tested-by: Jari Tahvanainen <jari.tahvanainen@intel.com> Reviewed-by: Mika Kuoppala <mika.kuoppala@linux.intel.com> Closing. According to CI results, this tests hasn't been failed on HSW for a while now. |
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.