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]
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
Should we have different bugs to gem / kms. This is propably due to test hangs and CI kills test?
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
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
(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.
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
*** Bug 112204 has been marked as a duplicate of this bug. ***
commit a6edbca74b305adc165e67065d7ee766006e6a48 Author: Chris Wilson <chris@chris-wilson.co.uk> Date: Wed Nov 20 16:55:13 2019 +0000 drm/i915/gt: Close race between engine_park and intel_gt_retire_requests
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.