On Wed, 12 Dec 2012, Alan Stern wrote:
> > Nehalem seems to be a particular CPU from 2008. ICH9 came out in 2007.
> > So I guess your hardware is a year older than what the devs are looking
> > for. I would suggest you test on the newer box anyway.
>
> I just finished the test. The ICH9 system
On Mon, 10 Dec 2012, Sarah Sharp wrote:
> > > Ok. The hardware devs are asking if this problem is hit on newer
> > > hardware. They think that most of the kinks in the EHCI host should
> > > have been worked out by the Nehalem generation. Do you have access to a
> > > newer EHCI system? If not
On Mon, Dec 10, 2012 at 02:35:02PM -0500, Alan Stern wrote:
> On Mon, 10 Dec 2012, Sarah Sharp wrote:
>
> > > > Sure, I'll try to track the right hardware person down. I'm afraid they
> > > > might not be able to help, because they may not remember hardware that
> > > > is
> > > > that old. :-/
On Mon, 10 Dec 2012, Sarah Sharp wrote:
> > > Sure, I'll try to track the right hardware person down. I'm afraid they
> > > might not be able to help, because they may not remember hardware that is
> > > that old. :-/
> >
> > For all I know, newer hardware might behave the same way. It's easy
On Sat, Dec 08, 2012 at 11:02:00PM -0500, Alan Stern wrote:
> On Fri, 7 Dec 2012, Sarah Sharp wrote:
>
> > On Fri, Dec 07, 2012 at 05:51:55PM -0500, Alan Stern wrote:
> > > Sarah:
> > >
> > > I just tracked down a tricky problem, which appears to be caused by a
> > > genuine hardware bug. It's h
On Fri, 7 Dec 2012, Sarah Sharp wrote:
> On Fri, Dec 07, 2012 at 05:51:55PM -0500, Alan Stern wrote:
> > Sarah:
> >
> > I just tracked down a tricky problem, which appears to be caused by a
> > genuine hardware bug. It's hard to believe this has escaped everyone's
> > notice for so many years --
On Fri, Dec 07, 2012 at 05:51:55PM -0500, Alan Stern wrote:
> Sarah:
>
> I just tracked down a tricky problem, which appears to be caused by a
> genuine hardware bug. It's hard to believe this has escaped everyone's
> notice for so many years -- maybe my results are wrong. But as far as
> I can
Sarah:
I just tracked down a tricky problem, which appears to be caused by a
genuine hardware bug. It's hard to believe this has escaped everyone's
notice for so many years -- maybe my results are wrong. But as far as
I can tell, they aren't.
Anyway, I don't know what to do about it. Can you f
