[Bug 101154] [BAT][SKL] Test assertion failure function kmstest_dumb_create, file igt_kms.c:508 on fi-skl-6700hq

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Tue May 23 12:48:55 UTC 2017


https://bugs.freedesktop.org/show_bug.cgi?id=101154

--- Comment #2 from Chris Wilson <chris at chris-wilson.co.uk> ---
[  419.523545] [drm:intel_atomic_check [i915]] [CONNECTOR:48:eDP-1] checking
for sink bpp constrains
[  419.523568] [drm:intel_atomic_check [i915]] clamping display bpp (was 36) to
EDID reported max of 18
[  419.523590] [drm:intel_dp_compute_config [i915]] DP link computation with
max lane count 1 max bw 270000 pixel clock 138700KHz
[  419.523610] [drm:intel_atomic_check [i915]] Encoder config failure


Which boils down to it failing to find a suitable link:

        for (; bpp >= 6*3; bpp -= 2*3) {
                mode_rate = intel_dp_link_required(adjusted_mode->crtc_clock,
                                                   bpp);

                for (clock = min_clock; clock <= max_clock; clock++) {
                        for (lane_count = min_lane_count;
                                lane_count <= max_lane_count;
                                lane_count <<= 1) {

                                link_clock = intel_dp->common_rates[clock];
                                link_avail = intel_dp_max_data_rate(link_clock,
                                                                   
lane_count);

                                if (mode_rate <= link_avail) {
                                        goto found;
                                }
                        }
                }
        }

because we need 2 lanes for the panel, and the max_lane_count has been left as
1 after the link training fudging.

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are the QA Contact for the bug.
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20170523/155bc820/attachment.html>


More information about the intel-gfx-bugs mailing list