From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: boot warning from the final tree
Date: Mon, 17 Nov 2025 20:22:14 +1100 [thread overview]
Message-ID: <20251117202214.4f710f02@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 2283 bytes --]
Hi all,
Today's linux-next qemu boot (powerpc pseries_le_defconfig) produced
this warning:
ftrace: allocating 48915 entries in 288 pages
ftrace: allocated 287 pages with 6 groups
------------[ cut here ]------------
DEBUG_LOCKS_WARN_ON(lock->magic != lock)
WARNING: kernel/locking/mutex.c:156 at mutex_lock+0xcc/0x100, CPU#0: swapper/0/0
Modules linked in:
CPU: 0 UID: 0 PID: 0 Comm: swapper/0 Not tainted 6.18.0-rc6-09359-g921087e37218 #1 VOLUNTARY
Hardware name: IBM pSeries (emulated by qemu) POWER9 (architected) 0x4e1202 0xf000005 of:SLOF,HEAD hv:linux,kvm pSeries
NIP: c00000000148041c LR: c000000001480418 CTR: 0000000000000000
REGS: c000000002957a10 TRAP: 0700 Not tainted (6.18.0-rc6-09359-g921087e37218)
MSR: 8000000002021033 <SF,VEC,ME,IR,DR,RI,LE> CR: 24022240 XER: 00000000
CFAR: c00000000021123c IRQMASK: 3
GPR00: c000000001480418 c000000002957cb0 c000000001a3a100 0000000000000028
GPR04: 00000000ffffe04a c0000000026abe88 0000000000000001 000000000000004b
GPR08: c0000000026abd28 0000000000000000 0000000000000000 0000000044022240
GPR12: 0000000000000000 c000000002ae9000 0000000000000000 0000000001bff430
GPR16: 000000007e68f070 c00000007f79c480 c000000002969160 c000000002a0f5d8
GPR20: c0000000026a1138 c0000000026a1120 0000000000000000 c0000000019541b8
GPR24: c00000000218a480 c00000000296e1d0 000000007d612000 c00000000380be10
GPR28: c00000000380be20 c00000000380be00 c000000002640100 c00000000380be20
NIP [c00000000148041c] mutex_lock+0xcc/0x100
LR [c000000001480418] mutex_lock+0xc8/0x100
Call Trace:
[c000000002957cb0] [c000000001480418] mutex_lock+0xc8/0x100 (unreliable)
[c000000002957d20] [c00000000024a60c] alloc_workqueue_noprof+0x38c/0x8ec
[c000000002957e00] [c00000000203018c] workqueue_init_early+0x4d8/0x6ec
[c000000002957f30] [c000000002004448] start_kernel+0x74c/0xa4c
[c000000002957fe0] [c00000000000e99c] start_here_common+0x1c/0x20
Code: 4182ffb4 3d2200f3 392971e4 81290000 2c090000 4082ffa0 3c82ffe0 3c62ffe0 3884bfe0 3863bf68 4ad90d45 60000000 <0fe00000> 4bffff80 60000000 60000000
---[ end trace 0000000000000000 ]---
rcu: Hierarchical RCU implementation.
I have no idea what caused this.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2025-11-17 9:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-17 9:22 Stephen Rothwell [this message]
2025-11-21 21:58 ` linux-next: boot warning from the final tree Nathan Chancellor
2025-11-21 22:33 ` Boqun Feng
2025-11-22 7:37 ` Nathan Chancellor
2025-11-23 0:50 ` Waiman Long
2025-11-24 7:45 ` Sebastian Andrzej Siewior
2025-11-25 14:54 ` [PATCH] locking/mutex: Initialize mutex::magic even when LOCKDEP=n Boqun Feng
2025-11-28 5:08 ` Stephen Rothwell
2025-11-28 9:55 ` Peter Zijlstra
2025-11-28 10:29 ` Stephen Rothwell
2025-11-28 9:36 ` Peter Zijlstra
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=20251117202214.4f710f02@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox