Bug 274716 - iwm: phy ctx + mac ctx erros, iwm_newstate: could not move to auth stat
Summary: iwm: phy ctx + mac ctx erros, iwm_newstate: could not move to auth stat
Status: Closed Overcome By Events
Alias: None
Product: Base System
Classification: Unclassified
Component: wireless (show other bugs)
Version: CURRENT
Hardware: Any Any
: --- Affects Only Me
Assignee: Bjoern A. Zeeb
URL:
Keywords:
Depends on:
Blocks: 278175
  Show dependency tree / graph
 
Reported: 2023-10-25 18:14 UTC by Bjoern A. Zeeb
Modified: 2024-12-07 01:33 UTC (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Bjoern A. Zeeb freebsd_committer freebsd_triage 2023-10-25 18:14:50 UTC 
Trying to reach (or not reach) a specific bssid I restarted wpa_supplicant and did a netif restart on a wlan0 based by iwm.  This shows similar problems that trigger the KASSERTs in LinuxKPI 802.11 code for iwm(4):

(1)

wlan0: link state changed to DOWN
iwm0: PHY ctxt cmd error. ret=35
iwm0: iwm_auth: failed update phy ctxt
iwm0: iwm_newstate: could not move to auth state: 35
wlan0: link state changed to UP

(2)

iwm0: iwm_auth: failed to update power management
iwm0: iwm_newstate: could not move to auth state: 35
wlan0: link state changed to UP

(3)

iwm0: iwm_mac_ctxt_send_cmd: Failed to send MAC context (action:2): 35
iwm0: iwm_bring_down_firmware: Failed to change mac context: 35
Comment 1 Bjoern A. Zeeb freebsd_committer freebsd_triage 2024-03-05 21:07:08 UTC 
Close this as well;  was good to have as a reference happening on iwm(4) as well while hunting down these things on iwlwifi.