Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Alexey Fisher <bug-track@fisher-privat.net>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [regression] drm/i915: Flush pending writes on i830/i845 after updating GTT
Date: Thu, 30 Dec 2010 12:23:24 +0100	[thread overview]
Message-ID: <1293708204.6744.2.camel@zwerg> (raw)
In-Reply-To: <0d30dc$kjsbet@orsmga001.jf.intel.com>

Am Donnerstag, den 30.12.2010, 10:31 +0000 schrieb Chris Wilson:
> On Thu, 30 Dec 2010 11:09:56 +0100, Alexey Fisher <bug-track@fisher-privat.net> wrote:
> > The screencast is attached.
> 
> Yeah, definitely looks like a missing RenderCache flush. Is compiz part of
> the critical path?
> -Chris

No. I get same issue without compiz too. Some gtk programs get
destruction too.

-- 
Regards,
        Alexey

  reply	other threads:[~2010-12-30 11:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-30  9:36 [regression] drm/i915: Flush pending writes on i830/i845 after updating GTT Alexey Fisher
2010-12-30  9:51 ` Chris Wilson
2010-12-30 10:09   ` Alexey Fisher
2010-12-30 10:31     ` Chris Wilson
2010-12-30 11:23       ` Alexey Fisher [this message]
2010-12-30 18:06         ` Chris Wilson

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=1293708204.6744.2.camel@zwerg \
    --to=bug-track@fisher-privat.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox