Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Subject: Re: update on hyperthreading system for cgf From: Adrian Cox To: cygwin@cygwin.com In-Reply-To: <20050114005832.GA19741@trixie.casa.cgf.cx> References: <20050110172023.GA2023@trixie.casa.cgf.cx> <20050110221922.GA5174@trixie.casa.cgf.cx> <20050114005832.GA19741@trixie.casa.cgf.cx> Content-Type: text/plain Date: Fri, 14 Jan 2005 09:34:17 +0000 Message-Id: <1105695257.28030.28.camel@localhost> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes On Thu, 2005-01-13 at 19:58 -0500, Christopher Faylor wrote: > This is still pretty far off from the goal but I would still appreciate > it if anyone could recommend a cheap system which demonstrates the > problem. So far, I don't recall anyone giving specific details about a > name brand computer or a specific motherboard. If I start getting names > I can start doing research on the best place to purchase a system. I just put together a machine with an Intel D865PERL motherboard and 3.0GHz P4 (1MB cache, 800MHz bus), PC3200 RAM on two banks. It shows the bug within minutes when running XP Pro. The same machine runs the test case for a very long time without incident under Windows 2000. -- Adrian Cox -- 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/