From: Sasha Levin <sasha.levin@oracle.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Tejun Heo <tj@kernel.org>,
tglx@linutronix.de, LKML <linux-kernel@vger.kernel.org>,
trinity@vger.kernel.org
Subject: Re: timer: lockup in run_timer_softirq()
Date: Wed, 10 Jul 2013 10:47:40 -0400 [thread overview]
Message-ID: <51DD740C.5090000@oracle.com> (raw)
In-Reply-To: <20130710095459.GE17211@twins.programming.kicks-ass.net>
On 07/10/2013 05:54 AM, Peter Zijlstra wrote:
> On Tue, Jul 09, 2013 at 06:35:27PM -0400, Sasha Levin wrote:
>> While going through the NMI dump, I noticed that it's very incomplete, and full of:
>>
>> [ 2536.500130] INFO: NMI handler (arch_trigger_all_cpu_backtrace_handler)
>> took too long to run: 697182.008 msecs
>
> Now I would actually expect arch_trigger_all_cpu_backtrace_handler() to
> issue this warning, that said, ~700 seconds is a bit long, I'm fairly
> sure it didn't actually take that long, you'd have noticed your vm being
> 'away' for 10+ minutes I'd think, no?
>
>
> There's something entirely fishy with that stuff, let me to stare at it.
Yeah, it didn't actually hang that long - that number is bogus.
Thanks,
Sasha
next prev parent reply other threads:[~2013-07-10 14:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-09 22:35 timer: lockup in run_timer_softirq() Sasha Levin
2013-07-09 22:47 ` Dave Jones
2013-07-09 22:49 ` Sasha Levin
2013-07-09 23:03 ` Dave Jones
2013-07-09 23:09 ` Sasha Levin
2013-07-10 9:52 ` Peter Zijlstra
2013-07-10 12:27 ` Steven Rostedt
2013-07-10 12:42 ` Peter Zijlstra
2013-07-10 12:58 ` Steven Rostedt
2013-07-11 16:42 ` Peter Zijlstra
2013-07-11 16:55 ` Steven Rostedt
2013-07-11 16:59 ` Steven Rostedt
2013-07-11 17:11 ` Peter Zijlstra
2014-04-03 20:43 ` Sasha Levin
2013-07-10 9:54 ` Peter Zijlstra
2013-07-10 14:47 ` Sasha Levin [this message]
2013-07-11 10:02 ` Peter Zijlstra
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=51DD740C.5090000@oracle.com \
--to=sasha.levin@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=tj@kernel.org \
--cc=trinity@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;
as well as URLs for NNTP newsgroup(s).