From: Vince Weaver <vincent.weaver@maine.edu>
To: Vince Weaver <vincent.weaver@maine.edu>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@kernel.org>,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: perf: perf_fuzzer quickly locks up on 4.15-rc7
Date: Thu, 11 Jan 2018 13:20:10 -0500 (EST) [thread overview]
Message-ID: <alpine.DEB.2.21.1801111318060.22460@macbook-air> (raw)
In-Reply-To: <alpine.DEB.2.21.1801111302580.22460@macbook-air>
On Thu, 11 Jan 2018, Vince Weaver wrote:
> on the same core2 machine I got this which didn't crash the machine (but
> the perf_fuzzer process is stuck)
also got this one:
Cannot open /sys/kernel/tracing/kprobe_events
[ 408.159243] watchdog: BUG: soft lockup - CPU#1 stuck for 23s! [perf_fuzzer:22326]
[ 408.193102] CPU: 1 PID: 22326 Comm: perf_fuzzer Tainted: G D 4.15.0-rc7+ #211
[ 408.201507] Hardware name: AOpen DE7000/nMCP7ALPx-DE R1.06 Oct.19.2012, BIOS 080015 10/19/2012
[ 408.210436] RIP: 0010:smp_call_function_single+0xac/0xc3
[ 408.215797] RSP: 0018:ffffc90008307de0 EFLAGS: 00000202 ORIG_RAX: ffffffffffffff11
[ 408.223421] RAX: 0000000000000000 RBX: ffffc90008307de0 RCX: 0000000000000000
[ 408.230602] RDX: 0000000000000001 RSI: 00000000000008fb RDI: 0000000000000300
[ 408.237777] RBP: ffffc90008307e30 R08: fffffffc3146e801 R09: 0000000000000003
[ 408.244957] R10: 0000000000000000 R11: ffff88011a98af80 R12: 0000000000000001
[ 408.252137] R13: 0000000000000000 R14: 00007f05bdefb104 R15: 000000000000001f
[ 408.259318] FS: 00007f05be10d700(0000) GS:ffff88011fc80000(0000) knlGS:0000000000000000
[ 408.267462] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 408.273258] CR2: 0000000000735980 CR3: 000000011a31a000 CR4: 00000000000407e0
[ 408.280439] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[ 408.287620] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000600
[ 408.294798] Call Trace:
[ 408.297300] ? perf_event_sysfs_show+0x1d/0x1d
[ 408.301792] ? ctx_resched+0x84/0x84
[ 408.305418] ? task_function_call+0x35/0x48
[ 408.309649] task_function_call+0x35/0x48
[ 408.313706] ? perf_ctx_lock+0x1e/0x1e
[ 408.317506] event_function_call+0x60/0xa5
[ 408.321652] ? ctx_resched+0x84/0x84
[ 408.325278] ? _perf_event_disable+0x3e/0x3e
[ 408.329598] perf_event_for_each_child+0x4d/0x6b
[ 408.334267] perf_event_task_enable+0x66/0x9a
[ 408.338673] SyS_prctl+0x152/0x3ca
[ 408.342126] ? SyS_write+0x69/0x78
[ 408.345581] entry_SYSCALL_64_fastpath+0x17/0x70
[ 408.350248] RIP: 0033:0x7f05bdc3ee7a
[ 408.353872] RSP: 002b:00007ffc80e425c8 EFLAGS: 00000202
[ 408.353874] Code: 01 74 04 f3 90 eb f4 83 48 18 01 48 89 d1 44 89 d7 48 89 f2 48 89 de e8 c9 fe ff ff 45 85 e4 74 12 8b 53 18 80 e2 01 74 04 f3 90 <eb> f4 eb 04 0f ff eb ad 48 83 c4 38 5b 41 5a 41 5c 5d 49 8d 62
next prev parent reply other threads:[~2018-01-11 18:20 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-08 16:12 perf: perf_fuzzer quickly locks up on 4.15-rc7 Vince Weaver
2018-01-08 17:30 ` Ingo Molnar
2018-01-08 20:29 ` Vince Weaver
2018-01-09 10:25 ` Peter Zijlstra
2018-01-09 13:26 ` Peter Zijlstra
2018-01-09 13:36 ` Peter Zijlstra
2018-01-09 13:44 ` Vince Weaver
2018-01-09 15:12 ` Peter Zijlstra
2018-01-09 15:24 ` Vince Weaver
2018-01-09 15:33 ` Peter Zijlstra
2018-01-09 15:56 ` Vince Weaver
2018-01-09 16:05 ` Peter Zijlstra
2018-01-09 17:07 ` Josh Poimboeuf
2018-01-11 5:25 ` Josh Poimboeuf
2018-01-11 19:00 ` Vince Weaver
2018-01-11 19:21 ` Josh Poimboeuf
2018-01-11 19:50 ` Peter Zijlstra
2018-01-11 19:57 ` Vince Weaver
2018-01-11 20:43 ` Vince Weaver
2018-05-01 13:29 ` perf: fuzzer causes stack going in wrong direction warnings Vince Weaver
2018-05-01 13:58 ` Josh Poimboeuf
2018-05-01 19:59 ` Vince Weaver
2018-05-01 22:04 ` Josh Poimboeuf
2018-05-02 20:50 ` Josh Poimboeuf
2018-05-04 14:35 ` Vince Weaver
2018-05-04 16:25 ` Josh Poimboeuf
2018-05-04 17:00 ` Vince Weaver
2018-05-05 15:38 ` Vince Weaver
2018-05-05 18:29 ` Josh Poimboeuf
2018-05-06 23:49 ` Josh Poimboeuf
2018-05-10 13:48 ` Peter Zijlstra
2018-05-10 14:27 ` Josh Poimboeuf
2018-05-10 23:16 ` Josh Poimboeuf
2018-01-09 16:16 ` perf: perf_fuzzer quickly locks up on 4.15-rc7 Ingo Molnar
2018-01-09 16:20 ` Peter Zijlstra
2018-01-09 17:18 ` Vince Weaver
2018-01-10 15:28 ` Vince Weaver
2018-01-09 16:14 ` Peter Zijlstra
2018-01-09 17:53 ` Steven Rostedt
2018-01-09 18:02 ` Peter Zijlstra
2018-01-09 18:09 ` Steven Rostedt
2018-01-09 19:53 ` Peter Zijlstra
2018-01-11 9:13 ` Peter Zijlstra
2018-01-11 15:26 ` Vince Weaver
2018-01-11 15:38 ` Peter Zijlstra
2018-01-11 16:41 ` Vince Weaver
2018-01-11 16:58 ` Vince Weaver
2018-01-11 17:03 ` Peter Zijlstra
2018-01-11 18:04 ` Vince Weaver
2018-01-11 18:20 ` Vince Weaver [this message]
2018-01-11 19:01 ` Peter Zijlstra
2018-01-11 19:11 ` Peter Zijlstra
2018-01-11 20:15 ` Vince Weaver
2018-01-11 20:40 ` Vince Weaver
2018-01-11 20:57 ` Peter Zijlstra
2018-01-12 19:48 ` Vince Weaver
2018-01-11 20:42 ` Peter Zijlstra
2018-01-11 15:29 ` Peter Zijlstra
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.21.1801111318060.22460@macbook-air \
--to=vincent.weaver@maine.edu \
--cc=acme@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).