[Bug 213456] Problem with iwn firmware on 11-RELEASE
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Thu Oct 13 16:38:22 UTC 2016
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213456
Bug ID: 213456
Summary: Problem with iwn firmware on 11-RELEASE
Product: Base System
Version: 11.0-STABLE
Hardware: amd64
OS: Any
Status: New
Severity: Affects Some People
Priority: ---
Component: wireless
Assignee: freebsd-wireless at FreeBSD.org
Reporter: kpect at protonmail.com
CC: freebsd-amd64 at FreeBSD.org
CC: freebsd-amd64 at FreeBSD.org
Hello.
After upgrading from 10.3 to 11.0 I've got new problems with my iwn driver on
Lenovo T430. Before 11 I didn't have such issues.
$ uname -a
FreeBSD KPECT 11.0-RELEASE-p1 FreeBSD 11.0-RELEASE-p1 #0: Tue Oct 11 20:41:43
MSK 2016 root at KPECT amd64
wlan0: Ethernet address: a4:4e:31:2a:64:5c
iwn0: iwn_read_firmware: ucode rev=0x12a80601
wlan0: link state changed to UP
wlan0: link state changed to DOWN
iwn0: device timeout
iwn0: iwn_read_firmware: ucode rev=0x12a80601
iwn0: scan timeout
iwn0: iwn_read_firmware: ucode rev=0x12a80601
wlan0: link state changed to UP
Link goes up and down several times before actual authentication which is much
longer now. Once I even got following:
Oct 12 19:07:57 KPECT kernel: wlan0: Ethernet address: a4:4e:31:2a:64:5c
Oct 12 19:07:57 KPECT kernel: iwn0: iwn_read_firmware: ucode rev=0x12a80601
Oct 12 19:07:57 KPECT kernel: wlan0: link state changed to UP
Oct 12 19:07:57 KPECT kernel: iwn0: iwn_intr: fatal firmware error
Oct 12 19:07:57 KPECT kernel: firmware error log:
Oct 12 19:07:57 KPECT kernel: error type = "UNKNOWN" (0x00000038)
Oct 12 19:07:57 KPECT kernel: program counter = 0x00009918
Oct 12 19:07:57 KPECT kernel: source line = 0x000003C4
Oct 12 19:07:57 KPECT kernel: error data = 0x0000000000000000
Oct 12 19:07:57 KPECT kernel: branch link = 0x0000991400009914
Oct 12 19:07:57 KPECT kernel: interrupt link = 0x0000D6BE00000000
Oct 12 19:07:57 KPECT kernel: time = 7449
Oct 12 19:07:57 KPECT kernel: driver status:
Oct 12 19:07:57 KPECT kernel: tx ring 0: qid=0 cur=0 queued=0
Oct 12 19:07:57 KPECT kernel: tx ring 1: qid=1 cur=0 queued=0
Oct 12 19:07:57 KPECT kernel: tx ring 2: qid=2 cur=0 queued=0
Oct 12 19:07:57 KPECT kernel: tx ring 3: qid=3 cur=2 queued=0
Oct 12 19:07:57 KPECT kernel: tx ring 4: qid=4 cur=0 queued=0
Oct 12 19:07:57 KPECT kernel: tx ring 5: qid=5 cur=0 queued=0
Oct 12 19:07:57 KPECT kernel: tx ring 6: qid=6 cur=0 queued=0
Oct 12 19:07:57 KPECT kernel: tx ring 7: qid=7 cur=0 queued=0
Oct 12 19:07:57 KPECT kernel: tx ring 8: qid=8 cur=0 queued=0
Oct 12 19:07:57 KPECT kernel: tx ring 9: qid=9 cur=83 queued=0
Oct 12 19:07:57 KPECT kernel: tx ring 10: qid=10 cur=0 queued=0
Oct 12 19:07:57 KPECT kernel: tx ring 11: qid=11 cur=0 queued=0
Oct 12 19:07:57 KPECT kernel: tx ring 12: qid=12 cur=0 queued=0
Oct 12 19:07:57 KPECT kernel: tx ring 13: qid=13 cur=0 queued=0
Oct 12 19:07:57 KPECT kernel: tx ring 14: qid=14 cur=0 queued=0
Oct 12 19:07:57 KPECT kernel: tx ring 15: qid=15 cur=0 queued=0
Oct 12 19:07:57 KPECT kernel: tx ring 16: qid=16 cur=0 queued=0
Oct 12 19:07:57 KPECT kernel: tx ring 17: qid=17 cur=0 queued=0
Oct 12 19:07:57 KPECT kernel: tx ring 18: qid=18 cur=0 queued=0
Oct 12 19:07:57 KPECT kernel: tx ring 19: qid=19 cur=0 queued=0
Oct 12 19:07:57 KPECT kernel: rx ring: cur=5
Oct 12 19:07:57 KPECT kernel: iwn0: iwn_panicked: controller panicked, iv_state
= 5; restarting
Oct 12 19:07:57 KPECT kernel: wlan0: link state changed to DOWN
Oct 12 19:07:57 KPECT kernel: iwn0: iwn_read_firmware: ucode rev=0x12a80601
Oct 12 19:07:57 KPECT kernel: wlan0: link state changed to UP
Oct 12 19:07:57 KPECT kernel: wlan0: link state changed to DOWN
Oct 12 19:07:57 KPECT kernel: iwn0: device timeout
Oct 12 19:07:57 KPECT kernel: iwn0: iwn_read_firmware: ucode rev=0x12a80601
Oct 12 19:07:57 KPECT kernel: iwn0: scan timeout
Oct 12 19:07:57 KPECT kernel: iwn0: iwn_read_firmware: ucode rev=0x12a80601
Oct 12 19:07:57 KPECT kernel: wlan0: link state changed to UP
Regards,
Sergey.
--
You are receiving this mail because:
You are on the CC list for the bug.
More information about the freebsd-amd64
mailing list