All of lore.kernel.org
 help / color / mirror / Atom feed
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

  reply	other threads:[~2008-10-03 16:58 UTC|newest]

Thread overview: 60+ 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 --
2012-05-30 21:48 Dave Jones
2012-05-31  7:52 ` Thomas Gleixner
2012-05-31  7:56   ` Eric Dumazet
2012-05-31 14:04     ` Dave Jones
2012-06-08 16:46       ` Nikos Chantziaras
2012-06-01 22:57   ` Francois Romieu
2012-06-02 20:58     ` Marc Dionne
2012-06-05 23:15       ` Francois Romieu
2012-06-06  1:46         ` Dave Jones
2012-06-06  5:42           ` Francois Romieu
2012-06-08  2:34             ` Dave Jones
2012-06-08  7:57               ` Thomas Gleixner
2012-06-08 14:23                 ` Dave Jones
2012-06-08 14:51                   ` Thomas Gleixner
2012-06-08 20:27                     ` Francois Romieu
2012-06-08 20:41                       ` Thomas Gleixner
2012-06-08 21:53                         ` Francois Romieu
2012-06-08 22:33                           ` Marc Dionne
2012-06-10 20:40                             ` Dave Jones
2012-06-25 12:38                           ` Johannes Stezenbach
2012-06-25 19:28                             ` Francois Romieu
2012-06-25 19:52                               ` Dave Jones
2012-06-08  8:32               ` Johannes Stezenbach
2009-10-11  9:52 Dave Young
2009-10-11 10:08 ` Johannes Berg
2009-10-11 10:17   ` Michael Buesch
2009-10-11 10:37     ` Johannes Berg
2009-10-11 10:38     ` David Miller
2009-10-11 10:55   ` Dave Young
2009-10-11 11:18   ` Tilman Schmidt
2009-10-11 11:40     ` Johannes Berg
2009-10-12  8:28       ` Tilman Schmidt
2009-10-12  8:28         ` Tilman Schmidt
2009-10-12 10:32         ` David Miller
2009-10-12 10:32           ` David Miller
2009-10-12 11:25           ` Tilman Schmidt
2009-10-12 11:25             ` Tilman Schmidt
2009-10-15 11:40         ` Jarek Poplawski
2009-10-15 11:40           ` Jarek Poplawski
2009-10-15 17:53           ` Jarek Poplawski
2009-10-15 17:53             ` Jarek Poplawski
2009-10-21 18:46             ` Tilman Schmidt
2009-10-21 18:46               ` Tilman Schmidt
2009-10-22 23:37               ` Tilman Schmidt
2009-10-22 23:37                 ` Tilman Schmidt
2009-10-23 13:34                 ` Johannes Berg
2009-10-23 13:34                   ` Johannes Berg
2009-10-23 14:27                   ` Tilman Schmidt
2009-10-23 14:27                     ` Tilman Schmidt
2009-10-23 14:31                     ` Johannes Berg
2009-10-23 14:31                       ` Johannes Berg
2009-10-23 16:33                       ` Tilman Schmidt
2009-10-23 16:33                         ` Tilman Schmidt
2009-10-11 16:39 ` Joe Korty
2008-10-02 18:30 liran raz
2007-05-29  6:01 Rafał Bilski
2007-05-28 21:04 Rafał Bilski
2007-05-28 22:12 ` Anant Nitya

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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.