From: Scott Wood <scottwood@freescale.com>
To: liran raz <liranrazlinux@gmail.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: NOHZ: local_softirq_pending 08
Date: Fri, 03 Oct 2008 11:55:48 -0500 [thread overview]
Message-ID: <48E64E94.3080807@freescale.com> (raw)
In-Reply-To: <e3b3ab5c0810030940l3100e494id6b4fcdec71991a7@mail.gmail.com>
liran raz wrote:
> hi,
> I have a driver that uses the scc1 intertupts.
> After enabling the scc1 interrupts I see this message
> coming from the kernel for some time:
> NOHZ: local_softirq_pending 08
> 1. What is the meaning of this message? does
> 2. Does it indicate that something is wrong & need a fix?
> 3. How can I get rid of it?
> (The interrupt is connected to an ISR by using
> the standard request_irq() routine).
> Kernel 2.6.24
> Processor: MPC8272
> Thanks,
> Liran.
The error comes from generic timer code; I'd test with the latest kernel
and then ask on the linux-kernel list.
-Scott
next prev parent reply other threads:[~2008-10-03 16:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-03 16:40 NOHZ: local_softirq_pending 08 liran raz
2008-10-03 16:55 ` Scott Wood [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-10-02 18:30 liran raz
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=48E64E94.3080807@freescale.com \
--to=scottwood@freescale.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=liranrazlinux@gmail.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).