[Bug 288186] rtw88 not working with "unknown channel 234!!" during installation

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=288186

--- Comment #13 from commit-hook@FreeBSD.org ---
A commit in branch releng/15.0 references this bug:

URL:
https://cgit.FreeBSD.org/src/commit/?id=f490eae83f7f90de8be5d1dea593227dbfb98f36

commit f490eae83f7f90de8be5d1dea593227dbfb98f36
Author:     Bjoern A. Zeeb <bz@FreeBSD.org>
AuthorDate: 2025-11-10 19:41:08 +0000
Commit:     Colin Percival <cperciva@FreeBSD.org>
CommitDate: 2025-11-12 18:46:14 +0000

    LinuxKPI: 802.11: clear CONF_IDLE earlier

    When starting to scan and ending a scan we clear/set the hardware to
    idle.  Similarly we set the hw to idle when we remove the channel
    context but when starting we only set it to non-idle when we went from
    assoc to run.  This apparently was not a problem most of the time
    as the switch from a failed hardware scan to a software scan was
    racing against net80211.  ad4ddc83ebf8 fixed that specifically for
    rtw88 and while we were more consistently scanning, this broke
    authentication as the setting of idle at the end of the scan was
    now happening reliably.  Move the unsetting of idle from assoc_to_run
    to scan_to_auth for when we  create the chanctx to keep it
    symmetrical.  This makes authentication work again for rtw88 (though
    not for everyone due to other possible problems with net80211).

    This likely also fixes the problems in the listed PRs.

    iwlwifi(4) mvm and mld driver parts do not use this information at
    all and were never affected.

    Approved by:    re (cperciva)
    Sponsored by:   The FreeBSD Foundation
    PR:             290850, 288186, 281979
    PR:             272145 (the non skb-mem-limit parts)

    (cherry picked from commit b568711f8ef1afd7c86ea2d8bd2f94f399f54dc1)
    (cherry picked from commit a77abd53e83c4357ad8a8006a6e89759e65e3a5b)

 sys/compat/linuxkpi/common/src/linux_80211.c | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

-- 
You are receiving this mail because:
You are the assignee for the bug.