From: Valdis.Kletnieks@vt.edu
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.21-mm2 - 100% CPU on ksoftirqd/1
Date: Wed, 09 May 2007 12:08:43 -0400 [thread overview]
Message-ID: <4123.1178726923@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Wed, 09 May 2007 01:23:22 PDT." <20070509012322.199f292b.akpm@linux-foundation.org>
[-- Attachment #1: Type: text/plain, Size: 1127 bytes --]
On Wed, 09 May 2007 01:23:22 PDT, Andrew Morton said:
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.21/2.6.21-mm2/
Boots up to multiuser mostly OK. However...
It comes up with a screaming ksoftirqd - usually /1 but one boot had /0.
Just sitting there, 100% CPU according to 'top'. Tried 'echo t > /proc/sysrq-trigger' to get
a trace, but it was always running on the other CPU - even after I reniced
it down to 19 and launched 2 'for(;;)' C programs to suck the cycles. It would
be failing to get any CPU - until I did the 'echo t' and then it would be
"running" again. Anybody got any good debugging ideas here?
Oddly enough, the kernel panic I was seeing at X server shutdown, related to
-x86_64-mm-reloc64-__pa-and-__pa_symbol-address-space-separation.patch,
seems to be gone now (not extensively tested - but it did survive one shutdown
without crashing at a point that *had* been a 100% fatal from -rc5-mm3 to 21-mm1.
I wish I understood why.
Replicated with a boot to single-user and an untainted kernel - by that point,
it was spinning at 100% already.
Any ideas how to debug this one?
[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]
next prev parent reply other threads:[~2007-05-09 16:08 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-09 8:23 2.6.21-mm2 Andrew Morton
2007-05-09 14:57 ` 2.6.21-mm2 - Kconfig horkage Valdis.Kletnieks
2007-05-09 17:07 ` Christoph Lameter
2007-05-09 17:16 ` Valdis.Kletnieks
2007-05-09 18:36 ` Christoph Lameter
2007-05-09 16:08 ` Valdis.Kletnieks [this message]
2007-05-09 17:31 ` 2.6.21-mm2 - 100% CPU on ksoftirqd/1 Andrew Morton
2007-05-09 18:12 ` Jeremy Fitzhardinge
2007-05-09 20:13 ` Valdis.Kletnieks
2007-05-11 2:52 ` Valdis.Kletnieks
2007-05-09 16:51 ` 2.6.21-mm2 - hanging with initcall_debug and netconsole Valdis.Kletnieks
2007-05-09 17:37 ` Andrew Morton
2007-05-10 11:29 ` 2.6.21-mm2 -- compat_core_sys_select() kmalloc(0) Andy Whitcroft
2007-05-10 11:48 ` 2.6.21-mm2 -- powerpc missing kset Andy Whitcroft
2007-05-10 12:16 ` Stephen Rothwell
2007-05-10 15:48 ` Randy Dunlap
2007-05-10 23:45 ` Stephen Rothwell
2007-05-10 12:21 ` ixp4xx compile error (was Re: 2.6.21-mm2) Frederik Deweerdt
2007-05-10 12:45 ` Frederik Deweerdt
2007-05-10 12:56 ` Dmitry Torokhov
2007-05-10 16:11 ` 2.6.21-mm2 Marc Dietrich
2007-05-10 19:22 ` 2.6.21-mm2 Andrew Morton
2007-05-10 20:40 ` 2.6.21-mm2 Marc Dietrich
2007-05-11 8:27 ` [-mm patch] make csum_and_copy_from_user arch independent (was Re: 2.6.21-mm2) Frederik Deweerdt
2007-05-11 8:33 ` Andrew Morton
2007-05-11 9:14 ` [-mm patch] make csum_and_copy_from_user arch independent David Miller
2007-05-11 13:56 ` Frederik Deweerdt
2007-05-11 17:04 ` Russell King
2007-05-11 18:03 ` 2.6.21-mm2 boot failure, raid autodetect, bd_set_size+0xb/0x80 thunder7
2007-05-11 18:18 ` Andrew Morton
2007-05-11 18:53 ` thunder7
2007-05-15 3:25 ` 2.6.21-mm2 - CONFIG_STATISTIC and Intel PowerTOP Valdis.Kletnieks
2007-05-15 14:25 ` Martin Peschke
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=4123.1178726923@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=akpm@linux-foundation.org \
--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
all inboxes | Powered by JetHome®