[Dri-users] X hangs when starting glxgears on r350

[Bellido N. <nb...@sk...>]

Hi all,

I have a Radeon 9800Pro that I'm trying to get working with the R300 tree on 
my Gentoo box.

I'm running a 2.6.12-gentoo-r4 kernel with the X11 6.8.99.15 ebuild.
As I saw a post recently on the dri-devel list, I built DRI and Mesa from CVS.

When the radeon module is loaded, i get in the kernel logs:

Linux agpgart interface v0.101 (c) Dave Jones
agpgart: Detected VIA KT880 chipset
agpgart: AGP aperture is 128M @ 0xe0000000
[drm] Initialized drm 1.0.0 20040925
ACPI: PCI Interrupt 0000:01:00.0[A] -> GSI 16 (level, low) -> IRQ 16
[drm] Initialized radeon 1.16.0 20050311 on minor 0: ATI Technologies Inc 
Radeon R350 [Radeon 9800 Pro]

And, when X starts:

agpgart: Found an AGP 3.5 compliant device at 0000:00:00.0.
agpgart: Putting AGP V3 device at 0000:00:00.0 into 4x mode
agpgart: Putting AGP V3 device at 0000:01:00.0 into 4x mode
[drm] Loading R300 Microcode

Nothing special, I suppose. In the X log (in attach), every looks normal too.

A glxinfo tells me that direct rendering is enabled.

However, when I start glxgears, I get:

# glxgears
*****[...]***WARN_ONCE*****[...]***
File r300_state.c function r300Enable line 456
TODO - double side stencil !
*******[...]***
No ctx->FragmentProgram._Current!!

And then, X hangs. Mouse and keyboard are not responsive anymore, although I 
can still ssh to the pc.

In the kernel log, I see:

[drm:radeon_cp_cmdbuf] *ERROR* bad cmd_type 0 at ec560024

Note that once, I saw:

[drm:radeon_cp_cmdbuf] *ERROR* buffer index 248 (of 31 max)

That time, I was able to kill X, and restart it.

Any idea ?

Thx,

Nicolas.

PS: In my bios AGP Fast Write is disabled, the AGP bus is in x4 mode, and the 
aperture size is 128M. I set the options in my xorg.conf accordingly