https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214435
Bug ID: 214435
Summary: controller panic: iwn0: iwn_intr: fatal firmware error
error type = "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: markusalbertg...@gmail.com
CC: freebsd-am...@freebsd.org
CC: freebsd-am...@freebsd.org
Created attachment 176910
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=176910&action=edit
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 network.
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 dmesg,
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="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 booting
about some wrong pararameter, but *no panic either*.
This errormessage flashes by, to fast to read, and does not show up in either
dmesg or messages.
Putting
if_iwn_load="YES"
iwn1000fw_load="YES"
into loader.conf, does not change anything except reporting "module iwn already
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=0x271f0501
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=0x271f0501
iwn0: scan timeout
iwn0: iwn_read_firmware: ucode rev=0x271f0501
wlan0: link state changed to UP
iwn0: iwn_intr: fatal firmware error
firmware error log:
error type = "BAD_COMMAND" (0x00000007)
program counter = 0x000024D8
source line = 0x00000446
error data = 0x0000000000000000
branch link = 0x000024D6000024D6
interrupt link = 0x0000082600000000
time = 8365
driver status:
tx ring 0: qid=0 cur=0 queued=0
tx ring 1: qid=1 cur=0 queued=0
tx ring 2: qid=2 cur=0 queued=0
tx ring 3: qid=3 cur=2 queued=0
tx ring 4: qid=4 cur=58 queued=0
tx ring 5: qid=5 cur=0 queued=0
tx ring 6: qid=6 cur=0 queued=0
tx ring 7: qid=7 cur=0 queued=0
tx ring 8: qid=8 cur=0 queued=0
tx ring 9: qid=9 cur=0 queued=0
tx ring 10: qid=10 cur=0 queued=0
tx ring 11: qid=11 cur=0 queued=0
tx ring 12: qid=12 cur=0 queued=0
tx ring 13: qid=13 cur=0 queued=0
tx ring 14: qid=14 cur=0 queued=0
tx ring 15: qid=15 cur=0 queued=0
tx ring 16: qid=16 cur=0 queued=0
tx ring 17: qid=17 cur=0 queued=0
tx ring 18: qid=18 cur=0 queued=0
tx ring 19: qid=19 cur=0 queued=0
rx ring: cur=19
iwn0: iwn_panicked: controller panicked, iv_state = 5; restarting
wlan0: link state changed to DOWN
iwn0: iwn_read_firmware: ucode rev=0x271f0501
wlan0: link state changed to UP
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
freebsd-wireless@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
