Red Hat Bugzilla – Bug 802056
ath9k_htc: Unable to allocate URBs
Last modified: 2012-11-14 11:38:41 EST
Card: Netgear WNA1100
[root@system ~]# uname -r
[root@system ~]# lsusb | grep -i netgear
Bus 003 Device 003: ID 0846:9030 NetGear, Inc. WNA1100 Wireless-N 150 [Atheros AR9271]
[root@system ~]# dmesg | grep -E 'usb 3-2|ath9k'
[ 429.296229] usb 3-2: new high-speed USB device number 3 using xhci_hcd
[ 429.322854] usb 3-2: New USB device found, idVendor=0846, idProduct=9030
[ 429.322857] usb 3-2: New USB device strings: Mfr=16, Product=32, SerialNumber=48
[ 429.322860] usb 3-2: Product: WNA1100
[ 429.322862] usb 3-2: Manufacturer: NETGEAR WNA
[ 429.322864] usb 3-2: SerialNumber: 12345
[ 429.323304] usb 3-2: ep 0x1 - rounding interval to 32768 microframes, ep desc says 0 microframes
[ 429.323312] usb 3-2: ep 0x82 - rounding interval to 32768 microframes, ep desc says 0 microframes
[ 429.323319] usb 3-2: ep 0x5 - rounding interval to 32768 microframes, ep desc says 0 microframes
[ 429.323323] usb 3-2: ep 0x6 - rounding interval to 32768 microframes, ep desc says 0 microframes
[ 429.737919] usb 3-2: ath9k_htc: Transferred FW: htc_9271.fw, size: 51272
[ 429.752019] usb 3-2: ath9k_htc: Unable to allocate URBs
[ 429.752035] ath9k_htc: probe of 3-2:1.0 failed with error -22
[ 429.752059] usbcore: registered new interface driver ath9k_htc
There is a patch on the mailing list that says it fixes this issue. I don't know if it's already applied in Fedora but here's the link - http://comments.gmane.org/gmane.linux.kernel.wireless.general/58495
# Mass update to all open bugs.
Kernel 3.6.2-1.fc16 has just been pushed to updates.
This update is a significant rebase from the previous version.
Please retest with this kernel, and let us know if your problem has been fixed.
In the event that you have upgraded to a newer release and the bug you reported
is still present, please change the version field to the newest release you have
encountered the issue with. Before doing so, please ensure you are testing the
latest kernel update in that release and attach any new and relevant information
you may have gathered.
If you are not the original bug reporter and you still experience this bug,
please file a new report, as it is possible that you may be seeing a
(Please don't clone this bug, a fresh bug referencing this bug in the comment is sufficient).
With no response, we are closing this bug under the assumption that it is no longer an issue. If you still experience this bug, please feel free to reopen the bug report.