public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Rafał Bilski" <rafalbilski@interia.pl>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: NOHZ: local_softirq_pending 08
Date: Tue, 29 May 2007 08:01:03 +0200	[thread overview]
Message-ID: <465BC19F.5070309@interia.pl> (raw)

>>  Hi!
>>
>> A lot of "NOHZ: local_softirq_pending 08" messages (about 100) and
>> then suddenly stoped to show. I have 2.6.21.1. I checked .2 and .3
>> changelogs but I don't see anything about this message.
>> What does it mean?
>>
>> Is "08" IRQ number?
>>   8:          2    XT-PIC-XT        rtc
>>
>> Please CC me.
> Does this patch [ http://lkml.org/lkml/2007/5/22/35 ] helps you fix it ?
> 
> Regards 
> Ananitya

Thanks. Looks like it will.

Regards
Rafał



----------------------------------------------------------------------
Ile masz w domu niepotrzebnych rzeczy?
Wymien sie z sasiadami >> http://link.interia.pl/f1a93



             reply	other threads:[~2007-05-29  6:01 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-29  6:01 Rafał Bilski [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-05-30 21:48 NOHZ: local_softirq_pending 08 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 10:32         ` David Miller
2009-10-12 11:25           ` Tilman Schmidt
2009-10-15 11:40             ` Jarek Poplawski
2009-10-15 17:53               ` Jarek Poplawski
2009-10-21 18:46                 ` Tilman Schmidt
2009-10-22 23:37                   ` Tilman Schmidt
2009-10-23 13:34                     ` Johannes Berg
2009-10-23 14:27                       ` Tilman Schmidt
2009-10-23 14:31                         ` Johannes Berg
2009-10-23 16:33                           ` Tilman Schmidt
2009-10-11 16:39 ` Joe Korty
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=465BC19F.5070309@interia.pl \
    --to=rafalbilski@interia.pl \
    --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