From: Ben Greear <greearb@candelatech.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: ksoftirqd_CPU0 spinning in 2.4.21-pre3
Date: Wed, 22 Jan 2003 11:44:16 -0800 [thread overview]
Message-ID: <3E2EF490.20402@candelatech.com> (raw)
I happened to notice that my ksoftirqd_CPU0 process started spinning
at 99% CPU when I plugged in the ports to a tulip NIC. I didn't see
any significant amount of interrupts when I looked at /proc/interrupts,
and there was no traffic running.
However, this is also running a hacked up tulip-napi driver, so it
could very well be my problem. I have not seen this on any other kernel
in several months though...
Anyway, if anyone has seen this, I'd like to know. Otherwise, I'll blame
my code and start poking at things...
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com> <Ben_Greear AT excite.com>
President of Candela Technologies Inc http://www.candelatech.com
ScryMUD: http://scry.wanfear.com http://scry.wanfear.com/~greear
next reply other threads:[~2003-01-22 19:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-22 19:44 Ben Greear [this message]
2003-01-23 14:58 ` ksoftirqd_CPU0 spinning in 2.4.21-pre3 Robert Olsson
2003-01-23 18:32 ` Ben Greear
2003-01-24 12:21 ` Robert Olsson
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=3E2EF490.20402@candelatech.com \
--to=greearb@candelatech.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