On Mon, Jul 08, 2002 at 11:55:55AM +0200, Felix Kühling wrote:
>Hi,
>
>I just read Davids mail about bzflag performance on mach64. Incidentally
>last night I tried bzflag for the first time on mach64 and it froze the
>X server reproducibly (tried it twice) just after starting bzflag. By
>now I found out that it's related to switching the screen resoultion.
>Without switching it works just fine. When I have bzflag switch to
>640x480 it fails. I updated just before so I guess I have the latest
>version of the branch. bzflag version is:
>
>BZFlag client, version 1.7e4
> protocol 1.7e
>
>Symptoms: I start bzflag. It changes resolution to 640x480. For a
>fraction of a second I see the frame of the status window flashing on
>the screen. Then it goes black and IIRC the mouse pointer freezes.
>
>Here is the kernel log:
[...]
>Jul 8 02:23:48 viking kernel: [drm] 0x0051c060: 0x007ffe48 0xd0018000 0xc0000000
>0x00000000 (head)
^^^^^^^^^^
A 0-length buffer was commited to the ring. This is a situation that
had never been experienced and it wasn't known to cause problems, so it
isn't checked by the current code.
A fix should be straightforward since these buffers can just be
dismissed. I'll get back to you when I've done it so that you can test
again.
>Jul 8 02:23:48 viking kernel: [drm] 0x0051c070: 0x00000000 0x00000000 0x00000000
>0x00000000 (tail)
[...]
>
>This was repeated in about 2 sec intervals until I rebooted.
>
José Fonseca
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Oh, it's good to be a geek.
http://thinkgeek.com/sf
_______________________________________________
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
