From: P@draigBrady.com
To: Andrew Morton <akpm@osdl.org>
Cc: netdev@oss.sgi.com, dav@neocom.fr
Subject: Re: Fw: [Bugme-new] [Bug 2782] New: ksoftirqd load system, kernel hang after a few minuts
Date: Fri, 28 May 2004 11:35:31 +0100 [thread overview]
Message-ID: <40B715F3.9010200@draigBrady.com> (raw)
In-Reply-To: <20040527115311.472d3c3a.akpm@osdl.org>
Andrew Morton wrote:
> Suggest you try an up-to-date kernel.
>
> Begin forwarded message:
>
> Date: Thu, 27 May 2004 09:19:49 -0700
> From: bugme-daemon@osdl.org
> To: bugme-new@lists.osdl.org
> Subject: [Bugme-new] [Bug 2782] New: ksoftirqd load system, kernel hang after a few minuts
>
>
> http://bugme.osdl.org/show_bug.cgi?id=2782
>
> Summary: ksoftirqd load system, kernel hang after a few minuts
> Kernel Version: 2.4.20-2.4.22
> Status: NEW
> Severity: blocking
> Owner: other_other@kernel-bugs.osdl.org
> Submitter: dav@neocom.fr
I've just seen something similar with official 2.4.20+e1000 v5.2.30.1
on a Dual Intel Xeon CPU 2.6G+hyperthreading. Note I use IRQ affinity
so both ksoftirqd_CPU[02] are at 100%.
The following is repeatable in about a minute which is good.
I send in around 700,000 packets per second on each of 2 interfaces,
and let the packets continually overflow the (4096 entry) buffers.
After about a minute I can't receive any traffic, and a couple
of occasions the machine just rebooted, so something is getting
corrupted. I was suspecting the e1000 driver buffer management until
I seen this?
Pádraig.
next prev parent reply other threads:[~2004-05-28 10:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-27 18:53 Fw: [Bugme-new] [Bug 2782] New: ksoftirqd load system, kernel hang after a few minuts Andrew Morton
2004-05-28 10:35 ` P [this message]
2004-05-28 12:00 ` Fw: [Bugme-new] [Bug 2782] New: ksoftirqd load system, kernelha ng " David TILLOY
2004-07-13 12:10 ` Fw: [Bugme-new] [Bug 2782] New: ksoftirqd load system, kernel h anga fter " David TILLOY
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=40B715F3.9010200@draigBrady.com \
--to=p@draigbrady.com \
--cc=akpm@osdl.org \
--cc=dav@neocom.fr \
--cc=netdev@oss.sgi.com \
/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;
as well as URLs for NNTP newsgroup(s).