[Bug 230801] iwm_intr: controller panicked
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Tue Aug 21 14:34:18 UTC 2018
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230801
Bug ID: 230801
Summary: iwm_intr: controller panicked
Product: Base System
Version: CURRENT
Hardware: amd64
OS: Any
Status: New
Severity: Affects Some People
Priority: ---
Component: kern
Assignee: bugs at FreeBSD.org
Reporter: phk at FreeBSD.org
Created attachment 196419
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=196419&action=edit
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.
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the freebsd-bugs
mailing list