public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Damien Lespiau <damien.lespiau@intel.com>
Cc: "David Airlie" <airlied@linux.ie>,
	intel-gfx <intel-gfx@lists.freedesktop.org>,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
	"Jörg Otte" <jrg.otte@gmail.com>,
	"Dave Airlie" <airlied@redhat.com>,
	"Linus Torvalds" <torvalds@linux-foundation.org>
Subject: Re: [3.14.0-rc4] regression: drm FIFO underruns
Date: Tue, 13 May 2014 18:48:20 +0200	[thread overview]
Message-ID: <20140513164820.GQ3908@phenom.ffwll.local> (raw)
In-Reply-To: <20140513164631.GA16632@strange.amr.corp.intel.com>

On Tue, May 13, 2014 at 05:46:31PM +0100, Damien Lespiau wrote:
> On Tue, May 13, 2014 at 06:38:32PM +0200, Daniel Vetter wrote:
> > > Doesn't work for me, I still have an underrun at boot-up.
> > 
> > I'm at a loss tbh with ideas. We successfully disable both pipes, then
> > enable pipe A and it all works.
> > 
> > Then we enable pipe B and _both_ pipes underrun immediately afterwards.
> > Really strange. Can you please reproduce the issue again on
> > drm-intel-nightly (latest -nightly should also have the display
> > corruptions fixed, so good to retest anyway) and attach a new dmesg with
> > drm.debug=0xe.
> > 
> > Meanwhile I'll try to come up with new theories and ideas.
> 
> I do remember a reporter saying a BIOS upgrade fixed that for him. This
> is one of the reasons Paulo put that BIOS update message.
> 
> It's worth the try if you ask me (the BIOS update will bring new memory
> latency values).

The fifo underrun code should be able to cope with bios stupidity - that's
why we don't enable it on takeover. Apparently there's a bug in that logic
somewhere.
-Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch

  reply	other threads:[~2014-05-13 16:48 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CADDKRnCwxmJ8RonvZaizTT9R1jPU++tPPSQAH5OKD5=h9bQhMA@mail.gmail.com>
2014-05-09 12:22 ` [3.14.0-rc4] regression: drm FIFO underruns Daniel Vetter
2014-05-09 16:11   ` Jörg Otte
2014-05-09 16:14     ` 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
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 [this message]
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=20140513164820.GQ3908@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 \
    /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