Re: kern/176104: [iwn] iwn0: iwn_intr: fatal firmware error

2013-12-26 Thread Michael Gmelin
The following reply was made to PR kern/176104; it has been noted by GNATS.

From: Michael Gmelin 
To: bug-follo...@freebsd.org, me...@bristol.ac.uk
Cc:  
Subject: Re: kern/176104: [iwn] iwn0: iwn_intr: fatal firmware error
Date: Thu, 26 Dec 2013 17:56:39 +

 Did you ever find a solution to this? I'm experiencing the same issue
 and it's happening way too often to ignore it.
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"


Re: kern/176104: [iwn] iwn0: iwn_intr: fatal firmware error

2013-06-26 Thread hiren panchasara
On Wed, Jun 26, 2013 at 7:10 PM, Anton Shterenlikht  wrote:
> The following reply was made to PR kern/176104; it has been noted by GNATS.
>
> From: Anton Shterenlikht 
> To: bug-follo...@freebsd.org
> Cc:
> Subject: RE: kern/176104: [iwn] iwn0: iwn_intr: fatal firmware error
> Date: Tue, 25 Jun 2013 14:28:51 +0100 (BST)
>
>  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?

AFAIK, no.

Hiren
> ___
> freebsd-wireless@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
> To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"


RE: kern/176104: [iwn] iwn0: iwn_intr: fatal firmware error

2013-06-26 Thread Anton Shterenlikht
The following reply was made to PR kern/176104; it has been noted by GNATS.

From: Anton Shterenlikht 
To: bug-follo...@freebsd.org
Cc:  
Subject: RE: kern/176104: [iwn] iwn0: iwn_intr: fatal firmware error
Date: Tue, 25 Jun 2013 14:28:51 +0100 (BST)

 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?
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"


Re: kern/176104: [iwn] iwn0: iwn_intr: fatal firmware error

2013-06-25 Thread hiren panchasara
The following reply was made to PR kern/176104; it has been noted by GNATS.

From: hiren panchasara 
To: mexas 
Cc: bug-follo...@freebsd.org
Subject: Re: kern/176104: [iwn] iwn0: iwn_intr: fatal firmware error
Date: Tue, 25 Jun 2013 08:52:43 -0700

 On Tue, Jun 25, 2013 at 4:48 AM, Anton Shterenlikht  wrote:
 > From hiren.panchas...@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:  mem 0xdf2fe000-0xdf2f 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 
 > #
 >
 > 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
 >
 >
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"


Re: kern/176104: [iwn] iwn0: iwn_intr: fatal firmware error

2013-06-25 Thread Anton Shterenlikht
The following reply was made to PR kern/176104; it has been noted by GNATS.

From: Anton Shterenlikht 
To: bug-follo...@freebsd.org, hi...@freebsd.org, me...@bristol.ac.uk
Cc:  
Subject: Re: kern/176104: [iwn] iwn0: iwn_intr: fatal firmware error
Date: Tue, 25 Jun 2013 12:48:16 +0100 (BST)

From hiren.panchas...@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:  mem 0xdf2fe000-0xdf2f 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 
 #
 
 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
 
 
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"


Re: kern/176104: [iwn] iwn0: iwn_intr: fatal firmware error

2013-06-24 Thread hiren panchasara
The following reply was made to PR kern/176104; it has been noted by GNATS.

From: hiren panchasara 
To: bug-follo...@freebsd.org, me...@bristol.ac.uk
Cc:  
Subject: Re: kern/176104: [iwn] iwn0: iwn_intr: fatal firmware error
Date: Mon, 24 Jun 2013 11:09:18 -0700

 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
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"


RE: kern/176104: [iwn] iwn0: iwn_intr: fatal firmware error

2013-06-24 Thread Anton Shterenlikht
The following reply was made to PR kern/176104; it has been noted by GNATS.

From: Anton Shterenlikht 
To: bug-follo...@freebsd.org
Cc:  
Subject: RE: kern/176104: [iwn] iwn0: iwn_intr: fatal firmware error
Date: Mon, 24 Jun 2013 09:07:42 +0100 (BST)

 This problem still persists in r252033:
 
 iwn0: iwn_intr: fatal firmware error
 firmware error log:
   error type  = "NMI_INTERRUPT_WDG" (0x0004)
   program counter = 0x046C
   source line = 0x00D0
   error data  = 0x00020703
   branch link = 0x837004C2
   interrupt link  = 0x06DA18B8
   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 :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" (0x0004)
   program counter = 0x046C
   source line = 0x00D0
   error data  = 0x00020703
   branch link = 0x837004C2
   interrupt link  = 0x06DA18B8
   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" (0x0004)
   program counter = 0x046C
   source line = 0x00D0
   error data  = 0x00020203
   branch link = 0x5CEE04C2
   interrupt link  = 0x06DE7386
   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.
 
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"


Re: kern/176104: [iwn] iwn0: iwn_intr: fatal firmware error

2013-02-13 Thread linimon
Old Synopsis: iwn0: iwn_intr: fatal firmware error
New Synopsis: [iwn] iwn0: iwn_intr: fatal firmware error

Responsible-Changed-From-To: freebsd-bugs->freebsd-wireless
Responsible-Changed-By: linimon
Responsible-Changed-When: Wed Feb 13 16:01:42 UTC 2013
Responsible-Changed-Why: 
Over to maintainer(s).

http://www.freebsd.org/cgi/query-pr.cgi?pr=176104
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"