From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: linux-rt-users <linux-rt-users@vger.kernel.org>
Subject: Re: Crap, ksoftirqd/0 looping forever in softirq
Date: Thu, 11 Oct 2012 10:21:31 -0400 [thread overview]
Message-ID: <20121011142130.GA22583@windriver.com> (raw)
In-Reply-To: <20121011001637.GA18628@windriver.com>
[Crap, ksoftirqd/0 looping forever in softirq] On 10/10/2012 (Wed 20:16) Paul Gortmaker wrote:
> Seeing the above message, I added a trivial change to print out the
> Mask and Pending, and I consistently saw it was (both p/m) in every
> case `was __IRQF_TIMER (0x200).
Of cource it helps if I look up the value in the right list.
I guess the ffs had me thinking "bits", instead of looking up
the value in the softirq enum list.
When I add a change to record the last vecs used and dump them
out when the Crap message is triggered (using softirq_to_name
instead of looking things up in random tables!) I get this:
[ 20.887137] Crap, ksoftirqd/0 looping forever in softirq
[ 20.887150] Last: RCU RCU RCU RCU RCU RCU RCU RCU RCU RCU RCU RCU RCU RCU RCU RCU RCU RCU RCU
[ 20.920168] Crap, ksoftirqd/0 looping forever in softirq
[ 20.920179] Last: RCU RCU RCU RCU RCU RCU RCU RCU RCU RCU RCU RCU RCU RCU RCU RCU RCU RCU RCU
[ 20.954200] Crap, ksoftirqd/0 looping forever in softirq
[ 20.954213] Last: RCU RCU RCU RCU RCU RCU RCU RCU RCU RCU RCU RCU RCU RCU RCU RCU RCU RCU RCU
Which makes my previous guess complete garbage...
Paul.
next prev parent reply other threads:[~2012-10-11 14:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-11 0:16 Crap, ksoftirqd/0 looping forever in softirq Paul Gortmaker
2012-10-11 2:38 ` Mike Galbraith
2012-10-11 14:21 ` Paul Gortmaker [this message]
2012-10-11 15:34 ` Paul Gortmaker
2012-10-15 13:36 ` Paul E. McKenney
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=20121011142130.GA22583@windriver.com \
--to=paul.gortmaker@windriver.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=tglx@linutronix.de \
/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).