Bug 230801

Summary: iwm_intr: controller panicked
Product: Base System Reporter: Poul-Henning Kamp <phk>
Component: kernAssignee: freebsd-wireless (Nobody) <wireless>
Status: Closed FIXED    
Severity: Affects Some People CC: asensiolaizola
Priority: ---    
Version: CURRENT   
Hardware: amd64   
OS: Any   
Attachments:
Description Flags
Full /var/log/messages from iwm panic. none

Description Poul-Henning Kamp freebsd_committer freebsd_triage 2018-08-21 14:34:16 UTC
Created attachment 196419 [details]
Full /var/log/messages from iwm panic.

I tried to attach to an open of several open networks at "BornHack" yesterday and only managed to panic the iwm driver repeatedly.

I belive the AP's were Ubiquity, and I can probably get hold of the people who runs them if need be.

I have attached the full /var/log/messages as attachment, but here are what I guess is the top-level info:

    Aug 20 15:32:24 critter kernel: iwm0:   rx ring: cur=96
    Aug 20 15:32:24 critter kernel: iwm0:   802.11 state 3
    Aug 20 15:32:24 critter kernel: iwm0: iwm_intr: controller panicked, iv_state = 3; restarting
    Aug 20 15:32:24 critter kernel: wlan0: ieee80211_new_state_locked: pending ASSOC -> AUTH transition lost
    Aug 20 15:32:25 critter kernel: iwm0: Failed to send binding (action:1): 35
    Aug 20 15:32:25 critter kernel: iwm0: iwm_auth: binding update cmd
    Aug 20 15:32:25 critter kernel: iwm0: iwm_newstate: could not move to auth state: 35
    Aug 20 15:32:26 critter kernel: iwm0: iwm_newstate: Failed to remove station: 35
    Aug 20 15:32:27 critter kernel: iwm0: iwm_mvm_mac_ctxt_send_cmd: Failed to send MAC context (action:2): 35
    Aug 20 15:32:27 critter kernel: iwm0: iwm_newstate: Failed to change mac context: 35
    Aug 20 15:32:28 critter kernel: iwm0: Failed to send binding (action:3): 35
    Aug 20 15:32:28 critter kernel: iwm0: iwm_newstate: Failed to remove channel ctx: 35
    Aug 20 15:32:29 critter kernel: iwm0: iwm_newstate: failed to update power management


Machine is Lenovo T480.
Comment 1 eaosfu 2020-04-01 05:04:11 UTC
I'm experiencing the same issue. Running the same release of FreeBSD as OP.

One difference in my case is that I get this error typically after resuming from sleep when connected to home network. Driver panics with iv_state = 2 rather than iv_state = 3 as in the original post.

According to the messages my wireless device is:
Intel(R) Dual Band Wireless AC 7265
Comment 2 eaosfu 2020-07-26 16:38:56 UTC
Just wanted to update here. After upgrading to 12.1 the issue seems to have been resolved.
Comment 3 Poul-Henning Kamp freebsd_committer freebsd_triage 2021-12-22 11:31:43 UTC
Seems to have been fixed along the way.