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>
Subject: Re: perf: perf_fuzzer triggers instant reboot
Date: Mon, 8 Sep 2014 20:51:15 +0200 [thread overview]
Message-ID: <20140908185115.GI6758@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <alpine.DEB.2.11.1409081343270.29974@vincent-weaver-1.umelst.maine.edu>
[-- Attachment #1: Type: text/plain, Size: 250 bytes --]
On Mon, Sep 08, 2014 at 01:47:11PM -0400, Vince Weaver wrote:
> Hello
>
> so I finally had time to run my perf_fuzzer again and it has rapidly
> turned up an alarming crash that instant-reboots my core2 test machine.
Urgh, of course :/
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2014-09-08 18:51 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 [this message]
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
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=20140908185115.GI6758@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=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.