public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: "Jörg Otte" <jrg.otte@gmail.com>
Cc: "Ville Syrjälä" <ville.syrjala@linux.intel.com>,
	"Damien Lespiau" <damien.lespiau@intel.com>,
	"David Airlie" <airlied@linux.ie>,
	intel-gfx <intel-gfx@lists.freedesktop.org>,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
	"Dave Airlie" <airlied@redhat.com>,
	"Linus Torvalds" <torvalds@linux-foundation.org>
Subject: Re: [Intel-gfx] [3.14.0-rc4] regression: drm FIFO underruns
Date: Tue, 13 May 2014 15:22:00 +0200	[thread overview]
Message-ID: <20140513132200.GC3908@phenom.ffwll.local> (raw)
In-Reply-To: <CAKMK7uGy3bKdj-B21rCpeF2EPEE4Wi8CxLbDWFBGpLWskoDj3w@mail.gmail.com>

On Tue, May 13, 2014 at 12:38:41PM +0200, Daniel Vetter wrote:
> On Tue, May 13, 2014 at 12:29 PM, Jörg Otte <jrg.otte@gmail.com> wrote:
> >>> Branch drm-intel-nightly as of
> >>> ed60c27 drm-intel-nightly: 2014y-05m-09d-21h-51m-45s integration manifest
> >>> looks badly:
> >>>    - KDE splash screen on boot-up is not visible
> >>>    - x-windows don't have title and menu bars
> >>>    - KDE system menu is not visible
> >>>    - moving windows around destroys its content
> >>
> >> Ugh, that's ugly. Nothing else change like e.g. the version of
> >> xfree-video-intel?
> >
> >  (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so
> >  (II) Module intel: vendor="X.Org Foundation"
> >  compiled for 1.11.3, module version = 2.17.0
> >  Module class: X.Org Video Driver
> >  ABI class: X.Org Video Driver, version 11.0
> 
> Chris, any ideas? It's an ivybridge apparently.
> 
> For the fifo underruns I think we've fully confirmed that they only
> happen on boot-up. I'll try to come up with some ideas what could have
> gone wrong there.

Please test the below patch.
-Daniel

diff --git a/drivers/gpu/drm/i915/i915_irq.c b/drivers/gpu/drm/i915/i915_irq.c
index b10fbde1d5ee..63ced2dee027 100644
--- a/drivers/gpu/drm/i915/i915_irq.c
+++ b/drivers/gpu/drm/i915/i915_irq.c
@@ -427,9 +427,6 @@ bool __intel_set_cpu_fifo_underrun_reporting(struct drm_device *dev,
 
 	ret = !intel_crtc->cpu_fifo_underrun_disabled;
 
-	if (enable == ret)
-		goto done;
-
 	intel_crtc->cpu_fifo_underrun_disabled = !enable;
 
 	if (enable && (INTEL_INFO(dev)->gen < 5 || IS_VALLEYVIEW(dev)))
@@ -441,7 +438,6 @@ bool __intel_set_cpu_fifo_underrun_reporting(struct drm_device *dev,
 	else if (IS_GEN8(dev))
 		broadwell_set_fifo_underrun_reporting(dev, pipe, enable);
 
-done:
 	return ret;
 }
 
-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch

  parent reply	other threads:[~2014-05-13 13:22 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-05  7:51 [3.14.0-rc4] regression: drm FIFO underruns Jörg Otte
2014-05-09 12:22 ` Daniel Vetter
2014-05-09 16:11   ` Jörg Otte
2014-05-09 16:14     ` [Intel-gfx] " Damien Lespiau
2014-05-09 17:03       ` Ville Syrjälä
2014-05-09 21:18         ` Dave Airlie
2014-05-11 16:45           ` Daniel Vetter
2014-05-10  8:52         ` Jörg Otte
2014-05-11 16:49           ` Daniel Vetter
2014-05-12 11:25             ` Jörg Otte
2014-05-12 19:03               ` Daniel Vetter
2014-05-13 10:29                 ` Jörg Otte
2014-05-13 10:38                   ` Daniel Vetter
2014-05-13 10:59                     ` Chris Wilson
2014-05-13 11:42                       ` Daniel Vetter
2014-05-13 13:22                     ` Daniel Vetter [this message]
2014-05-13 15:21                       ` Jörg Otte
2014-05-13 16:38                         ` Daniel Vetter
2014-05-13 16:46                           ` Damien Lespiau
2014-05-13 16:48                             ` Daniel Vetter
2014-05-14  8:52                           ` Jörg Otte
2014-05-16 11:53                           ` Ville Syrjälä
2014-05-16 17:25                             ` Jörg Otte

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20140513132200.GC3908@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=airlied@linux.ie \
    --cc=airlied@redhat.com \
    --cc=damien.lespiau@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jrg.otte@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=ville.syrjala@linux.intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox