Created attachment 173392 [details] /var/log/messages iwm (ac 7260) panic on 11.0-BETA4. (A version tag was selected 11.0-BETA3 because 11.0-BETA4 was not in menu on bugzilla.) My pc (dell xps 12 9q33) was not panic up to 11.0-BETA3. % ifconfig lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384 options=600003<RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6> inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1 inet 127.0.0.1 netmask 0xff000000 nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL> groups: lo ue0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=8000b<RXCSUM,TXCSUM,VLAN_MTU,LINKSTATE> ether 5c:51:4f:11:73:f3 nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL> media: Ethernet autoselect (1000baseT <full-duplex>) status: active wlan0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 ether 5c:51:4f:11:73:f3 nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL> media: IEEE 802.11 Wireless Ethernet OFDM/36Mbps mode 11g status: associated ssid ishorg-qiRF5O5h-g channel 11 (2462 MHz 11g) bssid dc:fb:02:2b:d9:80 regdomain JAPAN country JP authmode WPA2/802.11i privacy ON deftxkey UNDEF AES-CCM 3:128-bit txpower 23 bmiss 10 scanvalid 60 protmode CTS wme roaming MANUAL groups: wlan lagg0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 ether 5c:51:4f:11:73:f3 inet6 fe80::5e51:4fff:fe11:73f3%lagg0 prefixlen 64 scopeid 0x3 inet6 2400:7800:4d3a:6100:5e51:4fff:fe11:73f3 prefixlen 64 autoconf inet 192.168.1.8 netmask 0xffffff00 broadcast 192.168.1.255 nd6 options=23<PERFORMNUD,ACCEPT_RTADV,AUTO_LINKLOCAL> media: Ethernet autoselect status: active groups: lagg laggproto failover lagghash l2,l3,l4 laggport: wlan0 flags=0<> laggport: ue0 flags=5<MASTER,ACTIVE>
iwm (ac7260) panic on 11.0-RC1 too. It was good working on 11.0-BETA1, BETA2 and BETA3.
Hi, Can you attach backtrace of the panic? (/var/log/messages contains only firmware exceptions)
(In reply to Andriy Voskoboinyk from comment #2) > Can you attach backtrace of the panic? How can I get backtrace log ? When iwm driver was paniced, it is restart automatically or stays bad state until /etc/rc.d/netif restart.
iwm on r303326 and iwm7260fw on r286441 is good working for me. iwm on r303327 and iwm7260fw on r303322 is controller panicked.
After MFC to r303628, iwm controller panicked frequently. And this MFC was done within 6 days after introducing new firmware and new logic to the head branch. So, this new patches had not been fully tested. Please revert r303628(iwm) and r303322(ifm*fw) and rollback to r302408(iwm) and r302408 (iwm*fw) on 11.0-RC and 11-stable. After fully tested on head, MFC to 11-stable and 11.1-RELEASE.
I installed OpenBSD 6.0 and found that iwm driver of OpenBSD was not stable. Firmware (iwm-7260-16) crash was often occured on OpenBSD 6.0.
I rollbacked /sys/dev/iwm, /sys/contrib/dev/iwm and /sys/modules/iwmfw on my pc to r303627 at 11.0-RC3 and iwm driver is good working.
(In reply to Masachika ISHIZUKA from comment #7) 11.0-RELEASE with if_iwm.ko and iwm7260fw.ko at 11-stable r303627 (i.e. checkout -r 303627) is good working. And 12-CURRENT at r306286 is almost working but it rarely stops (firmware panicked).
sbruno MFC'd commits mentioned in comment 5, CC accordingly
iwm on 11.1-RC1 is not working.
iwm (ac 7260) is not panic on 11.2-BETA1.