[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <46F18AED.4090906@gmail.com>
Date: Wed, 19 Sep 2007 22:47:41 +0200
From: Jiri Slaby <jirislaby@...il.com>
To: Valdis.Kletnieks@...edu
CC: Andi Kleen <andi@...stfloor.org>,
Andrew Morton <akpm@...ux-foundation.org>,
linux-kernel@...r.kernel.org
Subject: Re: X-freeze after clflush changes [Was: 2.6.23-rc6-mm1]
On 09/19/2007 10:32 PM, Valdis.Kletnieks@...edu wrote:
> On Wed, 19 Sep 2007 21:57:27 +0200, Jiri Slaby said:
>> On 09/19/2007 09:54 PM, Andi Kleen wrote:
>>>> Yeah. (But X doesn't run -- this is maybe the known issue in this release)
> .
>>> What do you mean with not run?
>> (II) intel(0): Initializing HW Cursor
>> (II) intel(0): xf86BindGARTMemory: bind key 0 at 0x005ff000 (pgoffset 1535)
>> (WW) intel(0): xf86BindGARTMemory: binding of gart memory with key 0
>> at offset 0x5ff000 failed (Invalid argument)
>>
>> Fatal server error:
>> Couldn't bind memory for front buffer
>>
>> I thought I'd seen a thread about this issue, but I can't find it now. Is it
>> known or am I seeing ghosts yet, Andrew?
>
> That would probably have been me, saying that x86_64-mm-cpa-clflush.patch broke
> the NVidia graphics driver in 23-rc3-mm1. Is it breaking *other* X drivers as
> well?
Yes, the issue is there from rc3-mm1, see (intel and radeon cards are affected
in my case):
http://lkml.org/lkml/2007/9/9/51
But now I'm talking about another issue -- a regression since rc4-mm1, where X
server is unable to bind agp memory (those x logs above). The clflush issue has
solved andi in
http://lkml.org/lkml/2007/9/19/334
recently
regards,
--
Jiri Slaby (jirislaby@...il.com)
Faculty of Informatics, Masaryk University
-
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