[Mesa-dev] [PATCH 1/6] glx: Convert to automake.

[Marek Olšák]

On Tue, Mar 6, 2012 at 3:37 AM, Eric Anholt <eric at anholt.net> wrote:
> On Thu, 1 Mar 2012 19:18:50 +0100, Marek Olšák <maraeo at gmail.com> wrote:
>> On Thu, Mar 1, 2012 at 5:28 PM, Eric Anholt <eric at anholt.net> wrote:
>> > On Thu, 1 Mar 2012 16:50:40 +0100, Marek Olšák <maraeo at gmail.com> wrote:
>> >> Hi Eric,
>> >>
>> >> this commit breaks StarCraft II running on Wine traced by apitrace
>> >> on r600g. Wine is most probably stuck in a deadlock. It prints these
>> >> error messages:
>> >>
>> >> err:seh:setup_exception_record stack overflow 2412 bytes in thread
>> >> 0024 eip 00437fdb esp 00c409c4 stack 0xc40000-0xc41000-0xd40000
>> >> err:ntdll:RtlpWaitForCriticalSection section 0x7dce41e0
>> >> "x11drv_main.c: X11DRV_CritSection" wait timed out in thread 0025,
>> >> blocked by 0024, retrying (60 sec)
>> >> err:ntdll:RtlpWaitForCriticalSection section 0x72e200 "?" wait timed
>> >> out in thread 0023, blocked by 0024, retrying (60 sec)
>> >> err:ntdll:RtlpWaitForCriticalSection section 0x72e200 "?" wait timed
>> >> out in thread 0009, blocked by 0024, retrying (60 sec)
>> >> etc.
>> >>
>> >> Reverting this commit (and also the egl automake commits to avoid
>> >> conflicts) fixes the issue.
>> >>
>> >> Do you have any idea about what might have gone wrong?
>> >
>> > Hmm, weird.  Defines were my first idea, the diff of all defines used in
>> > the compile is:
> [...]
>> >
>> > Could you stick a debugger on it and see where it's stopped, at least?
>>
>> Sorry, I haven't been able to obtain a useful backtrace from wine. I
>> have no idea how to debug this.
>
> Just to be clear: Is the failure mode only when apitracing wine, and not
> when running wine standalone or when running glretrace of any resulting
> trace?

Sorry that I did not reply earlier.

The failure is only when apitracing wine.

>
> Does it require SC2, or can other apps be used to reproduce the failure?
> Any freely downloadable apps by chance?

It seems that all wine apps segfault or deadlock with Mesa master when
apitracing. It's always stack overflow. Surprisingly enough, they
don't segfault with the glx patch reverted.

Reverting the patch is not trivial without build and other failures.
Here's what I had to do:
http://cgit.freedesktop.org/~mareko/mesa/log/?h=revert-glx-automake

Marek