Comment 22 for bug 802902

Thanks Mike for quick answer. It is nice to find out that there is some body alive in this bug :D

It was only in this example with that
new kernel (3.11.0-2-lowlatency #1-Ubuntu SMP PREEMPT Fri Aug 16 22:06:58 UTC 2013 i686)
when Netgear usb adapter give 100% lost,
with older kernel (3.8.0-30-lowlatency #22-Ubuntu SMP PREEMPT Mon Aug 26 22:31:40 UTC 2013 x86_64 x86_64 x86_64) adapter was working, but so so slugish like hell.... and average pakage lost was up til 50% or
60%, and sometimes up til 20%.
The router was just in average 10 m distance with the wooden wall. So it is nothing to do with signal strenght
because another adapter with intel chip with all most the same signal quality gives 0% of pakage lost when pinging to router.
And a bit rate, i think, i set it it to auto or something, but if i want i can set it up til to 54mb/s
with sudo iwconfig wlan1 rate 54M fixed but there is no point set rate to 54mb/s with internet speed i have . It is the same like when your car
can go on road max 200km/h and put 400km/h on speedometer. the car will not became faster just for that ;)

And on athe laptop with 13.04 ubuntustudio with
kernel (3.8.0-30-lowlatency #22-Ubuntu SMP PREEMPT Mon Aug 26 22:31:40 UTC 2013 x86_64 x86_64 x86_64)
with setings
sudo iwconfig wlan1 rate 5.5M fixed
sudo iwconfig wlan1 frag 2346
and laptop about 15m distance from router

pinging to router gives
ping 10.0.0.138
PING 10.0.0.138 (10.0.0.138) 56(84) bytes of data.
64 bytes from 10.0.0.138: icmp_req=9 ttl=64 time=1.67 ms
64 bytes from 10.0.0.138: icmp_req=10 ttl=64 time=3.45 ms
64 bytes from 10.0.0.138: icmp_req=12 ttl=64 time=2.04 ms
64 bytes from 10.0.0.138: icmp_req=13 ttl=64 time=2.60 ms
^C
--- 10.0.0.138 ping statistics ---
15 packets transmitted, 4 received, 73% packet loss, time 14005ms
rtt min/avg/max/mdev = 1.677/2.445/3.452/0.671 ms

and with sudo iwconfig wlan1 txpower 15

ping 10.0.0.138
PING 10.0.0.138 (10.0.0.138) 56(84) bytes of data.
64 bytes from 10.0.0.138: icmp_req=4 ttl=64 time=1.71 ms
64 bytes from 10.0.0.138: icmp_req=6 ttl=64 time=1.45 ms
64 bytes from 10.0.0.138: icmp_req=7 ttl=64 time=3.05 ms
64 bytes from 10.0.0.138: icmp_req=8 ttl=64 time=1.58 ms
64 bytes from 10.0.0.138: icmp_req=9 ttl=64 time=1.75 ms
64 bytes from 10.0.0.138: icmp_req=10 ttl=64 time=1.27 ms
^C
--- 10.0.0.138 ping statistics ---
10 packets transmitted, 6 received, 40% packet loss, time 9008ms
rtt min/avg/max/mdev = 1.273/1.805/3.054/0.582 ms

So i think it is the same or allmost the same like yours situation,
because with this % of packet lost i also shall get slow download speed.

Actualy adapter in 2012 up till august was working fine. Then router was changed
and i began to have connection problems with this adpter. I don't remember what kernel was at that momem in use.
Now i began to remember that maybe i made experiment with another router dlink some have year ago,
and adapter was pinging fine, but now can not verify it 100% if I remember it 100% exactly.

Mike what is router name that your adapter is connecting ?