dbc4a9b
From: Adam Jackson <ajax@redhat.com>
dbc4a9b
Date: Wed, 13 Nov 2013 10:17:24 -0500
dbc4a9b
Subject: [PATCH] drm/i915: hush check crtc state
04ee959
049a74e
This is _by far_ the most common backtrace for i915 on retrace.fp.o, and
049a74e
it's mostly useless noise.  There's not enough context when it's generated
049a74e
to know if something actually went wrong.  Downgrade the message to
049a74e
KMS debugging so we can still get it if we want it.
049a74e
dbc4a9b
Bugzilla: 1027037 1028785
dbc4a9b
Upstream-status: http://lists.freedesktop.org/archives/intel-gfx/2013-November/035948.html
dbc4a9b
---
dbc4a9b
 drivers/gpu/drm/i915/intel_display.c | 2 +-
dbc4a9b
 1 file changed, 1 insertion(+), 1 deletion(-)
dbc4a9b
dbc4a9b
diff --git a/drivers/gpu/drm/i915/intel_display.c b/drivers/gpu/drm/i915/intel_display.c
dbc4a9b
index d8324c69fa86..ee0ca36930f8 100644
dbc4a9b
--- a/drivers/gpu/drm/i915/intel_display.c
dbc4a9b
+++ b/drivers/gpu/drm/i915/intel_display.c
dbc4a9b
@@ -10656,7 +10656,7 @@ check_crtc_state(struct drm_device *dev)
049a74e
 
049a74e
 		if (active &&
049a74e
 		    !intel_pipe_config_compare(dev, &crtc->config, &pipe_config)) {
049a74e
-			WARN(1, "pipe state doesn't match!\n");
049a74e
+			DRM_DEBUG_KMS("pipe state doesn't match!\n");
049a74e
 			intel_dump_pipe_config(crtc, &pipe_config,
049a74e
 					       "[hw state]");
049a74e
 			intel_dump_pipe_config(crtc, &crtc->config,
dbc4a9b
-- 
dbc4a9b
1.9.3
dbc4a9b