https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_8/fi-bsw-n3050/igt@gem_exec_suspend@basic-s4-devices.html run.log: running: igt/gem_exec_suspend/basic-s4-devices [14/99] skip: 9, pass: 5 - FATAL: command execution failed ... Completed CI_IGT_test drmtip_8/fi-bsw-n3050/12 : FAILURE CI_IGT_test runtime 140 seconds Rebooting fi-bsw-n3050 dmesg: <7>[ 114.553802] [IGT] gem_exec_suspend: starting subtest basic-S4-devices <6>[ 116.312277] PM: hibernation entry <6>[ 116.312920] PM: Syncing filesystems ... <6>[ 116.327489] PM: done. <6>[ 121.833579] PM: hibernation exit <6>[ 121.833689] PM: hibernation entry <6>[ 122.860989] PM: Syncing filesystems ... pstore need examitation from GEM person: <0>[ 123.959096] gem_exec-1323 1..s. 116358371us : execlists_submission_tasklet: rcs0 cs-irq head=4 [4?], tail=5 [5?] ... <0>[ 123.971241] kworker/-83 1.... 117776754us : i915_request_retire: rcs0(2053) fence 18c:2053, global_seqno 2053 <0>[ 123.971372] --------------------------------- <0>[ 123.971444] Kernel Offset: 0x1f000000 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffffbfffffff)
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_13/fi-bsw-n3050/igt@kms_cursor_legacy@flip-vs-cursor-varying-size.html run.log: running: igt/kms_cursor_legacy/flip-vs-cursor-varying-size [05/75] skip: 2, pass: 2, fail: 1 / FATAL: command execution failed ... Completed CI_IGT_test drmtip_13/fi-bsw-n3050/20 : FAILURE CI_IGT_test runtime 181 seconds Rebooting fi-bsw-n3050 there is pstore , but no usable backtrace due to ftrace overwrite
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_4221/fi-bsw-cyan/igt@drv_module_reload@basic-no-display.html Nothing in the logs...
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_50/fi-bsw-n3050/igt@gem_tiled_wc.html
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_4278_45/fi-bsw-n3050/igt@gem_ctx_switch@basic-default-heavy.html
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_4370_34/fi-bsw-cyan/igt@gem_exec_basic@basic-bsd2.html https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_4519/fi-bsw-n3050/igt@drm_mm@insert_range.html https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_4549/fi-bsw-kefka/igt@drv_selftest@live_requests.html
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_4591/fi-bsw-cyan/igt@kms_pipe_crc_basic@suspend-read-crc-pipe-a.html https://intel-gfx-ci.01.org/tree/drm-tip/IGT_4586/fi-bsw-cyan/igt@kms_addfb_basic@too-high.html https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_4576/fi-bsw-cyan/igt@gem_exec_reloc@basic-gtt-read-active.html
Last time the issue was seen on IGT_4593/CI_DRM_4653 3 weeks 2 days ago. Before that this issue used to occur once in every few rounds (~10). Need to keep this issue open for few more weeks to confirm that it is closed if no failures.
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_4840/fi-bsw-cyan/igt@kms_addfb_basic@bad-pitch-128.html
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_114/fi-bsw-n3050/igt@kms_flip@dpms-off-confusion.html
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_136/fi-bsw-n3050/igt@gem_exec_reuse@baggage.html
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_142/fi-bsw-n3050/igt@gem_exec_schedule@smoketest-all.html I suspect that the shard was a little too long.
Setting to medium since it's a meta-bug of sorts.
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_5186_108/fi-bsw-n3050/igt@gem_ctx_create@basic-files.html https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_5186_106/fi-bsw-n3050/igt@gem_ctx_create@basic-files.html <6> [61.453968] Console: switching to colour dummy device 80x25 <6> [61.454171] [IGT] gem_ctx_create: executing <5> [61.475031] Setting dangerous option reset - tainting kernel <6> [61.487405] [IGT] gem_ctx_create: starting subtest basic-files https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_5186_242/fi-bsw-kefka/igt@gem_ctx_create@basic-files.html Starting subtest: basic-files (gem_ctx_create:995) igt_aux-CRITICAL: Test assertion failure function sig_abort, file ../lib/igt_aux.c:500: (gem_ctx_create:995) igt_aux-CRITICAL: Failed assertion: !"GPU hung"
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_5186_265/fi-bsw-cyan/igt@kms_chamelium@hdmi-crc-fast.html https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_5186_185/fi-bsw-n3050/igt@i915_module_load@reload-with-fault-injection.html
Latest occurrences seem to be caused by CRC errors: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_5510/fi-bsw-n3050/igt@kms_pipe_crc_basic@suspend-read-crc-pipe-c.html
No more occurrences so far, but this is so sporadic that it's hard to say it's gone. At least it's not high priority.
A CI Bug Log filter associated to this bug has been updated: {- BSW: igt@* - Incomplete - system hang? -} {+ BSW: igt@* - Incomplete - system hang? +} New failures caught by the filter: * https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_5681/fi-bsw-cyan/igt@i915_selftest@live_active.html
A CI Bug Log filter associated to this bug has been updated: {- BSW: igt@* - Incomplete - system hang? -} {+ BSW: igt@* - Incomplete - system hang? +} New failures caught by the filter: * https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_5761/fi-bsw-cyan/igt@kms_flip@basic-flip-vs-modeset.html
A CI Bug Log filter associated to this bug has been updated: {- BSW: igt@* - Incomplete - system hang? -} {+ BSW: igt@* - Incomplete - system hang? +} New failures caught by the filter: * https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_5835/fi-bsw-cyan/igt@gem_exec_fence@basic-busy-default.html
A CI Bug Log filter associated to this bug has been updated: {- BSW: igt@* - Incomplete - system hang? -} {+ BSW: igt@* - Incomplete - system hang? +} New failures caught by the filter: * https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_270/fi-bsw-n3050/igt@gem_pwrite@big-cpu-backwards.html
A CI Bug Log filter associated to this bug has been updated: {- BSW: igt@* - Incomplete - system hang? -} {+ BSW: igt@* - Incomplete - system hang? +} New failures caught by the filter: * https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_270/fi-bsw-kefka/igt@gem_persistent_relocs@forked-faulting-reloc.html
A CI Bug Log filter associated to this bug has been updated: {- BSW: igt@* - Incomplete - system hang? -} {+ BSW: igt@* - Incomplete - system hang? +} New failures caught by the filter: * https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6020/fi-bsw-kefka/igt@i915_selftest@live_hangcheck.html * https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6025/fi-bsw-kefka/igt@i915_selftest@live_hangcheck.html
A CI Bug Log filter associated to this bug has been updated: {- BSW: igt@* - Incomplete - system hang? -} {+ BSW: igt@* - Incomplete - system hang/timeout? +} New failures caught by the filter: * https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_306/fi-bsw-kefka/igt@gem_persistent_relocs@forked-interruptible-faulting-reloc-thrash-inactive.html
A CI Bug Log filter associated to this bug has been updated: {- BSW: igt@* - Incomplete - system hang/timeout? -} {+ BSW: igt@* - Incomplete - system hang/timeout? +} New failures caught by the filter: * https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_310/fi-bsw-kefka/igt@gem_ctx_isolation@vcs0-s3.html
A CI Bug Log filter associated to this bug has been updated: {- BSW: igt@* - Incomplete - system hang/timeout? -} {+ BSW: igt@* - Incomplete - system hang/timeout? +} New failures caught by the filter: * https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_308/fi-bsw-n3050/igt@gem_persistent_relocs@forked-interruptible-thrash-inactive.html
A CI Bug Log filter associated to this bug has been updated: {- BSW: igt@* - Incomplete - system hang/timeout? -} {+ BSW: igt@* - Incomplete - system hang/timeout? +} New failures caught by the filter: * https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_333/fi-bsw-n3050/igt@gem_eio@hibernate.html
(In reply to CI Bug Log from comment #26) > A CI Bug Log filter associated to this bug has been updated: > > {- BSW: igt@* - Incomplete - system hang/timeout? -} > {+ BSW: igt@* - Incomplete - system hang/timeout? +} > > New failures caught by the filter: > > * > https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_333/fi-bsw-n3050/ > igt@gem_eio@hibernate.html Well that's not out bug (it's a GPF in the usb driver).
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.