public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Theodore Tso <tytso@mit.edu>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: "Carlos R. Mafra" <crmafra2@gmail.com>,
	Eric Anholt <eric@anholt.net>,
	linux-kernel@vger.kernel.org, Keith Packard <keithp@keithp.com>
Subject: Re: 2.6.32 regression (bisected): Video tearing/glitching with T400 laptops
Date: Tue, 13 Oct 2009 15:00:55 -0400	[thread overview]
Message-ID: <20091013190055.GI8175@mit.edu> (raw)
In-Reply-To: <20091013100135.2b3d914f@jbarnes-g45>

Thanks, should I apply this on top of your previous patch, or on a
completely virgin 2.6.32-rc3 tree?


I don't know if this helps, but the amount of tearing seems to be
roughly proportional to how many "white" pixels are on the screen.
There isn't much tearing if I just have my (brown) Ubuntu 9.04 default
background image.  There is a bit more tearing on the virtual desktop
once I open an 80x52 black-on-white gnome-terminal window, so that 45%
of my widescreen has white pixels due to the backgrouin of the
gnome-terminal.

On the virtual desktop where my firefox browser is opened, the
tearing/glitching is much more frequent.  And where the
tearing/glitching is seems to be be roughly related to where the mouse
cursor happens to be.  (Usually starting at the horizontol row of
pixels where the mouse is going down towards the bottom of the screen;
although sometimes if the mouse is very close to the bottom of the
screen, there is some tearing at the top of the screen as well.)

Does this description help at all?  Would a video clip of the
tearing/glitching be useful?

						- Ted

  reply	other threads:[~2009-10-13 19:02 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-02 22:40 2.6.32 regression (bisected): Video tearing/glitching with T400 laptops Theodore Ts'o
2009-10-02 22:44 ` Jesse Barnes
2009-10-04 13:43 ` Arkadiusz Miskiewicz
2009-10-05 20:47 ` Jesse Barnes
2009-10-08 17:36 ` Jesse Barnes
2009-10-10 20:41   ` Theodore Tso
2009-10-12 16:54     ` Jesse Barnes
2009-10-12 18:46       ` Carlos R. Mafra
2009-10-12 19:05         ` Jesse Barnes
2009-10-13  2:31           ` Theodore Tso
2009-10-13 17:01             ` Jesse Barnes
2009-10-13 19:00               ` Theodore Tso [this message]
2009-10-13 19:14                 ` Jesse Barnes
2009-10-14 21:22                   ` Jesse Barnes
2009-10-15  2:26                     ` Theodore Tso
2009-10-15  4:02                       ` Theodore Tso
2009-10-19  1:04                         ` Jesse Barnes
2009-10-19  1:15                           ` Jesse Barnes
2009-10-21  4:48                             ` Theodore Tso
2009-10-26  7:25                             ` Paul Rolland
2009-10-27 16:37                             ` Johan Hovold
2009-10-15 15:30                       ` Jesse Barnes
2009-10-15  1:23               ` Theodore Tso
2009-10-13 19:19           ` Fabio Comolli
2009-10-13 19:25             ` Jesse Barnes
2009-10-13 20:03               ` Fabio Comolli

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=20091013190055.GI8175@mit.edu \
    --to=tytso@mit.edu \
    --cc=crmafra2@gmail.com \
    --cc=eric@anholt.net \
    --cc=jbarnes@virtuousgeek.org \
    --cc=keithp@keithp.com \
    --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