RE: IO-APIC on nforce2 [PATCH]

[Craig Bradney <cbradney@zip.com.au>]

[-- Attachment #1: Type: text/plain, Size: 1809 bytes --]

On Thu, 2004-04-15 at 20:33, Allen Martin wrote:
> > True it is a bios thing but I have yet to see an nforce2 MOBO 
> > that is not 
> > routed in this way. I am thinking it is internal to the 
> > chipset. I have seen
> > none route it into io-apic pin2.
> 
> It was a bug in our original nForce reference BIOS that we gave out to vendors.  Since then we fixed the reference BIOS, but since it was after products shipped, most of the motherboard vendors won't pick up the change unless they get complaints from customers.
> 
> We've fixed it for our reference BIOS for future products though.

Would it not be worth Nvidia advising the vendors (possibly already
done) that there are nForce BIOS issues causing reproducable hard
crashes with their existing BIOS versions with relation to the issue
here? I realise that these manufacturers (in my case ASUS) may have no
obligation and have their own product schedules of course.

There would seem to be many people puchasing nForce based systems and
many will not find out how or why there is the problem.

I for one, will not be buying another nForce based motherboard until I'm
sure this issue is sorted properly. Yes, I will probably find issues on
other boards, but I have no such hard crashes on an old P3 Sis chipset
board, a VIA KT Abit Duron board, nor on this P4 board with the very
same kernel source.

While my single purchases make no difference in the scheme of things,
the lack of support from the various manufacturers given to the kernel
developers  (I refer in this case to Ross Dickson trying to get help
from Nvidia and another, I think AMD) is turning me away (back to Intel
CPUs).

Of course, I am very happy to finally see a response from someone from
Nvidia now.

With best regards
Craig Bradney



[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]