Bug 103049

It started from the earlier suspend, nothing to do with the flink tests per-se.

So started from this problem?
https://bugs.freedesktop.org/show_bug.cgi?id=102850

*** This bug has been marked as a duplicate of bug 103170 ***

I agree that it appear as if on BAT for KBL-r there is a pattern, see for example CI_DRM_3248 on KBL-r. It starts at: 

https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3248/fi-kbl-r/igt@gem_exec_suspend@basic-s3.html
fail: 	
(gem_exec_suspend:3243) igt-aux-CRITICAL: Test assertion failure function sig_abort, file igt_aux.c:484:
(gem_exec_suspend:3243) igt-aux-CRITICAL: Failed assertion: !"GPU hung"
Then same fail issue on:
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3248/fi-kbl-r/igt@gem_exec_suspend@basic-s4-devices.html

Then we get dmesg-warn on the gem_flink_basic tests:
[  393.405168] [drm:i915_gem_idle_work_handler [i915]] *ERROR* Timeout waiting for engines to idle

and then there is a softdog incomplete on: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3248/fi-kbl-r/igt@gem_linear_blits@basic.html

BUG 103170 is about KBL incompletes without pstore logs. I don't want this dmesg-warn to be duplicate on that, if this should be douplicated it should be on where this started which is igt@gem_exec_suspend@basic-s3. However, since igt@gem_exec_suspend@basic-s3 is covered by BUG 102846, which is about softdog incomplete, we are currently hiding this fail on !"GPU hung". We are currently working on improving cibuglog tracking so that we track on the different fail reasons instead of any reason for a specific test.

Created attachment 135204 [details]
Output_basic-s4-devices

(In reply to Marta Löfstedt from comment #4)
> ... we are currently hiding this fail on !"GPU hung". We are
> currently working on improving cibuglog tracking so that we track on the
> different fail reasons instead of any reason for a specific test.
Ok, so if I understand then this goes here:
With IGT-Version: 1.20-g7aac0e8 (x86_64) (Linux: 4.14.0-rc7-drm-intel-qa-ww44-commit-ec9f758+ x86_64) on KBL I got the same assertion on test igt@gem_exec_suspend@basic-s4-devices
 
(gem_exec_suspend:21954) igt-aux-CRITICAL: Test assertion failure function sig_abort, file igt_aux.c:484:
(gem_exec_suspend:21954) igt-aux-CRITICAL: Failed assertion: !"GPU hung"
Subtest basic-S4-devices failed.

Same with igt@gem_exec_suspend@basic-s3.

I'm seeing this behavior on BXT also with test igt@gem_exec_suspend@basic-s3 and IGT-Version: 1.20-gf370d59 (x86_64) (Linux: 4.14.0-rc8-drm-intel-qa-ww46-commit-9a81c14+ x86_64)

Subtest basic-S3-devices: FAIL (15.404s)
[cmd] rtcwake: assuming RTC uses UTC ...
rtcwake: wakeup from "mem" using /dev/rtc0 at Tue Nov 14 17:33:42 2017
(gem_exec_suspend:3828) igt-aux-CRITICAL: Test assertion failure function sig_abort, file igt_aux.c:484:
(gem_exec_suspend:3828) igt-aux-CRITICAL: Failed assertion: !"GPU hung"

(In reply to Elizabeth from comment #5)
> Created attachment 135204 [details]
> Output_basic-s4-devices
> 
> (In reply to Marta Löfstedt from comment #4)
> > ... we are currently hiding this fail on !"GPU hung". We are
> > currently working on improving cibuglog tracking so that we track on the
> > different fail reasons instead of any reason for a specific test.
> Ok, so if I understand then this goes here:
> With IGT-Version: 1.20-g7aac0e8 (x86_64) (Linux:
> 4.14.0-rc7-drm-intel-qa-ww44-commit-ec9f758+ x86_64) on KBL I got the same
> assertion on test igt@gem_exec_suspend@basic-s4-devices
>  
> (gem_exec_suspend:21954) igt-aux-CRITICAL: Test assertion failure function
> sig_abort, file igt_aux.c:484:
> (gem_exec_suspend:21954) igt-aux-CRITICAL: Failed assertion: !"GPU hung"
> Subtest basic-S4-devices failed.

No, this is not related.

Rising priority since it is BAT.

*** This bug has been marked as a duplicate of bug 103165 ***