From: Will Deacon <will.deacon@arm.com>
To: Drew Richardson <drew.richardson@arm.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>, Arnaldo <acme@redhat.com>,
Pawel Moll <Pawel.Moll@arm.com>,
Wade Cherry <Wade.Cherry@arm.com>
Subject: Re: Perf Oops on 3.14-rc2
Date: Tue, 18 Feb 2014 10:18:31 +0000 [thread overview]
Message-ID: <20140218101831.GB4178@mudshark.cambridge.arm.com> (raw)
In-Reply-To: <20140210221758.GB11542@dreric01-Precision-T1600>
On Mon, Feb 10, 2014 at 10:17:59PM +0000, Drew Richardson wrote:
> While adding CPU on/offlining support during perf captures I get an
> Oops both on ARM as well as my desktop x86_64. Below is a small
> program that duplicates the issue.
[...]
FWIW I can reproduce this easily with -rc3 on my x86 laptop running
hackbench in parallel with a tweaked version of your test (using
_SC_NPROCESSORS_ONLN instead of _SC_NPROCESSORS_CONF and hotplugging off
both CPU2 and CPU3).
I've included part of the log below, but I also saw a WARN which I
unfortunately only managed to get a photo of.
http://www.willdeacon.ukfsn.org/bitbucket/oopsen/x86/
Will
--->8
BUG: unable to handle kernel NULL pointer dereference at 0000000000000078
IP: [<ffffffff811195fe>] perf_event_aux_ctx+0x4e/0x80
PGD 0
Oops: 0000 [#1608] SMP
Modules linked in:
CPU: 1 PID: 2270 Comm: hackbench Tainted: G D W 3.14.0-rc3 #2
Hardware name: System76, Inc. Lemur Ultra/Lemur Ultra, BIOS 4.6.4 10/07/2011
task: ffff8800d1ec6180 ti: ffff8800d1fb4000 task.ti: ffff8800d1fb4000
RIP: 0010:[<ffffffff811195fe>] [<ffffffff811195fe>] perf_event_aux_ctx+0x4e/0x80
RSP: 0018:ffff8800d1fb5d98 EFLAGS: 00010207
RAX: 0000000000000000 RBX: 0000000000000000 RCX: 00000000000fffd8
RDX: 0000000000000001 RSI: 00000000000fffd8 RDI: ffff8800d1fb5c98
RBP: ffff88021fa55e60 R08: 00000000000fffd8 R09: 00000000df1aa3e9
R10: ffffffff8108790e R11: ffffea000347dec0 R12: ffff8800d1fb5e18
R13: ffffffff8111f580 R14: ffff8800d1fb5e18 R15: ffff8800d1ec6180
FS: 0000000000000000(0000) GS:ffff88021fa40000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000078 CR3: 0000000001ad5000 CR4: 00000000000407e0
Stack:
00007f8618b68cc0 0000000000000000 ffff8800d1ec6180 ffffffff81ae17e0
0000000000000000 ffffffff8111f580 ffff8800d1ec6180 ffffffff811196cb
0000000000000064 ffffffff81ae17e0 0000000000000004 0000000000000000
Call Trace:
[<ffffffff8111f580>] ? perf_event_task_tick+0xe0/0xe0
[<ffffffff811196cb>] ? perf_event_aux+0x9b/0xd0
[<ffffffff81119e48>] ? perf_event_task+0x78/0xa0
[<ffffffff81122c80>] ? perf_event_exit_task+0xb0/0x200
[<ffffffff81087928>] ? do_exit+0x2b8/0xa00
[<ffffffff8117798c>] ? vfs_write+0x17c/0x1e0
[<ffffffff81088178>] ? do_group_exit+0x38/0xa0
[<ffffffff810881f2>] ? SyS_exit_group+0x12/0x20
[<ffffffff817be922>] ? system_call_fastpath+0x16/0x1b
Code: 39 eb 75 27 eb 47 0f 1f 80 00 00 00 00 65 8b 14 25 1c b0 00 00 39 d0 74 26 48 8b 03 48 89 44 24 08 48 8b 5c 24 08 48 39 eb 74 22 <44> 8b 4b 78 45 85 c9 78 e5 8b 83 3c 02 00 00 83 f8 ff 75 ce 4c
RIP [<ffffffff811195fe>] perf_event_aux_ctx+0x4e/0x80
RSP <ffff8800d1fb5d98>
CR2: 0000000000000078
---[ end trace 0e9345db7c92edc0 ]---
Fixing recursive fault but reboot is needed!
next prev parent reply other threads:[~2014-02-18 10:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-10 22:17 Drew Richardson
2014-02-18 10:18 ` Will Deacon [this message]
2014-02-18 10:52 ` Peter Zijlstra
2014-02-18 11:03 ` Will Deacon
2014-02-18 10:54 ` Peter Zijlstra
2014-02-18 11:01 ` Will Deacon
2014-02-19 16:28 ` Peter Zijlstra
2014-02-19 18:03 ` Stephane Eranian
2014-02-19 18:36 ` Peter Zijlstra
2014-02-19 19:59 ` Stephane Eranian
2014-02-19 20:24 ` Peter Zijlstra
2014-02-19 19:37 ` Drew Richardson
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=20140218101831.GB4178@mudshark.cambridge.arm.com \
--to=will.deacon@arm.com \
--cc=Pawel.Moll@arm.com \
--cc=Wade.Cherry@arm.com \
--cc=acme@redhat.com \
--cc=drew.richardson@arm.com \
--cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®