From: Thorsten Leemhuis <regressions@leemhuis.info>
To: "regressions@lists.linux.dev" <regressions@lists.linux.dev>
Subject: Re: DEAD callback error for CPU, WARNING: CPU: 3 PID: 1134 at kernel/cpu.c:1163 _cpu_down+0x20a/0x3a0
Date: Mon, 15 Nov 2021 20:35:04 +0100 [thread overview]
Message-ID: <03dd4dd9-344c-6f85-74b1-c361187cddaf@leemhuis.info> (raw)
In-Reply-To: <d37ce254-e3b6-760d-42a0-3529b8b4ea6d@leemhuis.info>
On 15.11.21 15:23, Thorsten Leemhuis wrote:
> On 07.11.21 18:38, Thorsten Leemhuis wrote:
>> On 07.11.21 12:59, 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
>>> […]
>>> See bug report https://bugzilla.kernel.org/show_bug.cgi?id=214955
>>
>> #regzbot ^introduced: v5.13..
>> #regzbot link: https://bugzilla.kernel.org/show_bug.cgi?id=214955
>> Bugzilla Ticket
>> #regzbot activity-ignore
>
> #regzbot ^introduced: 7a89d7eacf8e84f2afb94db5ae9d9f9faa93f01c
> #regzbot monitor:
> https://lore.kernel.org/lkml/20211108062345.273855-1-daniel.lezcano@linaro.org/
> #rezbot fixed-by: 4d1cd1443db3d5605ebcde8672869b1944ade92d
Presented by the "stupid typos department":
#regzbot fixed-by: 4d1cd1443db3d5605ebcde8672869b1944ade92d
#regzbot ignore-activity
prev parent reply other threads:[~2021-11-15 19:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <f6a0f4be-ad53-489c-0036-09dead99f368@gmail.com>
2021-11-07 12:00 ` Fwd: DEAD callback error for CPU, WARNING: CPU: 3 PID: 1134 at kernel/cpu.c:1163 _cpu_down+0x20a/0x3a0 Colin King (gmail)
2021-11-07 17:29 ` Thorsten Leemhuis
2021-11-07 17:35 ` Thorsten Leemhuis
2021-11-07 17:38 ` Thorsten Leemhuis
2021-11-15 14:23 ` Thorsten Leemhuis
2021-11-15 19:35 ` Thorsten Leemhuis [this message]
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=03dd4dd9-344c-6f85-74b1-c361187cddaf@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=regressions@lists.linux.dev \
/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).