Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Fri, 24 Dec 2004 10:51:36 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: "Hyperthreading" problems Message-ID: <20041224155136.GE22966@trixie.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i On Fri, Dec 24, 2004 at 09:01:17AM +0100, St?phane Donz? wrote: >we have encountered random hangs and crashes in cygwin (see output of >cygcheck attached to this message) on a dual-processor server running >Windows Server 2003. IMHO, the so-called "hyperthreading problems" reported >recently on this mailing list just have nothing to do with hyperthreading, >but are more generally related to multi-processor issues. If you have followed the thread, then you know that I have a multi-processor system and I don't have the problem. >I used the following test (found on this mailing list archive, posted 6 Apr >2004 by Chuck McDevitt): > > > >#! /bin/ksh >mypath=$(pwd) >while [[ ! -z $mypath ]] >do > mypath=$(pwd) > if [[ -z $mypath ]] > then > echo "Test Failed......Path is empty" > fi >done There is no point in reposting scripts. There is no point in recapitulating the problem. There is no point in making obvious observations about what one would suspect the cause would be without bothering to look at the code. Your options are to fix the problem yourself or wait until I someday have a system which demonstrates the problem. cgf -- 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/