Summary: | [CI][DRMTIP] igt@kms_plane_lowres@pipe-* - dmesg-warn - pipe_off wait timed out | ||
---|---|---|---|
Product: | DRI | Reporter: | Lakshmi <lakshminarayana.vudum> |
Component: | DRM/Intel | Assignee: | Intel GFX Bugs mailing list <intel-gfx-bugs> |
Status: | CLOSED WORKSFORME | QA Contact: | Intel GFX Bugs mailing list <intel-gfx-bugs> |
Severity: | normal | ||
Priority: | medium | CC: | intel-gfx-bugs, vandita.kulkarni |
Version: | DRI git | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | ICL | i915 features: | display/Other |
Description
Lakshmi
2019-05-16 13:51:15 UTC
The CI Bug Log issue associated to this bug has been updated. ### New filters associated * ICL: igt@kms_plane_lowres@pipe-* - dmesg-warn - pipe_off wait timed out (No new failures associated) * ICL: igt@runner@aborted -fail - Previous test: kms_plane_lowres (pipe-b-tiling-yf) (No new failures associated) Vandita, can you look this or this this known issue? The reproduction rate of this failure is 100% on icl-dsi. (In reply to Lakshmi from comment #3) > The reproduction rate of this failure is 100% on icl-dsi. Correction: All the failures listed in the CI bug log under this bug is related to igt@runner@aborted. This failure has occurred only twice as mentioned in comment 1. But not seen later. The test does modesets by switching from higher resolution to a lower resolution and back. It may be the case that we try to switch back and forth modes too quickly and some delay would be required on the test case to settle things down. The dmesg shows that later on we are able to disable the pipe again within timeout window. I consider that the impact for the user is minimal. Maybe it just takes a while longer to disable the pipe. The issues was seen on average twice a week and disappeared completely about 7 weeks ago. 0.5 week * 10 = 5 weeks, so closing due to 10x reproduction rate rule. (In reply to Arek Hiler from comment #7) > The issues was seen on average twice a week and disappeared completely about > 7 weeks ago. 0.5 week * 10 = 5 weeks, so closing due to 10x reproduction > rate rule. Archiving the issue. The CI Bug Log issue associated to this bug has been archived. New failures matching the above filters will not be associated to this bug anymore. |
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.