X-Spam-Check-By:	sourceware.org
Message-ID:	<b08667d90706040119n66581d02xe414d44650a059b9@mail.gmail.com>
Date:	Mon, 4 Jun 2007 10:19:03 +0200
From:	"Nicolas Joyard" <joyard DOT nicolas AT gmail DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: 1.5.24: shell commands randomly skipped
MIME-Version:	1.0
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
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

> AFAIK this is a 'prescott' Pentium 4 Multithreaded CPU.
>
> There's been a lot of discussion recently about Cygwin and
> dual-core/MT-core CPUs.  I have one and often have these kind of
> problems, usually during building libtool-based packages, which is
> bash-intensive.
>
> Unfortunately nobody has found a solution yet.  I hope that someone with
> the knowledge to do so will take this seriously in the near future, as
> it seems to affect more and more people.

Thanks for your answer. It seems that forcing the affinity of the
first bash process to only one CPU solves this issue.

-- 
Nicolas JOYARD

--
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/

- Raw text -