Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Nilay Shroff <nilay@linux.ibm.com>
To: Venkat Rao Bagalkote <venkat88@linux.ibm.com>,
	Tejun Heo <tj@kernel.org>,
	jiangshanlai@gmail.com, hch@lst.de, sagi@grimberg.me,
	kbusch@kernel.org
Cc: LKML <linux-kernel@vger.kernel.org>,
	linux-nvme@lists.infradead.org, marco.crivellari@suse.com
Subject: Re: [linux-next20260529] WARNING: kernel/workqueue.c:5855 at __alloc_workqueue+0x62c/0x690
Date: Mon, 1 Jun 2026 12:16:49 +0530	[thread overview]
Message-ID: <0bd4b5ed-c292-490d-ba2a-df4e7590012a@linux.ibm.com> (raw)
In-Reply-To: <dab729b3-fa8e-4d17-894d-07f0c6845e01@linux.ibm.com>

On 6/1/26 11:40 AM, Venkat Rao Bagalkote wrote:
> Greetings!!!
> 
> I am observing following boot warning, appears to be triggered by recent WQ changes.
> 
> Test environment:
>    Kernel: linux-next-20260529 (7.1.0-rc5-next)
>    Arch: powerpc (Power11 / pSeries)
> 
> 
> Warnings:
> 
> 
> 
> [    1.933519] ------------[ cut here ]------------
> [    1.933523] workqueue: nvme_tcp_wq is using neither WQ_PERCPU or WQ_UNBOUND. Setting WQ_PERCPU.
> [    1.933531] WARNING: kernel/workqueue.c:5855 at __alloc_workqueue+0x62c/0x690, CPU#19: modprobe/573
> [    1.933539] Modules linked in: nvme_tcp(E+) sd_mod(E) nvme_fabrics(E) nvme_core(E) ibmvscsi(E) ibmveth(E) scsi_transport_srp(E) dm_mirror(E) dm_region_hash(E) dm_log(E) dm_multipath(E) dm_mod(E)
> [    1.933553] CPU: 19 UID: 0 PID: 573 Comm: modprobe Tainted: G   E       7.1.0-rc5-next-20260529 #1 PREEMPT
> [    1.933559] Tainted: [E]=UNSIGNED_MODULE
> [    1.933561] Hardware name: IBM,9080-HEX Power11 (architected) 0x820200 0xf000007 of:IBM,FW1110.01 (NH1110_069) hv:phyp pSeries
> [    1.933565] NIP:  c00000000026f59c LR: c00000000026f598 CTR: 00000000005d54a0
> [    1.933568] REGS: c0000000097ff600 TRAP: 0700   Tainted: G       E     (7.1.0-rc5-next-20260529)
> [    1.933572] MSR:  8000000002029033 <SF,VEC,EE,ME,IR,DR,RI,LE>  CR: 28222282  XER: 00000004
> [    1.933581] CFAR: c000000000234154 IRQMASK: 0
> [    1.933581] GPR00: c00000000026f598 c0000000097ff8c0 c00000000205b200 0000000000000053
> [    1.933581] GPR04: 3fffffffffff7fff c0000000097ff6b0 c0000000097ff6a8 00000013f6440000
> [    1.933581] GPR08: 0000000000000027 0000000000000000 c0000000c90b2a00 c0000000037ae1d0
> [    1.933581] GPR12: c000000003b2e160 c0000013fffa2300 0000000000000000 0000000000000000
> [    1.933581] GPR16: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
> [    1.933581] GPR20: 0000000000000000 0000000000000000 0000000000000000 c000000003fb5d18
> [    1.933581] GPR24: c000000003fb55b0 c000000008acc2b8 c008000005390180 c0000000097ff9c8
> [    1.933581] GPR28: 0000000000000000 c000000008acc200 0000000000000000 0000000000000058
> [    1.933619] NIP [c00000000026f59c] __alloc_workqueue+0x62c/0x690
> [    1.933623] LR [c00000000026f598] __alloc_workqueue+0x628/0x690
> [    1.933627] Call Trace:
> [    1.933629] [c0000000097ff8c0] [c00000000026f598] __alloc_workqueue+0x628/0x690 (unreliable)
> [    1.933635] [c0000000097ff970] [c00000000026f634] alloc_workqueue_noprof+0x34/0x50
> [    1.933640] [c0000000097ff990] [c008000005316428] nvme_tcp_init_module+0x54/0xf4 [nvme_tcp]
> [    1.933645] [c0000000097ffa10] [c000000000010f7c] do_one_initcall+0x5c/0x45c
> [    1.933650] [c0000000097ffb00] [c000000000358b10] do_init_module+0x70/0x380
> [    1.933655] [c0000000097ffb80] [c00000000035ac10] init_module_from_file+0x110/0x130
> [    1.933659] [c0000000097ffc60] [c00000000035ad84] idempotent_init_module+0x154/0x3c0
> [    1.933663] [c0000000097ffd20] [c00000000035b080] sys_finit_module+0x90/0x150
> [    1.933667] [c0000000097ffda0] [c000000000034318] system_call_exception+0x148/0x4b0
> [    1.933672] [c0000000097ffe30] [c00000000000d05c] system_call_vectored_common+0x15c/0x2ec
This is already reported here: https://lore.kernel.org/all/6a1a9a86.323e8352.141b09.0001.GAE@google.com/

And the fix is posted here: https://lore.kernel.org/all/20260530081059.428303-1-kuniyu@google.com/

Thanks,
--Nilay


      reply	other threads:[~2026-06-01  6:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-01  6:10 [linux-next20260529] WARNING: kernel/workqueue.c:5855 at __alloc_workqueue+0x62c/0x690 Venkat Rao Bagalkote
2026-06-01  6:46 ` Nilay Shroff [this message]

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=0bd4b5ed-c292-490d-ba2a-df4e7590012a@linux.ibm.com \
    --to=nilay@linux.ibm.com \
    --cc=hch@lst.de \
    --cc=jiangshanlai@gmail.com \
    --cc=kbusch@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=marco.crivellari@suse.com \
    --cc=sagi@grimberg.me \
    --cc=tj@kernel.org \
    --cc=venkat88@linux.ibm.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