public inbox for linux-rt-devel@lists.linux.dev
 help / color / mirror / Atom feed
From: Bert Karwatzki <spasswolf@web.de>
To: Tejun Heo <tj@kernel.org>
Cc: Bert Karwatzki <spasswolf@web.de>,
	Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
	Thomas Gleixner <tglx@linutronix.de>,
	calvin@wbinvd.org, dschatzberg@meta.com, peterz@infradead.org,
	linux-kernel@vger.kernel.org, linux-rt-devel@lists.linux.dev
Subject: ~90s reboot delay with v6.19 and PREEMPT_RT
Date: Thu, 19 Feb 2026 17:46:47 +0100	[thread overview]
Message-ID: <20260219164648.3014-1-spasswolf@web.de> (raw)
In-Reply-To: <aQufmyZ7X7NdfiCL@slm.duckdns.org>

Since linux v6.19 I noticed that rebooting my MSI Alpha 15 Laptop
would hang for about ~90s before rebooting. I bisected this (from
v6.18 to v6.19) and got this as the first bad commit:
9311e6c29b34 ("cgroup: Fix sleeping from invalid context warning on PREEMPT_RT")

Reverting this commit fixes the reboot delay but introduces these error (which
also seem to make the system crash sometimes):
[    T0] BUG: scheduling while atomic: swapper/0/0/0x00000002

Compiling the kernel without PREEMPT_RT also fixes the issue.

I've test these commits from "git log --oneline v6.19 kernel/cgroup"

This commit shows the reboot delay:
9311e6c29b34 cgroup: Fix sleeping from invalid context warning on PREEMPT_RT
These commits show no reboot delay, but "scheduling while atomic" warnings
and instability:
be04e96ba911 cgroup/cpuset: Globally track isolated_cpus update
b1034a690129 cgroup/cpuset: Ensure domain isolated CPUs stay in root or isolated partition
6cfeddbf4ade cgroup/cpuset: Move up prstate_housekeeping_conflict() helper
103b08709e8a cgroup/cpuset: Fail if isolated and nohz_full don't leave any housekeeping
55939cf28a48 cgroup/cpuset: Rename update_unbound_workqueue_cpumask() to update_isolation_cpumasks()
b66c7af4d86d cgroup: use credential guards in cgroup_attach_permissions()
d245698d727a cgroup: Defer task cgroup unlink until after the task is done switching out
This commit shows neither the reboot delay nor the "scheduling while atomic" problem:
260fbcb92bbe cgroup: Move dying_tasks cleanup from cgroup_task_release() to cgroup_task_free()

Bert Karwatzki



       reply	other threads:[~2026-02-19 16:47 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <aQufmyZ7X7NdfiCL@slm.duckdns.org>
2026-02-19 16:46 ` Bert Karwatzki [this message]
2026-02-19 20:53   ` ~90s reboot delay with v6.19 and PREEMPT_RT Calvin Owens
2026-02-19 23:10     ` Bert Karwatzki
2026-02-20  0:58       ` Steven Rostedt
2026-02-20  9:15         ` ~90s shutdown " Bert Karwatzki
2026-02-20 15:44           ` Steven Rostedt
2026-02-23  0:35             ` Bert Karwatzki
2026-02-23  8:22               ` Steven Rostedt
2026-02-23 13:36                 ` Bert Karwatzki
2026-02-23 23:36                   ` Bert Karwatzki
2026-02-24 12:44                     ` Bert Karwatzki
2026-02-24 12:58                       ` Bert Karwatzki
2026-02-24 14:20                     ` Steven Rostedt
2026-02-24 15:45       ` ~90s reboot " Sebastian Andrzej Siewior
2026-02-25 15:43   ` Sebastian Andrzej Siewior
2026-02-25 16:37     ` Bert Karwatzki
2026-02-25 16:59       ` Sebastian Andrzej Siewior
2026-02-25 22:31         ` Sebastian Andrzej Siewior
2026-02-26 13:24           ` Bert Karwatzki
2026-02-26 13:46             ` Sebastian Andrzej Siewior
2026-02-26 16:37             ` Steven Rostedt
2026-02-27 14:13           ` Sebastian Andrzej Siewior
2026-02-27 22:57             ` Bert Karwatzki
2026-03-02 11:15               ` Sebastian Andrzej Siewior

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=20260219164648.3014-1-spasswolf@web.de \
    --to=spasswolf@web.de \
    --cc=bigeasy@linutronix.de \
    --cc=calvin@wbinvd.org \
    --cc=dschatzberg@meta.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-devel@lists.linux.dev \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    --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