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: Mon, 17 Jan 2005 12:11:25 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: That alleged hyperthreading-related bug Message-ID: <20050117171125.GI20403@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 Mon, Jan 17, 2005 at 12:47:56AM -0800, Mark Geisert wrote: >Hi, I don't know how additional narrowing-down info about this can be >posted without sounding like a redundant annoying "me too" but here goes. > >I can easily reproduce it on a Dell Workstation PWS360 running WinXP SP1. >The CPU is a 2.8Ghz Pentium 4, 800MHz FSB. 1GB RAM installed but no more >than 350MB or so is used when I reproduce the bug. It's an i875P mobo. >I cannot reproduce it on a 2-CPU Win2K machine, echoing other reports. There is no need to report YA variation of the problem. Unless you are actually investigating code, reporting symptoms is not going to help. This. Is a recording. 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/