| Summary: | [CI][DRMTIP] igt@* - dmesg-warn - *ERROR* DPLL 1 not locked | ||
|---|---|---|---|
| Product: | DRI | Reporter: | Martin Peres <martin.peres> |
| Component: | DRM/Intel | Assignee: | Intel GFX Bugs mailing list <intel-gfx-bugs> |
| Status: | RESOLVED MOVED | QA Contact: | Intel GFX Bugs mailing list <intel-gfx-bugs> |
| Severity: | normal | ||
| Priority: | medium | CC: | intel-gfx-bugs |
| Version: | XOrg git | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | ReadyForDev | ||
| i915 platform: | CFL | i915 features: | display/Other |
|
Description
Martin Peres
2018-07-23 15:27:19 UTC
This bug is seen only rarely (~2% of runs); the last occurrence was two weeks ago. It can occur during pretty much any IGT test on the fi-cfl-8109u machine. The issue here arises when we're enabling DPLL1; as part of the enable sequence we're supposed to wait for the DPLL lock status to appear in the DPLL_STATUS register. For gen9 big core platforms, the bspec doesn't tell us how long we're supposed to wait the pll to lock before declaring a timeout, so we're reusing the same 5ms timeout that the bspec suggested for BDW. It seems possible that BDW's 5ms timeout might not be enough in some cases on gen9, so we should probably try bumping it up a bit to see if there's any impact on the CI results. I've submitted a patch here that will bump up the timeout: https://patchwork.freedesktop.org/series/66025/ -- 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/130. |
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.