From: Keith Packard <keithp@keithp.com>
To: Philipp Klaus Krause <pkk@spth.de>, intel-gfx@lists.freedesktop.org
Subject: Re: Screen corruption regression from 3.0 to 3.1rc4
Date: Tue, 06 Sep 2011 08:53:39 -0700 [thread overview]
Message-ID: <yunfwk9ekfw.fsf@aiko.keithp.com> (raw)
In-Reply-To: <4E661BF0.1040806@spth.de>
[-- Attachment #1.1: Type: text/plain, Size: 795 bytes --]
On Tue, 06 Sep 2011 15:11:12 +0200, Philipp Klaus Krause <pkk@spth.de> wrote:
> Here's the output from git-bisect:
>
> d74362c9e45689d8d7e3d4bcf6681c4358ef4f2e is the first bad commit
> commit d74362c9e45689d8d7e3d4bcf6681c4358ef4f2e
> Author: Keith Packard <keithp@keithp.com>
> Date: Thu Jul 28 14:47:14 2011 -0700
>
> drm/i915: Flush other plane register writes
>
> Writes to the plane control register are buffered in the chip until a
> write to the DSPADDR (pre-965) or DSPSURF (post-965) register
> occurs.
Makes me wonder if this is some interaction between page flipping and
frame buffer compression. Could you try turning it off with the
following kernel command line parameter?
i915.i915_enable_fbc=0
--
keith.packard@intel.com
[-- Attachment #1.2: Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2011-09-06 16:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-31 6:43 Screen corruption regression from 3.0 to 3.1rc4 Philipp Klaus Krause
2011-09-03 9:31 ` Philipp Klaus Krause
2011-09-03 10:43 ` Daniel Vetter
2011-09-03 10:52 ` Philipp Klaus Krause
2011-09-03 11:53 ` Daniel Vetter
2011-09-06 13:11 ` Philipp Klaus Krause
2011-09-06 15:53 ` Keith Packard [this message]
2011-09-07 17:16 ` Philipp Klaus Krause
2011-09-08 13:43 ` Eugeni Dodonov
2011-09-08 20:19 ` Philipp Klaus Krause
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=yunfwk9ekfw.fsf@aiko.keithp.com \
--to=keithp@keithp.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=pkk@spth.de \
/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.