Re: X-freeze after clflush changes [Was: 2.6.23-rc6-mm1]

[Andrew Morton <akpm@linux-foundation.org>]

On Wed, 19 Sep 2007 22:01:59 +0200
Jiri Slaby <jirislaby@gmail.com> wrote:

> On 09/19/2007 09:57 PM, Jiri Slaby wrote:
> > 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
> 
> Further info:
> 4690  write(0, "(II) intel(0): Initializing HW C"..., 38) = 38
> 4690  write(0, "(II) intel(0): xf86BindGARTMemor"..., 76) = 76
> 4690  ioctl(9, AGPIOC_BIND, 0x7fffbe1cb850) = -1 EINVAL (Invalid argument)
> 4690  write(0, "(WW) intel(0): xf86BindGARTMemor"..., 115) = 115
> 4690  write(2, "\nFatal server error:\n", 21) = 21
> 

This might be a Dave thing and not an Andi thing.

In my usual -mm-testing I only test X on the one machine (the Vaio,
natch).  Check that it runs glxgears, check suspend/resume to mem and disk.
It has intel graphics and I'm not seeing any such problems.

Have you time to bisect it? 
http://www.zip.com.au/~akpm/linux/patches/stuff/bisecting-mm-trees.txt
describes how.

As a quick test, perhaps build a tree with just
2.6.23-rc6+origin.patch+git-drm.patch?  Fortunately git-agpgart.patch is
presently empty.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/