Bug 111757 - [CI][BAT]igt@gem_eio@kms - dmesg-fail - Failed assertion: med < limit && max < 5 * limit
Summary: [CI][BAT]igt@gem_eio@kms - dmesg-fail - Failed assertion: med < limit && max ...
Status: NEW
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: DRI git
Hardware: Other All
: low normal
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-09-20 10:58 UTC by Lakshmi
Modified: 2019-11-01 18:54 UTC (History)
1 user (show)

See Also:
i915 platform: SNB
i915 features: display/Other


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Lakshmi 2019-09-20 10:58:37 UTC
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.
Comment 1 CI Bug Log 2019-09-20 11:01:41 UTC
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 &lt; limit &amp;&amp; max &lt; 5 * limit
  (No new failures associated)

* SNB: igt@runner@aborted - fail -Previous test: gem_eio (kms)
  (No new failures associated)
Comment 2 CI Bug Log 2019-09-30 10:03:47 UTC
A CI Bug Log filter associated to this bug has been updated:

{- SNB:igt@gem_eio@kms - dmesg-fail - Failed assertion: med &lt; limit &amp;&amp; max &lt; 5 * limit -}
{+ SNB:igt@gem_eio@kms - dmesg-fail/fail - Failed assertion: med &lt; limit &amp;&amp; max &lt; 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
Comment 3 Vanshidhar Konda 2019-11-01 18:54:05 UTC
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.


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.