Re: IO-APIC on nforce2 [PATCH] + [PATCH] for nmi_debug=1 + [PATCH]for idle=C1halt, 2.6.5

[Prakash K. Cheemplavam]

Hi all,

I have just made soem interesting experience. It seems Len's timer 
routing patch (or whatever you wanna call it) stabilizes my system to a 
certain amount or NOT using AGP stabilizes it to an amount...

The whole story: I am using Ross' C1halt patch to make the system stable 
in APIC mode, but due to a recent change I borked my kernel parameters 
and just had idle=halt instead of idle=C1halt as parameter, thus I had 
not activated Ross patch by accident. Nevertheless, the system survived 
a whole day! Usually it locks up within minutes, but this time no. I 
even did yome heavy copying from DVD to HD and from one HD to another 
with peaks of about 40mb/s. Finally the system crashed when I recorded 
from dvb to hd (but only after 20minutes). Then after a reboot (still 
NOT using Ross' patch) it survived dvb recording for about 30min.

I only manage to instantly lock the system when doing a hdparm (rather a 
second hdparm, the first one gives just about 20mb/sec, hello Jeff? What 
is libata doing here?) which goes up to >60mb/sec.

So Len, maybe try using a faster hd to crash your shuttle if it is one 
of the borked bioses...

As I used the open source NV driver all the time, AGP probably wasn't in 
use (or someone tell me how to use AGP with nv driver...), as ususally 
without Ross' patches using AGP I get fast lock-ups or as stated above 
Len's patch makes it a bit better. In fact I would need to try Len's 
patch and AGP on (with nvidia binary) to find out whether agp or Len's 
patch makes the difference. But currently I am too tired and not in the 
mood to further patch current mm-kernel to get Nvidia's binary running 
again...

Does anybody know a tool to generate certain amount of traffic on PCI 
bus? So I could test at which point the system wants to lock-up now. 
Only idea I have right now is to put an older hd into the system an test.

bye,

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/