Re: [PATCH] 2.6, 2.4, Nforce2, Experimental idle halt workaroundinstead of apic ack delay.

[Craig Bradney]

On Thu, 2004-02-12 at 22:52, Derek Foreman wrote:
> On Thu, 12 Feb 2004, Jesse Allen wrote:
> 
> > On Thu, Feb 12, 2004 at 12:17:12PM -0600, Derek Foreman wrote:
> > > Some nforce2 systems work just fine.  Is there a way to distinguish
> > > between systems that need it and those that don't?
> > >
> >
> > Some nforce2 systems are fixed in certain bioses.  The problem is we
> > don't know where/what it is in the bios.  C1 disconnect is a clue.
> 
> So a machine that locks up with stop grant enabled under one bios
> revision might run just fine with stop grant enabled on another?

Surely someone can decode the BIOS of an nforce user that is now ok
after a BIOS update?.

> > > (if anyone's running a betting pool, my money's on nforce2+cpu with half
> > > frequency multiplier ;)
> >
> > I don't know what your talking about.  My Shuttle AN35N nforce2 board
> > can run vanilla kernels with the 12-5-2003 dated bios version and not
> > lock up.  The frequencies I run are all the default/standard ones.
> 
> Some old (model 4, I think) athlons had a problem with disconnect, but
> only in the half multiplier versions.
> 
> Carlos' athlon has a 12.5 multiplier, so my theory's bogus

Whenthis thread first(?) started way back when in Nov or Dec last year I
was pretty happy.. no lockups until the 5th day. so what does "My
Shuttle AN35N nforce2 board can run vanilla kernels with the 12-5-2003
dated bios version and not lock up." mean?

Ross's v3 patches for 2.6/2.61 are still running well here on 2.6.1. I'm
waiting for work to settle down before trying his new ones.

Craig

Attachment: signature.asc
Description: This is a digitally signed message part