From: Mehmet Fide <mehmet.fide@gmail.com>
To: Ping-Ke Shih <pkshih@realtek.com>
Cc: Luka Gejak <luka.gejak@linux.dev>,
Sascha Hauer <s.hauer@pengutronix.de>,
Zong-Zhe Yang <kevin_yang@realtek.com>,
Tzu-En Huang <tehuang@realtek.com>,
Yan-Hsuan Chuang <yhchuang@realtek.com>,
Kalle Valo <kvalo@kernel.org>,
Stanislaw Gruszka <sgruszka@redhat.com>,
Brian Norris <briannorris@chromium.org>,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
mehmet.fide@screeningeagle.com
Subject: [PATCH rtw-next v3 0/5] wifi: rtw88: fixes around the firmware recovery
Date: Tue, 17 Nov 2026 18:09:58 +0100 [thread overview]
Message-ID: <20261117171003.1840491-1-mehmet.fide@gmail.com> (raw)
From: Mehmet Fide <mehmet.fide@screeningeagle.com>
Fixes for what a firmware crash test showed on an RTL8822CE, and for
what Luka found in v2. Patches 3 and 5 are new.
Tested on rtw-next on an i.MX8MP board with PROVE_LOCKING,
DEBUG_ATOMIC_SLEEP, DEBUG_LIST and kmemleak, with hostapd. The firmware
crashes were triggered from debugfs on the RTL8822CE:
- patch 1: three crashes with an associated station interface lost
five reserved pages before and none after; six crashes with an AP
interface lost three before and none after. With a test build that
holds the hardware restart for 4 s after the recovery, two hostapd
update_beacon calls in that window warned "Should not have an empty
reserved page" with v2 and did not with v3, and a beacon update work
queued during the reconfiguration downloaded the pages with v3 where
v2 skipped it (two runs each)
- patch 2: an unbind after the crashes warned "Have pending ack
frames!" before and did not after. With a test build that drops
every TX report of the firmware, the unbind of the RTL8822CE warned
before; after, neither it nor the RTL8822BU did
- patch 3: a test build that leaves the station out of the collection
during the recovery, as on a failed allocation, skipped its reset with
v2; v3 has no allocation left to fail. Three crashes with a station
pulling traffic: the station stayed, no list report
- patch 4: each of three crashes with an associated station gave the
"sleeping function called from invalid context" report before and
none did after; the link was back after every crash
- patch 5: with the AP stopped and its interface down in the same 4 s
window, the flag stayed set and writing fw_crash returned
-EINPROGRESS with v2; with v3 it was clear and a second crash
recovered (two runs)
With the five patches, AP, association, power save, firmware crash and
scan tests on the RTL8822CE, RTL8822BU and RTL8821CU on both bands gave
no kernel report, and three crashes with an idle and an associated
station interface gave no kmemleak report.
v3:
- patch 1: no RTW_FLAG_RESTARTING test in the beacon update work; the
page download and the page location H2C do nothing while no port is
in use (Luka Gejak)
- patch 3: new, rtw_iterate_stas() cannot skip a station (Luka Gejak)
- patch 5: new, RTW_FLAG_RESTARTING is cleared when the device stops
(Luka Gejak)
- patches 2 and 4: no change
- rebased on rtw-next
v2:
- patch 1: the beacon update work does nothing while
RTW_FLAG_RESTARTING is set (Luka Gejak)
- patches 2 and 3: Reviewed-by Luka Gejak, no change
- rebased on rtw-next
v2: https://lore.kernel.org/linux-wireless/20261116072014.1142494-1-mehmet.fide@gmail.com/
v1: https://lore.kernel.org/linux-wireless/20261111213239.569224-1-mehmet.fide@gmail.com/
Mehmet Fide (5):
wifi: rtw88: free the reserved pages of an interface on firmware
recovery
wifi: rtw88: report the frames purged from the TX report queue
wifi: rtw88: do not drop stations when collecting them for an
iteration
wifi: rtw88: reset the stations outside of RCU on firmware recovery
wifi: rtw88: clear the restart flag when the device is stopped
drivers/net/wireless/realtek/rtw88/fw.c | 6 +++++
drivers/net/wireless/realtek/rtw88/mac80211.c | 1 +
drivers/net/wireless/realtek/rtw88/main.c | 8 +++----
drivers/net/wireless/realtek/rtw88/main.h | 1 +
drivers/net/wireless/realtek/rtw88/tx.c | 20 ++++++++++++----
drivers/net/wireless/realtek/rtw88/tx.h | 1 +
drivers/net/wireless/realtek/rtw88/util.c | 24 +++++--------------
7 files changed, 34 insertions(+), 27 deletions(-)
base-commit: fb51e39dfaea5b5990e783e53c657534a37987d6
--
2.56.0
next reply other threads:[~2026-11-17 17:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-17 17:09 Mehmet Fide [this message]
2026-11-17 17:09 ` [PATCH rtw-next v3 1/5] wifi: rtw88: free the reserved pages of an interface on " Mehmet Fide
2026-11-17 17:10 ` [PATCH rtw-next v3 2/5] wifi: rtw88: report the frames purged from the TX report queue Mehmet Fide
2026-11-17 17:10 ` [PATCH rtw-next v3 3/5] wifi: rtw88: do not drop stations when collecting them for an iteration Mehmet Fide
2026-11-17 17:10 ` [PATCH rtw-next v3 4/5] wifi: rtw88: reset the stations outside of RCU on firmware recovery Mehmet Fide
2026-11-17 17:10 ` [PATCH rtw-next v3 5/5] wifi: rtw88: clear the restart flag when the device is stopped Mehmet Fide
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=20261117171003.1840491-1-mehmet.fide@gmail.com \
--to=mehmet.fide@gmail.com \
--cc=briannorris@chromium.org \
--cc=kevin_yang@realtek.com \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=luka.gejak@linux.dev \
--cc=mehmet.fide@screeningeagle.com \
--cc=pkshih@realtek.com \
--cc=s.hauer@pengutronix.de \
--cc=sgruszka@redhat.com \
--cc=tehuang@realtek.com \
--cc=yhchuang@realtek.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
all inboxes | Powered by JetHome®