Re: NForce2 pseudoscience stability testing (general)

[Ian Kumlien <pomac@vapor.com>]

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

Hi, 

I also have a nforce2 mb (a7n8x-x). And i have also seen the same
lockups, but, while NOT USING the amd/nvidia driver i had some not as
bad experiences... It did lockup for 30 seconds or so at a time but it
always come back and when doing dmesg i had constant statements about
lost interrupts.

And to quote Craig Bradney:
..TIMER: vector=0x31 pin1=2 pin2=-1
..MP-BIOS bug: 8254 timer not connected to IO-APIC
...trying to set up timer (IRQ0) through the 8259A ...  failed.
...trying to set up timer as Virtual Wire IRQ... failed.
...trying to set up timer as ExtINT IRQ... works.

This was the first time i saw that, i doubt it's in 2.4 and i bet that
it's related. Imho it could be the amd/nvidia driver not handling the
lost interrupt as nicely as the "Unified E-IDE" driver.
(Since thats the only difference between complete deadlock and stalling
for XX seconds)

Or is this apic workaround in 2.4.23 (the only kernel i have tested on
this mb)?

This is just how i see it, I had hoped that someone would have shared my
view... =P

CC, Since i'm not on this ml... And, Comments please.

-- 
Ian Kumlien <pomac@vapor.com>

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