Re: NForce2 pseudoscience stability testing (2.6.0-test11)

[Prakash K. Cheemplavam]

Julien Oster wrote:
> 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*.

At least since kernel 2.6-test8, I thin,k ACPI works with my Abit 
nforce2 mobo. Before it crapped out.


> Unfortunately, my onboard SATA controller is significantly slower when

> 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.


Intersting. My Windows locks up, as written in the other post, though 
this seldomly occurs. Sometimes the system runs for days (using s3 and 
s4). Then it could lock-up within minutes after boot-up.

kernel26 though locks up pretty fast when apic is enbled.

What kind of SATA Adapter hat the Asus? I have a Silicon image Si3112A. 
Maybe this is the root of all evil. ItÄs driver sucks hard, as doing a 
hdparm -d1 /dev/hde craps my drive up. (Though hdparm claims the drive 
is already running in DMA mode.)

What kind of SATA controller do the Epox users have? Or don't they have 
SATA onbaord?

I know that SiI Image produced corruption with early bioses, so maybe 
this really is the weak spot.


Prakash

-
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/