Bug 110633 - [CI][DRMTIP][gvt] igt@gem_exec_create@forked - dmesg-fail - *ERROR* rcs0 reset request timed out
Summary: [CI][DRMTIP][gvt] igt@gem_exec_create@forked - dmesg-fail - *ERROR* rcs0 rese...
Status: RESOLVED WORKSFORME
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: DRI git
Hardware: Other All
: medium normal
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard: ReadyForDev
Keywords:
Depends on:
Blocks:
 
Reported: 2019-05-07 07:57 UTC by Lakshmi
Modified: 2019-08-29 14:17 UTC (History)
1 user (show)

See Also:
i915 platform: SKL
i915 features: GEM/Other


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Lakshmi 2019-05-07 07:57:09 UTC
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_277/fi-skl-gvtdvm/igt@gem_exec_create@forked.html

Starting subtest: forked
(gem_exec_create:1040) igt_aux-CRITICAL: Test assertion failure function sig_abort, file ../lib/igt_aux.c:501:
(gem_exec_create:1040) igt_aux-CRITICAL: Failed assertion: !"GPU hung"
Subtest forked failed.
**** DEBUG ****
(gem_exec_create:1040) DEBUG: Test requirement passed: nengine
(gem_exec_create:1040) igt_debugfs-DEBUG: Opening debugfs directory '/sys/kernel/debug/dri/0'
(gem_exec_create:1040) igt_debugfs-DEBUG: Opening debugfs directory '/sys/kernel/debug/dri/0'
(gem_exec_create:1040) igt_aux-CRITICAL: Test assertion failure function sig_abort, file ../lib/igt_aux.c:501:
(gem_exec_create:1040) igt_aux-CRITICAL: Failed assertion: !"GPU hung"
(gem_exec_create:1040) igt_core-INFO: Stack trace:
(gem_exec_create:1040) igt_core-INFO:   #0 ../lib/igt_core.c:1476 __igt_fail_assert()
(gem_exec_create:1040) igt_core-INFO:   #1 ../lib/igt_aux.c:505 igt_fork_hang_detector()
(gem_exec_create:1040) igt_core-INFO:   #2 [killpg+0x40]
(gem_exec_create:1040) igt_core-INFO:   #3 ../sysdeps/unix/sysv/linux/wait.c:29 wait()
(gem_exec_create:1040) igt_core-INFO:   #4 ../lib/igt_core.c:1757 __igt_waitchildren()
(gem_exec_create:1040) igt_core-INFO:   #5 ../lib/igt_core.c:1808 igt_waitchildren()
(gem_exec_create:1040) igt_core-INFO:   #6 ../tests/i915/gem_exec_create.c:130 all()
(gem_exec_create:1040) igt_core-INFO:   #7 ../tests/i915/gem_exec_create.c:147 __real_main133()
(gem_exec_create:1040) igt_core-INFO:   #8 ../tests/i915/gem_exec_create.c:133 main()
(gem_exec_create:1040) igt_core-INFO:   #9 ../csu/libc-start.c:344 __libc_start_main()
(gem_exec_create:1040) igt_core-INFO:   #10 [_start+0x2a]
****  END  ****
Subtest forked: FAIL (10.209s)
gem_exec_create: ../lib/igt_core.c:1532: igt_exit: Assertion `!num_test_children' failed.
Received signal SIGABRT.
Stack trace: 
 #0 [fatal_sig_handler+0xd5]
 #1 [killpg+0x40]
 #2 [gsignal+0xc7]
 #3 [abort+0x141]
 #4 [uselocale+0x33a]
 #5 [__assert_fail+0x42]
 #6 [igt_exit+0x1e6]
 #7 [main+0x49]
 #8 [__libc_start_main+0xe7]
 #9 [_start+0x2a]

Dmesg-Warnings	
<3> [86.012100] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 00000001, RESET_CTL: 00000001}
<3> [86.017532] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 00000001, RESET_CTL: 00000001}
Comment 1 CI Bug Log 2019-05-07 07:57:58 UTC
The CI Bug Log issue associated to this bug has been updated.

### New filters associated

* SKL: igt@gem_exec_create@forked - dmesg-fail - *ERROR* rcs0 reset request timed out
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_277/fi-skl-gvtdvm/igt@gem_exec_create@forked.html
Comment 2 CI Bug Log 2019-06-13 06:30:54 UTC
A CI Bug Log filter associated to this bug has been updated:

{- SKL: igt@gem_exec_create@forked - dmesg-fail - *ERROR* rcs0 reset request timed out -}
{+ SKL: igt@gem_exec_create@forked - dmesg-fail - *ERROR* rcs0 reset request timed out +}

New failures caught by the filter:

  * https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_305/fi-skl-gvtdvm/igt@gem_exec_await@wide-contexts.html
Comment 3 CI Bug Log 2019-06-13 06:31:44 UTC
A CI Bug Log filter associated to this bug has been updated:

{- SKL: igt@gem_exec_create@forked - dmesg-fail - *ERROR* rcs0 reset request timed out -}
{+ SKL: igt@gem_exec_create@forked|igt@gem_exec_await@wide-contexts - dmesg-fail - *ERROR* rcs0 reset request timed out +}


  No new failures caught with the new filter
Comment 4 Francesco Balestrieri 2019-07-30 04:44:59 UTC
Happened only on SKL GVT configuration. A closer look at the logs is needed.
Comment 5 Chris Wilson 2019-08-09 07:28:00 UTC
Happened once, now 404. No longer actionable.
Comment 6 CI Bug Log 2019-08-29 14:10:42 UTC
A CI Bug Log filter associated to this bug has been updated:

{- SKL: igt@gem_exec_create@forked|igt@gem_exec_await@wide-contexts - dmesg-fail - *ERROR* rcs0 reset request timed out -}
{+ SKL GLK: random gem tests - dmesg-fail / dmesg-warn - *ERROR* rcs0 reset request timed out +}


  No new failures caught with the new filter
Comment 7 CI Bug Log 2019-08-29 14:12:46 UTC
A CI Bug Log filter associated to this bug has been updated:

{- SKL GLK: random gem tests - dmesg-fail / dmesg-warn - *ERROR* rcs0 reset request timed out -}
{+ SKL GLK: random gem tests - dmesg-fail / dmesg-warn - *ERROR* rcs0 reset request timed out +}


  No new failures caught with the new filter
Comment 8 Martin Peres 2019-08-29 14:14:43 UTC
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14110/shard-glk5/igt@i915_selftest@live_gtt.html

<3> [2209.947994] [drm:gen8_reset_engines [i915]] *ERROR* rcs'0 reset request timed out: {request: 00000001, RESET_CTL: 00000001}
<3> [2209.948914] [drm:gen8_reset_engines [i915]] *ERROR* rcs'0 reset request timed out: {request: 00000001, RESET_CTL: 00000001}
Comment 9 Chris Wilson 2019-08-29 14:17:17 UTC
(In reply to Martin Peres from comment #8)
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14110/shard-glk5/
> igt@i915_selftest@live_gtt.html
> 
> <3> [2209.947994] [drm:gen8_reset_engines [i915]] *ERROR* rcs'0 reset
> request timed out: {request: 00000001, RESET_CTL: 00000001}
> <3> [2209.948914] [drm:gen8_reset_engines [i915]] *ERROR* rcs'0 reset
> request timed out: {request: 00000001, RESET_CTL: 00000001}

That is not this bug. That is a TLB miss on initialisation.


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.