Summary: | [iwn] iwn0: iwn_intr: fatal firmware error | ||
---|---|---|---|
Product: | Base System | Reporter: | Anton Shterenlikht <as> |
Component: | wireless | Assignee: | freebsd-wireless (Nobody) <wireless> |
Status: | Open --- | ||
Severity: | Affects Only Me | CC: | amvandemore, bugmeister, lhersch, rene |
Priority: | Normal | ||
Version: | 10.0-CURRENT | ||
Hardware: | Any | ||
OS: | Any | ||
Bug Depends on: | |||
Bug Blocks: | 278175 |
Description
Anton Shterenlikht
2013-02-13 11:40:00 UTC
Responsible Changed From-To: freebsd-bugs->freebsd-wireless Over to maintainer(s). This problem still persists in r252033: iwn0: iwn_intr: fatal firmware error firmware error log: error type = "NMI_INTERRUPT_WDG" (0x00000004) program counter = 0x0000046C source line = 0x000000D0 error data = 0x0000000207030000 branch link = 0x00008370000004C2 interrupt link = 0x000006DA000018B8 time = 200035 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=1 tx ring 4: qid=4 cur=67 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 rx ring: cur=5 NVRM: GPU at 0000:01:00: GPU-a1a1491c-c546-eda9-3b1f-54ec998e9441 ifa_del_loopback_route: deletion failed: 48 wlan0: Ethernet address: 00:21:5c:50:68:c3 wlan0: link state changed to UP wlan0: link state changed to DOWN iwn0: device timeout iwn0: iwn_intr: fatal firmware error firmware error log: error type = "NMI_INTERRUPT_WDG" (0x00000004) program counter = 0x0000046C source line = 0x000000D0 error data = 0x0000000207030000 branch link = 0x00008370000004C2 interrupt link = 0x000006DA000018B8 time = 200035 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=1 tx ring 4: qid=4 cur=67 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 rx ring: cur=22 ifa_del_loopback_route: deletion failed: 48 wlan0: Ethernet address: 00:21:5c:50:68:c3 iwn0: iwn_intr: fatal firmware error firmware error log: error type = "NMI_INTERRUPT_WDG" (0x00000004) program counter = 0x0000046C source line = 0x000000D0 error data = 0x0000000202030000 branch link = 0x00005CEE000004C2 interrupt link = 0x000006DE00007386 time = 220366 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=4 queued=0 tx ring 4: qid=4 cur=97 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 rx ring: cur=42 ifa_del_loopback_route: deletion failed: 48 wlan0: Ethernet address: 00:21:5c:50:68:c3 etc. Assuming you have 4965 chipset, this seems to be some weird firmware error. I see many users (including linux) reporting similar issues but could not find any definitive solution. At most you can try getting the latest firmware for your chipset and try it out. Probably from http://wireless.kernel.org/en/users/Drivers/iwlegacy Good luck, Hiren From hiren.panchasara@gmail.com Mon Jun 24 19:31:55 2013 Assuming you have 4965 chipset, yes, I do: iwn0@pci0:3:0:0: class=0x028000 card=0x11108086 chip=0x42308086 rev=0x61 hdr=0x00 vendor = 'Intel Corporation' device = 'PRO/Wireless 4965 AG or AGN [Kedron] Network Connection' class = network iwn0: <Intel Wireless WiFi Link 4965> mem 0xdf2fe000-0xdf2fffff irq 17 at device 0.0 on pci3 and I have: device iwn # Intel 4965/1000/5000/6000 wireless NICs. device iwn4965fw in the kernel config. this seems to be some weird firmware error. I see many users (including linux) reporting similar issues but could not find any definitive solution. At most you can try getting the latest firmware for your chipset and try it out. Probably from http://wireless.kernel.org/en/users/Drivers/iwlegacy # cat /usr/src/sys/modules/iwnfw/iwn4965/Makefile # $FreeBSD: head/sys/modules/iwnfw/iwn4965/Makefile 201209 2009-12-29 19:47:34Z rpaulo $ KMOD= iwn4965fw IMG= iwlwifi-4965-228.61.2.24 .include <bsd.kmod.mk> # According to your link, this is the latest version. However, there is a question mark (?) against it. I don't know what it means, perhaps that they are not sure if it works correctly. I wonder if an earlier version should be used instead? Thanks Anton One thing I noticed is that this problem occurs more often when running on battery, and less frequently when running from mains. Could this be related to some energy saving code? On Tue, Jun 25, 2013 at 4:48 AM, Anton Shterenlikht <mexas@bris.ac.uk> wrote: > From hiren.panchasara@gmail.com Mon Jun 24 19:31:55 2013 > > Assuming you have 4965 chipset, > > yes, I do: > > iwn0@pci0:3:0:0: class=0x028000 card=0x11108086 chip=0x42308086 rev=0x61 hdr=0x00 > vendor = 'Intel Corporation' > device = 'PRO/Wireless 4965 AG or AGN [Kedron] Network Connection' > class = network > > iwn0: <Intel Wireless WiFi Link 4965> mem 0xdf2fe000-0xdf2fffff irq 17 at device 0.0 on pci3 > > and I have: > > device iwn # Intel 4965/1000/5000/6000 wireless NICs. > device iwn4965fw > > in the kernel config. > > this seems to be some weird firmware > error. I see many users (including linux) reporting similar issues but > could not find any definitive solution. > > At most you can try getting the latest firmware for your chipset and try it out. > Probably from http://wireless.kernel.org/en/users/Drivers/iwlegacy > > # cat /usr/src/sys/modules/iwnfw/iwn4965/Makefile > # $FreeBSD: head/sys/modules/iwnfw/iwn4965/Makefile 201209 2009-12-29 19:47:34Z rpaulo $ > > KMOD= iwn4965fw > IMG= iwlwifi-4965-228.61.2.24 > > .include <bsd.kmod.mk> > # > > According to your link, this is the latest version. > However, there is a question mark (?) against it. > I don't know what it means, perhaps that they are > not sure if it works correctly. > I wonder if an earlier version should be used instead? Yeah, no harm in trying. :-) cheers, Hiren > > Thanks > > Anton > > Did you ever find a solution to this? I'm experiencing the same issue and it's happening way too often to ignore it. Still the same in r264294 amd64: iwn0: <Intel Wireless WiFi Link 4965> mem 0xdf2fe000-0xdf2fffff irq 17 at device 0.0 on pci3 iwn0: device timeout wlan0: link state changed to UP wlan0: link state changed to DOWN iwn0: iwn_intr: fatal firmware error firmware error log: error type = "NMI_INTERRUPT_WDG" (0x00000004) program counter = 0x0000046C source line = 0x000000D0 error data = 0x0000000203430000 branch link = 0x00007A10000004C2 interrupt link = 0x000006DE00007A4C time = 201920 driver status: tx ring 0: qid=0 cur=20 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=23 queued=0 tx ring 4: qid=4 cur=111 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 rx ring: cur=29 wlan0: Ethernet address: 00:21:5c:50:68:c3 iwn0: iwn_intr: fatal firmware error firmware error log: error type = "NMI_INTERRUPT_WDG" (0x00000004) program counter = 0x0000046C source line = 0x000000D0 error data = 0x0000000202030000 branch link = 0x00005CEE000004C2 interrupt link = 0x000006DE00007386 time = 270960 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=3 queued=0 tx ring 4: qid=4 cur=67 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 rx ring: cur=45 wlan0: Ethernet address: 00:21:5c:50:68:c3 wlan0: link state changed to UP iwn0: iwn_intr: fatal firmware error firmware error log: error type = "NMI_INTERRUPT_WDG" (0x00000004) program counter = 0x0000046C source line = 0x000000D0 error data = 0x0000000207030000 branch link = 0x00003BBA000004C2 interrupt link = 0x000006DE00003C5A time = 3270454051 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=3 queued=0 tx ring 4: qid=4 cur=78 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 rx ring: cur=23 wlan0: link state changed to DOWN wlan0: Ethernet address: 00:21:5c:50:68:c3 wlan0: Ethernet address: 00:21:5c:50:68:c3 iwn0: iwn_intr: fatal firmware error firmware error log: error type = "NMI_INTERRUPT_WDG" (0x00000004) program counter = 0x0000046C source line = 0x000000D0 error data = 0x0000000207030000 branch link = 0x00008370000004C2 interrupt link = 0x000006DE000018B8 time = 11589053 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=1 queued=0 tx ring 4: qid=4 cur=45 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 rx ring: cur=42 wlan0: Ethernet address: 00:21:5c:50:68:c3 wlan0: link state changed to UP See also http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/189802 Seems iwn causes panic now. I'm seeing the same (or quite similar) fatal firmware errors on my Acer 7738G with this chip: iwn0: <Intel WiFi Link 5100> mem 0xf5200000-0xf5201fff irq 17 at device 0.0 on pci3 This is on 10.0-RELEASE amd64, with firmware version iwlwifi-5150-8.24.2.2 Same issue here: FreeBSD m6600.galacticdominator.com 10.2-PRERELEASE FreeBSD 10.2-PRERELEASE #5 r286157: Sat Aug 1 10:22:41 CDT 2015 adam@m6600.galacticdominator.com:/usr/obj/usr/src/sys/M6600 amd64 It has been occuring much more frequently after I upgraded to r286157. Downing interfaces, powering off wireless, waiting 30 secs, upping interfaces seems a reliable way to recover. Aug 10 19:04:33 m6600 kernel: iwn0: iwn_intr: fatal firmware error Aug 10 19:04:33 m6600 kernel: firmware error log: Aug 10 19:04:33 m6600 kernel: error type = "NMI_INTERRUPT_WDG" (0x00000004) Aug 10 19:04:33 m6600 kernel: program counter = 0x000006B4 Aug 10 19:04:33 m6600 kernel: source line = 0x00007B20 Aug 10 19:04:33 m6600 kernel: error data = 0x0000000202230000 Aug 10 19:04:33 m6600 kernel: branch link = 0x0000067A0000071A Aug 10 19:04:33 m6600 kernel: interrupt link = 0x0000153200006874 Aug 10 19:04:33 m6600 kernel: time = 1209333766 Aug 10 19:04:33 m6600 kernel: driver status: Aug 10 19:04:33 m6600 kernel: tx ring 0: qid=0 cur=36 queued=0 Aug 10 19:04:33 m6600 kernel: tx ring 1: qid=1 cur=0 queued=0 Aug 10 19:04:33 m6600 kernel: tx ring 2: qid=2 cur=107 queued=0 Aug 10 19:04:33 m6600 kernel: tx ring 3: qid=3 cur=59 queued=0 Aug 10 19:04:33 m6600 kernel: tx ring 4: qid=4 cur=134 queued=0 Aug 10 19:04:33 m6600 kernel: tx ring 5: qid=5 cur=0 queued=0 Aug 10 19:04:33 m6600 kernel: tx ring 6: qid=6 cur=0 queued=0 Aug 10 19:04:33 m6600 kernel: tx ring 7: qid=7 cur=0 queued=0 Aug 10 19:04:33 m6600 kernel: tx ring 8: qid=8 cur=0 queued=0 Aug 10 19:04:33 m6600 kernel: tx ring 9: qid=9 cur=0 queued=0 Aug 10 19:04:33 m6600 kernel: tx ring 10: qid=10 cur=0 queued=0 Aug 10 19:04:33 m6600 kernel: tx ring 11: qid=11 cur=0 queued=0 Aug 10 19:04:33 m6600 kernel: tx ring 12: qid=12 cur=101 queued=1 Aug 10 19:04:33 m6600 kernel: tx ring 13: qid=13 cur=0 queued=0 Aug 10 19:04:33 m6600 kernel: tx ring 14: qid=14 cur=0 queued=0 Aug 10 19:04:33 m6600 kernel: tx ring 15: qid=15 cur=0 queued=0 Aug 10 19:04:33 m6600 kernel: tx ring 16: qid=16 cur=0 queued=0 Aug 10 19:04:33 m6600 kernel: tx ring 17: qid=17 cur=0 queued=0 Aug 10 19:04:33 m6600 kernel: tx ring 18: qid=18 cur=0 queued=0 Aug 10 19:04:33 m6600 kernel: tx ring 19: qid=19 cur=0 queued=0 Aug 10 19:04:33 m6600 kernel: rx ring: cur=8 batch change: For bugs that match the following - Status Is In progress AND - Untouched since 2018-01-01. AND - Affects Base System OR Documentation DO: Reset to open status. Note: I did a quick pass but if you are getting this email it might be worthwhile to double check to see if this bug ought to be closed. ^Triage: is this still a problem on supported versions of FreeBSD? no, not for me. (In reply to Mark Linimon from comment #13) My comment relates to a laptop that I haven't used since 2015 or so and newer laptops use different drivers. |