From: "Jörg Otte" <jrg.otte@gmail.com>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: Damien Lespiau <damien.lespiau@intel.com>,
David Airlie <airlied@linux.ie>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
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: Sat, 10 May 2014 10:52:30 +0200 [thread overview]
Message-ID: <CADDKRnAiQawK6vi0XO2FDdfGDbcwWQzdeu-rfEU8viJzARO+yQ@mail.gmail.com> (raw)
In-Reply-To: <20140509170335.GZ18465@intel.com>
2014-05-09 19:03 GMT+02:00 Ville Syrjälä <ville.syrjala@linux.intel.com>:
> On Fri, May 09, 2014 at 05:14:38PM +0100, Damien Lespiau wrote:
>> On Fri, May 09, 2014 at 06:11:37PM +0200, Jörg Otte wrote:
>> > > Jörg, can you please boot with drm.debug=0xe, reproduce the issue and
>> > > then attach the complete dmesg? Please make sure that the dmesg
>> > > contains the boot-up stuff too.
>> > >
>> > > Thanks, Daniel
>> > Here it is. I should mention it only happens at boot-up.
>>
>> [ 0.374095] [drm] Wrong MCH_SSKPD value: 0x20100406
>> [ 0.374096] [drm] This can cause pipe underruns and display issues.
>> [ 0.374097] [drm] Please upgrade your BIOS to fix this.
>
> That can be a factor, but I think we may have some more general issue
> in the modeset sequence which causes these to get reported. I'm getting
> some on my machine as well where SSKPD looks more sane. Maybe we turn on
> the error reporting too early or something.
>
> But I'm not going to spend time worrying about these before my previous
> watermark stuff gets merged. Also the underrun reporting code itself
> would need some kind of rewrite to be really useful.
>
> If the display doesn't blank out during use everything is more or less
> fine and you can ignore these errors. It's quite likely that the
> errors were always present and you didn't know it. We just made them
> more prominent recently.
>
> --
> Ville Syrjälä
> Intel OTC
It comes out on the boot-up screen which is normally clean. So it becomes
highly visible for anyone.
Thanks, Jörg
next prev parent reply other threads:[~2014-05-10 8:52 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-05 7:51 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 [this message]
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
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=CADDKRnAiQawK6vi0XO2FDdfGDbcwWQzdeu-rfEU8viJzARO+yQ@mail.gmail.com \
--to=jrg.otte@gmail.com \
--cc=airlied@linux.ie \
--cc=airlied@redhat.com \
--cc=damien.lespiau@intel.com \
--cc=daniel.vetter@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--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
all inboxes | Powered by JetHome®