Dan Armbrust <daniel.armbrust.list@xxxxxxxxx> wrote: > Restarted the machine, ran my app, and boom - it connects up, and pulls in data. > > Now, I'm back on-topic for this thread - the machine load still > spirals out of control when it runs. > > Here is the last capture from top that I was able to get (this is > after the program had been running for a couple of minutes) > > top - 18:28:57 up 12 min, 2 users, load average: 27.42, 14.38, 6.40 > Tasks: 98 total, 14 running, 84 sleeping, 0 stopped, 0 zombie > Cpu(s): 27.8% us, 72.2% sy, 0.0% ni, 0.0% id, 0.0% wa, 0.0% hi, 0.0% si > Mem: 256064k total, 253268k used, 2796k free, 16544k buffers > Swap: 522104k total, 0k used, 522104k free, 113640k cached > > PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND > 5916 vortex 16 0 1573m 13m 7448 S 55.4 5.5 2:05.46 heavy weather.e > 5919 vortex 15 0 25248 21m 748 R 46.4 8.5 1:31.39 wineserver > 4687 root 18 0 9340 5192 1896 R 0.2 2.0 0:01.78 perl > 4683 root 16 0 9712 4640 1828 S 0.1 1.8 0:01.17 perl Ok, I guess that you only pasted the first lines. What is a little confusing is your high load. Not only do wineserver and Heavy Weather eat up all of the CPU, there also are some 20 other apps competing for it. Either the first two are hogging the CPU so much that everything else has to wait, or wine spawned a lot of children; my guess is on the first option. What is the output of 'setserial -a /dev/ttyS0'? > And here is the output that I got from the launch of the app: > > wine heavy\ weather.exe > fixme:win:EnumDisplayDevicesW ((null),0,0x7bbbf7f4,0x00000000), stub! > fixme:win:EnumDisplayDevicesW ((null),1,0x7bbbf7f4,0x00000000), stub! > fixme:win:EnumDisplayDevicesW ((null),0,0x7bbbf7f4,0x00000000), stub! > fixme:win:EnumDisplayDevicesW ((null),1,0x7bbbf7f4,0x00000000), stub! > fixme:comm:SetupComm insize 1298 outsize 1298 unimplemented stub > fixme:comm:SetupComm insize 1298 outsize 1298 unimplemented stub > err:ntdll:RtlpWaitForCriticalSection section 0x685f8f58 "?" wait timed > out in thread 0059, blocked by 0009, retrying (60 sec) > err:ntdll:RtlpWaitForCriticalSection section 0x685f8f58 "?" wait timed > out in thread 000c, blocked by 0009, retrying (60 sec) > err:ntdll:RtlpWaitForCriticalSection section 0x685f8f58 "?" wait timed > out in thread 000c, blocked by 0009, retrying (60 sec) > err:ntdll:RtlpWaitForCriticalSection section 0x685f8f58 "?" wait timed > out in thread 000c, blocked by 0009, retrying (60 sec) Not surprising given the above top listing. Daniel _______________________________________________ wine-users mailing list wine-users@xxxxxxxxxx http://www.winehq.org/mailman/listinfo/wine-users
