Re: That alleged hyperthreading-related bug

2005-01-17 Thread Yitzchak Scott-Thoennes
On Mon, Jan 17, 2005 at 04:06:52PM -0500, Christopher Faylor wrote: > On Mon, Jan 17, 2005 at 12:17:52PM -0800, Mark Geisert wrote: > >If you have by now identified the hardware/OSversion you need to > >reproduce the problem yourself, please let us know so we can stop > >annoying you. > > I did as

Re: That alleged hyperthreading-related bug

2005-01-17 Thread Christopher Faylor
On Mon, Jan 17, 2005 at 12:17:52PM -0800, Mark Geisert wrote: >If you have by now identified the hardware/OSversion you need to >reproduce the problem yourself, please let us know so we can stop >annoying you. I did ask for people to respond with hardware which shows the problem. A simple respons

Re: That alleged hyperthreading-related bug

2005-01-17 Thread Mark Geisert
Hi Christopher, If you have by now identified the hardware/OSversion you need to reproduce the problem yourself, please let us know so we can stop annoying you. If that info is not important, please let us know. If you haven't identified the hw/OS, how will you figure this out without more (ideal

Re: That alleged hyperthreading-related bug

2005-01-17 Thread Christopher Faylor
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