[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <21d7e9970709200033k3f0f46feq7dae4e0a106f0372@mail.gmail.com>
Date: Thu, 20 Sep 2007 17:33:45 +1000
From: "Dave Airlie" <airlied@...il.com>
To: "Jiri Slaby" <jirislaby@...il.com>
Cc: "Andi Kleen" <andi@...stfloor.org>,
"Andrew Morton" <akpm@...ux-foundation.org>,
linux-kernel@...r.kernel.org, zhenyu.z.wang@...el.com
Subject: Re: X-freeze after clflush changes [Was: 2.6.23-rc6-mm1]
> >> 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?
> >>
> >
> > Can you send me a complete Xorg log file?
>
> Maybe you are rather interested in these dmesg lines:
> Linux agpgart interface v0.102
> agpgart: suspend/resume problematic: resume with 3D/DRI active may lockup X.Org
> on some chipset/BIOS combos (see DEBUG_AGP_PM in intel-agp.c)
> agpgart: Detected an Intel G33 Chipset.
> agpgart: Detected 8192K stolen memory.
> agpgart: AGP aperture is 256M @ 0xd0000000
> [drm] Initialized drm 1.1.0 20060810
> ACPI: PCI Interrupt 0000:00:02.0[A] -> GSI 16 (level, low) -> IRQ 16
> [drm] Initialized i915 1.6.0 20060119 on minor 0
> ...
> set status page addr 0x00033000
> agpgart: pg_start == 0x000005ff,intel_private.gtt_entries == 0x00000800
> agpgart: Trying to insert into local/stolen memory
>
> So the problem is, that X passes too low start.
>
> The X log:
> http://www.fi.muni.cz/~xslaby/sklad/Xorg.0.log.old
>
I've cc'd Zhenyu who might be able to shed some light on this? can you
try 2.6.23-rc7 as maybe the G33 support still needs some work.. or
maybe I'm missing a patch in the drm..
Dave.
-
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