https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5193/shard-snb6/igt@gem_eio@kms.html Starting subtest: kms (gem_eio:5457) CRITICAL: Test assertion failure function check_wait_elapsed, file ../tests/i915/gem_eio.c:310: (gem_eio:5457) CRITICAL: Failed assertion: med < limit && max < 5 * limit (gem_eio:5457) CRITICAL: Wake up following reset+wedge took 408.048+-1243.639ms (min:1.450ms, median:15.048ms, max:4156.385ms); limit set to 250ms on average and 1250ms maximum Subtest kms failed.
The CI Bug Log issue associated to this bug has been updated. ### New filters associated * SNB:igt@gem_eio@kms - dmesg-fail - Failed assertion: med < limit && max < 5 * limit (No new failures associated) * SNB: igt@runner@aborted - fail -Previous test: gem_eio (kms) (No new failures associated)
A CI Bug Log filter associated to this bug has been updated: {- SNB:igt@gem_eio@kms - dmesg-fail - Failed assertion: med < limit && max < 5 * limit -} {+ SNB:igt@gem_eio@kms - dmesg-fail/fail - Failed assertion: med < limit && max < 5 * limit +} New failures caught by the filter: * https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_380/fi-snb-2600/igt@gem_eio@kms.html
This test fails consistently on the SNB platform (3-4 failures) every week. Looking at the logs for the failures, recovering from a reset takes longer on the blitter engine than the other engines; hundreds of milliseconds on blitter vs tens of milliseconds on the other engines. This issue doesn't seem to occur on other platforms in the CI system - hence setting a low priority on the bug.
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/intel/issues/436.
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.