From: Bert Karwatzki <spasswolf@web.de>
To: Mike Rapoport <rppt@kernel.org>
Cc: linux-kernel@vger.kernel.org, spasswolf@web.de,
Liam.Howlett@oracle.com, akpm@linux-foundation.org,
andreas@gaisler.com, ardb@kernel.org, bp@alien8.de,
brauner@kernel.org, catalin.marinas@arm.com, chleroy@kernel.org,
dave.hansen@linux.intel.com, davem@davemloft.net,
david@kernel.org, devicetree@vger.kernel.org,
dvyukov@google.com, elver@google.com, glider@google.com,
hannes@cmpxchg.org, hpa@zytor.com, ilias.apalodimas@linaro.org,
iommu@lists.linux.dev, jack@suse.cz, jackmanb@google.com,
kasan-dev@googlegroups.com,
linux-arm-kernel@lists.infradead.org, linux-efi@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-mm@kvack.org,
linux-trace-kernel@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org, lorenzo.stoakes@oracle.com,
m.szyprowski@samsung.com, maddy@linux.ibm.com,
mhiramat@kernel.org, mhocko@suse.com, mingo@redhat.com,
mpe@ellerman.id.au, npiggin@gmail.com, robh@kernel.org,
robin.murphy@arm.com, saravanak@kernel.org,
sparclinux@vger.kernel.org, surenb@google.com, tglx@kernel.org,
vbabka@kernel.org, viro@zeniv.linux.org.uk, will@kernel.org,
x86@kernel.org, ziy@nvidia.com
Subject: Re: Warning from free_reserved_area() in next-20260325+
Date: Fri, 27 Mar 2026 20:54:24 +0100 [thread overview]
Message-ID: <59508c77abe7605636cde616c8c3b3291c6acf54.camel@web.de> (raw)
In-Reply-To: <aca6blFFWskxAcAr@kernel.org>
Am Freitag, dem 27.03.2026 um 20:12 +0300 schrieb Mike Rapoport:
> Hi Bert,
>
> On Fri, Mar 27, 2026 at 03:01:08PM +0100, Bert Karwatzki wrote:
> > Starting with linux next-20260325 I see the following warning early in the
> > boot process of a machine running debian stable (trixie) (except for the kernel):
>
> Thanks for the report!
>
> > [ 0.027118] [ T0] ------------[ cut here ]------------
> > [ 0.027118] [ T0] Cannot free reserved memory because of deferred initialization of the memory map
> > [ 0.027119] [ T0] WARNING: mm/memblock.c:904 at __free_reserved_area+0xa9/0xc0, CPU#0: swapper/0/0
> > [ 0.027122] [ T0] Modules linked in:
> > [ 0.027123] [ T0] CPU: 0 UID: 0 PID: 0 Comm: swapper/0 Not tainted 7.0.0-rc5-next-20260326-master #385 PREEMPT_RT
> > [ 0.027125] [ T0] Hardware name: ASUS System Product Name/ROG STRIX B850-F GAMING WIFI, BIOS 1627 02/05/2026
> > [ 0.027125] [ T0] RIP: 0010:__free_reserved_area+0xa9/0xc0
> > [ 0.027126] [ T0] Code: 48 89 df 48 89 ee e8 06 fe ff ff 48 89 c3 48 39 e8 72 a0 5b 4c 89 e8 5d 41 5c 41 5d 41 5e c3 cc cc cc cc 48 8d 3d 97 c2 c6 00 <67> 48 0f b9 3a 45 31 ed eb df 66 66 2e 0f 1f 84 00 00 00 00 00 66
> > [ 0.027127] [ T0] RSP: 0000:ffffffff9b203e98 EFLAGS: 00010202
> > [ 0.027128] [ T0] RAX: 0000000e91c00001 RBX: ffffffff9b100c0f RCX: 0000000080000001
> > [ 0.027128] [ T0] RDX: 00000000000000cc RSI: 0000000e2d42d000 RDI: ffffffff9b32ef60
> > [ 0.027128] [ T0] RBP: ffff9eeafdd6fbc0 R08: 0000000000000000 R09: 0000000000000001
> > [ 0.027129] [ T0] R10: 0000000000001000 R11: 8000000000000163 R12: 000000000000006f
> > [ 0.027129] [ T0] R13: 0000000000000000 R14: 0000000000000045 R15: 000000005c8a1000
> > [ 0.027129] [ T0] FS: 0000000000000000(0000) GS:ffff9eeb21c05000(0000) knlGS:0000000000000000
> > [ 0.027130] [ T0] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> > [ 0.027130] [ T0] CR2: ffff9ee8ad801000 CR3: 0000000e2ce1e000 CR4: 0000000000f50ef0
> > [ 0.027131] [ T0] PKRU: 55555554
> > [ 0.027131] [ T0] Call Trace:
> > [ 0.027132] [ T0] <TASK>
> > [ 0.027132] [ T0] free_reserved_area+0x89/0xd0
> > [ 0.027133] [ T0] alternative_instructions+0xee/0x110
> > [ 0.027136] [ T0] arch_cpu_finalize_init+0x10f/0x160
> > [ 0.027138] [ T0] start_kernel+0x686/0x710
> > [ 0.027140] [ T0] x86_64_start_reservations+0x24/0x30
> > [ 0.027141] [ T0] x86_64_start_kernel+0xd4/0xe0
> > [ 0.027142] [ T0] common_startup_64+0x13e/0x141
> > [ 0.027143] [ T0] </TASK>
> > [ 0.027144] [ T0] ---[ end trace 0000000000000000 ]---
>
> Does this patch fix it for you?
>
> diff --git a/arch/x86/kernel/alternative.c b/arch/x86/kernel/alternative.c
> index e87da25d1236..62936a3bde19 100644
> --- a/arch/x86/kernel/alternative.c
> +++ b/arch/x86/kernel/alternative.c
> @@ -2448,19 +2448,31 @@ void __init alternative_instructions(void)
> __smp_locks, __smp_locks_end,
> _text, _etext);
> }
> +#endif
>
> + restart_nmi();
> + alternatives_patched = 1;
> +
> + alt_reloc_selftest();
> +}
> +
> +#ifdef CONFIG_SMP
> +/*
> + * With CONFIG_DEFERRED_STRUCT_PAGE_INIT enabled we can free_init_pages() only
> + * after the deferred initialization of the memory map is complete.
> + */
> +static int __init free_smp_locks(void)
> +{
> if (!uniproc_patched || num_possible_cpus() == 1) {
> free_init_pages("SMP alternatives",
> (unsigned long)__smp_locks,
> (unsigned long)__smp_locks_end);
> }
> -#endif
>
> - restart_nmi();
> - alternatives_patched = 1;
> -
> - alt_reloc_selftest();
> + return 0;
> }
> +arch_initcall(free_smp_locks);
> +#endif
>
> /**
> * text_poke_early - Update instructions on a live kernel at boot time
>
> > Bert Karwatzki
Yes, your patch fixes the issue in next-20260326.
Tested-By: Bert Karwatzki <spasswolf@web.de>
Bert Karwatzki
next prev parent reply other threads:[~2026-03-27 19:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-23 7:48 [PATCH v2 0/9] memblock: improve late freeing of reserved memory Mike Rapoport
2026-03-23 7:48 ` [PATCH v2 1/9] memblock: reserve_mem: fix end caclulation in reserve_mem_release_by_name() Mike Rapoport
2026-03-23 7:48 ` [PATCH v2 2/9] powerpc: fadump: pair alloc_pages_exact() with free_pages_exact() Mike Rapoport
2026-03-23 7:48 ` [PATCH v2 3/9] powerpc: opal-core: " Mike Rapoport
2026-03-23 7:48 ` [PATCH v2 4/9] mm: move free_reserved_area() to mm/memblock.c Mike Rapoport
2026-03-30 9:00 ` Vlastimil Babka (SUSE)
2026-03-23 7:48 ` [PATCH v2 5/9] memblock: make free_reserved_area() more robust Mike Rapoport
2026-03-23 7:48 ` [PATCH v2 6/9] memblock: extract page freeing from free_reserved_area() into a helper Mike Rapoport
2026-03-23 7:48 ` [PATCH v2 7/9] memblock: make free_reserved_area() update memblock if ARCH_KEEP_MEMBLOCK=y Mike Rapoport
2026-03-23 7:48 ` [PATCH v2 8/9] memblock, treewide: make memblock_free() handle late freeing Mike Rapoport
2026-03-23 7:48 ` [PATCH v2 9/9] memblock: warn when freeing reserved memory before memory map is initialized Mike Rapoport
2026-03-27 14:01 ` Warning from free_reserved_area() in next-20260325+ Bert Karwatzki
2026-03-27 17:12 ` Mike Rapoport
2026-03-27 19:54 ` Bert Karwatzki [this message]
2026-03-25 8:51 ` [PATCH v2 0/9] memblock: improve late freeing of reserved memory Mike Rapoport
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=59508c77abe7605636cde616c8c3b3291c6acf54.camel@web.de \
--to=spasswolf@web.de \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=andreas@gaisler.com \
--cc=ardb@kernel.org \
--cc=bp@alien8.de \
--cc=brauner@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=chleroy@kernel.org \
--cc=dave.hansen@linux.intel.com \
--cc=davem@davemloft.net \
--cc=david@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dvyukov@google.com \
--cc=elver@google.com \
--cc=glider@google.com \
--cc=hannes@cmpxchg.org \
--cc=hpa@zytor.com \
--cc=ilias.apalodimas@linaro.org \
--cc=iommu@lists.linux.dev \
--cc=jack@suse.cz \
--cc=jackmanb@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=m.szyprowski@samsung.com \
--cc=maddy@linux.ibm.com \
--cc=mhiramat@kernel.org \
--cc=mhocko@suse.com \
--cc=mingo@redhat.com \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
--cc=robh@kernel.org \
--cc=robin.murphy@arm.com \
--cc=rppt@kernel.org \
--cc=saravanak@kernel.org \
--cc=sparclinux@vger.kernel.org \
--cc=surenb@google.com \
--cc=tglx@kernel.org \
--cc=vbabka@kernel.org \
--cc=viro@zeniv.linux.org.uk \
--cc=will@kernel.org \
--cc=x86@kernel.org \
--cc=ziy@nvidia.com \
/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