From: Dave Jones <davej@redhat.com>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: nohz fail (was: perf related boot hang.)
Date: Mon, 11 Aug 2014 16:09:31 -0400 [thread overview]
Message-ID: <20140811200931.GA18865@redhat.com> (raw)
In-Reply-To: <20140807131646.GB19662@localhost.localdomain>
On Thu, Aug 07, 2014 at 03:16:49PM +0200, Frederic Weisbecker wrote:
> > > <<EOE>> <IRQ> [<ffffffff8a0ccd2f>] lock_acquired+0xaf/0x450
> > > [<ffffffff8a0f74c5>] ? lock_hrtimer_base.isra.20+0x25/0x50
> > > [<ffffffff8a7fc678>] _raw_spin_lock_irqsave+0x78/0x90
> > > [<ffffffff8a0f74c5>] ? lock_hrtimer_base.isra.20+0x25/0x50
> > > [<ffffffff8a0f74c5>] lock_hrtimer_base.isra.20+0x25/0x50
> > > [<ffffffff8a0f7723>] hrtimer_try_to_cancel+0x33/0x1e0
> > > [<ffffffff8a0f78ea>] hrtimer_cancel+0x1a/0x30
> > > [<ffffffff8a109237>] tick_nohz_restart+0x17/0x90
> > > [<ffffffff8a10a213>] __tick_nohz_full_check+0xc3/0x100
> > > [<ffffffff8a10a25e>] nohz_full_kick_work_func+0xe/0x10
> > > [<ffffffff8a17c884>] irq_work_run_list+0x44/0x70
> > > [<ffffffff8a17c8da>] irq_work_run+0x2a/0x50
> > > [<ffffffff8a0f700b>] update_process_times+0x5b/0x70
> > > [<ffffffff8a109005>] tick_sched_handle.isra.21+0x25/0x60
> > > [<ffffffff8a109b81>] tick_sched_timer+0x41/0x60
> > > [<ffffffff8a0f7aa2>] __run_hrtimer+0x72/0x470
> > > [<ffffffff8a109b40>] ? tick_sched_do_timer+0xb0/0xb0
> > > [<ffffffff8a0f8707>] hrtimer_interrupt+0x117/0x270
> > > [<ffffffff8a034357>] local_apic_timer_interrupt+0x37/0x60
> > > [<ffffffff8a80010f>] smp_apic_timer_interrupt+0x3f/0x50
> > > [<ffffffff8a7fe52f>] apic_timer_interrupt+0x6f/0x80
> >
> > And that looks like someone trying to cancel a timer from a timer, I
> > guess that won't work, seeing how cancel will wait for the timer handler
> > completion etc.
> >
> > This is because of the fallback irq_work_run() in the tick
> > (update_process_times).
> >
>
> Indeed, I saw that too but very rarely.
FWIW, I'm now seeing this quite often (several times a day) when I run
trinity on current git master.
Dave
next prev parent reply other threads:[~2014-08-11 20:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-06 14:36 perf related boot hang Dave Jones
2014-08-06 16:19 ` Peter Zijlstra
2014-08-06 16:23 ` Dave Jones
2014-08-06 19:46 ` Dave Jones
2014-08-07 9:03 ` nohz fail (was: perf related boot hang.) Peter Zijlstra
2014-08-07 13:16 ` Frederic Weisbecker
2014-08-11 20:09 ` Dave Jones [this message]
2014-08-20 20:31 ` Catalin Iacob
2014-08-21 14:56 ` Frederic Weisbecker
2014-08-22 6:01 ` Catalin Iacob
2014-08-22 14:00 ` Dave Jones
2014-09-01 20:14 ` Frederic Weisbecker
2014-09-02 13:41 ` Dave Jones
2014-09-02 18:23 ` Catalin Iacob
2014-09-04 20:07 ` Catalin Iacob
2014-09-04 20:17 ` Frederic Weisbecker
2014-09-04 21:05 ` Catalin Iacob
2014-09-04 21:29 ` Frederic Weisbecker
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=20140811200931.GA18865@redhat.com \
--to=davej@redhat.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.