[DragonFlyBSD - Bug #3453] (New) iwm(4): reset and rescan after a fatal firmware error

[sigttou]

Issue #3453 has been reported by sigttou.

----------------------------------------
Bug #3453: iwm(4): reset and rescan after a fatal firmware error
http://bugs.dragonflybsd.org/issues/3453

* Author: sigttou
* Status: New
* Priority: Normal
* Category: Driver
* Target version: 6.6
* Start date: 2026-10-16
----------------------------------------
After a firmware error (SW_ERR) iwm(4) calls ieee80211_restart_all(). On an Intel AC 9260 this does not bring the link
back. After the reset the VAP is still in RUN, and with manual roaming (wpa_supplicant) ieee80211_start_all() does not
start a new scan. Wi-Fi stays down until the interface is brought down and up by hand.

Run a full iwm_stop()/iwm_init() from the driver task queue, serialised with IWM_FLAG_BUSY as in iwm_init_task(). Then
move each VAP to SCAN so that wpa_supplicant reassociates.

See also OpenBSD df45c061928f

---Files--------------------------------
0001-iwm-4-reset-and-rescan-after-a-fatal-firmware-error.patch (2.75 KB)


-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account