From: Ping-Ke Shih <pkshih@realtek.com>
To: Zenm Chen <zenmchen@gmail.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"marco.crivellari@suse.com" <marco.crivellari@suse.com>,
"rtl8821cerfe2@gmail.com" <rtl8821cerfe2@gmail.com>
Subject: RE: [PATCH rtw-next] Revert "wifi: rtw88: add WQ_UNBOUND to alloc_workqueue users"
Date: Mon, 8 Dec 2025 02:11:17 +0000 [thread overview]
Message-ID: <c5ea34777592402caeb7fb83af7d6f07@realtek.com> (raw)
In-Reply-To: <20251208014243.3512-1-zenmchen@gmail.com>
Hi Zenm,
Zenm Chen <zenmchen@gmail.com>
> Hi,
>
> Last weekend I tried applying the v1 [1] to the kernel 6.17.9, but that one didn't work, either.
>
> [1]
> https://patchwork.kernel.org/project/linux-wireless/patch/20251113160605.381777-3-marco.crivellari@sus
> e.com/
>
> [ 306.035759] usb 3-2: new high-speed USB device number 5 using ehci-pci
> [ 306.162258] usb 3-2: New USB device found, idVendor=0bda, idProduct=b82c, bcdDevice= 2.10
> [ 306.162272] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
> [ 306.162278] usb 3-2: Product: 802.11ac NIC
> [ 306.162282] usb 3-2: Manufacturer: Realtek
> [ 306.162286] usb 3-2: SerialNumber: 123456
> [ 306.239143] ------------[ cut here ]------------
> [ 306.239148] WARNING: CPU: 3 PID: 2886 at kernel/workqueue.c:5667 alloc_workqueue_noprof+0x676/0x770
I think this is because kernel 6.17.9 defines:
__WQ_BH_ALLOWS = WQ_BH | WQ_HIGHPRI,
and the latest is:
__WQ_BH_ALLOWS = WQ_BH | WQ_HIGHPRI | WQ_PERCPU,
next prev parent reply other threads:[~2025-12-08 2:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-06 18:32 [PATCH rtw-next] Revert "wifi: rtw88: add WQ_UNBOUND to alloc_workqueue users" Bitterblue Smith
2025-12-08 0:40 ` Ping-Ke Shih
2025-12-08 1:42 ` Zenm Chen
2025-12-08 2:11 ` Ping-Ke Shih [this message]
2025-12-08 3:20 ` Zenm Chen
2025-12-08 3:46 ` Ping-Ke Shih
2025-12-09 9:56 ` Marco Crivellari
2025-12-10 0:17 ` Ping-Ke Shih
2025-12-10 9:58 ` Marco Crivellari
2025-12-15 8:49 ` Ping-Ke Shih
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=c5ea34777592402caeb7fb83af7d6f07@realtek.com \
--to=pkshih@realtek.com \
--cc=linux-wireless@vger.kernel.org \
--cc=marco.crivellari@suse.com \
--cc=rtl8821cerfe2@gmail.com \
--cc=zenmchen@gmail.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