Re: NForce2 pseudoscience stability testing (2.6.0-test11)

[Julien Oster]

Alistair John Strachan <s0348365@xxxxxxxxxxxx> writes:

Hello Alistair,

> It's evidently a configuration problem, albeit BIOS, mainboard revision,
> memory quality, etc. because I and many others like me are able to run Linux
> 2.4/2.6 with all the options you tested and still achieve absolute stability,
> on the nForce 2 platform.

No, it's most evidently a mainboard problem, as everybody using an
ASUS A7N8X (Deluxe) reported so far that the mainboard will lock up
completely unless you turn of ACPI, APIC and local APIC. There is no
other possibility to work this lockup madness around, as many users of
that mainboard including me really tried *everything*.

We know that other NForce2 Mainboards don't have this kind of problem,
but sadly that isn't of any help whatsoever for us A7N8X users.

Unfortunately, my onboard SATA controller is significantly slower when
using XT-PIC interrupts (and I don't have many of them which aren't
crowded anyway). I can verify this by booting with ACPI and APIC
enabled and doing a simple hdparm -t multiple times on my SATA
softraid. I won't have much time to do this, though, since the
mainboard loves locking up very soon especially by doing hdparm -t.

HOWEVER, I tested it several times under Windows 2000 (I installed it
solely for this purpose, my machine used to be completely Redmond
free), and although Windows 2000 also routes the PCI interrupts via
APIC and ACPI, there's no such lockup occuring.

So, somehow, Linux should be able to allow the Asus A7N8X operate with
APIC and ACPI and any help in finally getting it in an usable state
would be strongly appreciated. I would have hacked the kernel myself,
but unfortunately I have no clue of the ACPI and APIC/local APIC stuff
in the kernel source.

Regards,
Julien
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/