public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David John <davidjon@xenontk.org>
To: chris@chris-wilson.co.uk
Cc: Jesse Barnes <jbarnes@virtuousgeek.org>,
	eric@anholt.net, airlied@gmail.com,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	hohndel@infradead.org
Subject: Re: [Regression 2] i915: Commit 0d9c778978 causes flickering in 2.6.32
Date: Thu, 10 Dec 2009 16:57:40 +0530	[thread overview]
Message-ID: <4B20DB2C.5040404@xenontk.org> (raw)
In-Reply-To: <4B1FDAE3.9050602@xenontk.org>

On 12/09/2009 10:44 PM, David John wrote:
> Hi All,
> 
> I have a Dell Inspiron with a GM45 Express chipset and an Acer 23"
> display connected to the VGA out. I switch off the internal LVDS LCD
> on X start-up with xrandr. X works fine but if I switch to a console,
> it flickers horribly with the text all pushed to the right. Switching
> back to X causes X to start flickering as well. Turning the internal
> LVDS back _on_ solves the issue. It works like a switch so it is easily
> reproducible. Reverting commit 0e442c60 also fixes the problem.
> 
> There isn't anything unusual in the kernel or X logs that I could see,
> but they're attached.
> 
> Regards,
> David.

Hi,

Reverting the above commit fixes 95% of the problem, the console no
longer flickers. However, the same sequence: Switch off LVDS->
Switch to console->Switch back to X causes slight flicker in X with
the commit 0d9c778978. Turning the internal LVDS back on solves the
issue. Reverting commit 0d9c778978 fixes the problem completely (Both
commits have to be reverted).

Regards,
David.


      reply	other threads:[~2009-12-10 11:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-09 17:14 [Regression] i915: Commit 0e442c60 causes flickering in 2.6.32 David John
2009-12-10 11:27 ` David John [this message]

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=4B20DB2C.5040404@xenontk.org \
    --to=davidjon@xenontk.org \
    --cc=airlied@gmail.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=eric@anholt.net \
    --cc=hohndel@infradead.org \
    --cc=jbarnes@virtuousgeek.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