9a25d0e
Bugzilla: 1027037 1028785
9a25d0e
Upstream-status: http://lists.freedesktop.org/archives/intel-gfx/2013-November/035948.html
9a25d0e
9a25d0e
This is _by far_ the most common backtrace for i915 on retrace.fp.o, and
9a25d0e
it's mostly useless noise.  There's not enough context when it's generated
9a25d0e
to know if something actually went wrong.  Downgrade the message to
9a25d0e
KMS debugging so we can still get it if we want it.
9a25d0e
9a25d0e
diff -up linux-3.13.0-0.rc0.git2.1.fc21.x86_64/drivers/gpu/drm/i915/intel_display.c.jx linux-3.13.0-0.rc0.git2.1.fc21.x86_64/drivers/gpu/drm/i915/intel_display.c
9a25d0e
--- linux-3.13.0-0.rc0.git2.1.fc21.x86_64/drivers/gpu/drm/i915/intel_display.c.jx	2013-11-03 18:41:51.000000000 -0500
9a25d0e
+++ linux-3.13.0-0.rc0.git2.1.fc21.x86_64/drivers/gpu/drm/i915/intel_display.c	2013-11-13 10:12:05.781301624 -0500
9a25d0e
@@ -8803,7 +8803,7 @@ check_crtc_state(struct drm_device *dev)
9a25d0e
 
9a25d0e
 		if (active &&
9a25d0e
 		    !intel_pipe_config_compare(dev, &crtc->config, &pipe_config)) {
9a25d0e
-			WARN(1, "pipe state doesn't match!\n");
9a25d0e
+			DRM_DEBUG_KMS("pipe state doesn't match!\n");
9a25d0e
 			intel_dump_pipe_config(crtc, &pipe_config,
9a25d0e
 					       "[hw state]");
9a25d0e
 			intel_dump_pipe_config(crtc, &crtc->config,