On 2002.04.29 02:01 Peter Andersson wrote:
>> mmm.. don't see why it didn't work. Well, from a ssh session do:
>>
>> export DISPLAY=:0.0
>> DRI_MACH64_DEBUG=sync,api,msg,ioctl glxgears
>
>
> Here is the output from the telnet session. Unfortunatley my telnet
> client doesn´t have any scrollbar (do you know of any windows compatible
> that do?). This means that some of the debug messages got lost. I am
> sorry about this.
>
> ...
>
>> also load the kernel module with debug option and redirect it to a
>> file (as specified in a previous email), to see if there is anything
>> unusual there.
>
> The kmsg is included as an attatchment...
>
> Peter
I didn't noticed anything unusual in the logs. The last lines showed
nothing new relative to the previous lines. Let's try narrow this down.
On xc/lib/GL/mesa/src/drv/mach64:150-156 you'll find this:
/* HACK!!! This is evil shit...
*/
if ( mmesa->dirty ) {
mach64EmitHwStateLocked( mmesa );
}
drmMach64FlushVertexBuffer( fd, prim, buffer->idx, buffer->used, 1 );
First, comment out the line as:
/* drmMach64FlushVertexBuffer( fd, prim, buffer->idx, buffer->used, 1
); */
and test it. If it still locks, then comment out the line as:
/* mach64EmitHwStateLocked( mmesa ); */
and test it again.
Before testing you have to build and install in both cases. Just do on the
same dir:
make
su -c "make install"
You do not to worry about debug logging. If it doesn't lock the program
should exit with an error message like
"Error: Could not get new VB... exiting",
which is fine as we are always asking more vertex buffers but never return
any.
Depending on which cases it locks we should know where to search further &
deeper.
José Fonseca
_______________________________________________
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
