From: Dan Creswell <dan@dcrdev.demon.co.uk>
To: linux-kernel@vger.kernel.org
Cc: Zwane Mwaikambo <zwane@linuxpower.ca>
Subject: Re: Hard locks under high interrupt load?
Date: Fri, 27 Feb 2004 13:59:00 +0000 [thread overview]
Message-ID: <403F4D24.6040802@dcrdev.demon.co.uk> (raw)
In-Reply-To: <Pine.LNX.4.58.0402270744240.17504@montezuma.fsmlabs.com>
This box is running Fedora Core 1 and so, yes, it's running a userspace
balance daemon (Redhat's).
I'll try out the noirqbalance option and get back to the list on that one.
Zwane Mwaikambo wrote:
>On Fri, 27 Feb 2004, Dan Creswell wrote:
>
>
>
>>I'm having zero success in getting 2.6.3 stable under interrupt load. I
>>can kill my machine in a variety of fashions all of which appear, to my
>>naive eye, related to interrupt load:
>>
>>(1) LAN traffic via E1000 card (X is not running)
>>(2) Running X for more than a few minutes - starting up a couple of
>>applications whilst performing some disk-based activity (such as a
>>compile) usually seems to do the trick.
>>
>>(2) is worth a little more examination. I have an NVIDIA card (I can
>>hear you all groan) *but* I get the same results with the XFree driver
>>*or* the proprietary NVIDIA driver.
>>
>>Disabling IO-APIC usage seems to resolve the problem.
>>
>>
>
>Does the 'noirqbalance' kernel parameter also serve as a workaround? Are
>you using any userspace irq balancers?
>
>
>
>>Machine is a dual Xeon, Tyan S2665 (E7505 chipset) with an MPT-Fusion
>>SCSI controller.
>>
>>2.4.26-pre1 and various other 2.4 kernels give me no problems at all. I
>>really want to switch my machines over to 2.6 but I can't whilst this
>>problem persists.
>>
>>
>
>
>
next prev parent reply other threads:[~2004-02-27 13:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-27 10:55 Hard locks under high interrupt load? Dan Creswell
2004-02-27 13:10 ` Zwane Mwaikambo
2004-02-27 13:59 ` Dan Creswell [this message]
2004-02-27 14:07 ` Zwane Mwaikambo
2004-02-27 18:34 ` Jeff Garzik
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=403F4D24.6040802@dcrdev.demon.co.uk \
--to=dan@dcrdev.demon.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=zwane@linuxpower.ca \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.