From: Peter Zijlstra <peterz@infradead.org>
To: "Colin King (gmail)" <colin.i.king@googlemail.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: DEAD callback error for CPU, WARNING: CPU: 3 PID: 1134 at kernel/cpu.c:1163 _cpu_down+0x20a/0x3a0
Date: Mon, 8 Nov 2021 09:12:00 +0100 [thread overview]
Message-ID: <YYjb0OZxlDJpA6wr@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <f6a0f4be-ad53-489c-0036-09dead99f368@gmail.com>
On Sun, Nov 07, 2021 at 11:59:17AM +0000, Colin King (gmail) wrote:
> On a SMP system in a VM, a deadlock callback error can be reproduced with
> 5.15, tested from head at commit d4439a1189f93d0ac1eaf0197db8e6b3e197d5c7
>
> Didn't see this issue on 5.13
>
> How to reproduce:
>
> git clone https://github.com/ColinIanKing/stress-ng
> cd stress-ng
> make -j $(nproc)
> sudo ./stress-ng --cpu-online 0 -t 15 --pathological
>
> Tested on a 8 thread virtual machine, 4MB of memory.
>
> [ 2239.378724] smpboot: CPU 6 is now offline
> [ 2239.379443] smpboot: Booting Node 0 Processor 6 APIC 0x6
> [ 2239.380169] kvm-clock: cpu 6, msr 79201181, secondary cpu clock
> [ 2239.401652] ------------[ cut here ]------------
> [ 2239.401658] DEAD callback error for CPU6
> [ 2239.401721] WARNING: CPU: 3 PID: 1134 at kernel/cpu.c:1163
> _cpu_down+0x20a/0x3a0
Can you do the same with whatever magic is required to get the
pr_debug() output from cpuhp_down_callbacks() included?
next prev parent reply other threads:[~2021-11-08 8:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-07 11:59 DEAD callback error for CPU, WARNING: CPU: 3 PID: 1134 at kernel/cpu.c:1163 _cpu_down+0x20a/0x3a0 Colin King (gmail)
2021-11-08 8:12 ` Peter Zijlstra [this message]
2021-11-08 22:25 ` Colin King (gmail)
2021-11-14 10:32 ` Josef Johansson
2021-11-14 20:00 ` Josef Johansson
2021-11-14 22:20 ` Daniel Lezcano
2021-11-15 8:30 ` Josef Johansson
2021-11-15 12:02 ` Colin King (gmail)
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=YYjb0OZxlDJpA6wr@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=colin.i.king@googlemail.com \
--cc=linux-kernel@vger.kernel.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).