Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <9587061CFA8BD511878400D0B7828EE610F667A5@zfr11exm01.ea.freescale.net>
From: Guerte Yves-r57319 <Yves DOT Guerte AT freescale DOT com>
To: "'cygwin AT cygwin DOT com'" <cygwin AT cygwin DOT com>
Subject: RE: Hyperthreaded machine and cygwin
Date: Mon, 14 Mar 2005 11:29:30 +0100
MIME-Version: 1.0
Content-Type: text/plain

	Hi,
I want to insist on Earl message because I have seen no answer and I think
it is very similar (if not equal) to the problem I related in cygwin Issue 4105:
"env command seems to take all CPU".

Since then I had the same problem again occurring sometime with a "stucked" Perl script:
its execution was finished and it did not want to "really" end because its header 
was "#!/usr/bin/env perl" and the "env" command was stucked.

I had to kill the "env" process with the Windows task manager and Perl script did then end normally.

I tried to reproduce it in a systematic way with no success.

Best regards,
Yves

-----Original Message-----
From: cygwin-owner AT cygwin DOT com [mailto:cygwin-owner AT cygwin DOT com] On Behalf Of cygwin-digest-help AT cygwin DOT com
Sent: Friday, March 11, 2005 3:13 PM
To: cygwin AT cygwin DOT com
Subject: cygwin Digest 11 Mar 2005 14:12:41 -0000 Issue 4144
-----Original Message-----
From: Earl Chew [mailto:earl_chew AT agilent DOT com] 
Sent: Friday, March 11, 2005 1:39 AM
To: cygwin AT cygwin DOT com
Subject: Hyperthreaded machine and cygwin

I'd like some guidance or suggestions as to how to debug a
problem that I suspect has to do with my hyperthreaded cpu machine.
The symptom is that I have two build scripts executing. The scripts
traverse directories, use make, bash, sh, perl, etc. I have two
hyperthreaded cpus running XP, and very quickly the PC locks with 25%
of the time spent running some cygwin application (mostly sh.exe, but
once it was perl.exe).
Once the machine locks, it's unusable, though it continues to spin
on the stuck application.
The only way I can recover is to power cycle the machine.
I've tried cygwin-1.5.12 and cygwin.1.5.13-1.
Earl

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/