From: Dave Jones <davej@redhat.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Peter Anvin <hpa@zytor.com>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: Yet more softlockups.
Date: Sat, 6 Jul 2013 20:24:42 -0400 [thread overview]
Message-ID: <20130707002442.GA3679@redhat.com> (raw)
In-Reply-To: <20130706072408.GA14865@gmail.com>
On Sat, Jul 06, 2013 at 09:24:08AM +0200, Ingo Molnar wrote:
>
> * Dave Jones <davej@redhat.com> wrote:
>
> > On Fri, Jul 05, 2013 at 05:15:07PM +0200, Thomas Gleixner wrote:
> > > On Fri, 5 Jul 2013, Dave Jones wrote:
> > >
> > > > BUG: soft lockup - CPU#3 stuck for 23s! [trinity-child1:14565]
> > > > perf samples too long (2519 > 2500), lowering kernel.perf_event_max_sample_rate to 50000
> > > > INFO: NMI handler (perf_event_nmi_handler) took too long to run: 238147.002 msecs
> > >
> > > So we see a softlockup of 23 seconds and the perf_event_nmi_handler
> > > claims it did run 23.8 seconds.
> > >
> > > Are there more instances of NMI handler messages ?
> >
> > [ 2552.006181] perf samples too long (2511 > 2500), lowering kernel.perf_event_max_sample_rate to 50000
> > [ 2552.008680] INFO: NMI handler (perf_event_nmi_handler) took too long to run: 500392.002 msecs
>
> Dave, could you pull in the latest perf fixes at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git perf/urgent
>
> In particular this:
>
> e5302920da9e perf: Fix interrupt handler timing harness
>
> could make a difference - if your tests somehow end up activating perf.
Not seeing the NMI printk (yet?), but saw this..
[ 2322.758913] perf samples too long (2502 > 2500), lowering kernel.perf_event_max_sample_rate to 50000
Dave
next prev parent reply other threads:[~2013-07-07 0:25 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-04 1:55 scheduling while atomic & hang Dave Jones
2013-07-04 2:49 ` Linus Torvalds
2013-07-04 4:43 ` H. Peter Anvin
2013-07-04 7:49 ` Dave Jones
2013-07-04 17:22 ` Linus Torvalds
2013-07-10 20:54 ` J. Bruce Fields
2013-07-04 18:08 ` H. Peter Anvin
2013-07-05 6:51 ` Ingo Molnar
2013-07-05 7:19 ` Frederic Weisbecker
2013-07-05 10:05 ` Ingo Molnar
2013-07-05 19:27 ` Linus Torvalds
2013-07-06 8:02 ` Frederic Weisbecker
2013-07-06 8:07 ` Ingo Molnar
2013-07-05 14:38 ` Yet more softlockups Dave Jones
2013-07-05 15:15 ` Thomas Gleixner
2013-07-05 16:00 ` Dave Jones
2013-07-05 16:02 ` Thomas Gleixner
2013-07-05 16:41 ` H. Peter Anvin
2013-07-05 18:20 ` Seiji Aguchi
2013-07-05 22:21 ` Thomas Gleixner
2013-07-06 7:24 ` Ingo Molnar
2013-07-07 0:24 ` Dave Jones [this message]
2013-07-10 15:13 ` Dave Jones
2013-07-10 15:20 ` Markus Trippelsdorf
2013-07-10 15:40 ` Dave Jones
2013-07-12 10:31 ` Ingo Molnar
2013-07-12 15:38 ` Dave Hansen
2013-07-12 15:45 ` Dave Jones
2013-07-12 15:55 ` Dave Hansen
2013-07-12 17:00 ` Dave Jones
2013-07-12 17:12 ` David Ahern
2013-07-12 17:18 ` Dave Jones
2013-07-12 17:40 ` David Ahern
2013-07-12 17:50 ` Dave Jones
2013-07-12 18:07 ` David Ahern
2013-07-12 18:22 ` Dave Hansen
2013-07-12 20:13 ` Dave Hansen
2013-07-13 1:40 ` Vince Weaver
2013-07-10 15:39 ` Vince Weaver
2013-07-10 15:45 ` Dave Jones
2013-07-10 21:54 ` Dave Jones
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=20130707002442.GA3679@redhat.com \
--to=davej@redhat.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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