From: Linus Torvalds <torvalds@linux-foundation.org>
To: Jesse Barnes <jbarnes@virtuousgeek.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 14:31:33 -0800 [thread overview]
Message-ID: <AANLkTinbyTOirefH91=9feSAUZtgRO1xyHsZsewfz3DG@mail.gmail.com> (raw)
In-Reply-To: <20110112142206.37a1b76d@jbarnes-desktop>
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.
> Are these both desktop type machines with DVI attached monitors?
DVI on the Core i5, plain analog VGA on the sandybridge one (I can
hear you asking "Why?". Because the silly intel motherboard doesn't
_have_ DVI out, and I didn't have a hdmi cable)
> If it's an FDI or transcoder problem, something like the below may give
> us more info.
See above. It's long-term, it was just the video behavior that made me
originally think it was temporary.
> Can you take a picture of the corruption?
Will do. I'll have to reboot to the broken kernel (my bisection ended
in a non-broken case)
Linus
WARNING: multiple messages have this Message-ID (diff)
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: 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 14:31:33 -0800 [thread overview]
Message-ID: <AANLkTinbyTOirefH91=9feSAUZtgRO1xyHsZsewfz3DG@mail.gmail.com> (raw)
In-Reply-To: <20110112142206.37a1b76d@jbarnes-desktop>
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.
> Are these both desktop type machines with DVI attached monitors?
DVI on the Core i5, plain analog VGA on the sandybridge one (I can
hear you asking "Why?". Because the silly intel motherboard doesn't
_have_ DVI out, and I didn't have a hdmi cable)
> If it's an FDI or transcoder problem, something like the below may give
> us more info.
See above. It's long-term, it was just the video behavior that made me
originally think it was temporary.
> Can you take a picture of the corruption?
Will do. I'll have to reboot to the broken kernel (my bisection ended
in a non-broken case)
Linus
next prev parent reply other threads:[~2011-01-12 22:32 UTC|newest]
Thread overview: 14+ 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 21:28 ` Linus Torvalds
2011-01-12 22:22 ` Jesse Barnes
2011-01-12 22:31 ` Linus Torvalds [this message]
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='AANLkTinbyTOirefH91=9feSAUZtgRO1xyHsZsewfz3DG@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=airlied@linux.ie \
--cc=chris@chris-wilson.co.uk \
--cc=dri-devel@lists.freedesktop.org \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.