From: Catalin Iacob <iacobcatalin@gmail.com>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: Dave Jones <davej@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Catalin Iacob <iacobcatalin@gmail.com>
Subject: Re: nohz fail (was: perf related boot hang.)
Date: Wed, 20 Aug 2014 22:31:31 +0200 [thread overview]
Message-ID: <1408566691-3023-1-git-send-email-iacobcatalin@gmail.com> (raw)
In-Reply-To: <20140811200931.GA18865@redhat.com>
I've also just hit what seems to be the same panic in 3.17-rc1 (ignore the 1
local patch, it's an unrelated change in a comment) twice in less than 1
hour. Hitting this twice in a short amount of time seems to be proof that the
3.17 merge window made it trigger more often. Both times I was running a grep
over a Firefox build tree which was taking a long time.
The stacktraces are slightly different but both have the "cancel timer from a
timer, followed by nmi" pattern. Pictures of the 2 stacktraces:
https://drive.google.com/file/d/0B_fRjDygGZSNY0RIc2dyYTExTjg/edit?usp=sharing
https://drive.google.com/file/d/0B_fRjDygGZSNS1pSWFkteURrOTQ/edit?usp=sharing
next prev parent reply other threads:[~2014-08-20 20:32 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
2014-08-20 20:31 ` Catalin Iacob [this message]
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=1408566691-3023-1-git-send-email-iacobcatalin@gmail.com \
--to=iacobcatalin@gmail.com \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome