Hi Neal,

Thanks for your investigations. 

So yet another package had to be installed on the machine :-). 

The gdb indeed show quite a similar result, line #6 is different though:

0x000002000012c860 in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
(gdb) bt
#0  0x000002000012c860 in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x0000000080129558 in ?? ()
#2  0x0000000080113cd8 in ?? ()
#3  0x00000000800b956e in mono_thread_manage ()
#4  0x000000008001d6ca in mono_main ()
#5  0x00000200001f9898 in __libc_start_main () from /lib64/libc.so.6
#6  0x000000008001bac2 in g_get_current_dir ()

Installed packages for mono (SLES11 SP1):
nl24...@nlzlx121:~> rpm -qa | grep mono
mono-nunit-2.0.1-1.19.1
mono-data-sqlite-2.0.1-1.19.1
mono-data-2.0.1-1.19.1
mono-web-2.0.1-1.19.1
mono-winforms-2.0.1-1.19.1
apache2-mod_mono-2.0-1.26
mono-core-2.0.1-1.19.1

Regards, Berry.


-----Original Message-----
From: Linux on 390 Port [mailto:[email protected]] On Behalf Of
Neale Ferguson
Sent: woensdag 18 augustus 2010 15:48
To: [email protected]
Subject: Re: mono keep guest active - ban the blips.

My mistake! I have checked with the mono folks and gone through the
code. It turns out that the culprit is pthread_cond_timedwait() used to
check for changes to the .config file. This has, apparently, been fixed
in later releases/versions of mono. What level are you on?

You can verify that the culprit is as I suggest by using gdb with the -p
<pid> option from root. It should stop in that API and a backtrace (bt
comand) should show something like this:


----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
----------------------------------------------------------------------
For more information on Linux on System z, visit
http://wiki.linuxvm.org/
ÿþDit bericht is vertrouwelijk en kan 
geheime informatie bevatten enkel

bestemd voor de geadresseerde. Indien 
dit bericht niet voor u is bestemd,

verzoeken wij u dit onmiddellijk aan 
ons te melden en het bericht te

vernietigen.

Aangezien de integriteit van het 
bericht niet veilig gesteld is middels

verzending via internet, kan Atos 
Origin niet aansprakelijk worden 
gehouden

voor de inhoud daarvan.

Hoewel wij ons inspannen een virusvrij 
netwerk te hanteren, geven

wij geen enkele garantie dat dit 
bericht virusvrij is, noch aanvaarden 
wij

enige aansprakelijkheid voor de 
mogelijke aanwezigheid van een virus in 
dit

bericht.

 

Op al onze rechtsverhoudingen, 
aanbiedingen en overeenkomsten 
waaronder

Atos Origin goederen en/of diensten 
levert zijn met uitsluiting van alle

andere voorwaarden de 
Leveringsvoorwaarden van Atos Origin 
van toepassing.

Deze worden u op aanvraag direct 
kosteloos toegezonden.

 

This e-mail and the documents attached 
are confidential and intended solely

for the addressee; it may also be 
privileged. If you receive this e-mail

in error, please notify the sender 
immediately and destroy it.

As its integrity cannot be secured on 
the Internet, the Atos Origin group

liability cannot be triggered for the 
message content. Although the

sender endeavours to maintain a 
computer virus-free network, the sender

does not warrant that this transmission 
is virus-free and will not be

liable for any damages resulting from 
any virus transmitted.

 

On all offers and agreements under 
which Atos Origin supplies goods and/or

services of whatever nature, the Terms 
of Delivery from Atos Origin

exclusively apply. 

The Terms of Delivery shall be promptly 
submitted to you on your request.

 

Atos Origin Nederland B.V. / Utrecht

KvK Utrecht 30132762

Reply via email to