[Intel-gfx] i810 Linux driver: [drm:i810_wait_ring] kernel error.

[Charles Bradshaw]

I am installing Debian 5.0.3 on a PC having integrated i810 graphics hardware.
During boot I see a kernel error.

Extract from /var/log/kern.log:

Dec 16 16:39:50 tiny650 kernel: [   53.492677] [drm] Using v1.4 init.
Dec 16 16:39:53 tiny650 kernel: [   56.668078] [drm:drm_release] *ERROR*
reclaim_buffers_locked() deadlock. Please rework this
Dec 16 16:39:53 tiny650 kernel: [   56.668089]  driver to use
reclaim_buffers_idlelocked() instead.
Dec 16 16:39:53 tiny650 kernel: [   56.668094]  I will go on reclaiming the
buffers anyway.
Dec 16 16:39:59 tiny650 kernel: [   62.620067] eth0: no IPv6 routers present
Dec 16 16:47:16 tiny650 kernel: [  496.312042] [drm:drm_release] *ERROR*
reclaim_buffers_locked() deadlock. Please rework this
Dec 16 16:47:16 tiny650 kernel: [  496.312054]  driver to use
reclaim_buffers_idlelocked() instead.
Dec 16 16:47:16 tiny650 kernel: [  496.312059]  I will go on reclaiming the
buffers anyway.
Dec 16 16:47:16 tiny650 kernel: [  499.316031] [drm:i810_wait_ring] *ERROR*
space: 65520 wanted 65528
Dec 16 16:47:16 tiny650 kernel: [  499.316040] [drm:i810_wait_ring] *ERROR* lockup
Dec 16 16:47:22 tiny650 kernel: [  502.332153] [drm:drm_release] *ERROR*
reclaim_buffers_locked() deadlock. Please rework this

... repeated 3 times
...

Dec 16 17:50:17 tiny650 kernel: [ 4277.332046]  driver to use
reclaim_buffers_idlelocked() instead.
Dec 16 17:50:17 tiny650 kernel: [ 4277.332051]  I will go on reclaiming the
buffers anyway.
Dec 16 17:50:17 tiny650 kernel: [ 4280.336033] [drm:i810_wait_ring] *ERROR*
space: 65520 wanted 65528
Dec 16 17:50:17 tiny650 kernel: [ 4280.336089] [drm:i810_wait_ring] *ERROR* lockup
Dec 16 17:50:17 tiny650 kernel: [ 4280.484268] [drm] DMA Cleanup

I see this from lspci ⎥ grep VGA :

00:01.0 VGA compatible controller: Intel Corporation 82810 (GCG) Chipset
Graphics Controller (rev 03)

There are no errors apparent in Xorg.0.log

I see a lot of references to this problem in various mailing list archives,
but no answers anywhere.

Has this problem ever been solved? If so where can I find the driver?

TIA Charles Bradshaw