From: Bob <recbo@nishanet.com>
To: kernel list <linux-kernel@vger.kernel.org>
Subject: Re: PROBLEM: nForce2 keeps crashing during network activity
Date: Mon, 22 Dec 2003 08:18:50 -0500 [thread overview]
Message-ID: <3FE6EF3A.4090402@nishanet.com> (raw)
In-Reply-To: <200312221208.13218.cleanerx@au.hadiko.de>
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
next prev parent reply other threads:[~2003-12-22 13:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-22 4:51 PROBLEM: nForce2 keeps crashing during network activity Ross Dickson
2003-12-22 11:08 ` Jens Kübler
2003-12-22 13:18 ` Bob [this message]
2003-12-22 14:06 ` Ross Dickson
2003-12-31 15:58 ` Jens Kübler
-- strict thread matches above, loose matches on Subject: below --
2003-12-21 14:24 Jens Kübler
2003-12-21 19:51 ` Thomas Backlund
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3FE6EF3A.4090402@nishanet.com \
--to=recbo@nishanet.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox