Summary: | [HSW] [BAT] gem_exec_fence@await-hang-default hangs on CI | ||
---|---|---|---|
Product: | DRI | Reporter: | Jani Saarinen <jani.saarinen> |
Component: | DRM/Intel | Assignee: | Intel GFX Bugs mailing list <intel-gfx-bugs> |
Status: | CLOSED DUPLICATE | QA Contact: | Intel GFX Bugs mailing list <intel-gfx-bugs> |
Severity: | major | ||
Priority: | high | CC: | intel-gfx-bugs |
Version: | DRI git | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | HSW | i915 features: | GEM/Other |
Description
Jani Saarinen
2017-02-09 11:56:13 UTC
Private dmesg; please always attach and extract any intresting snippets. Looking at https://intel-gfx-ci.01.org/CI/CI_DRM_2176/fi-hsw-4770/dmesg-during.log gives no information as to the cause. If it was a BUG_ON, CI didn't capture the trace. Maybe this was just one occurrence. https://intel-gfx-ci.01.org/CI/fi-hsw-4770.html Should we move to staging? Only if that is a means to investigate igt/CI as to why it failed to capture the relevant info here. I saw a single hangup on this test case across 210 runs. While I don't have dmesg from it, vga console showed messages akin to: mce: [Hardware Error] CPU: HSW-4770R kernel: 15ccc64 config: from https://intel-gfx-ci.01.org/CI/CI_DRM_2243/kernel.config.bz2 OS: Fedora 25 hardware: GIGABYTE M4HM87P-00 Seen hanging twice same: https://intel-gfx-ci.01.org/CI/CI_DRM_2259/fi-hsw-4770/igt@gem_exec_fence@await-hang-default.html https://intel-gfx-ci.01.org/CI/CI_DRM_2277/fi-hsw-4770/igt@gem_exec_fence@await-hang-default.html Making a bold assumption this is a dupe of the irq issue. *** This bug has been marked as a duplicate of bug 100130 *** Seen again: https://intel-gfx-ci.01.org/CI/CI_DRM_2497/fi-hsw-4770/igt@gem_exec_fence@await-hang-default.html Documenting / marking issue known on CI. Forward duping to likely patch. *** This bug has been marked as a duplicate of bug 10672 *** *** This bug has been marked as a duplicate of bug 100672 *** |
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.