[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080504090429.GC29318@elte.hu>
Date: Sun, 4 May 2008 11:04:29 +0200
From: Ingo Molnar <mingo@...e.hu>
To: Frans Pop <elendil@...net.nl>
Cc: Jesse Barnes <jesse.barnes@...el.com>,
"Pallipadi, Venkatesh" <venkatesh.pallipadi@...el.com>,
linux-kernel@...r.kernel.org,
"Packard, Keith" <keith.packard@...el.com>,
Arjan van de Ven <arjan@...radead.org>,
Thomas Gleixner <tglx@...utronix.de>,
"H. Peter Anvin" <hpa@...or.com>
Subject: Re: [git head] Should X86_PAT really default to yes?
* Frans Pop <elendil@...net.nl> wrote:
> On Friday 02 May 2008, Jesse Barnes wrote:
> > This is just a transient issue during VT switch or server exit though,
> > right? X functionality isn't affected, and your VTs work fine?
>
> Transient only. I've just tested again and this time the band was
> visible on top of the text on VT1 for about 2 seconds. Then it
> disappeared. The artifacts also appear when I log out from KDE (i.e.
> without exiting the server), and I also get the messages when logging
> out and logging in again.
>
> I do not see any performance issues, but I've only used this kernel
> for a very short time.
>
> > If so, it might not be a PAT issue but just a different memory
> > layout or something (and therefore it would really just be a
> > cosmetic bug in the X driver).
>
> The artifacts may not be a PAT issue directly, but it is a clear
> regression for me as I currently have a nice clean screen when X shuts
> down. I'm also 100% sure that it is caused by enabling PAT. A kernel
> with same config and only PAT disabled does not show the artifacts.
ok, Cc:-ed more folks - this bug has to be resolved regardless of the
default selection.
Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists