From: Peter Zijlstra <peterz@infradead.org>
To: Dave Jones <davej@redhat.com>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: perf related boot hang.
Date: Wed, 6 Aug 2014 18:19:34 +0200 [thread overview]
Message-ID: <20140806161934.GF19379@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <20140806143621.GA13832@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1523 bytes --]
On Wed, Aug 06, 2014 at 10:36:21AM -0400, Dave Jones wrote:
> On Linus current tree, when I cold-boot one of my boxes, it locks up
> during boot up with this trace..
>
> Kernel panic - not syncing: Watchdog detected hard LOCKUP on cpu 2
> CPU: 2 PID: 577 Comm: in:imjournal Not tainted 3.16.0+ #33
> ffff880244c06c88 000000008b73013e ffff880244c06bf0 ffffffffb47ee207
> ffffffffb4c51118 ffff880244c06c78 ffffffffb47ebcf8 0000000000000010
> ffff880244c06c88 ffff880244c06c20 000000008b73013e 0000000000000000
> Call Trace:
> <NMI> [<ffffffffb47ee207>] dump_stack+0x4e/0x7a
> [<ffffffffb47ebcf8>] panic+0xd4/0x207
> [<ffffffffb4145448>] watchdog_overflow_callback+0x118/0x120
> [<ffffffffb4186f0e>] __perf_event_overflow+0xae/0x350
> [<ffffffffb4185380>] ? perf_event_task_disable+0xa0/0xa0
> [<ffffffffb401a4ef>] ? x86_perf_event_set_period+0xbf/0x150
> [<ffffffffb4187d34>] perf_event_overflow+0x14/0x20
> [<ffffffffb40203a6>] intel_pmu_handle_irq+0x206/0x410
> [<ffffffffb401939b>] perf_event_nmi_handler+0x2b/0x50
> [<ffffffffb4007b72>] nmi_handle+0xd2/0x390
> [<ffffffffb4007aa5>] ? nmi_handle+0x5/0x390
> [<ffffffffb40d8301>] ? lock_acquired+0x131/0x450
> [<ffffffffb4008062>] default_do_nmi+0x72/0x1c0
>
>
> If I reset it, it then seems to always boot up fine.
Uhm,. cute! And that's the entire stacktrace? It would seem to me there
would be at least a 'task' context below that. CPUs simply do not _only_
run NMI code, and that trace starts at default_do_nmi().
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2014-08-06 16:19 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 [this message]
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
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=20140806161934.GF19379@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=davej@redhat.com \
--cc=linux-kernel@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).