From: Cyrill Gorcunov <gorcunov@gmail.com>
To: Vince Weaver <vincent.weaver@maine.edu>
Cc: Peter Zijlstra <peterz@infradead.org>,
linux-kernel@vger.kernel.org,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Namhyung Kim <namhyung@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Jiri Olsa <jolsa@redhat.com>,
Stephane Eranian <eranian@google.com>
Subject: Re: perf: perf_fuzzer crashes on Pentium 4 systems
Date: Wed, 3 Apr 2019 18:13:18 +0300 [thread overview]
Message-ID: <20190403151317.GG1421@uranus.lan> (raw)
In-Reply-To: <alpine.DEB.2.21.1904031043170.29188@macbook-air>
On Wed, Apr 03, 2019 at 10:59:32AM -0400, Vince Weaver wrote:
>
> so moving this to its own thread.
>
> There was a two-part question asked.
> 1. Can the perf-fuzzer crash a Pentium 4 system
> 2. Does anyone care anymore?
>
> The answer to #1 turns out to be "yes"
> I'm not sure about #2 (but it's telling my p4 test system hadn't been
> turned on in over 3 years).
>
> In any case the perf_fuzzer can crash my p4 system within an hour or so.
> The debugging from this isn't great, I forget what the preferred debug
> things to enable in the kernel hacking menu are.
>
> Here is one crash that just happened:
>
> The instruction at RIP is unhelpfully
> ./arch/x86/include/asm/processor.h:400
> which is
> DECLARE_PER_CPU_FIRST(union irq_stack_union, irq_stack_union) __visible;
>
> Though looking at the assembly it looks like
> p4_pmu_enable_event() is called with NULL as the paramater.
>
Interesting! I'll look more carefully at evening. As far as I remember we
rely on active_mask bit set completely, not sure how it could happen that
we get nil here. Thanks for pointing!
next prev parent reply other threads:[~2019-04-03 15:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-03 14:59 Vince Weaver
2019-04-03 15:13 ` Cyrill Gorcunov [this message]
2019-04-03 19:19 ` Cyrill Gorcunov
2019-04-03 20:31 ` Cyrill Gorcunov
2019-04-04 13:25 ` Vince Weaver
2019-04-04 13:33 ` Cyrill Gorcunov
2019-04-04 16:37 ` Vince Weaver
2019-04-04 16:47 ` Cyrill Gorcunov
2019-04-04 19:01 ` Vince Weaver
2019-04-04 20:20 ` Cyrill Gorcunov
2019-04-07 20:20 ` Cyrill Gorcunov
2019-04-09 16:38 ` Vince Weaver
2019-04-09 17:00 ` 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=20190403151317.GG1421@uranus.lan \
--to=gorcunov@gmail.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=bp@alien8.de \
--cc=eranian@google.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--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
Powered by JetHome