All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brad Laue <brad@brad-x.com>
To: "Hmamouche, Youssef" <youssef@ece.utexas.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ksoftirqd using mysteriously high amounts of CPU time
Date: Fri, 12 Mar 2004 02:06:03 -0500	[thread overview]
Message-ID: <4051615B.1030009@brad-x.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0403111916570.3466-100000@linux08.ece.utexas.edu>

Hmamouche, Youssef wrote:
  > Is there any way you could replace one of the network cards and 
test? I have a
> feeling it's a hardware problem where the interrupt never gets acknowledged in
> some situations - ksoftirq gets crazy.
> 
> you

This has occurred on any combination of the following six things:

Network cards:
Realtek 8139
SiS 900 Integrated
NE2K
3Com 3c905b

Motherboard chipsets:
ALI M1541
SiS 740
AMD 760

On the following kernel versions: 2.4.20, 2.4.21, 2.4.22, 2.4.23 (and 
-aa variants of 2.4.22, .23), 2.6.1, 2.6.2, 2.6.3.

It could well be a BIOS setting I'm habitually setting and forgetting 
about which is common to all motherboards, I'll have to check on that. 
Are there any of these I should be looking out for?

       reply	other threads:[~2004-03-12  7:00 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.21.0403111916570.3466-100000@linux08.ece.utexas.edu>
2004-03-12  7:06 ` Brad Laue [this message]
2004-03-10 21:16 ksoftirqd using mysteriously high amounts of CPU time Brad Laue
2004-03-10 23:57 ` Andrew Morton
2004-03-11  8:45   ` Brad Laue
2004-03-11  9:28     ` Brad Laue
2004-03-11 10:08       ` Andrew Morton
2004-03-11 14:05         ` Yury V. Umanets
2004-03-11 17:22           ` Brad Laue
2004-03-11 18:09             ` Yury V. Umanets
2004-03-11 18:21               ` Brad Laue
2004-03-11 18:24         ` Brad Laue
2004-03-12 17:51         ` Brad Laue
2004-03-11 14:00       ` Yury V. Umanets

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=4051615B.1030009@brad-x.com \
    --to=brad@brad-x.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=youssef@ece.utexas.edu \
    /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.