From: Dave Jones <davej@redhat.com>
To: Sasha Levin <sasha.levin@oracle.com>
Cc: Tejun Heo <tj@kernel.org>,
tglx@linutronix.de, Peter Zijlstra <peterz@infradead.org>,
LKML <linux-kernel@vger.kernel.org>,
trinity@vger.kernel.org
Subject: Re: timer: lockup in run_timer_softirq()
Date: Tue, 9 Jul 2013 18:47:06 -0400 [thread overview]
Message-ID: <20130709224706.GA13855@redhat.com> (raw)
In-Reply-To: <51DC902F.3070403@oracle.com>
On Tue, Jul 09, 2013 at 06:35:27PM -0400, Sasha Levin wrote:
> Hi all,
>
> While fuzzing with trinity inside a KVM tools guest running latest -next, I've
> stumbled on the following spew:
>
> [ 2536.440007] BUG: soft lockup - CPU#0 stuck for 23s! [trinity-child86:12368]
> [ 2536.440007] Call Trace:
> [ 2536.440007] <IRQ>
> [ 2536.440007] [<ffffffff8113d180>] run_timer_softirq+0x2d0/0x330
> [ 2536.440007] [<ffffffff8113b400>] ? lock_timer_base+0x70/0x70
> [ 2536.440007] [<ffffffff81132b21>] __do_softirq+0x261/0x4d0
> [ 2536.440007] [<ffffffff81132ed6>] irq_exit+0x86/0x120
> [ 2536.440007] [<ffffffff841a43ea>] smp_apic_timer_interrupt+0x4a/0x60
> [ 2536.440007] [<ffffffff841a2d32>] apic_timer_interrupt+0x72/0x80
> [ 2536.440007] <EOI>
> [ 2536.440007] [<ffffffff84198ef7>] ? retint_restore_args+0x13/0x13
> [ 2536.440007] [<ffffffff812355e5>] ? user_enter+0x135/0x150
> [ 2536.440007] [<ffffffff81077d6d>] syscall_trace_leave+0x12d/0x160
> [ 2536.440007] [<ffffffff841a2337>] int_check_syscall_exit_work+0x34/0x3d
> [ 2536.440007] Code: 01 fd 48 89 df e8 45 5b 8f fd e8 b0 f1 00 fd 48 83 3d 30 e6 8a 01 00 75 0e 0f
> 0b 0f 1f 40 00 eb fe 66 0f 1f 44 00 00 fb 66 66 90 <66> 66 90 bf 01 00 00 00 e8 17 4f 00 00 65 48 8b
> 04 25 88 d9 00
>
> 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
I've been reporting these (and other traces) for a while https://lkml.org/lkml/2013/7/5/185 [1]
on bare-metal.
I've not managed to find time yet to try and narrow down the exact combination
of trinity syscalls that causes this. Sometimes it happens quickly, sometimes
after a few hours (even when run with the same seeds, it seems variable)
Dave
[1] lkml.org seems to be down right now. again. Sigh.
See
Subject: Yet more softlockups.
and
Subject: scheduling while atomic & hang
next prev parent reply other threads:[~2013-07-09 22: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 [this message]
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
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=20130709224706.GA13855@redhat.com \
--to=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=sasha.levin@oracle.com \
--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).