Bug 218697 - rtw88_8821ce timed out to flush queue 2
Summary: rtw88_8821ce timed out to flush queue 2
Status: NEW
Alias: None
Product: Drivers
Classification: Unclassified
Component: network-wireless (show other bugs)
Hardware: Intel Linux
: P3 low
Assignee: drivers_network-wireless@kernel-bugs.osdl.org
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-04-08 22:38 UTC by Lewis
Modified: 2024-04-16 20:41 UTC (History)
0 users

See Also:
Kernel Version: 6.8.4, 6.8.5
Subsystem:
Regression: No
Bisected commit-id:

Attachments
lsmod (8.12 KB, text/plain)
2024-04-08 22:38 UTC, Lewis 		Details
dmesg (132.60 KB, text/plain)
2024-04-08 22:38 UTC, Lewis 		Details
lspci (1.19 KB, text/plain)
2024-04-08 22:39 UTC, Lewis 		Details
journal (2.40 KB, text/plain)
2024-04-15 17:24 UTC, Lewis 		Details
Add an attachment (proposed patch, testcase, etc.)

Description Lewis 2024-04-08 22:38:33 UTC 
Created attachment 306109 [details]
lsmod

WiFi works fine, and no performance loss but my `dmesg` is full of warnings like this: timed out to flush queue 2. It seems to happen roughly every 30 seconds (some-kind of roaming?)

I am using kernel 6.8.4 (mainline).

It'd be good if I could some-how limit how much is sent to my dmesg buffer. I don't want to lower the `print_k` level for the whole kernel -- just this driver.
Comment 1 Lewis 2024-04-08 22:38:54 UTC 
Created attachment 306110 [details]
dmesg
Comment 2 Lewis 2024-04-08 22:39:12 UTC 
Created attachment 306111 [details]
lspci
Comment 3 Lewis 2024-04-15 17:23:28 UTC 
It seems this warning is issued ~10 seconds after `iwd` starts a `roam-scan`.
Comment 4 Lewis 2024-04-15 17:24:28 UTC 
Created attachment 306156 [details]
journal
Comment 5 Lewis 2024-04-15 23:11:03 UTC 
I have done some more digging, it seems this is related to ieee80211_scan commands. This is the stack trace for the dev_warn log entry.

[Tue Apr 16 00:00:25 2024] rtw_8821ce 0000:02:00.0: timed out to flush queue 2
[Tue Apr 16 00:00:25 2024] CPU: 1 PID: 363059 Comm: kworker/u8:1 Tainted: G           OE      6.8.5-arch1-1 #1 5f12b795066ab8d27a5fe9971245067df4fb99ed
[Tue Apr 16 00:00:25 2024] Hardware name:  /, BIOS 5.26 09/26/2023
[Tue Apr 16 00:00:25 2024] Workqueue: events_unbound cfg80211_wiphy_work [cfg80211]
[Tue Apr 16 00:00:25 2024] Call Trace:
[Tue Apr 16 00:00:25 2024]  <TASK>
[Tue Apr 16 00:00:25 2024]  dump_stack_lvl+0x47/0x60
[Tue Apr 16 00:00:25 2024]  rtw_mac_flush_queues+0x148/0x190 [rtw88_core 0d7ad2d9d6116c633c0aab4e7bc6016d572d75d4]
[Tue Apr 16 00:00:25 2024]  rtw_ops_flush+0x5a/0x70 [rtw88_core 0d7ad2d9d6116c633c0aab4e7bc6016d572d75d4]
[Tue Apr 16 00:00:25 2024]  __ieee80211_flush_queues+0x10b/0x2e0 [mac80211 5d0b446baffe1290bc56d55aa496e941688b7b40]
[Tue Apr 16 00:00:25 2024]  ieee80211_scan_work+0x3e3/0x520 [mac80211 5d0b446baffe1290bc56d55aa496e941688b7b40]
[Tue Apr 16 00:00:25 2024]  cfg80211_wiphy_work+0xa7/0xe0 [cfg80211 b36d5437ba649ace42ea92e8f83a3ec499e0d5b7]
[Tue Apr 16 00:00:25 2024]  process_one_work+0x178/0x350
[Tue Apr 16 00:00:25 2024]  worker_thread+0x30f/0x450
[Tue Apr 16 00:00:25 2024]  ? __pfx_worker_thread+0x10/0x10
[Tue Apr 16 00:00:25 2024]  kthread+0xe5/0x120
[Tue Apr 16 00:00:25 2024]  ? __pfx_kthread+0x10/0x10
[Tue Apr 16 00:00:25 2024]  ret_from_fork+0x31/0x50
[Tue Apr 16 00:00:25 2024]  ? __pfx_kthread+0x10/0x10
[Tue Apr 16 00:00:25 2024]  ret_from_fork_asm+0x1b/0x30
[Tue Apr 16 00:00:25 2024]  </TASK>
[Tue Apr 16 00:00:26 2024] rtw_8821ce 0000:02:00.0: failed to get tx report from firmware
Note You need to log in before you can comment on or make changes to this bug.