From: Daniel Palmer <daniel@0x0f.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Joshua Hahn <joshua.hahnjy@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
Dave Hansen <dave.hansen@intel.com>,
Brendan Jackman <jackmanb@google.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Michal Hocko <mhocko@suse.com>,
Suren Baghdasaryan <surenb@google.com>,
Vlastimil Babka <vbabka@suse.cz>, Zi Yan <ziy@nvidia.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
kernel-team@meta.com, Geert Uytterhoeven <geert@linux-m68k.org>,
linux-m68k@lists.linux-m68k.org
Subject: Re: [PATCH v2 2/2] mm/page_alloc: Prevent reporting pcp->batch = 0 [mcf5208evb boot failure]
Date: Wed, 17 Dec 2025 08:20:10 +0900 [thread overview]
Message-ID: <CAFr9PXkRRQwMGzAQyhkaZU-BLFHP02rd3nHy7HR9Z+T5eUaUJg@mail.gmail.com> (raw)
In-Reply-To: <42143500-c380-41fe-815c-696c17241506@roeck-us.net>
Hi Guenter,
On Wed, 17 Dec 2025 at 06:47, Guenter Roeck <linux@roeck-us.net> wrote:
> With this patch in the tree, the qemu 'mcf5208evb' machine fails to boot
> with memory errors such as
>
> S01syslogd: page allocation failure: order:7, mode:0xcc0(GFP_KERNEL), nodemask=(null)
> CPU: 0 UID: 0 PID: 34 Comm: S01syslogd Not tainted 6.19.0-rc1 #1 NONE
> Stack from 407d7ce0:
> 407d7ce0 403df960 403df960 00000000 00000001 00000007 40027c60 403df960
> 400c06be 00000cc0 00000001 407d7d7e 400bf614 407d7d34 403df3ba 407d7d14
> 407d7db8 400c0e5c 00000cc0 00000000 403df3ba 00000007 00000007 00000cc0
> 000d8000 00000018 0000006c 00000001 00000000 40fe6640 00000000 40fe81e4
> 403ffa40 4085eff4 00000000 00000400 00000000 001008c0 00000000 40854041
> f4fe0000 00004041 f4fe0000 00000000 00010000 403ffa40 4085ed00 4085e800
> Call Trace: [<40027c60>] dump_stack+0xc/0x10
> [<400c06be>] warn_alloc+0xdc/0x1bc
> [<400bf614>] get_page_from_freelist+0x0/0xfa6
> [<400c0e5c>] __alloc_frozen_pages_noprof+0x6be/0x8be
> [<400c1358>] get_free_pages_noprof+0x16/0x3e
I reported a different issue but with the same change:
https://lore.kernel.org/lkml/CAFr9PX=_HaM3_xPtTiBn5Gw5-0xcRpawpJ02NStfdr0khF2k7g@mail.gmail.com/
https://lore.kernel.org/lkml/20251211102607.2538595-1-daniel@thingy.jp/
Cheers,
Daniel
next prev parent reply other threads:[~2025-12-16 23:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-09 19:29 [PATCH v2 0/2] mm/page_alloc: pcp->batch cleanups Joshua Hahn
2025-10-09 19:29 ` [PATCH v2 1/2] mm/page_alloc: Clarify batch tuning in zone_batchsize Joshua Hahn
2025-10-13 12:55 ` Vlastimil Babka
2025-10-09 19:29 ` [PATCH v2 2/2] mm/page_alloc: Prevent reporting pcp->batch = 0 Joshua Hahn
2025-10-13 12:58 ` Vlastimil Babka
2025-12-16 21:47 ` [PATCH v2 2/2] mm/page_alloc: Prevent reporting pcp->batch = 0 [mcf5208evb boot failure] Guenter Roeck
2025-12-16 23:20 ` Daniel Palmer [this message]
2025-12-17 5:16 ` Joshua Hahn
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=CAFr9PXkRRQwMGzAQyhkaZU-BLFHP02rd3nHy7HR9Z+T5eUaUJg@mail.gmail.com \
--to=daniel@0x0f.com \
--cc=akpm@linux-foundation.org \
--cc=dave.hansen@intel.com \
--cc=geert@linux-m68k.org \
--cc=hannes@cmpxchg.org \
--cc=jackmanb@google.com \
--cc=joshua.hahnjy@gmail.com \
--cc=kernel-team@meta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=linux-mm@kvack.org \
--cc=linux@roeck-us.net \
--cc=mhocko@suse.com \
--cc=surenb@google.com \
--cc=vbabka@suse.cz \
--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