From: "Paul E. McKenney" <paulmck@kernel.org>
To: Tejun Heo <tj@kernel.org>
Cc: jiangshanlai@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: Workqueues splat due to ending up on wrong CPU
Date: Fri, 29 Nov 2019 07:58:50 -0800 [thread overview]
Message-ID: <20191129155850.GA17002@paulmck-ThinkPad-P72> (raw)
In-Reply-To: <20191128161823.GA24667@paulmck-ThinkPad-P72>
On Thu, Nov 28, 2019 at 08:18:23AM -0800, Paul E. McKenney wrote:
> On Wed, Nov 27, 2019 at 07:50:27AM -0800, Paul E. McKenney wrote:
[ . . . ]
> And still -ENOREPRODUCE. It did happen on this system with
> hyperthreading, so the next step is to make rcutorture better tolerate
> very large hyperthreaded systems and try again.
[ . . . ]
And hyperthreading seems to have done the trick! One splat thus far,
shown below. The run should complete this evening, Pacific Time.
Thanx, Paul
------------------------------------------------------------------------
[29139.777628] ------------[ cut here ]------------
[29139.779342] expected on cpu 0 but on cpu 2, pool 0, workfn=sync_rcu_exp_select_node_cpus
[29139.780564] WARNING: CPU: 2 PID: 4 at kernel/workqueue.c:2186 process_one_work+0x53b/0x550
[29139.781854] Modules linked in:
[29139.782376] CPU: 2 PID: 4 Comm: rcu_par_gp Not tainted 5.4.0-rc1+ #35
[29139.783418] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.11.0-2.el7 04/01/2014
[29139.784701] Workqueue: 0x0 (rcu_par_gp)
[29139.785308] RIP: 0010:process_one_work+0x53b/0x550
[29139.786058] Code: 99 0f 0b eb d2 c6 05 3c dd 6d 01 01 65 8b 15 64 78 b8 74 41 8b 4c 24 40 4c 8b 43 18 48 c7 c7 08 72 6c 8c 31 c0 e8 55 08 fe ff <0f> 0b e9 53 fb ff ff 0f 1f 40 00 66 2e 0f 1f 84 00 00 00 00 00 41
[29139.788978] RSP: 0000:ffff91d7c002fe30 EFLAGS: 00010086
[29139.789766] RAX: 0000000000000000 RBX: ffffffff8ca65f68 RCX: ffff91d7c002fcdc
[29139.790851] RDX: 0000000000000002 RSI: ffffffff8ca627d8 RDI: 00000000ffffffff
[29139.791982] RBP: ffff8d369ec95600 R08: 0000000000000001 R09: 0000000000000000
[29139.793129] R10: 757063206e6f2074 R11: 7562203020757063 R12: ffff8d369f228a80
[29139.794219] R13: ffff8d369f22d400 R14: 0000000000000000 R15: ffff8d369ec95600
[29139.795316] FS: 0000000000000000(0000) GS:ffff8d369f280000(0000) knlGS:0000000000000000
[29139.796596] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[29139.797509] CR2: 0000000000000148 CR3: 000000001a81e000 CR4: 00000000000006e0
[29139.798625] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[29139.799752] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
[29139.801185] Call Trace:
[29139.801765] rescuer_thread+0x1b5/0x2e0
[29139.802544] kthread+0xf3/0x130
[29139.803054] ? worker_thread+0x3c0/0x3c0
[29139.803664] ? kthread_cancel_delayed_work_sync+0x10/0x10
[29139.804730] ret_from_fork+0x35/0x40
[29139.805338] ---[ end trace a630d585ddfc6bd2 ]---
next prev parent reply other threads:[~2019-11-29 15:58 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-25 23:03 Paul E. McKenney
2019-11-26 18:33 ` Tejun Heo
2019-11-26 22:05 ` Paul E. McKenney
2019-11-27 15:50 ` Paul E. McKenney
2019-11-28 16:18 ` Paul E. McKenney
2019-11-29 15:58 ` Paul E. McKenney [this message]
2019-12-02 1:55 ` Paul E. McKenney
2019-12-02 20:13 ` Tejun Heo
2019-12-02 23:39 ` Paul E. McKenney
2019-12-03 10:00 ` Peter Zijlstra
2019-12-03 17:45 ` Paul E. McKenney
2019-12-03 18:13 ` Tejun Heo
2019-12-03 9:55 ` Peter Zijlstra
2019-12-03 10:06 ` Peter Zijlstra
2019-12-03 15:42 ` Tejun Heo
2019-12-03 16:04 ` Paul E. McKenney
2019-12-04 20:11 ` Paul E. McKenney
2019-12-05 10:29 ` Peter Zijlstra
2019-12-05 10:32 ` Peter Zijlstra
2019-12-05 14:48 ` Paul E. McKenney
2019-12-06 3:19 ` Paul E. McKenney
2019-12-06 18:52 ` Paul E. McKenney
2019-12-06 22:00 ` Paul E. McKenney
2019-12-09 18:59 ` Paul E. McKenney
2019-12-10 9:08 ` Peter Zijlstra
2019-12-10 22:56 ` Paul E. McKenney
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=20191129155850.GA17002@paulmck-ThinkPad-P72 \
--to=paulmck@kernel.org \
--cc=jiangshanlai@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@kernel.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
Powered by JetHome