Bug 112126 - [CI][SHARDS] GEM tests - timeout - Received signal SIGQUIT. Stack trace: #0 [fatal_sig_handler+0xd6]
Summary: [CI][SHARDS] GEM tests - timeout - Received signal SIGQUIT. Stack trace: #0 [...
Status: NEW
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: DRI git
Hardware: Other All
: not set not set
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
: 112204 (view as bug list)
Depends on:
Blocks:
 
Reported: 2019-10-25 05:47 UTC by Lakshmi
Modified: 2019-11-04 11:42 UTC (History)
1 user (show)

See Also:
i915 platform: TGL
i915 features:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Lakshmi 2019-10-25 05:47:45 UTC
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7167/shard-tglb7/igt@gem_linear_blits@interruptible.html
Received signal SIGQUIT.
Stack trace: 
 #0 [fatal_sig_handler+0xd6]
 #1 [killpg+0x40]
 #2 [__write+0x12]
 #3 [writeN+0x2d]
 #4 [igt_sysfs_vprintf+0xf4]
 #5 [igt_sysfs_printf+0x8f]
 #6 [igt_drop_caches_set+0x2a]
 #7 [drm_open_driver+0x60]
 #8 [__real_main223+0x169]
 #9 [main+0x27]
 #10 [__libc_start_main+0xe7]
 #11 [_start+0x2a]
Comment 1 CI Bug Log 2019-10-25 05:48:35 UTC
The CI Bug Log issue associated to this bug has been updated.

### New filters associated

* TGL: igt@gem_linear_blits@interruptible|igt@kms_color@pipe-b-ctm-red-to-blue - timeout - Received signal SIGQUIT. Stack trace: #0 [fatal_sig_handler+0xd6]
  - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7167/shard-tglb7/igt@gem_linear_blits@interruptible.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7167/shard-tglb7/igt@kms_color@pipe-b-ctm-red-to-blue.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14953/shard-tglb1/igt@gem_linear_blits@interruptible.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14953/shard-tglb1/igt@kms_color@pipe-b-ctm-red-to-blue.html
Comment 2 Jani Saarinen 2019-10-25 16:25:59 UTC
Should we have different bugs to gem / kms. This is propably due to test hangs and CI kills test?
Comment 3 CI Bug Log 2019-10-28 08:17:17 UTC
A CI Bug Log filter associated to this bug has been updated:

{- TGL: igt@gem_linear_blits@interruptible|igt@kms_color@pipe-b-ctm-red-to-blue - timeout - Received signal SIGQUIT. Stack trace: #0 [fatal_sig_handler+0xd6] -}
{+ TGL: All tests - timeout - Received signal SIGQUIT. Stack trace: #0 [fatal_sig_handler+0xd6] +}

New failures caught by the filter:

  * https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7173/shard-tglb8/igt@kms_ccs@pipe-b-missing-ccs-buffer.html
  * https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7173/shard-tglb8/igt@kms_flip@2x-plain-flip.html
  * https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5241/shard-tglb7/igt@gem_mocs_settings@mocs-reset-bsd1.html
  * https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5241/shard-tglb7/igt@kms_prop_blob@invalid-set-prop-any.html
Comment 4 CI Bug Log 2019-10-29 11:14:32 UTC
A CI Bug Log filter associated to this bug has been updated:

{- TGL: All tests - timeout - Received signal SIGQUIT. Stack trace: #0 [fatal_sig_handler+0xd6] -}
{+ TGL: GEM tests- timeout - Received signal SIGQUIT. Stack trace: #0 [fatal_sig_handler+0xd6] +}


  No new failures caught with the new filter
Comment 5 Lakshmi 2019-10-29 11:18:29 UTC
(In reply to Jani Saarinen from comment #2)
> Should we have different bugs to gem / kms. This is propably due to test
> hangs and CI kills test?

Bug 112168 is created for kms tests.
Comment 6 CI Bug Log 2019-10-30 11:24:20 UTC
A CI Bug Log filter associated to this bug has been updated:

{- TGL: GEM tests- timeout - Received signal SIGQUIT. Stack trace: #0 [fatal_sig_handler+0xd6] -}
{+ TGL: GEM tests- timeout - Received signal SIGQUIT. Stack trace: #0 [fatal_sig_handler+0xd6] +}

New failures caught by the filter:

  * https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7213/shard-tglb7/igt@syncobj_wait@wait-all-for-submit-delayed-submit.html
Comment 7 Chris Wilson 2019-11-04 11:42:04 UTC
*** Bug 112204 has been marked as a duplicate of this bug. ***


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.