From: Nix <nix@esperi.org.uk>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, e1000-devel@lists.sourceforge.net,
netdev@vger.kernel.org
Subject: Re: 2.6.30rc7: ksoftirqd CPU saturation (x86-64 only, not x86-32) (e1000e-related?)
Date: Mon, 01 Jun 2009 01:16:26 +0100 [thread overview]
Message-ID: <87ljoczu3p.fsf@hades.wkstn.nix> (raw)
In-Reply-To: <20090531170350.1355b3f1.akpm@linux-foundation.org> (Andrew Morton's message of "Sun, 31 May 2009 17:03:50 -0700")
On 1 Jun 2009, Andrew Morton said:
> Let's cc netdev on this.
>
> Presumably it is a post-2.6.29 regression.
I don't know: the earliest kernel this machine has ever run was
2.6.30rc5, and this failing 2.6.30rc7 kernel is the first 64-bit kernel
I've ever run on it. So currently I have one single data point.
I plan to try out 2.6.29 (and back to 2.6.25 or thereabouts) tomorrow
and see if it ever worked: if it did I'll bisect for it (rendered tricky
by the out-of-tree e1000e driver, but doable: it would be easier if I
had a clue where the e1000-devel git tree is, if anywhere, but I still
have no idea despite considerable searching).
It seems to go wrong instantly, so replication is trivial, and this
system can compile a kernel in slightly under a minute, so it shouldn't
take too long to complete the bisection.
next prev parent reply other threads:[~2009-06-01 0:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-31 22:59 Nix
2009-06-01 0:03 ` Andrew Morton
2009-06-01 0:16 ` Nix [this message]
2009-06-01 4:58 ` David Miller
2009-06-01 19:12 ` 2.6.30rc7: ksoftirqd CPU saturation (x86-64 and x86-32 both) (in-tree e1000e at fault) Nix
2009-06-01 16:48 ` [E1000-devel] 2.6.30rc7: ksoftirqd CPU saturation (x86-64 only, not x86-32) (e1000e-related?) Brandeburg, Jesse
2009-06-01 19:33 ` Nix
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=87ljoczu3p.fsf@hades.wkstn.nix \
--to=nix@esperi.org.uk \
--cc=akpm@linux-foundation.org \
--cc=e1000-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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
all inboxes | Powered by JetHome®