public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: "Frédéric Weisbecker" <fweisbec@gmail.com>,
	"Linux Kernel" <linux-kernel@vger.kernel.org>
Subject: Re: [crash] Re: [PATCH 1/3] tracing/function-graph-tracer: introduce __notrace_funcgraph to filter special functions
Date: Fri, 12 Dec 2008 12:31:26 +0100	[thread overview]
Message-ID: <20081212113126.GG32640@elte.hu> (raw)
In-Reply-To: <alpine.DEB.1.10.0812091639390.19875@gandalf.stny.rr.com>


* Steven Rostedt <rostedt@goodmis.org> wrote:

> 
> On Tue, 9 Dec 2008, Fr?d?ric Weisbecker wrote:
> > 2008/12/9 Fr?d?ric Weisbecker <fweisbec@gmail.com>:
> > 
> > 
> > I built this config on an smp x86-64 and booted several times (and
> > tested the function tracer manually) with and without the following
> > options:
> > 
> > initcall_debug apic=verbose sysrq_always_enabled ignore_loglevel
> > selinux=0 nmi_watchdog=2 idle=poll
> > 
> > And I can't reproduce this bug.... That might be a very nasty race condition...
> 
> Neither can I :-(
> 
> Ingo, is this on the box that stresses NMIs?

yes. You could try to inject even more NMIs than i normally do, 
artificially, by picking up tip/master and running KernelTop with a 
100,000 cycles IRQ interval:

    http://redhat.com/~mingo/perfcounters/kerneltop.c

run it like this:

    ./kerneltop -c 100000

and run an infinite loop per process:

    while :; do :; done &

to get the NMIs going intensely:

------------------------------------------------------------------------------
 KernelTop:  115437 irqs/sec  [NMI, 100000 cycles],  (all, 16 CPUs)
------------------------------------------------------------------------------

             events         RIP          kernel function
  ______     ______   ________________   _______________

           81224.00 - ffffffffff6001a4 : vread_hpet
            3119.00 - ffffffff8027cf99 : perf_read
            2484.00 - ffffffff802227d5 : read_hpet
            1157.00 - ffffffff8056b69a : mutex_lock
            1041.00 - ffffffffff600000 : vgettimeofday
             986.00 - ffffffff80333db5 : avc_has_perm_noaudit
             896.00 - ffffffff8026be2d : audit_syscall_exit
             653.00 - ffffffff8056c8f5 : _spin_lock
             577.00 - ffffffff802ecd14 : dnotify_parent
             528.00 - ffffffff8033679c : file_has_perm
             489.00 - ffffffff802bc060 : dput
             470.00 - ffffffff8026c366 : audit_syscall_entry


	Ingo

  reply	other threads:[~2008-12-12 11:31 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-06  2:40 [PATCH 1/3] tracing/function-graph-tracer: introduce __notrace_funcgraph to filter special functions Frederic Weisbecker
2008-12-06  3:01 ` Frederic Weisbecker
2008-12-08 14:14 ` Ingo Molnar
2008-12-08 15:25   ` Frédéric Weisbecker
2008-12-08 15:50     ` Ingo Molnar
2008-12-09  2:38       ` [crash] " Ingo Molnar
2008-12-09  8:59         ` Frédéric Weisbecker
2008-12-09 20:05           ` Frédéric Weisbecker
2008-12-09 21:40             ` Steven Rostedt
2008-12-12 11:31               ` Ingo Molnar [this message]
2008-12-08 15:57     ` [PATCH] tracing/function-graph-tracer: fix 'flags' variable mismatch Ingo Molnar

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=20081212113126.GG32640@elte.hu \
    --to=mingo@elte.hu \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rostedt@goodmis.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