UltimaOnLine: X11DRV_CritSection deadlock

[Diego 'Flameeyes' Pettenò]

Hi,
I'm playing Ultima OnLine using wine in the last times, it works fine,
except that wine processes eat all the cpu time and sometimes I have this
fixme on stderr:
fixme:bitblt:X11DRV_BitBlt potential optimization - client-side DIBcopy

But the true problem is that if I'm idle for some time, I get this error,
and kde stops responding at mouse (and sometimes also keyboard) events:

err:ntdll:RtlpWaitForCriticalSection section 0x41bd6220 "x11drv_main.c:
X11DRV_CritSection" wait timed out in thread 0009, blocked by 000a,
retrying (60 sec)

Seems like a deadlock, but I don't know what can generate this problem, so I
can't reproduce it after launching winedbg.
Also when I close the client, wine remains open until I ctrl-c it.
Trying to tracing this is quite impossible, because it's already heavy when
launched directly, I don't think it's possible to have a +all with it
without using the delayed debug, but I'm not able to find out the patch
into wine-patches, if someone can point a link for it, I'll try to do that.

If no one has idea of what problem is this, I'll report it as a bug, but
maybe it's only an application's problem.

TIA,
-- 
Diego "Flameeyes" Pettenò
dgp85(a)users.sourceforge.net - http://flameeyes.web.ctonet.it/

[Roger Olson]

Diego 'Flameeyes' Pettenò Wrote:
> But the true problem is that if I'm idle for some time, I get this error,
> and kde stops responding at mouse (and sometimes also keyboard) events:

I have a setiathome type app (United Devices) that processes data in the
background.  While it's bg processing, Linux apps become noticibly lethargic
like waiting 20-30 seconds for Mozilla to open.
> err:ntdll:RtlpWaitForCriticalSection section 0x41bd6220 "x11drv_main.c:
> X11DRV_CritSection" wait timed out in thread 0009, blocked by 000a,
> retrying (60 sec)

Often when my app completes it's workunit and should phone home, it just
sits their appearing to work but actually not doing anything. When I shut it
down I receive this errror:

err:ntdll:RtlpWaitForCriticalSecion section 0x401f001c "?" wait timed out in
thread 0023, blocked by thread 0025, retrying (60 sec)

Other times, the app does what it is supposed to only to do the above again
at some later time.
> If no one has idea of what problem is this, I'll report it as a bug, but
> maybe it's only an application's problem.
>
> TIA,
> -- 
> Diego "Flameeyes" Pettenò

Sounds like a definate bug in Wine to me.  The two threads involved in the
blocking are app assgned Windows Normal(4) and Idle(1) so it may be related
to how these relate to Linux Equivalents.

Roger

[James Hawkins]

> I have a setiathome type app

Maybe I'm confused, but if you're running a win32 setiathome binary on
wine, you're better off downloading the linux binary and using that.


On Wed, 8 Sep 2004 09:57:56 -0700, Roger Olson <u60(a)comcast.net> wrote:
> Diego 'Flameeyes' Pettenò Wrote:
> > But the true problem is that if I'm idle for some time, I get this error,
> > and kde stops responding at mouse (and sometimes also keyboard) events:
>
> I have a setiathome type app (United Devices) that processes data in the
> background.  While it's bg processing, Linux apps become noticibly lethargic
> like waiting 20-30 seconds for Mozilla to open.
> > err:ntdll:RtlpWaitForCriticalSection section 0x41bd6220 "x11drv_main.c:
> > X11DRV_CritSection" wait timed out in thread 0009, blocked by 000a,
> > retrying (60 sec)
>
> Often when my app completes it's workunit and should phone home, it just
> sits their appearing to work but actually not doing anything. When I shut it
> down I receive this errror:
>
> err:ntdll:RtlpWaitForCriticalSecion section 0x401f001c "?" wait timed out in
> thread 0023, blocked by thread 0025, retrying (60 sec)
>
> Other times, the app does what it is supposed to only to do the above again
> at some later time.
> > If no one has idea of what problem is this, I'll report it as a bug, but
> > maybe it's only an application's problem.
> >
> > TIA,
> > --
> > Diego "Flameeyes" Pettenò
>
> Sounds like a definate bug in Wine to me.  The two threads involved in the
> blocking are app assgned Windows Normal(4) and Idle(1) so it may be related
> to how these relate to Linux Equivalents.
>
> Roger

-- 
James Hawkins

[Roger Olson]

James Hawkins Wrote:
> Maybe I'm confused, but if you're running a win32 setiathome binary on
> wine, you're better off downloading the linux binary and using that.

The United Devices Agent is a Setiathome like app except it processes
chemical interactions between protiens and drug molecules in an attempt find
a cure for cancer instead of looking for ET's.  United Devices does not
offer the Agent in native Linux or any other OS except win32, written in
VB6.

Thanks, Roger

[James Hawkins]

> a cure for cancer instead of looking for ET's.  United Devices does not
> offer the Agent in native Linux or any other OS except win32, written in
> VB6.

Sorry to hear that. :-\ 


On Wed, 8 Sep 2004 10:52:34 -0700, Roger Olson <u60(a)comcast.net> wrote:
> James Hawkins Wrote:
> > Maybe I'm confused, but if you're running a win32 setiathome binary on
> > wine, you're better off downloading the linux binary and using that.
>
> The United Devices Agent is a Setiathome like app except it processes
> chemical interactions between protiens and drug molecules in an attempt find
> a cure for cancer instead of looking for ET's.  United Devices does not
> offer the Agent in native Linux or any other OS except win32, written in
> VB6.
>
> Thanks, Roger

-- 
James Hawkins

[Lionel Ulmer]

(Answering this one as the original mail is lost in my HUGE wine-devel
 folder that takes ages to load on my puny P120 used to read mails :-) )
> > But the true problem is that if I'm idle for some time, I get this error,
> > and kde stops responding at mouse (and sometimes also keyboard) events:

When you say 'idle for some time', you are sure that the screensaver does
not kick in ?
> > err:ntdll:RtlpWaitForCriticalSection section 0x41bd6220 "x11drv_main.c:
> > X11DRV_CritSection" wait timed out in thread 0009, blocked by 000a,
> > retrying (60 sec)

It seems that Wine crashed somewhere during a call to an X11 function. An
idea would be to attach 'winedbg' to the Wine session and see what thread is
currently holding the X11 critical section (I will let winedbg experts
explain how to do this :-) ).

Then we would know which X11 call failed or blocked and be able to work
around the issue.

       Lionel

-- 
		 Lionel Ulmer - http://www.bbrox.org/

[Uwe Bonnes]

> > > > > "Lionel" == Lionel Ulmer <lionel.ulmer(a)free.fr> writes:

Lionel> (Answering this one as the original mail is lost in my HUGE
    Lionel> wine-devel folder that takes ages to load on my puny P120 used
    Lionel> to read mails :-) )

    >> > But the true problem is that if I'm idle for some time, I get this
    >> error, > and kde stops responding at mouse (and sometimes also
    >> keyboard) events:

    Lionel> When you say 'idle for some time', you are sure that the
    Lionel> screensaver does not kick in ?

    >> > err:ntdll:RtlpWaitForCriticalSection section 0x41bd6220
    >> "x11drv_main.c: > X11DRV_CritSection" wait timed out in thread 0009,
    >> blocked by 000a, > retrying (60 sec)

    Lionel> It seems that Wine crashed somewhere during a call to an X11
    Lionel> function. An idea would be to attach 'winedbg' to the Wine
    Lionel> session and see what thread is currently holding the X11
    Lionel> critical section (I will let winedbg experts explain how to do
    Lionel> this :-) ).

Also setting
[x11drv]
; Run in synchronous mode (useful for debugging X11 problems)
"Synchronous" = "Y"

can help pinpoint.

Bye
-- 
Uwe Bonnes                bon(a)elektron.ikp.physik.tu-darmstadt.de

Institut fuer Kernphysik  Schlossgartenstrasse 9  64289 Darmstadt
--------- Tel. [phone] -------- Fax. [phone] ----------

[Diego 'Flameeyes' Pettenò]

Lionel Ulmer wrote:
> When you say 'idle for some time', you are sure that the screensaver does
> not kick in ?
> I've no screensaver at all, I set the monitor to dpms when I'm idle for 20
> minutes.
> And sometimes the problem is before the monitor goes stand by.
> It seems that Wine crashed somewhere during a call to an X11 function. An
> idea would be to attach 'winedbg' to the Wine session and see what thread
> is currently holding the X11 critical section (I will let winedbg experts
> explain how to do this :-) ).
> I'm not sure if Wine crashed in this case, because the game still works,
> it's the rest of the system which is a lot slower after that.

Using winedbg can be an idea, but to reproduce the error I need to play, so
I don't think I can put wine in synchronous mode, which IIRC make it slower
than before.

-- 
Diego "Flameeyes" Pettenò
dgp85(a)users.sourceforge.net - http://flameeyes.web.ctonet.it/