Created attachment 1239 [details]
Xorg log with i810 support option set

Created attachment 1240 [details]
Xorg log with i810 support option unset

This looks to me an i810 bug only and I cannot make it happen on my i815 setup
which isn't helping me debug it,

It looks to be an issue only with 24-bit i810 support where there is not DRI
support (hardware only support 16-bit acceleration),

Quite why 2.6.9 would display any different behaviour than 2.6.8 is mystifying
me as the DRM device is never opened in this case, so AGP is the only think I
can think to point at.

Do you have i810 framebuffer support built into the kernel?

attach your .config and both those log files look to me like X crashes....

Created attachment 1244 [details]
Config file of the kernel

I confirm : it's a 24-bit support problem.  With 16-bit it works perfectly with 
2.6.9 ;-)

Can you recompile your kernel with CONFIG_FB_I810 turned off? and try again with
24-bit?

if that has no affect, can you try making CONFIG_DRM_I810=m and not loading the
module with 24-bit.... 

Created attachment 1246 [details]
CONFIG_FB_I810 turned off, colordepth : 24-bit

Created attachment 1247 [details]
CONFIG_DRM_I810=m, module not loaded, colordepth : 24-bit

Okay one last test if you have a chance please..

build with CONFIG_DRM_I810 turned off completely.. this could be an AGP bug...

Created attachment 1294 [details]
CONFIG_DRM_I810 off, colordepth : 24-bit

Hello,
I am experiencing the same problem. (http://bugs.gentoo.org/show_bug.cgi?id=72098)
But I noticed one thing, when I do startx from my root account, there is no
problem. Maybe this is a problem with permissions somewhere?

See bug #1771 among others for more info.

Ok, I *finnally* was able to reproduce the bug over here.
It is indeed a i810 only related problem, i815 seems to run flawlessly.
However, I also get an "Active ring not flushed" with 16bit, and not with 24bit
only. It might be still the same problem, though.

I'll try something about that next week.

*Sigh*

I give up. It seems to be that I stumbled upon some effect due to a completely
broken setup. I tried to reproduce the version of X/kernel at which the driver
freezes, and right now I'm running a SuSE 9.1 with CVS X and vanila 2.6.9 kernel
and *everything* works - 16bit w/ DRI, 24bit w/o DRI, no crash, no lockups,
nothing. And yes, this is a i810.

Just like with bug 1771 this might well be broken hardware, which is only
triggered by kernel module changes.

Sorry, but I can't do a thing about that when I cannot reproduce it.

I'm seeing ring errors with gentoo kernel 2.6.8 and all gentoo releases of X
6.8.0, last gentoo X 6.7 works fine. - Paul Pierce

I'm tracking an SIS bug and it only happens between 2.6.8 and 2.6.9 as well...

it seems to be caused by the address layout changes..

if someone has an original i810 maybe try running the X server using the setarch 
http://people.redhat.com/mingo/flexible-mmap/setarch-1.4-2.tar.gz

setarch -L i386 startx

Somebody replied to Debian bug #355125 saying that this "Active ring not flushed" error still happens on i810 with kernel 2.6.18 and Intel driver 2.0. It happens once every 2 weeks or so. See the latest posts in http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=355125

Is the "address layout changes" still considered a good candidate for causing this error? Or does anybody have any idea how to fix it?

Brice

This issue is affecting a hardware component which is not being actively worked on anymore.

Moving the assignee to the dri-devel list as contact, to give this issue a better coverage.

i810 is dead, xaa is gone and with it all acceleration.