diff options
Diffstat (limited to 'freed-ora/tags/f27/4.15.9-300.fc27.gnu/drm-i915-hush-check-crtc-state.patch')
| -rw-r--r-- | freed-ora/tags/f27/4.15.9-300.fc27.gnu/drm-i915-hush-check-crtc-state.patch | 32 |
1 files changed, 32 insertions, 0 deletions
diff --git a/freed-ora/tags/f27/4.15.9-300.fc27.gnu/drm-i915-hush-check-crtc-state.patch b/freed-ora/tags/f27/4.15.9-300.fc27.gnu/drm-i915-hush-check-crtc-state.patch new file mode 100644 index 000000000..cec67aaaa --- /dev/null +++ b/freed-ora/tags/f27/4.15.9-300.fc27.gnu/drm-i915-hush-check-crtc-state.patch @@ -0,0 +1,32 @@ +From 63a9dfe66b3b82b6eb10c6548aaf22dd7e543d2d Mon Sep 17 00:00:00 2001 +From: Adam Jackson <ajax@redhat.com> +Date: Mon, 10 Jul 2017 08:11:48 -0700 +Subject: [PATCH] drm/i915: hush check crtc state + +This is _by far_ the most common backtrace for i915 on retrace.fp.o, and +it's mostly useless noise. There's not enough context when it's generated +to know if something actually went wrong. Downgrade the message to +KMS debugging so we can still get it if we want it. + +Bugzilla: 1027037 1028785 +Upstream-status: http://lists.freedesktop.org/archives/intel-gfx/2013-November/035948.html +--- + drivers/gpu/drm/i915/intel_display.c | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +diff --git a/drivers/gpu/drm/i915/intel_display.c b/drivers/gpu/drm/i915/intel_display.c +index dec9e58..620f378a 100644 +--- a/drivers/gpu/drm/i915/intel_display.c ++++ b/drivers/gpu/drm/i915/intel_display.c +@@ -12277,7 +12277,7 @@ verify_crtc_state(struct drm_crtc *crtc, + sw_config = to_intel_crtc_state(new_crtc_state); + if (!intel_pipe_config_compare(dev_priv, sw_config, + pipe_config, false)) { +- I915_STATE_WARN(1, "pipe state doesn't match!\n"); ++ DRM_DEBUG_KMS("pipe state doesn't match!\n"); + intel_dump_pipe_config(intel_crtc, pipe_config, + "[hw state]"); + intel_dump_pipe_config(intel_crtc, sw_config, +-- +2.7.5 + |
