From: Vince Weaver <vincent.weaver@maine.edu>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Vince Weaver <vincent.weaver@maine.edu>,
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:04:18 -0500 (EST) [thread overview]
Message-ID: <alpine.DEB.2.21.1801111302580.22460@macbook-air> (raw)
In-Reply-To: <20180111170347.GG6176@hirez.programming.kicks-ass.net>
on the same core2 machine I got this which didn't crash the machine (but
the perf_fuzzer process is stuck)
[ 4592.608066] INFO: task systemd-logind:488 blocked for more than 120 seconds.
[ 4592.615159] Not tainted 4.15.0-rc7+ #211
[ 4592.619648] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 4592.627512] systemd-logind D 0 488 1 0x80000006
[ 4592.633039] Call Trace:
[ 4592.635529] ? __schedule+0x35d/0x507
[ 4592.639239] ? usleep_range+0x51/0x51
[ 4592.642948] ? schedule+0x7b/0x84
[ 4592.646310] ? schedule_timeout+0x21/0xc7
[ 4592.650368] ? ttwu_do_wakeup+0x19/0x10d
[ 4592.654339] ? do_wait_for_common+0xfe/0x12f
[ 4592.658653] ? wake_up_q+0x40/0x40
[ 4592.662106] ? wait_for_common+0x35/0x3f
[ 4592.666075] ? __wait_rcu_gp+0xe9/0xfa
[ 4592.669872] ? synchronize_sched+0x3e/0x43
[ 4592.674019] ? call_rcu_bh+0x13/0x13
[ 4592.677641] ? trace_raw_output_rcu_utilization+0x42/0x42
[ 4592.683086] ? evdev_release+0x81/0xcf [evdev]
[ 4592.687578] ? __fput+0xdf/0x18f
[ 4592.690852] ? task_work_run+0x6b/0x7f
[ 4592.694650] ? do_exit+0x4b1/0x994
[ 4592.698103] ? __perf_event_task_sched_out+0x62/0x302
[ 4592.703200] ? do_group_exit+0x3b/0xa9
[ 4592.707000] ? get_signal+0x490/0x50b
[ 4592.710714] ? do_signal+0x23/0x5ea
[ 4592.714249] ? schedule_hrtimeout_range_clock+0x38/0xcf
[ 4592.719521] ? ep_scan_ready_list+0x176/0x195
[ 4592.723926] ? SYSC_epoll_wait+0x2ea/0x39d
[ 4592.728074] ? prepare_exit_to_usermode+0xd1/0x102
[ 4592.732913] ? entry_SYSCALL_64_fastpath+0x6e/0x70
[ 4601.468052] INFO: rcu_sched detected stalls on CPUs/tasks:
[ 4601.473590] 1-...0: (1 GPs behind) idle=74e/140000000000000/0 softirq=139228/139229 fqs=28744
[ 4601.482338] (detected by 0, t=60007 jiffies, g=67462, c=67461, q=1637)
[ 4601.488996] Sending NMI from CPU 0 to CPUs 1:
next prev parent reply other threads:[~2018-01-11 18:04 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-08 16:12 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 [this message]
2018-01-11 18:20 ` Vince Weaver
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.1801111302580.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
all inboxes | Powered by JetHome®