From: Peter Zijlstra <peterz@infradead.org>
To: Cyrill Gorcunov <gorcunov@gmail.com>
Cc: Pavel Machek <pavel@ucw.cz>,
Vince Weaver <vincent.weaver@maine.edu>,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@kernel.org>
Subject: Re: perf_fuzzer crash on pentium 4
Date: Wed, 28 May 2014 17:20:11 +0200 [thread overview]
Message-ID: <20140528152011.GX11096@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <20140528140632.GH2570@moon>
[-- Attachment #1: Type: text/plain, Size: 854 bytes --]
On Wed, May 28, 2014 at 06:06:32PM +0400, Cyrill Gorcunov wrote:
> On Wed, May 28, 2014 at 03:56:17PM +0200, Pavel Machek wrote:
> > Hi!
> >
> > > So just to be difficult I fired up the perf_fuzzer on a Pentium 4 machine.
> > >
> > > It crashes more or less instantly (sorry for the line wrapping,
> > > just got the serial console hooked up and don't have minicom configured
> > > right yet).
> > >
> > > this is 3.15-rc4 with the anti-memory corruption patch applied.
> > >
> > > [ 67.872274] BUG: unable to handle kernel NULL pointer dereference at 00000004
> > > [ 67.876146] IP: [<ffffffff81013df2>] p4_pmu_schedule_events+0xa5/0x331
> >
> > Pentium 4 's were not 64bit, were they?
>
> Not all, but there were 64bit varians (Xeons iirc).
http://en.wikipedia.org/wiki/Pentium_d
consumer netburst chip with x86_64.
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2014-05-28 15:20 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-06 15:42 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
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 [this message]
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=20140528152011.GX11096@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=gorcunov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=pavel@ucw.cz \
--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