On Sat, Jul 13, 2002 at 11:24:44PM +0200, Felix Kühling wrote:
> Hi,
>
> I tried another game: Torcs. Occasionally (about once in 1 or 2 hours)
> it crashes with "Error flushing vertex buffer: return = -11". This is
> the corresponding kernel log:
>
> Jul 13 23:04:30 viking kernel: [drm:mach64_freelist_get] *ERROR* Empty ring with
>non-idle engine!
Here it says the engine was idle....
[...]
> Jul 13 23:04:30 viking kernel: [drm] 0x0051e310: 0x007ffe48 0xd00cc000 0x40000048
>0x00000000 (head) (tail)
... but the engine here seems to be idle...
[...]
> Jul 13 23:04:30 viking kernel: [drm] GUI_STAT = 0x01800100
^
... and here is the confirmation!
I don't know how this can be but I already had to override another "safety
check" like this one because of the same problem.
The reads are made using the kernel 'readl' macro, which deals with the
compiler ordering, and the memory barriers. Since it's a read there
isn't caching on the PCI bus.
But the fact remains that the reads from GUI_STAT aren't reliable. I
wonder if the chip creats some transient values...
[...]
>
> I can restart torcs after that without problems. Maybe other programmes
> have the same problem but I didn't test them that "thoroughly" ;)
BTW, I'm also trying to figure out a problem reported by David Willmore
is always reproducible on gltestperf, which seems to happens due to
excess rate of tris/sec.
José Fonseca
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
