All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cyrill Gorcunov <gorcunov@gmail.com>
To: Vince Weaver <vincent.weaver@maine.edu>
Cc: Don Zickus <dzickus@redhat.com>,
	linux-kernel@vger.kernel.org,
	Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@kernel.org>
Subject: Re: perf_fuzzer crash on pentium 4
Date: Fri, 9 May 2014 20:30:38 +0400	[thread overview]
Message-ID: <20140509163038.GH320@moon.sw.swsoft.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1405091211430.13652@vincent-weaver-1.umelst.maine.edu>

On Fri, May 09, 2014 at 12:19:49PM -0400, Vince Weaver wrote:
> On Thu, 8 May 2014, Cyrill Gorcunov wrote:
> > 
> > Updated.
> > ---
> >  arch/x86/kernel/cpu/perf_event_p4.c |   67 ++++++++++++++++--------------------
> >  1 file changed, 30 insertions(+), 37 deletions(-)
> 
> I tried this patch, and even though it seemed to fix one of the NMI storms 
> I was experiencing I've managed to trigger again using a different random 
> seed.

Thanks a lot for help in testing, Vince! I think the patch would be still
needed so I will prepare normal change log explaining what has been fixed
in the patch.

> I've been trying to track down a trace of what is triggering things, but 
> this is very difficult as the full log isn't making it to the serial 
> console, even when I fsync() stdout.

I see. Need to think. Maybe something comes to mind. Debuggin it is really
a hard job :/ I've been promised to get access to real p4 machine next
week, maybe I find something.

> Maybe related, but the following messages tend to happen a lot while 
> fuzzing, and always happen before the fuzzing that eventually locks up:
> 
> The warnings are for
> 	if (WARN_ON_ONCE(!(event->hw.state & PERF_HES_STOPPED)))
> and
> 	WARN_ON_ONCE(hwc->state & PERF_HES_STOPPED);	

Thanks for info, Vince! Look, every time you start perf_fuzzer (note,
I didn't read its code yet, that's why I'm asking) -- does it log
which events are passed to kernel from userspace? Btw, do you run
kernel with nmi-watchdog turned on?

  reply	other threads:[~2014-05-09 16:30 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
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 [this message]
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=20140509163038.GH320@moon.sw.swsoft.com \
    --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 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.