From: Ben Widawsky <ben@bwidawsk.net>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
"Runyan, Arthur J" <arthur.j.runyan@intel.com>
Subject: Re: [PATCH] drm/i915: detect wrong MCH watermark values
Date: Sat, 9 Feb 2013 12:24:02 -0800 [thread overview]
Message-ID: <20130209202401.GA8121@lundgren.kumite> (raw)
In-Reply-To: <1360440222-21830-1-git-send-email-daniel.vetter@ffwll.ch>
On Sat, Feb 09, 2013 at 09:03:42PM +0100, Daniel Vetter wrote:
> Some early bios versions seem to ship with the wrong tuning values for
> the MCH, possible resulting in pipe underruns under load. Especially
> on DP outputs this can lead to black screen, since DP really doesn't
> like an occasional whack from an underrun.
>
> Unfortunately the registers seem to be locked after boot, so the only
> thing we can do is politely point out issues and suggest a BIOS
> upgrade.
>
> Arthur Runyan pointed us at this issue while discussion DP bugs - thus
> far no confirmation from a bug report yet that it helps. But at least
> some of my machines here have wrong values, so this might be useful in
> understanding bug reports.
>
> v2: After a bit more discussion with Art and Ben we've decided to only
> the check the watermark values, since the OREF ones could be be a
> notch more aggressive on certain machines.
>
> Cc: Ben Widawsky <ben@bwidawsk.net>
> Cc: Runyan, Arthur J <arthur.j.runyan@intel.com>
> Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
I wouldn't mind if you printed the OREF values, even if you didn't use
them to detect.
But,
Reviewed-by: Ben Widawsky <ben@bwidawsk.net>
[snip]
--
Ben Widawsky, Intel Open Source Technology Center
next prev parent reply other threads:[~2013-02-09 20:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-07 14:23 [PATCH] drm/i915: implement MCH pipe underrun prevention for snb/ivb Daniel Vetter
2013-02-07 18:09 ` Ben Widawsky
2013-02-09 20:03 ` [PATCH] drm/i915: detect wrong MCH watermark values Daniel Vetter
2013-02-09 20:24 ` Ben Widawsky [this message]
2013-02-12 13:44 ` Daniel Vetter
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=20130209202401.GA8121@lundgren.kumite \
--to=ben@bwidawsk.net \
--cc=arthur.j.runyan@intel.com \
--cc=daniel.vetter@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.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