All of lore.kernel.org
 help / color / mirror / Atom feed
From: Colin Guthrie <intel@colin.guthr.ie>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: Graphical corruption post 2.6.38
Date: Wed, 23 Mar 2011 15:26:04 +0000	[thread overview]
Message-ID: <4D8A110C.3060802@colin.guthr.ie> (raw)
In-Reply-To: <b9dded$ic7hef@orsmga002.jf.intel.com>

'Twas brillig, and Chris Wilson at 23/03/11 14:08 did gyre and gimble:
> On Wed, 23 Mar 2011 13:54:11 +0000, Colin Guthrie <intel@colin.guthr.ie> wrote:
>> Hi,
>>
>> Running latest drivers from git + recent drm+xserver.
>>
>> After upgrading to 2.6.38 I seem to get occasional graphical corruption.
>> This manifests itself mostly obviously in e.g gnome-terminal when
>> getting git status and such like (although there are many other triggers
>> - have seen it in various apps).
>>
>> Here is an example of what it looks like, but it can be much worse.
>> http://colin.guthr.ie/intel-2.6.38.png
>>
>> Any idea of what could cause this before I go digging too deeply?
> 
> First try:
> 
> commit 29c5a587284195278e233eec5c2234c24fb2c204
> Author: Chris Wilson <chris@chris-wilson.co.uk>
> Date:   Thu Mar 17 15:23:22 2011 +0000
> 
>     drm/i915: Fix tiling corruption from pipelined fencing

Looks like a good bet. I'll try and get this tested sometime soon :)

Cheers

Col

-- 

+------------------------+
|     Colin Guthrie      |
+------------------------+
| http://colin.guthr.ie/ |
+------------------------+

  reply	other threads:[~2011-03-23 15:26 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-23 13:54 Graphical corruption post 2.6.38 Colin Guthrie
2011-03-23 14:08 ` Chris Wilson
2011-03-23 15:26   ` Colin Guthrie [this message]
2011-03-23 18:35   ` Tino Keitel
2011-03-23 18:51     ` Chris Wilson
2011-03-26 13:26       ` Colin Guthrie
2011-03-26 17:26         ` Chris Wilson
2011-03-27 15:57           ` Colin Guthrie
2011-04-25 16:58         ` Paul Menzel
2011-04-25 21:13           ` Chris Wilson
2011-04-29 20:16             ` Paul Menzel
2011-05-12 21:37               ` Paul Menzel

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=4D8A110C.3060802@colin.guthr.ie \
    --to=intel@colin.guthr.ie \
    --cc=chris@chris-wilson.co.uk \
    --cc=intel-gfx@lists.freedesktop.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.