Bug 103049 - [BAT] several igt@gem_flink_basic tests gives dmesg warning
Summary: [BAT] several igt@gem_flink_basic tests gives dmesg warning
Status: CLOSED DUPLICATE of bug 103165
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: DRI git
Hardware: Other All
: high critical
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-10-01 08:17 UTC by Jani Saarinen
Modified: 2018-01-04 20:01 UTC (History)
1 user (show)

See Also:
i915 platform: BXT, KBL
i915 features: power/suspend-resume


Attachments
Output_basic-s4-devices (7.12 KB, text/plain)
2017-11-01 19:58 UTC, Elizabeth
no flags Details

Description Jani Saarinen 2017-10-01 08:17:41 UTC
On CI_DRM_3158 on kbl-7560u several dmesg warning from igt@gem_flink_basic tests. 

https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3158/fi-kbl-7560u/

igt@gem_flink_basic@basic
igt@gem_flink_basic@flink-lifetime
igt@gem_flink_basic@double-flink
igt@gem_flink_basic@bad-flink
igt@gem_flink_basic@bad-open

All give same:
[drm:i915_gem_idle_work_handler [i915]] *ERROR* Timeout waiting for engines to idle
[drm:drm_atomic_helper_wait_for_dependencies] *ERROR* [CRTC:36:pipe A] flip_done timed out
[drm:drm_atomic_helper_wait_for_dependencies] *ERROR* [PLANE:27:plane 1A] flip_done timed out
[drm:drm_atomic_helper_wait_for_flip_done] *ERROR* [CRTC:36:pipe A] flip_done timed out
Comment 1 Chris Wilson 2017-10-01 09:13:20 UTC
It started from the earlier suspend, nothing to do with the flink tests per-se.
Comment 2 Jani Saarinen 2017-10-02 06:16:36 UTC
So started from this problem?
https://bugs.freedesktop.org/show_bug.cgi?id=102850
Comment 3 Chris Wilson 2017-10-14 17:43:33 UTC

*** This bug has been marked as a duplicate of bug 103170 ***
Comment 4 Marta Löfstedt 2017-10-17 06:31:27 UTC
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.
Comment 5 Elizabeth 2017-11-01 19:58:26 UTC
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.
Comment 6 Elizabeth 2017-11-01 20:01:05 UTC
Same with igt@gem_exec_suspend@basic-s3.
Comment 7 Elizabeth 2017-11-13 22:54:47 UTC
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"
Comment 8 Chris Wilson 2017-11-13 22:57:33 UTC
(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.
Comment 9 Elizabeth 2017-11-14 20:05:21 UTC
Rising priority since it is BAT.
Comment 10 Marta Löfstedt 2017-11-20 14:39:02 UTC

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


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.