From: Peter Zijlstra <peterz@infradead.org>
To: Vince Weaver <vincent.weaver@maine.edu>
Cc: linux-kernel@vger.kernel.org, Paul Mackerras <paulus@samba.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Steven Rostedt <rostedt@goodmis.org>
Subject: Re: perf: perf_fuzzer triggers instant reboot
Date: Wed, 10 Sep 2014 10:31:36 +0200 [thread overview]
Message-ID: <20140910083136.GP6758@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <alpine.DEB.2.11.1409091352260.15874@vincent-weaver-1.umelst.maine.edu>
[-- Attachment #1: Type: text/plain, Size: 1735 bytes --]
On Tue, Sep 09, 2014 at 01:53:50PM -0400, Vince Weaver wrote:
>
> OK so trying to use ftrace to track this issue, and this happens (on
> core2, 3.17-rc4)
>
> [ 295.992012] PANIC: double fault, error_code: 0x0
> [ 295.992012] CPU: 1 PID: 2916 Comm: trace-cmd Not tainted 3.17.0-rc4+ #82
> [ 295.992012] Hardware name: AOpen DE7000/nMCP7ALPx-DE R1.06 Oct.19.2012, BIOS 080015 10/19/2012
> [ 295.992012] task: ffff8800cb20a800 ti: ffff8800ca30c000 task.ti: ffff8800ca30c000
> [ 295.992012] RIP: 0010:[<ffffffff81037b92>] [<ffffffff81037b92>] perf_trace_x86_exceptions+0x2d/0xb7
> [ 295.992012] RSP: 0018:ffff8800bfffff58 EFLAGS: 00010082
> [ 295.992012] RAX: 0000000000000001 RBX: ffff880037c9f490 RCX: 0000000000000000
> [ 295.992012] RDX: ffff8800c0000098 RSI: ffffe8ffffc81010 RDI: ffffffff81a26600
> [ 295.992012] RBP: ffff8800c0000058 R08: 0000000000044ea5 R09: ffffe8ffffc81010
> [ 295.992012] R10: 0000000000000000 R11: ffff8800ca30fc48 R12: ffff8800c0000098
> [ 295.992012] R13: ffffe8ffffc81010 R14: 0000000000000000 R15: ffffffff81a26600
> [ 295.992012] FS: 00007f4217f82700(0000) GS:ffff88011fc80000(0000) knlGS:0000000000000000
> [ 295.992012] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
> [ 295.992012] CR2: ffff8800bfffff48 CR3: 00000000ca0b9000 CR4: 00000000000407e0
> [ 295.992012] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
> [ 295.992012] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000600
> [ 295.992012] Stack:
> [ 295.992012] PANIC: double fault, error_code: 0x0
>
Sasha reported something from his KVM based fuzzing, maybe that's the
same. But that x86_exceptions thing is interesting, lemme go look at
that first.
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2014-09-10 8:31 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-08 17:47 perf: perf_fuzzer triggers instant reboot Vince Weaver
2014-09-08 18:51 ` Peter Zijlstra
2014-09-08 19:08 ` Vince Weaver
2014-09-09 16:06 ` Vince Weaver
2014-09-09 17:20 ` Vince Weaver
2014-09-09 17:53 ` Vince Weaver
2014-09-10 8:31 ` Peter Zijlstra [this message]
2014-09-10 13:18 ` Vince Weaver
2014-09-10 13:28 ` Peter Zijlstra
2014-09-10 14:01 ` Sasha Levin
2014-09-10 14:30 ` Vince Weaver
2014-09-10 14:33 ` Peter Zijlstra
2014-09-11 13:27 ` Vince Weaver
2014-09-25 4:59 ` Vince Weaver
2014-09-25 16:38 ` Cong Wang
2014-09-28 4:09 ` Sasha Levin
2014-09-29 11:11 ` Peter Zijlstra
2014-09-29 17:01 ` Sasha Levin
2014-09-30 8:54 ` Peter Zijlstra
2014-09-30 17:23 ` Peter Zijlstra
2014-10-01 11:16 ` Sasha Levin
2014-10-02 15:06 ` Vince Weaver
2014-10-02 16:06 ` Vince Weaver
2014-10-03 5:27 ` [tip:perf/urgent] perf: Fix unclone_ctx() vs. locking tip-bot for Peter Zijlstra
2014-09-29 5:21 ` perf: perf_fuzzer triggers instant reboot Vince Weaver
2014-09-30 17:58 ` Cong Wang
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=20140910083136.GP6758@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=acme@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=paulus@samba.org \
--cc=rostedt@goodmis.org \
--cc=vincent.weaver@maine.edu \
/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.