From: Borislav Petkov <bp@alien8.de>
To: Bert Karwatzki <spasswolf@web.de>
Cc: seanjc@google.com,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-rt-devel@lists.linux.dev,
Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, Jakub Kicinski <kuba@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
torvalds@linux-foundation.org, x86@kernel.org,
tglx@linutronix.de
Subject: Re: (Re)boot hangs and refcount errors on next-20250829
Date: Sun, 31 Aug 2025 17:39:41 +0200 [thread overview]
Message-ID: <20250831153941.GCaLRsvf1V_ST2GPAd@fat_crate.local> (raw)
In-Reply-To: <20250831141426.2786-1-spasswolf@web.de>
On Sun, Aug 31, 2025 at 04:14:24PM +0200, Bert Karwatzki wrote:
> I think I hit the the same error (and some more ...) when booting next-20250829
> on my amd64 laptop (no VMs and no kexec were used here):
>
> When I try booting next-20250829 on my debian stable(trixie) amd64 system the boot
> process hangs every few attempts (without any log messages recorded). When the
> boot process succeeds the following error message appears in dmesg:
>
> [ 8.337248] [ T44] ------------[ cut here ]------------
> [ 8.337250] [ T44] WARNING: kernel/futex/core.c:1604 at futex_ref_rcu+0xe8/0x100, CPU#6: rcuc/6/44
I believe that got fixed, pls try:
https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/log/?h=locking/urgent
which got updated to contain the fix for the warning above.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
prev parent reply other threads:[~2025-08-31 15:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-31 14:14 (Re)boot hangs and refcount errors on next-20250829 Bert Karwatzki
2025-08-31 15:21 ` Bert Karwatzki
2025-08-31 15:39 ` Borislav Petkov [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=20250831153941.GCaLRsvf1V_ST2GPAd@fat_crate.local \
--to=bp@alien8.de \
--cc=akpm@linux-foundation.org \
--cc=bigeasy@linutronix.de \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-rt-devel@lists.linux.dev \
--cc=peterz@infradead.org \
--cc=seanjc@google.com \
--cc=spasswolf@web.de \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=x86@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.