From: Daniel Vetter <daniel@ffwll.ch>
To: Indan Zupancic <indan@nul.nu>
Cc: Chris Wilson <chris@chris-wilson.co.uk>,
LKML <linux-kernel@vger.kernel.org>,
dri-devel@lists.freedesktop.org
Subject: Re: [BUG] drm/i915 Screen corruption introduced by a00b10c360b35d6431a94cb
Date: Sun, 20 Feb 2011 10:20:13 +0100 [thread overview]
Message-ID: <20110220092012.GA3514@viiv.ffwll.ch> (raw)
In-Reply-To: <92f5b87a3559ed7f1b7c46b7497c1ad5.squirrel@webmail.greenhost.nl>
Hi,
On Sun, Feb 20, 2011 at 03:20:15AM +0100, Indan Zupancic wrote:
> Sorry, I plainly forgot to mention that. I'm on my Thinkpad X40 with gen 2
> hardware, 855GM.
Ah, craptastic i855gm. Is this with the HIC poke patch?
<snip>
> > I've created two quick patches to check a few theories, please test them
> > (both patches independently and both together). Patches attached.
>
> Tried with both applied, doesn't change anything.
Well, these two patches completely undo the patch by Chris Wilson (and
I've re-reviewed it to check whether there are any other hidden bugs in
it). I suspect that your bisect went wrong because the range
a00b10c360b35d6431a94cb..5e78330126e23e00950 is known to be broken on your
hw. Could you recheck these two endpoints to confirm that breakage was
introduce in that range? If so, could you rebase this range and squash the
three patches by me you've mentioned in the original report into the patch
by Chris and re-run git bisect on this new branch?
Thanks, Daniel
--
Daniel Vetter
Mail: daniel@ffwll.ch
Mobile: +41 (0)79 365 57 48
next prev parent reply other threads:[~2011-02-20 9:20 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-19 5:58 Indan Zupancic
2011-02-19 18:25 ` Daniel Vetter
2011-02-20 2:20 ` Indan Zupancic
2011-02-20 2:26 ` Indan Zupancic
2011-02-20 9:20 ` Daniel Vetter [this message]
2011-02-20 11:02 ` Indan Zupancic
2011-02-20 10:55 ` Daniel Vetter
2011-02-20 11:19 ` Indan Zupancic
2011-02-20 13:21 ` Daniel Vetter
2011-02-21 1:11 ` Indan Zupancic
[not found] ` <1298395549-4064-1-git-send-email-daniel.vetter@ffwll.ch>
[not found] ` <ed85db84d2d5ea460898d78e1179c6ca.squirrel@webmail.greenhost.nl>
2011-02-23 7:10 ` [PATCH] drm/i915: fix corruptions on i8xx due to relaxed fencing Daniel Vetter
2011-03-10 5:06 ` Indan Zupancic
2011-03-10 7:52 ` Daniel Vetter
2011-03-10 10:36 ` Indan Zupancic
2011-03-10 13:31 ` Daniel Vetter
2011-03-11 1:08 ` Indan Zupancic
2011-03-11 9:23 ` Daniel Vetter
2011-02-21 2:51 ` [BUG] drm/i915 Screen corruption introduced by a00b10c360b35d6431a94cb Indan Zupancic
2011-02-20 3:51 ` Peter Stuge
2011-02-20 6:13 ` Indan Zupancic
2011-02-21 4:10 ` Peter Stuge
2011-02-21 5:26 ` Indan Zupancic
2011-02-22 3:25 Indan Zupancic
2011-02-22 3:39 ` Indan Zupancic
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=20110220092012.GA3514@viiv.ffwll.ch \
--to=daniel@ffwll.ch \
--cc=chris@chris-wilson.co.uk \
--cc=dri-devel@lists.freedesktop.org \
--cc=indan@nul.nu \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome