<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_ASSIGNED "
title="ASSIGNED - [CI] igt@drv_module_reload@basic-reload| igt@gem_exec_schedule@* - fail - !"GPU hung""
href="https://bugs.freedesktop.org/show_bug.cgi?id=102848#c29">Comment # 29</a>
on <a class="bz_bug_link
bz_status_ASSIGNED "
title="ASSIGNED - [CI] igt@drv_module_reload@basic-reload| igt@gem_exec_schedule@* - fail - !"GPU hung""
href="https://bugs.freedesktop.org/show_bug.cgi?id=102848">bug 102848</a>
from <span class="vcard"><a class="email" href="mailto:chris@chris-wilson.co.uk" title="Chris Wilson <chris@chris-wilson.co.uk>"> <span class="fn">Chris Wilson</span></a>
</span></b>
<pre>(In reply to Elizabeth from <a href="show_bug.cgi?id=102848#c28">comment #28</a>)
<span class="quote">> We have it on today's KBL results with test
> igt@gem_exec_suspend@basic-s4-devices:
>
> (gem_exec_suspend:9573) igt-aux-CRITICAL: Test assertion failure function
> sig_abort, file igt_aux.c:482:
> (gem_exec_suspend:9573) igt-aux-CRITICAL: Failed assertion: !"GPU hung"
> Subtest basic-S4-devices failed.
>
> IGT-Version: 1.20-g476c4b4 (x86_64) (Linux:
> 4.15.0-rc1-drm-intel-qa-ww48-commit-807db75+ x86_64)
> Stack trace:
> #0 [__igt_fail_assert+0x101]
> #1 [sig_abort+0x3a]
> #2 [killpg+0x40]
> #3 [__write_nocancel+0x7]
> #4 [igt_sysfs_write+0x43]
> #5 [igt_sysfs_set+0x2e]
> #6 [igt_system_suspend_autoresume+0x420]
> #7 [run_test+0x486]
> #8 [__real_main243+0x13c]
> #9 [main+0x23]
> #10 [__libc_start_main+0xf1]
> #11 [_start+0x29]
> #12 [<unknown>+0x29]
> Subtest basic-S4-devices: FAIL (16.261s)</span >
which is nothing to do with this bug.
This bug is either the sporadic SNB hang on module load, or that the timeout
for gem_exec_schedule results in a reported hung GPU. (Strange dup.)</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are on the CC list for the bug.</li>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>