Linux USB
 help / color / mirror / Atom feed
From: Michal Pecio <michal.pecio@gmail.com>
To: 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 09:15:56 +0200	[thread overview]
Message-ID: <20260903091556.751544ce.michal.pecio@gmail.com> (raw)
In-Reply-To: <20260902143351.7b6d5e0a@gandalf.local.home>

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

> [   32.898333] RIP: 0010:__alloc_frozen_pages_noprof (mm/page_alloc.c:5340 (discriminator 12) mm/page_alloc.c:5397 (discriminator 12))
> [   32.902745] Code: 89 44 24 0c 45 89 ee e8 ad f0 ff ff 44 8b 44 24 0c e9 96 f6 ff ff 80 3d 95 5b 9b 04 00 0f 85 7c f7 ff ff c6 05 88 5b 9b 04 01 <0f> 0b e9 6e f7 ff ff f3 90 8b 05 e0 b4 29 04 a8 01 75 f4 89 84 24
> All code
> ========
>    0:	89 44 24 0c          	mov    %eax,0xc(%rsp)
>    4:	45 89 ee             	mov    %r13d,%r14d
>    7:	e8 ad f0 ff ff       	call   0xfffffffffffff0b9
>    c:	44 8b 44 24 0c       	mov    0xc(%rsp),%r8d
>   11:	e9 96 f6 ff ff       	jmp    0xfffffffffffff6ac
>   16:	80 3d 95 5b 9b 04 00 	cmpb   $0x0,0x49b5b95(%rip)        # 0x49b5bb2
>   1d:	0f 85 7c f7 ff ff    	jne    0xfffffffffffff79f
>   23:	c6 05 88 5b 9b 04 01 	movb   $0x1,0x49b5b88(%rip)        # 0x49b5bb2
>   2a:*	0f 0b                	ud2		<-- trapping instruction
>   2c:	e9 6e f7 ff ff       	jmp    0xfffffffffffff79f
>   31:	f3 90                	pause
>   33:	8b 05 e0 b4 29 04    	mov    0x429b4e0(%rip),%eax        # 0x429b519
>   39:	a8 01                	test   $0x1,%al
>   3b:	75 f4                	jne    0x31
>   3d:	89                   	.byte 0x89
>   3e:	84                   	.byte 0x84
>   3f:	24                   	.byte 0x24
> 
> Code starting with the faulting instruction
> ===========================================
>    0:	0f 0b                	ud2
>    2:	e9 6e f7 ff ff       	jmp    0xfffffffffffff775
>    7:	f3 90                	pause
>    9:	8b 05 e0 b4 29 04    	mov    0x429b4e0(%rip),%eax        # 0x429b4ef
>    f:	a8 01                	test   $0x1,%al
>   11:	75 f4                	jne    0x7
>   13:	89                   	.byte 0x89
>   14:	84                   	.byte 0x84
>   15:	24                   	.byte 0x24
> [   32.918421] RSP: 0000:ffff888100e66f90 EFLAGS: 00010246
> [   32.924467] RAX: 0000000000000000 RBX: 1ffff110201cce49 RCX: 1ffff110201cce0b
> [   32.937135] RDX: 0000000000000000 RSI: 0000000000000034 RDI: 0000000000000cc0
> [   32.948122] RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000cc0
> [   32.960471] R10: 0000000000000034 R11: ffffffff85810cb8 R12: ffff8881044540d0
> [   32.971576] R13: 1ffffffff0b0004b R14: 0000000000000000 R15: ffffffffffffffff
> [   32.982619] FS:  0000000000000000(0000) GS:ffff8882b4542000(0000) knlGS:0000000000000000
> [   32.996996] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> [   33.005932] CR2: 0000000000000000 CR3: 00000000060ec001 CR4: 0000000000172ef0
> [   33.016941] Call Trace:
> [   33.022138]  <TASK>
> [   33.024508]  ? __lock_acquire (kernel/locking/lockdep.c:4690 kernel/locking/lockdep.c:5208)
> [   33.028510]  ? kernel_init_freeable (init/main.c:1419 (discriminator 1) init/main.c:1435 (discriminator 1) init/main.c:1455 (discriminator 1) init/main.c:1670 (discriminator 1))
> [   33.032827] ata1: SATA link down (SStatus 0 SControl 300)
> [   33.033110]  ? __pfx_stack_trace_consume_entry (usercopy_64.c:?)
> [   33.041995]  ? __pfx___alloc_frozen_pages_noprof (mm/page_alloc.c:4022)
> [   33.047459]  ? rcu_is_watching (include/linux/context_tracking.h:128 (discriminator 1) kernel/rcu/tree.c:753 (discriminator 1))
> [   33.051447] ata3: SATA link down (SStatus 0 SControl 300)
> [   33.056403] ata4: SATA link down (SStatus 0 SControl 300)
> [   33.061341]  ? trace_preempt_on (include/trace/events/preemptirq.h:53 (discriminator 30) kernel/trace/trace_preemptirq.c:120 (discriminator 30))
> [   33.061735] ata5: SATA link down (SStatus 0 SControl 300)
> [   33.069156] ata2: SATA link down (SStatus 0 SControl 300)
> [   33.073741] ata6: SATA link down (SStatus 0 SControl 300)
> [   33.079200]  ? preempt_count_sub (kernel/sched/core.c:6012 (discriminator 2) kernel/sched/core.c:6009 (discriminator 2) kernel/sched/core.c:6034 (discriminator 2))
> [   33.085087]  ? _raw_spin_unlock_irqrestore (include/linux/spinlock_api_smp.h:211 kernel/locking/spinlock.c:221)
> [   33.089973]  ? stack_depot_save_flags (lib/stackdepot.c:728)
> [   33.094674]  ? kasan_save_stack (mm/kasan/common.c:57)
> [   33.098664]  ? kasan_save_track (mm/kasan/common.c:78)
> [   33.102720]  ? __kasan_kmalloc (mm/kasan/common.c:398 mm/kasan/common.c:415)
> [   33.106722]  ? __kmalloc_cache_node_noprof (include/linux/kasan.h:263 mm/slub.c:5582)
> [   33.113247]  ? xhci_ring_alloc (include/linux/slab.h:1196 drivers/usb/host/xhci-mem.c:379)
> [   33.117224]  ? xhci_alloc_interrupter (drivers/usb/host/xhci-mem.c:2311)

This trace does look like that, or something related.

Regards,
Michal

  reply	other threads:[~2026-09-03  7:16 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 [this message]
2026-09-03  8:32   ` Mathias Nyman
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=20260903091556.751544ce.michal.pecio@gmail.com \
    --to=michal.pecio@gmail.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=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