From: Valentin Schneider <valentin.schneider@arm.com>
To: Oleksandr Natalenko <oleksandr@natalenko.name>
Cc: linux-rt-users@vger.kernel.org, linux-kernel@vger.kernel.org,
tglx@linutronix.de, peterz@infradead.org, rostedt@goodmis.org
Subject: Re: WARNING at kernel/sched/core.c:2013 migration_cpu_stop+0x2e3/0x330
Date: Mon, 16 Nov 2020 10:31:12 +0000 [thread overview]
Message-ID: <jhjzh3hwq33.mognet@arm.com> (raw)
In-Reply-To: <41d6aca71c6a52df8437cdb7b4a1b1c4@natalenko.name>
On 16/11/20 10:27, Oleksandr Natalenko wrote:
> Hi.
[...]
> Not sure whether the check is legitimate, but FWIW I've managed to put a
> test task [1] (it spawns a lot of threads and applies affinity) into a
> permanent unkillable D state here:
>
> ```
> [<0>] affine_move_task+0x2d3/0x620
> [<0>] __set_cpus_allowed_ptr+0x164/0x210
> [<0>] sched_setaffinity+0x21a/0x300
> [<0>] __x64_sys_sched_setaffinity+0x8c/0xc0
> [<0>] do_syscall_64+0x33/0x40
> [<0>] entry_SYSCALL_64_after_hwframe+0x44/0xa9
> ```
[...]
>
> I'm not positive about this being directly related to the original
> report, but I think it is still worth mentioning.
>
Aye, thanks, that one should be fixed by:
https://lore.kernel.org/r/20201113112414.2569-1-valentin.schneider@arm.com
> Thanks.
>
> [1] https://gitlab.com/post-factum/burn_scheduler
next prev parent reply other threads:[~2020-11-16 11:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-15 22:32 WARNING at kernel/sched/core.c:2013 migration_cpu_stop+0x2e3/0x330 Oleksandr Natalenko
2020-11-16 10:00 ` Valentin Schneider
2020-11-16 10:27 ` Oleksandr Natalenko
2020-11-16 10:31 ` Valentin Schneider [this message]
2020-11-16 10:32 ` Oleksandr Natalenko
2020-11-16 10:31 ` Oleksandr Natalenko
2020-11-17 11:06 ` Peter Zijlstra
2020-11-17 11:29 ` Valentin Schneider
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=jhjzh3hwq33.mognet@arm.com \
--to=valentin.schneider@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=oleksandr@natalenko.name \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.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