From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Dave Airlie <airlied@linux.ie>,
Chris Wilson <chris@chris-wilson.co.uk>,
linux-kernel@vger.kernel.org,
DRI mailing list <dri-devel@lists.freedesktop.org>
Subject: Re: [git pull] drm intel only fixes
Date: Wed, 12 Jan 2011 11:46:49 -0800 [thread overview]
Message-ID: <20110112114649.5365d518@jbarnes-desktop> (raw)
In-Reply-To: <AANLkTimgs8UfGWk5PCZi4PM5SsvejJd5Y4bb3nHGyZy2@mail.gmail.com>
On Wed, 12 Jan 2011 11:22:58 -0800
Linus Torvalds <torvalds@linux-foundation.org> wrote:
> On Tue, Jan 11, 2011 at 10:03 PM, Dave Airlie <airlied@linux.ie> wrote:
> >
> > I'm stuck at home with just my i5 laptop due to the office being shut due
> > to the ongoing floods. But I've booted and ran this for a few hours and it
> > seems to be better than the current tree. It contains a couple of patches
> > to fix DMAR interaction issues I see on this laptop on top of Chris's
> > pull.
>
> Hmm. I'm not seeing the screensaver issue any more, but there's
> something wrong with video. At least the TED ones (I'm not seeing it
> on a youtube video i tried). See for example
>
> http://www.ted.com/talks/lang/eng/david_gallo_shows_underwater_astonishments.html
>
> and when there is fast movement in the video (like when the octopus is
> spooked), I get these odd lines of noise.
>
> In fact, while I noticed the lines in the video itself, it's actually
> most repeatably noticeable in the buttons underneath while the video
> is playing: make your mouse go back-and-forth between the "rate" and
> "share" buttons, and they get corrupted (and it also corrupts the
> progress bar).
>
> It looks a bit like the noise you get with insufficient memory
> bandwidth, but I doubt that's the case here. Perhaps just some
> motion-comp problem?
>
> Any ideas?
Since I doubt we're actually offloading to our video decode kernels for
Flash video on your machine, it could very well be a memory bw issue.
Can you try this small patch to see if one of the low power watermarks
is giving you trouble (note: cut & pasted)?
It could also be the normal power watermarks though too; you could just
make plane-wm and cursor_wm higher to test that.
--
Jesse Barnes, Intel Open Source Technology Center
diff --git a/drivers/gpu/drm/i915/intel_display.c b/drivers/gpu/drm/i915/intel_d
index 9ef5578..4e8af4d 100644
--- a/drivers/gpu/drm/i915/intel_display.c
+++ b/drivers/gpu/drm/i915/intel_display.c
@@ -3600,6 +3600,8 @@ static void ironlake_update_wm(struct drm_device *dev,
if (enabled != 1)
return;
+ return;
+
clock = planea_clock ? planea_clock : planeb_clock;
/* WM1 */
next prev parent reply other threads:[~2011-01-12 19:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-12 6:03 [git pull] drm intel only fixes Dave Airlie
2011-01-12 19:22 ` Linus Torvalds
2011-01-12 19:46 ` Jesse Barnes [this message]
2011-01-12 20:27 ` Linus Torvalds
2011-01-12 21:28 ` Linus Torvalds
2011-01-12 22:22 ` Jesse Barnes
2011-01-12 22:31 ` Linus Torvalds
2011-01-12 23:06 ` Jesse Barnes
2011-01-12 22:24 ` Linus Torvalds
2011-01-12 22:40 ` Chris Wilson
2011-01-12 23:05 ` Linus Torvalds
2011-01-12 23:18 ` Chris Wilson
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=20110112114649.5365d518@jbarnes-desktop \
--to=jbarnes@virtuousgeek.org \
--cc=airlied@linux.ie \
--cc=chris@chris-wilson.co.uk \
--cc=dri-devel@lists.freedesktop.org \
--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