git: iwm(4): reset and rescan after a fatal firmware error

[Aaron LI]

commit 4973045fded277a8122286f4e12e3017bda84cc8
Author: David Bidner <david at crap.solutions>
Date:   Fri Oct 16 18:23:07 2026 +0200

    iwm(4): reset and rescan after a fatal firmware error
    
    On a firmware error (SW_ERR) the driver calls ieee80211_restart_all().
    That does not bring the link back on a 9260: after the reset the VAP
    is still in RUN, and with manual roaming (wpa_supplicant)
    ieee80211_start_all() does not scan again, so Wi-Fi stays down until
    the interface is brought down and up.
    
    Do a full iwm_stop()/iwm_init() from the task queue instead, serialised
    with IWM_FLAG_BUSY like iwm_init_task(), then move each VAP to SCAN so
    that wpa_supplicant reassociates.
    
    See commit df45c061928f in OpenBSD.
    
    Bug: https://bugs.dragonflybsd.org/issues/3453

Summary of changes:
 sys/dev/netif/iwm/if_iwm.c | 33 ++++++++++++++++++++++++++++++++-
 1 file changed, 32 insertions(+), 1 deletion(-)

http://gitweb.dragonflybsd.org/dragonfly.git/commitdiff/4973045fded277a8122286f4e12e3017bda84cc8


-- 
DragonFly BSD source repository