Bug 65287

No need to bisect, it's a new self-check added in

commit 045ac3b5629d9711531a408e92f9074db6afe7ce
Author: Jesse Barnes <jbarnes@virtuousgeek.org>
Date:   Tue May 14 17:08:26 2013 -0700

    drm/i915: add encoder get_config function v5

One for Jesse to fix ;-)

Jesse?

Can you apply this patch so I can see which one is failing?

--- a/drivers/gpu/drm/i915/intel_display.c
+++ b/drivers/gpu/drm/i915/intel_display.c
@@ -8074,7 +8074,7 @@ intel_pipe_config_compare(struct drm_device *dev,
 
 #define PIPE_CONF_CHECK_FLAGS(name, mask)      \
        if ((current_config->name ^ pipe_config->name) & (mask)) { \
-               DRM_ERROR("mismatch in " #name " " \
+               DRM_ERROR("mismatch in " #name (#mask) " "         \
                          "(expected %i, found %i)\n", \
                          current_config->name & (mask), \
                          pipe_config->name & (mask)); \

Oops, I mean this one:

--- a/drivers/gpu/drm/i915/intel_display.c
+++ b/drivers/gpu/drm/i915/intel_display.c
@@ -8074,7 +8074,7 @@ intel_pipe_config_compare(struct drm_device *dev,
 
 #define PIPE_CONF_CHECK_FLAGS(name, mask)      \
        if ((current_config->name ^ pipe_config->name) & (mask)) { \
-               DRM_ERROR("mismatch in " #name " " \
+               DRM_ERROR("mismatch in " #name "(" #mask ") "      \
                          "(expected %i, found %i)\n", \
                          current_config->name & (mask), \
                          pipe_config->name & (mask)); \

Should be fixed with

commit b6b6cfc739dc879081dcc3fc25dcbea2ba1167d3
Author: Xiong Zhang <xiong.y.zhang@intel.com>
Date:   Fri Jun 28 12:59:06 2013 +0800

    drm/i915: correct intel_dp_get_config() function for DevCPT

(In reply to comment #5)
> Should be fixed with
> 
> commit b6b6cfc739dc879081dcc3fc25dcbea2ba1167d3
> Author: Xiong Zhang <xiong.y.zhang@intel.com>
> Date:   Fri Jun 28 12:59:06 2013 +0800
> 
>     drm/i915: correct intel_dp_get_config() function for DevCPT

Yes, this issue gone. Verified here.

I find this bug "*ERROR* mismatch in adjusted_mode.flags (expected 1, found 0)" disappeared, but the dmesg also not clean, so I file a new bug, and I comment here for tracing back.
Bug 66444 - [IVB DP] dmesg of machine boot up with "call trace" and "*ERROR* mismatch in clock (expected 28319, found 0"

Yeah, that's a new bug. See the kernel backtraces section in our bug filing BKM on how to distinguish different kinds of backtraces.

Closing old verified.