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 15:06:40 -0800 [thread overview]
Message-ID: <20110112150640.2a41602c@jbarnes-desktop> (raw)
In-Reply-To: <AANLkTinbyTOirefH91=9feSAUZtgRO1xyHsZsewfz3DG@mail.gmail.com>
On Wed, 12 Jan 2011 14:31:33 -0800
Linus Torvalds <torvalds@linux-foundation.org> wrote:
> On Wed, Jan 12, 2011 at 2:22 PM, Jesse Barnes <jbarnes@virtuousgeek.org> wrote:
> >
> > Ah, ok. So it could be our internal FDI link is underrunning; it goes
> > between the CPU and PCH and carries display bits.
>
> I'm not sure it's an underrun or anything like that: the corruption is
> long-term in the non-video case. So I take back the "looks like memory
> bandwidth problems", because it really looks more like a corrupted
> blit operation there.
Ah ok if it's long running then yeah it's more likely to be a rendering
issue. It could also be the FDI link getting its timings messed up
though, and consistently delivering the wrong bits; that could show up
in the same place on the screen each time, or it might move in a
pattern across the screen (usually from top to bottom).
> Will do. I'll have to reboot to the broken kernel (my bisection ended
> in a non-broken case)
Great, thanks.
--
Jesse Barnes, Intel Open Source Technology Center
next prev parent reply other threads:[~2011-01-12 23:06 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
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 [this message]
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=20110112150640.2a41602c@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;
as well as URLs for NNTP newsgroup(s).