Date: Sat, 12 Nov 2016 09:15:19 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-amd64@FreeBSD.org Subject: [Bug 214435] controller panic: iwn0: iwn_intr: fatal firmware error error type = "BAD_COMMAND" (0x00000007) Message-ID: <bug-214435-6@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D214435 Bug ID: 214435 Summary: controller panic: iwn0: iwn_intr: fatal firmware error error type =3D "BAD_COMMAND" (0x00000007) Product: Base System Version: 11.0-RELEASE Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: wireless Assignee: freebsd-wireless@FreeBSD.org Reporter: markusalbertgraf@gmail.com CC: freebsd-amd64@FreeBSD.org CC: freebsd-amd64@FreeBSD.org Created attachment 176910 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D176910&action= =3Dedit dmesg printout Hi all, I am new to freebsd, thank you for a wonderful system! I keep getting iwn controller panic while booting. Eventually the machine does come up and does connect to the wireless networ= k. But it takes quite long to boot and has most of the time one, sometimes up = to 4 rounds of iwn controller panic. Sometimes, but rarely, it does not panic. The relevant lines from rc.conf around the panic are below and I attach dme= sg, rc.conf and loader.conf The panic might have something to do with dhcp since I do not get it when I= use dhclient after boot. Thank you in advance for all tips Best regards Markus ** my system I am on a Lenovo SL520 Laptop the wlan is identified as iwn0: <Intel Centrino Wireless-N 1000> mem 0xf2200000-0xf2201fff irq 19 at device 0.0 on pci3 uname -a FreeBSD ########## 11.0-RELEASE-p2 FreeBSD 11.0-RELEASE-p2 #0: Mon Oct 24 06:55:27 UTC 2016 root at amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 freebsd-version 11.0-RELEASE-p3 ** when does the panic show up I only get this error when booting. I cannot remember having seen this panic when I delete the DHCP from ifconfig_wlan0=3D"WPA DHCP" and use dhclient later. When I play around manually, I never get the panic. Oddly. when I use SYNDHCP instead of DHCP I get an errormessage while booti= ng about some wrong pararameter, but *no panic either*. This errormessage flashes by, to fast to read, and does not show up in eith= er dmesg or messages. Putting if_iwn_load=3D"YES" iwn1000fw_load=3D"YES" into loader.conf, does not change anything except reporting "module iwn alr= eady present!" in line 9 of dmesg. The result without the two lines is the same. btw The wlan worked fine when I had PC-BSD 10.3 on the Laptop for a couple of weeks, but being new to BSD maybe I just didn't notice. ** Excerpt from dmesg ---------------------------------------------------------------------- iwn0: <Intel Centrino Wireless-N 1000> mem 0xf2200000-0xf2201fff irq 19 at device 0.0 on pci3 . . . wlan0: Ethernet address: ##:##:##:##:##:## ... iwn0: iwn_read_firmware: ucode rev=3D0x271f0501 wlan0: link state changed to UP re0: link state changed to UP ... wlan0: link state changed to DOWN iwn0: device timeout iwn0: iwn_read_firmware: ucode rev=3D0x271f0501 iwn0: scan timeout iwn0: iwn_read_firmware: ucode rev=3D0x271f0501 wlan0: link state changed to UP iwn0: iwn_intr: fatal firmware error firmware error log: error type =3D "BAD_COMMAND" (0x00000007) program counter =3D 0x000024D8 source line =3D 0x00000446 error data =3D 0x0000000000000000 branch link =3D 0x000024D6000024D6 interrupt link =3D 0x0000082600000000 time =3D 8365 driver status: tx ring 0: qid=3D0 cur=3D0 queued=3D0=20=20 tx ring 1: qid=3D1 cur=3D0 queued=3D0=20=20 tx ring 2: qid=3D2 cur=3D0 queued=3D0=20=20 tx ring 3: qid=3D3 cur=3D2 queued=3D0=20=20 tx ring 4: qid=3D4 cur=3D58 queued=3D0=20=20 tx ring 5: qid=3D5 cur=3D0 queued=3D0=20=20 tx ring 6: qid=3D6 cur=3D0 queued=3D0=20=20 tx ring 7: qid=3D7 cur=3D0 queued=3D0=20=20 tx ring 8: qid=3D8 cur=3D0 queued=3D0=20=20 tx ring 9: qid=3D9 cur=3D0 queued=3D0=20=20 tx ring 10: qid=3D10 cur=3D0 queued=3D0=20=20 tx ring 11: qid=3D11 cur=3D0 queued=3D0=20=20 tx ring 12: qid=3D12 cur=3D0 queued=3D0=20=20 tx ring 13: qid=3D13 cur=3D0 queued=3D0=20=20 tx ring 14: qid=3D14 cur=3D0 queued=3D0=20=20 tx ring 15: qid=3D15 cur=3D0 queued=3D0=20=20 tx ring 16: qid=3D16 cur=3D0 queued=3D0=20=20 tx ring 17: qid=3D17 cur=3D0 queued=3D0=20=20 tx ring 18: qid=3D18 cur=3D0 queued=3D0=20=20 tx ring 19: qid=3D19 cur=3D0 queued=3D0=20=20 rx ring: cur=3D19 iwn0: iwn_panicked: controller panicked, iv_state =3D 5; restarting wlan0: link state changed to DOWN iwn0: iwn_read_firmware: ucode rev=3D0x271f0501 wlan0: link state changed to UP --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-214435-6>