"iwn0: iwn_panicked: controller panicked..."

Wed Apr 4 12:51:35 UTC 2018

I seem to be seeing a fair number of these, especially running head
(at the moment, running:
FreeBSD g1-215.catwhisker.org 12.0-CURRENT FreeBSD 12.0-CURRENT #149  r331908M/331923:1200060: Tue Apr  3 04:48:56 PDT 2018     root at g1-215.catwhisker.org:/common/S3/obj/usr/src/amd64.amd64/sys/CANARY  amd64

building head @r332002).

Excerpt from /var/log/messages (times show UTC):

Apr  4 12:41:22 g1-215 wpa_supplicant[320]: wlan0: CTRL-EVENT-DISCONNECTED bssid=04:18:d6:22:22:1f reason=0
Apr  4 12:41:22 g1-215 kernel: iwn0: iwn_intr: fatal firmware error
Apr  4 12:41:22 g1-215 kernel: firmware error log:
Apr  4 12:41:22 g1-215 kernel:   error type      = "NMI_INTERRUPT_WDG" (0x00000004)
Apr  4 12:41:22 g1-215 kernel:   program counter = 0x000006B4
Apr  4 12:41:22 g1-215 kernel:   source line     = 0x00007B96
Apr  4 12:41:22 g1-215 kernel:   error data      = 0x0000000202630000
Apr  4 12:41:22 g1-215 kernel:   branch link     = 0x0000067A0000071A
Apr  4 12:41:22 g1-215 kernel:   interrupt link  = 0x000015320000E774
Apr  4 12:41:22 g1-215 kernel:   time            = 3996898653
Apr  4 12:41:22 g1-215 kernel: driver status:
Apr  4 12:41:22 g1-215 kernel:   tx ring  0: qid=0  cur=196 queued=152
Apr  4 12:41:22 g1-215 kernel:   tx ring  1: qid=1  cur=0   queued=0  
Apr  4 12:41:22 g1-215 kernel:   tx ring  2: qid=2  cur=5   queued=1  
Apr  4 12:41:22 g1-215 kernel:   tx ring  3: qid=3  cur=6   queued=0  
Apr  4 12:41:22 g1-215 kernel:   tx ring  4: qid=4  cur=57  queued=0  
Apr  4 12:41:22 g1-215 kernel:   tx ring  5: qid=5  cur=0   queued=0  
Apr  4 12:41:22 g1-215 kernel:   tx ring  6: qid=6  cur=0   queued=0  
Apr  4 12:41:22 g1-215 kernel:   tx ring  7: qid=7  cur=0   queued=0  
Apr  4 12:41:22 g1-215 kernel:   tx ring  8: qid=8  cur=0   queued=0  
Apr  4 12:41:22 g1-215 kernel:   tx ring  9: qid=9  cur=0   queued=0  
Apr  4 12:41:22 g1-215 kernel:   tx ring 10: qid=10 cur=0   queued=0  
Apr  4 12:41:22 g1-215 kernel:   tx ring 11: qid=11 cur=0   queued=0  
Apr  4 12:41:22 g1-215 kernel:   tx ring 12: qid=12 cur=0   queued=0  
Apr  4 12:41:22 g1-215 kernel:   tx ring 13: qid=13 cur=0   queued=0  
Apr  4 12:41:22 g1-215 kernel:   tx ring 14: qid=14 cur=0   queued=0  
Apr  4 12:41:22 g1-215 kernel:   tx ring 15: qid=15 cur=0   queued=0  
Apr  4 12:41:22 g1-215 kernel:   tx ring 16: qid=16 cur=0   queued=0  
Apr  4 12:41:22 g1-215 kernel:   tx ring 17: qid=17 cur=0   queued=0  
Apr  4 12:41:22 g1-215 kernel:   tx ring 18: qid=18 cur=0   queued=0  
Apr  4 12:41:22 g1-215 kernel:   tx ring 19: qid=19 cur=0   queued=0  
Apr  4 12:41:22 g1-215 kernel:   rx ring: cur=23
Apr  4 12:41:22 g1-215 kernel: iwn0: iwn_panicked: controller panicked, iv_state = 5; restarting
Apr  4 12:41:22 g1-215 kernel: wlan0: link state changed to DOWN
Apr  4 12:41:22 g1-215 wpa_supplicant[320]: ioctl[SIOCS80211, op=20, val=0, arg_len=7]: Can't assign requested address
Apr  4 12:41:22 g1-215 ntpd[57289]: ntpd exiting on signal 15 (Terminated)
Apr  4 12:41:22 g1-215 dhclient: Using ntp_servers: 172.17.0.1
Apr  4 12:41:22 g1-215 kernel: iwn0: iwn_read_firmware: ucode rev=0x09dd0401
Apr  4 12:41:23 g1-215 ntpd[57476]: ntpd 4.2.8p11-a (3): Starting
Apr  4 12:41:23 g1-215 dhclient: Exiting /etc/dhclient-exit-hooks (REBOOT) with exit_status 0
Apr  4 12:41:23 g1-215 wpa_supplicant[320]: wlan0: Trying to associate with 04:18:d6:22:22:1f (SSID='lmdhw-net' freq=2462 MHz)
Apr  4 12:41:23 g1-215 wpa_supplicant[320]: wlan0: Associated with 04:18:d6:22:22:1f
Apr  4 12:41:23 g1-215 kernel: wlan0: link state changed to UP
Apr  4 12:41:23 g1-215 wpa_supplicant[320]: wlan0: WPA: Key negotiation completed with 04:18:d6:22:22:1f [PTK=CCMP GTK=CCMP]
Apr  4 12:41:23 g1-215 wpa_supplicant[320]: wlan0: CTRL-EVENT-CONNECTED - Connection to 04:18:d6:22:22:1f completed [id=23 id_str=]
Apr  4 12:42:02 g1-215 devd: check_clients:  dropping disconnected client
Apr  4 12:42:09 g1-215 wpa_supplicant[320]: wlan0: CTRL-EVENT-DISCONNECTED bssid=04:18:d6:22:22:1f reason=0

(The last line pasted is the beginning of another such controller panic.)

Am I correct tha the "fatal firmware error" is in the (Intel-supplied?)
firmware for the device?

Anything I can do to make it "just work" a bit more?

Peace,
david
-- 
David H. Wolfskill				david at catwhisker.org
An investigator who doesn't make a perp nervous isn't doing his job.

See http://www.catwhisker.org/~david/publickey.gpg for my public key.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 618 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-wireless/attachments/20180404/f73905f1/attachment.sig>