| Summary: | [BAT][ILK] invalid max DP link bw val 11, using 1.62Gbps | ||
|---|---|---|---|
| Product: | DRI | Reporter: | Mika Kuoppala <mika.kuoppala> |
| Component: | DRM/Intel | Assignee: | Mika Kuoppala <mika.kuoppala> |
| Status: | CLOSED FIXED | QA Contact: | Intel GFX Bugs mailing list <intel-gfx-bugs> |
| Severity: | major | ||
| Priority: | medium | CC: | intel-gfx-bugs |
| Version: | DRI git | ||
| Hardware: | x86-64 (AMD64) | ||
| OS: | All | ||
| Whiteboard: | |||
| i915 platform: | ILK | i915 features: | display/DP |
|
Description
Mika Kuoppala
2016-11-01 16:27:22 UTC
Based on data all of these are affected: igt@drv_module_reload_basic igt@gem_exec_suspend@basic-s3 igt@kms_busy@basic-flip-default-a igt@kms_cursor_legacy@basic-flip-after-cursor-legacy igt@kms_cursor_legacy@basic-flip-after-cursor-varying-size igt@kms_cursor_legacy@basic-flip-before-cursor-legacy igt@kms_flip@basic-flip-vs-modeset igt@kms_pipe_crc_basic@bad-nb-words-1 igt@kms_pipe_crc_basic@bad-nb-words-3 igt@kms_pipe_crc_basic@bad-pipe igt@kms_pipe_crc_basic@bad-source igt@kms_pipe_crc_basic@hang-read-crc-pipe-a igt@kms_pipe_crc_basic@hang-read-crc-pipe-b igt@kms_pipe_crc_basic@nonblocking-crc-pipe-a igt@kms_pipe_crc_basic@nonblocking-crc-pipe-b igt@kms_pipe_crc_basic@nonblocking-crc-pipe-b-frame-sequence igt@kms_pipe_crc_basic@read-crc-pipe-a igt@kms_pipe_crc_basic@read-crc-pipe-b igt@kms_pipe_crc_basic@suspend-read-crc-pipe-a igt@kms_pipe_crc_basic@suspend-read-crc-pipe-b igt@kms_setmode@basic-clone-single-crtc Mika - is there some commit submitted that has resolved the issue? In latest CI executions verdicts for tests mentioned in comment 2 are either pass or skip. See https://intel-gfx-ci.01.org/CI/fi-ilk-650.html. We haven't seen this in at least the past 100 CI runs. There was lot of work in this area q4 of last year so something in there have made a difference. Finding the exact commit tho would be worksome. |
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.