From: Vince Weaver <vincent.weaver@maine.edu>
To: linux-kernel@vger.kernel.org
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@kernel.org>,
Cyrill Gorcunov <gorcunov@openvz.org>
Subject: perf_fuzzer crash on pentium 4
Date: Tue, 6 May 2014 11:42:58 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.2.10.1405061137560.3220@vincent-weaver-1.umelst.maine.edu> (raw)
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
[ 67.876146] PGD 3cea7067 PUD 3cea8067 PMD 0
[ 67.876146] Oops: 0000 [#1] SMP
[ 67.876146] Modules linked in: loop snd_hda_codec_analog snd_hda_codec_genern
[ 67.876146] CPU: 0 PID: 2192 Comm: perf_fuzzer Tainted: G W 3.15.1
[ 67.876146] Hardware name: LENOVO 88088NU/LENOVO, BIOS 2JKT37AUS 07/12/2007
[ 67.876146] task: ffff88003c0610d0 ti: ffff88003c062000 task.ti: ffff88003c00
[ 67.876146] RIP: 0010:[<ffffffff81013df2>] [<ffffffff81013df2>] p4_pmu_sche1
[ 67.876146] RSP: 0000:ffff88003f403d60 EFLAGS: 00010046
[ 67.876146] RAX: 0000000000000000 RBX: 0000000000000001 RCX: 00000000000003a2
[ 67.876146] RDX: ffff88003c0610d0 RSI: 0000000000000003 RDI: 0000000000000000
[ 67.876146] RBP: 0000000000000000 R08: 0000000000000003 R09: 0000000000000000
[ 67.876146] R10: 00007f156ab399d0 R11: 0000000000000246 R12: 0000000000000000
[ 67.876146] R13: 0000000000000002 R14: ffff88003f403de8 R15: ffff88003b766000
[ 67.876146] FS: 00007f156ab39700(0000) GS:ffff88003f400000(0000) knlGS:00000
[ 67.876146] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
[ 67.876146] CR2: 0000000000000004 CR3: 000000003c598000 CR4: 00000000000007f0
[ 67.876146] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[ 67.876146] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000600
[ 67.876146] Stack:
[ 67.876146] 0000000000000002 0000000000000000 ffff88003f40bb50 0000000100003
[ 67.876146] 0000000000000003 3000020c0403c200 0000000000000001 0000000000004
[ 67.876146] 0000000000000000 ffff88003f40bb50 ffff88003f403de8 0000000000003
[ 67.876146] Call Trace:
[ 67.876146] <IRQ>
[ 67.876146] [<ffffffff810104c7>] ? x86_pmu_commit_txn+0x45/0x8b
[ 67.876146] [<ffffffff8104d6c6>] ? search_exception_tables+0x1d/0x2d
[ 67.876146] [<ffffffff8102cc65>] ? fixup_exception+0x10/0x53
[ 67.876146] [<ffffffff813e65dd>] ? do_general_protection+0x30/0x12d
[ 67.876146] [<ffffffff813e6082>] ? general_protection+0x22/0x30
[ 67.876146] [<ffffffff810ba5ef>] ? event_sched_in+0x129/0x136
[ 67.876146] [<ffffffff810ba68a>] ? group_sched_in+0x8e/0x138
[ 67.876146] [<ffffffff810bb1af>] ? __perf_event_enable+0xea/0x128
[ 67.876146] [<ffffffff810b76c0>] ? remote_function+0x13/0x3b
[ 67.876146] [<ffffffff81084fb7>] ? generic_smp_call_function_single_interrua
[ 67.876146] [<ffffffff810227db>] ? smp_call_function_single_interrupt+0xf/0c
[ 67.876146] [<ffffffff813ebbba>] ? call_function_single_interrupt+0x6a/0x70
[ 67.876146] <EOI>
[ 67.876146] Code: 08 49 8b 97 28 01 00 00 48 89 d5 48 c1 ed 39 83 e5 3f 83 f
[ 67.876146] RIP [<ffffffff81013df2>] p4_pmu_schedule_events+0xa5/0x331
[ 67.876146] RSP <ffff88003f403d60>
[ 67.876146] CR2: 0000000000000004
[ 67.876146] ---[ end trace a88368266e292dfa ]---
[ 67.876146] Kernel panic - not syncing: Fatal exception in interrupt
[ 67.876146] Kernel Offset: 0x0 from 0xffffffff81000000 (relocation range: 0x)
[ 67.876146] drm_kms_helper: panic occurred, switching back to text console
[ 67.876146] ---[ end Kernel panic - not syncing: Fatal exception in interrupt
next reply other threads:[~2014-05-06 15:39 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-06 15:42 Vince Weaver [this message]
2014-05-06 15:46 ` perf_fuzzer crash on pentium 4 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
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=alpine.DEB.2.10.1405061137560.3220@vincent-weaver-1.umelst.maine.edu \
--to=vincent.weaver@maine.edu \
--cc=gorcunov@openvz.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
/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.