Re: PROBLEM: nForce2 keeps crashing during network activity

[Bob]

Jens Kübler wrote:

> > If the noapic or acpi=off stabilizes it for you and you want to run with
> > apic and io-apic then my patches may help.
> >
> > You can find them in this thread
> >
> > Updated Lockup Patches, 2.4.22 - 23 Nforce2, apic timer ack delay, ioapic
> > edge for NMI debug
> >
> > If unsubscribed you can find it here
> > http://linux.derkeiler.com/Mailing-Lists/Kernel/2003-12/4673.html
> > or here
> > http://lkml.org/lkml/2003/12/21/156
> >    
>
> I played a bit around with apic off and on and still it had no effect. My 
> board keeps crashing. Seems not to be related to apic.
>
> Jens
I would not count on that if it's an nforce2 board.
It's virtually an faq that if nforce2 is unstable then
you may actually need apic, local apic, ioapic, a
bios update, these patches, maybe athcool utility.

My nforce2 motherboard had ERR count and
excessive MIS count in /proc/interrupts due to
sharing interrupts between two pci cards. I
removed the ethernet card, used the motherboard
ethernet and forcedeth driver, so I was not sharing
interrupts between pci cards, and that gave me
ERR 0 and minimal MIS. Shared interrupts might
be your problem.

Personally I found that noapic or acpi=off could
not do anything for me either. Currently I have
pre-emptive kernel, apic, acpi, local apic.

You can try a bios flash update. This is most
hopeful for Award bios. Save your old bios
just in case when the flash software asks if you
want to save your old bios. We heard from one
person who needed to go back to his old bios,
but several got rid of their nforce2 crashes by
a bios update.

You can try athcool utility turning cpu disconnect
off--"athcool off". This stopped crashing for a few.
I don't need that.

You can try the patches; they can't hurt and would
be easy to remove. To make them work you need apic
on in bios, apic and local apic on in kernel config.

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