From: Mathias Nyman <mathias.nyman@linux.intel.com>
To: Michal Pecio <michal.pecio@gmail.com>,
Steven Rostedt <rostedt@goodmis.org>
Cc: Marek Szyprowski <m.szyprowski@samsung.com>,
Robin Murphy <robin.murphy@arm.com>,
iommu@lists.linux.dev, Mathias Nyman <mathias.nyman@intel.com>,
linux-usb@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [BUG v7.3-rc1] WARNING: mm/page_alloc.c:5340 at __alloc_frozen_pages_noprof
Date: Thu, 3 Sep 2026 11:32:33 +0300 [thread overview]
Message-ID: <41737353-533e-4d50-b687-272e6cbde36a@linux.intel.com> (raw)
In-Reply-To: <20260903091556.751544ce.michal.pecio@gmail.com>
On 9/3/26 10:15, Michal Pecio wrote:
> On Wed, 2 Sep 2026 14:33:51 -0400, Steven Rostedt wrote:
>> I'm triggering this warning on boot:
>>
>> [ 32.862044] ------------[ cut here ]------------
>> [ 32.864573] WARNING: mm/page_alloc.c:5340 at __alloc_frozen_pages_noprof+0xd81/0x30d0, CPU#3: swapper/0/1
>
> Apparently that's a nonsense allocation size.
>
>> [ 32.881048] Modules linked in:
>> [ 32.883735] CPU: 3 UID: 0 PID: 1 Comm: swapper/0 Not tainted 7.3.0-rc1-test #510 PREEMPT(full)
>> [ 32.890178] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.17.0-debian-1.17.0-1 04/01/2014
>
> Hmm, I recall hearing about QEMU recently.
>
> Could this be the "horrible splat" mentioned by 045b5bef916d ?
>
> Find it in usb-linus branch at
> git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git
>
Yes, this is the case
A patch switching to GENMASK and FIELD_GET has a flaw and changed the parsing of
the max segments value reported by xHCI host controller.
xHC returns _exponent_ of maximum segments supported, QEMU supports one segment
so value read is 0. Parsing fails and assumes maximum number of supported ring segments
is 0. Most hardware xHCI controllers (except some Mediatek) support more than one
segments so issue is not visible for those
Issue (7.3-rc1):
6d45e9556d4a ("usb: xhci: standardize multi bit-field macros") in parsing
Fix: (in Greg's tree, Hopeful it can make make 7.3-rc2)
045b5bef916d usb: xhci: Fix HCS_ERST_MAX conversion
Thanks
Mathias
next prev parent reply other threads:[~2026-09-03 8:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-02 18:33 [BUG v7.3-rc1] WARNING: mm/page_alloc.c:5340 at __alloc_frozen_pages_noprof Steven Rostedt
2026-09-03 7:15 ` Michal Pecio
2026-09-03 8:32 ` Mathias Nyman [this message]
2026-09-03 13:06 ` Steven Rostedt
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=41737353-533e-4d50-b687-272e6cbde36a@linux.intel.com \
--to=mathias.nyman@linux.intel.com \
--cc=iommu@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=mathias.nyman@intel.com \
--cc=michal.pecio@gmail.com \
--cc=robin.murphy@arm.com \
--cc=rostedt@goodmis.org \
--cc=torvalds@linux-foundation.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