From: Cyrill Gorcunov <gorcunov@gmail.com>
To: Vince Weaver <vincent.weaver@maine.edu>
Cc: linux-kernel@vger.kernel.org,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@kernel.org>, Don Zickus <dzickus@redhat.com>
Subject: Re: perf_fuzzer crash on pentium 4
Date: Thu, 8 May 2014 01:54:30 +0400 [thread overview]
Message-ID: <20140507215430.GH8607@moon> (raw)
In-Reply-To: <20140507215144.GG8607@moon>
On Thu, May 08, 2014 at 01:51:44AM +0400, Cyrill Gorcunov wrote:
>
> > When fuzzing on the p4 *other* things do happen.
> > * at least two warnings pop up almost instantly
> > * eventually the machine will crash in an endless NMI storm
> > * also I managed to get the machine wedged with an unkillable
> > process, sort of like the known problem PeterZ has.
> >
> > The NMI issue is probably the only one that is p4 related, and I do get
> > the NMI warnings on other machines too, it's just the p4 is the only one
> > where it brings down the machine.
>
> Vince, could you please provde more details on that? Is it possible
> to somehow log which events were used by perf?
There were a bug in p4 pmu Don (CC'ed) fixed not that long ago but I fear
not all corner cases might be covered yet.
next prev parent reply other threads:[~2014-05-07 21:54 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-06 15:42 perf_fuzzer crash on pentium 4 Vince Weaver
2014-05-06 15:46 ` Peter Zijlstra
2014-05-06 15:49 ` Cyrill Gorcunov
2014-05-06 16:05 ` Vince Weaver
2014-05-06 16:06 ` Cyrill Gorcunov
2014-05-06 16:11 ` Vince Weaver
2014-05-06 16:16 ` Cyrill Gorcunov
2014-05-06 17:56 ` Vince Weaver
2014-05-06 20:23 ` Cyrill Gorcunov
2014-05-06 21:30 ` Vince Weaver
2014-05-06 21:46 ` Cyrill Gorcunov
2014-05-07 16:46 ` Vince Weaver
2014-05-07 16:49 ` Cyrill Gorcunov
2014-05-07 16:58 ` Cyrill Gorcunov
2014-05-07 17:07 ` Vince Weaver
2014-05-07 18:24 ` Cyrill Gorcunov
2014-05-07 21:17 ` Vince Weaver
2014-05-07 21:51 ` Cyrill Gorcunov
2014-05-07 21:54 ` Cyrill Gorcunov [this message]
2014-05-08 5:14 ` Vince Weaver
2014-05-08 5:40 ` Cyrill Gorcunov
2014-05-08 2:00 ` Don Zickus
2014-05-08 5:38 ` Cyrill Gorcunov
2014-05-08 7:37 ` Cyrill Gorcunov
2014-05-08 7:49 ` Cyrill Gorcunov
2014-05-08 8:02 ` Cyrill Gorcunov
2014-05-09 16:19 ` Vince Weaver
2014-05-09 16:30 ` Cyrill Gorcunov
2014-05-14 20:39 ` Cyrill Gorcunov
2014-05-15 5:31 ` Vince Weaver
2014-05-15 22:09 ` Cyrill Gorcunov
2014-05-28 13:56 ` Pavel Machek
2014-05-28 14:06 ` Cyrill Gorcunov
2014-05-28 15:20 ` Peter Zijlstra
2014-05-28 15:43 ` Cyrill Gorcunov
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=20140507215430.GH8607@moon \
--to=gorcunov@gmail.com \
--cc=dzickus@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox