All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Clifton <pcjc2@cam.ac.uk>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: Corruption in glxgears with Compiz
Date: Fri, 22 Oct 2010 21:41:40 +0100	[thread overview]
Message-ID: <1287780100.14977.4.camel@pcjc2lap> (raw)
In-Reply-To: <5b55a1$ien4q1@fmsmga002.fm.intel.com>

On Fri, 2010-10-22 at 20:29 +0100, Chris Wilson wrote:
> On Fri, 22 Oct 2010 20:10:44 +0100, Peter Clifton <pcjc2@cam.ac.uk> wrote:
> > As an additional data-point, with the bug manifesting, if you go to
> > "expose" mode, (Win+E for default config), you find the corruption is
> > absent. It only appears to be present when the glxgears window is not
> > scaled by the window manager.
> 
> My guess is that it is a double application of the drawable offset when
> doing a CopyRegion swapbuffers. Does the corruption move in relation to
> the window as it moves?
> 
> This suggests that [my] recent changes to the ddx are to blame, and
> certainly a bisection on -intel might help - though it's probably just as
> easy to test before the shadow+dri changes to confirm.
> -Chris

Well, I'm as far back as:

commit d41684d54592cf93554a4d6534e7ea74562b1798
Author: Eric Anholt <eric@anholt.net>
Date:   Mon Jun 7 11:18:09 2010 -0700

And I'm still seeing the glitch. This is with drm backported from
878a3c37d36142a192bdf5b6bfcf920832f431d7

If it weren't for Alexey seeing it too with a non-backported version,
I'd suspect I'd made a mistake somewhere. Hmm.. what to try next?

I'd already attempted to revert mesa versions to when I (thought) it was
working nicely with compiz, but I can't recall quite what version that
was now. (I've purged my /var/cache/apt/archives)

Could the Xorg server cause this kind of issue? Looking at the commit
logs, I don't see much in the way of glx activity. (But would that
affect DRI rendering anyway?)

Are there any tests suggest I run?

Regards,

-- 
Peter Clifton

Electrical Engineering Division,
Engineering Department,
University of Cambridge,
9, JJ Thomson Avenue,
Cambridge
CB3 0FA

Tel: +44 (0)7729 980173 - (No signal in the lab!)
Tel: +44 (0)1223 748328 - (Shared lab phone, ask for me)

  parent reply	other threads:[~2010-10-22 20:41 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-22 12:53 Corruption in glxgears with Compiz Peter Clifton
2010-10-22 13:39 ` Chris Wilson
2010-10-22 14:04   ` Alexey Fisher
2010-10-22 19:10   ` Peter Clifton
2010-10-22 19:29     ` Chris Wilson
2010-10-22 19:38       ` Peter Clifton
2010-10-22 20:41       ` Peter Clifton [this message]
2010-10-23  3:35       ` Peter Clifton
2010-10-23  4:07         ` Peter Clifton
2010-10-23  8:23           ` Alexey Fisher
2010-10-23  9:10           ` Chris Wilson
2010-10-23  9:43             ` Alexey Fisher
2010-10-23 10:07               ` Chris Wilson
2010-10-23 11:42             ` Peter Clifton
2010-10-23 17:48               ` Chris Wilson
2010-10-23 18:33                 ` Peter Clifton
2010-10-24 23:06                 ` Peter Clifton
2010-10-22 19:13   ` Peter Clifton

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=1287780100.14977.4.camel@pcjc2lap \
    --to=pcjc2@cam.ac.uk \
    --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.