mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Indan Zupancic" <indan@nul.nu>
To: "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 03:20:15 +0100 (CET)	[thread overview]
Message-ID: <92f5b87a3559ed7f1b7c46b7497c1ad5.squirrel@webmail.greenhost.nl> (raw)
In-Reply-To: <20110219182511.GA3977@viiv.ffwll.ch>

Hi,

On Sat, February 19, 2011 19:25, Daniel Vetter wrote:
> Hi Indan,
>
> Please provide the usual details about your system (especially what gpu
> this is on). Also, screenshots of what typical corruptions look like can
> help a lot in tracking down such things.

Sorry, I plainly forgot to mention that. I'm on my Thinkpad X40 with gen 2
hardware, 855GM.

I uploaded a screenshot of Firefox to:
http://img406.imageshack.us/img406/9159/31827167.png

It happens a lot when scrolling in FF on pages with images, pageup or pagedown
don't exhibit it. Text gets corrupted as well, but in a less predictable way.
It must be something that FF does that triggers it easily, I haven't managed
to get it with other programs yet, though I do see some corruption in the
window decoration too sometimes (which is Fluxbox). Scrolling horizontally
doesn't show the same behaviour. The corruptions seems to be happening on
the right side of a surface/window.

Forcing a refresh makes it go away again (e.g. switching to another window or
opening another window on top of it. Moving a window doesn't though). I get
it with and without xcompmgr running.

Okay, interesting titbit: For text corruption, the stripes are one pixel high
for the default font size, no corruption for smaller sizes than the default,
two pixel lines for 1 ctrl+ bigger than the default, 3 pixels for +2 etc.
With bigger sizes (>=5) I get less corruption to the left of the text, but
more in the text itself. The distance between the lines continues to increase,
but the stripes thickness goes back to 1 pixel.

Perhaps an off-by-one error somewhere?

> 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.

Greetings,

Indan



  reply	other threads:[~2011-02-20  2: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 [this message]
2011-02-20  2:26     ` Indan Zupancic
2011-02-20  9:20     ` Daniel Vetter
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=92f5b87a3559ed7f1b7c46b7497c1ad5.squirrel@webmail.greenhost.nl \
    --to=indan@nul.nu \
    --cc=chris@chris-wilson.co.uk \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®