Skip site navigation (1)Skip section navigation (2)

Site Navigation

PRs for tag 'iwn'

This is an experimental report containing PRs for tag 'iwn' as of 5-30-2014. GNATS has no finer-grained categorization than 'kern', 'bin', 'ports', and so forth. To augment this, the bugmeisters have adopted the convention of adding '[<tagname>]' to the Synopsis field. Consider this a prototype of a better search function.

This report is generated statically.

Please give feedback on this report to Thanks.

PRs for tag 'iwn':
o2014/02/13kern/186733wireless[iwn] iwn device (5100) periodically times out killing network connectivity
o2014/01/02kern/185425wireless[iwn] iwn difficulties in busy radio environments
o2013/12/13kern/184756wireless[iwn] iwn(4) (5100 model) radio peridiocally gets disabled on Thinkpad X200
o2013/11/07kern/183759wireless[iwn] [wlan] Interface dies, OACTIVE set on wlan0
o2013/10/29kern/183430wireless[iwn] latest change to the rate code setup uses 11n rates on an 11n channel when 11n rates aren't provided
o2013/10/29kern/183428wireless[net80211] [iwn] Some APs seem to announce HT but no HT rates
o2013/10/24kern/183259[iwn] [4965] transmit seems to fail after a while
o2013/08/31kern/181694wireless[iwn] [suspend/resume] [patch] Initialize hardware in iwn(4) resume code
o2013/08/08kern/181132wireless[iwn] stream calculation is wrong for the Intel 4965
o2013/03/29kern/177465wireless[iwn] 20%-100% packet loss with iwn driver
o2013/02/13kern/176104wireless[iwn] iwn0: iwn_intr: fatal firmware error
o2013/01/10kern/175183wireless[iwn] iwn(4) becomes unresponsive during initial configuration
o2013/01/05kern/175053wireless[iwn] iwn firmware error on 9-stable with Ultimate-N 6300
o2012/11/25kern/173917wireless[iwn] wpa-supplicant issues on iwn
o2012/06/26kern/169433bschmidt[iwn] iwn(4) doesn't support 6235 chip.
o2012/05/12kern/167828wireless[iwn] iwn(4) doesn't recover automatically after firmware crash during roaming
o2011/12/09kern/163154[iwn] fatal firmware error on 9.0-RC3
o2011/10/05kern/161293wireless[iwn] hang at startup when starting network
18 problems total.

Bugs can be in one of several states:

o - open
A problem report has been submitted, no sanity checking performed.
a - analyzed
The problem is understood and a solution is being sought.
f - feedback
Further work requires additional information from the originator or the community - possibly confirmation of the effectiveness of a proposed solution.
p - patched
A patch has been committed, but some issues (MFC and / or confirmation from originator) are still open.
r - repocopy
The resolution of the problem report is dependent on a repocopy operation within the CVS repository which is awaiting completion.
s - suspended
The problem is not being worked on, due to lack of information or resources. This is a prime candidate for somebody who is looking for a project to do. If the problem cannot be solved at all, it will be closed, rather than suspended.
c - closed
A problem report is closed when any changes have been integrated, documented, and tested -- or when fixing the problem is abandoned.