From: "Indan Zupancic" <indan@nul.nu>
To: "Daniel Vetter" <daniel@ffwll.ch>
Cc: "Indan Zupancic" <indan@nul.nu>,
"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 12:19:14 +0100 (CET) [thread overview]
Message-ID: <b51c68e52b0495f1c354f200bc50c7ec.squirrel@webmail.greenhost.nl> (raw)
In-Reply-To: <20110220105514.GB3514@viiv.ffwll.ch>
Hi,
Good news:
On Sun, February 20, 2011 11:55, Daniel Vetter wrote:
>> > 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.
>
> I've just noticed that one of the patches (the 2nd one) doesn't work as
> advertised. Please retest with the attached one.
This one fixes it!
So ignore my other email, you nailed it. Thanks a heap Daniel.
Tomorrow I'll test more and double check, but it seems fixed.
Of course, looking at the patch, I guess it isn't generally
applicable, so perhaps either more digging or a special
exception for older chipsets is needed. I'm happy to test
any further patches if that helps, triggering the corruption
is really easy for me.
Thanks,
Indan
WARNING: multiple messages have this Message-ID (diff)
From: "Indan Zupancic" <indan@nul.nu>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: Indan Zupancic <indan@nul.nu>,
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 12:19:14 +0100 (CET) [thread overview]
Message-ID: <b51c68e52b0495f1c354f200bc50c7ec.squirrel@webmail.greenhost.nl> (raw)
In-Reply-To: <20110220105514.GB3514@viiv.ffwll.ch>
Hi,
Good news:
On Sun, February 20, 2011 11:55, Daniel Vetter wrote:
>> > 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.
>
> I've just noticed that one of the patches (the 2nd one) doesn't work as
> advertised. Please retest with the attached one.
This one fixes it!
So ignore my other email, you nailed it. Thanks a heap Daniel.
Tomorrow I'll test more and double check, but it seems fixed.
Of course, looking at the patch, I guess it isn't generally
applicable, so perhaps either more digging or a special
exception for older chipsets is needed. I'm happy to test
any further patches if that helps, triggering the corruption
is really easy for me.
Thanks,
Indan
next prev parent reply other threads:[~2011-02-20 11:19 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-19 5:58 [BUG] drm/i915 Screen corruption introduced by a00b10c360b35d6431a94cb Indan Zupancic
2011-02-19 5:58 ` Indan Zupancic
2011-02-19 18:25 ` Daniel Vetter
2011-02-19 18:25 ` Daniel Vetter
2011-02-20 2:20 ` Indan Zupancic
2011-02-20 2:20 ` Indan Zupancic
2011-02-20 2:26 ` Indan Zupancic
2011-02-20 2:26 ` Indan Zupancic
2011-02-20 9:20 ` Daniel Vetter
2011-02-20 11:02 ` Indan Zupancic
2011-02-20 11:02 ` Indan Zupancic
2011-02-20 10:55 ` Daniel Vetter
2011-02-20 11:19 ` Indan Zupancic [this message]
2011-02-20 11:19 ` Indan Zupancic
2011-02-20 13:21 ` Daniel Vetter
2011-02-21 1:11 ` Indan Zupancic
2011-02-21 1:11 ` Indan Zupancic
2011-02-22 17:25 ` [PATCH] drm/i915: fix corruptions on i8xx due to relaxed fencing Daniel Vetter
2011-02-22 17:32 ` Thierry Vignaud
2011-02-22 17:42 ` Daniel Vetter
2011-02-23 6:59 ` Indan Zupancic
2011-02-23 7:10 ` Daniel Vetter
2011-02-23 7:10 ` Daniel Vetter
2011-03-10 5:06 ` Indan Zupancic
2011-03-10 5:06 ` Indan Zupancic
2011-03-10 7:52 ` Daniel Vetter
2011-03-10 10:36 ` Indan Zupancic
2011-03-10 10:36 ` Indan Zupancic
2011-03-10 13:31 ` Daniel Vetter
2011-03-10 13:31 ` Daniel Vetter
2011-03-11 1:08 ` Indan Zupancic
2011-03-11 1:08 ` Indan Zupancic
2011-03-11 9:23 ` Daniel Vetter
2011-03-11 9:23 ` Daniel Vetter
2011-02-21 2:51 ` [BUG] drm/i915 Screen corruption introduced by a00b10c360b35d6431a94cb Indan Zupancic
2011-02-21 2:51 ` Indan Zupancic
2011-02-20 3:51 ` Peter Stuge
2011-02-20 6:13 ` Indan Zupancic
2011-02-20 6:13 ` Indan Zupancic
2011-02-21 4:10 ` Peter Stuge
2011-02-21 5:26 ` Indan Zupancic
2011-02-21 5:26 ` Indan Zupancic
2011-02-22 3:25 Indan Zupancic
2011-02-22 3:25 ` Indan Zupancic
2011-02-22 3:39 ` 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=b51c68e52b0495f1c354f200bc50c7ec.squirrel@webmail.greenhost.nl \
--to=indan@nul.nu \
--cc=chris@chris-wilson.co.uk \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.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.