From: Dave Jones <davej@redhat.com>
To: Francois Romieu <romieu@fr.zoreil.com>
Cc: Marc Dionne <marc.c.dionne@gmail.com>,
Thomas Gleixner <tglx@linutronix.de>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: NOHZ: local_softirq_pending 08
Date: Thu, 7 Jun 2012 22:34:20 -0400 [thread overview]
Message-ID: <20120608023420.GD7191@redhat.com> (raw)
In-Reply-To: <20120606054251.GA24467@electric-eye.fr.zoreil.com>
On Wed, Jun 06, 2012 at 07:42:51AM +0200, Francois Romieu wrote:
> My sequence was:
>
> echo 0 > tracing_on
> echo nop > current_tracer
> echo 10000 > buffer_size_kb
> echo function > current_tracer
> echo rtl* > set_ftrace_filter
> echo r8169* >> set_ftrace_filter
> echo tick_nohz_stop_sched_tick >> set_ftrace_filter
>
> I only enabled tracing_on right before 'ip link ... up'.
Ok. This was a bit of a pain to trace, as I can't trigger the NOHZ message
when I bring up/down the interface by hand. It only seems to happen
during boot now for some reason. So I modified the networking ifup scripts
to start/stop the logging. It's still a pain, because there are two NICs
in the affected machine, so everything happens twice.
It also seems to have started too early & finished too late.. oh well.
hopefully you can get something interesting out of it.
> tick_nohz_stop_sched_tick fills the log rather fast.
I don't have that symbol for some reason.
The log is still huge though. (68M uncompressed) at http://www.codemonkey.org.uk/junk/r8169-trace.txt.xz
Here's the order of events on that boot...
[ 53.086040] r8169 0000:01:00.0: eth0: link down
[ 53.086441] r8169 0000:01:00.0: eth0: link down
[ 53.086545] NOHZ: local_softirq_pending 08
[ 53.113025] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 54.773637] r8169 0000:01:00.0: eth0: link up
[ 54.783210] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 64.941664] r8169 0000:05:00.0: eth1: link down
[ 64.941748] r8169 0000:05:00.0: eth1: link down
[ 64.941792] NOHZ: local_softirq_pending 08
[ 64.968326] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
[ 67.948677] r8169 0000:05:00.0: eth1: link up
[ 67.961872] IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
Dave
next prev parent reply other threads:[~2012-06-08 2:34 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
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-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=20120608023420.GD7191@redhat.com \
--to=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.c.dionne@gmail.com \
--cc=romieu@fr.zoreil.com \
--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