[ltp] Re: Timeout with IBM minipci cvs atheros and 2.6

[Steve Krulewitz]

I've also had the timeout problem on my t40p and madwifi on both 2.4.25 
and 2.6.4.  Here are some typical ping times from my laptop to the 
wireless router (SMC 7400AWBR):

  steve@doolittle:~$ ping 192.168.123.254
  PING 192.168.123.254 (192.168.123.254): 56 data bytes
  64 bytes from 192.168.123.254: icmp_seq=0 ttl=64 time=9022.8 ms
  64 bytes from 192.168.123.254: icmp_seq=1 ttl=64 time=8029.7 ms
  64 bytes from 192.168.123.254: icmp_seq=2 ttl=64 time=7038.9 ms
  64 bytes from 192.168.123.254: icmp_seq=3 ttl=64 time=6038.9 ms
  64 bytes from 192.168.123.254: icmp_seq=4 ttl=64 time=5039.9 ms
  64 bytes from 192.168.123.254: icmp_seq=5 ttl=64 time=4040.7 ms
  64 bytes from 192.168.123.254: icmp_seq=6 ttl=64 time=3041.9 ms
  64 bytes from 192.168.123.254: icmp_seq=7 ttl=64 time=2044.0 ms
  64 bytes from 192.168.123.254: icmp_seq=8 ttl=64 time=1046.0 ms
  64 bytes from 192.168.123.254: icmp_seq=9 ttl=64 time=48.6 ms
  64 bytes from 192.168.123.254: icmp_seq=10 ttl=64 time=5.9 ms
  64 bytes from 192.168.123.254: icmp_seq=11 ttl=64 time=4.3 ms
  64 bytes from 192.168.123.254: icmp_seq=12 ttl=64 time=4.2 ms
  ... a few minutes pass ...
  64 bytes from 192.168.123.254: icmp_seq=77 ttl=64 time=4.1 ms
  64 bytes from 192.168.123.254: icmp_seq=78 ttl=64 time=4.1 ms
  64 bytes from 192.168.123.254: icmp_seq=79 ttl=64 time=4.1 ms
  64 bytes from 192.168.123.254: icmp_seq=81 ttl=64 time=11160.4 ms
  64 bytes from 192.168.123.254: icmp_seq=82 ttl=64 time=10161.3 ms
  64 bytes from 192.168.123.254: icmp_seq=83 ttl=64 time=9162.4 ms
  64 bytes from 192.168.123.254: icmp_seq=84 ttl=64 time=8163.3 ms
  64 bytes from 192.168.123.254: icmp_seq=85 ttl=64 time=7164.5 ms
  64 bytes from 192.168.123.254: icmp_seq=86 ttl=64 time=6167.5 ms
  64 bytes from 192.168.123.254: icmp_seq=87 ttl=64 time=5171.1 ms
  64 bytes from 192.168.123.254: icmp_seq=88 ttl=64 time=4174.8 ms
  64 bytes from 192.168.123.254: icmp_seq=89 ttl=64 time=3180.4 ms
  64 bytes from 192.168.123.254: icmp_seq=90 ttl=64 time=2182.7 ms
  64 bytes from 192.168.123.254: icmp_seq=91 ttl=64 time=1185.8 ms
  64 bytes from 192.168.123.254: icmp_seq=92 ttl=64 time=187.2 ms
  64 bytes from 192.168.123.254: icmp_seq=94 ttl=64 time=12016.2 ms
  64 bytes from 192.168.123.254: icmp_seq=95 ttl=64 time=11018.0 ms
  64 bytes from 192.168.123.254: icmp_seq=96 ttl=64 time=10019.1 ms
  64 bytes from 192.168.123.254: icmp_seq=97 ttl=64 time=9021.1 ms
  64 bytes from 192.168.123.254: icmp_seq=98 ttl=64 time=8021.4 ms
  64 bytes from 192.168.123.254: icmp_seq=99 ttl=64 time=7022.4 ms
  64 bytes from 192.168.123.254: icmp_seq=100 ttl=64 time=6029.5 ms
  64 bytes from 192.168.123.254: icmp_seq=101 ttl=64 time=5029.5 ms
  64 bytes from 192.168.123.254: icmp_seq=102 ttl=64 time=4029.5 ms
  64 bytes from 192.168.123.254: icmp_seq=103 ttl=64 time=3030.6 ms
  64 bytes from 192.168.123.254: icmp_seq=104 ttl=64 time=2032.5 ms
  64 bytes from 192.168.123.254: icmp_seq=105 ttl=64 time=1034.9 ms
  64 bytes from 192.168.123.254: icmp_seq=106 ttl=64 time=37.0 ms
  64 bytes from 192.168.123.254: icmp_seq=107 ttl=64 time=4.2 ms
  64 bytes from 192.168.123.254: icmp_seq=108 ttl=64 time=4.0 ms
  64 bytes from 192.168.123.254: icmp_seq=109 ttl=64 time=4.2 ms

Because of this, I've given up on madwifi and have been using the 
linuxant driver wrapper and it has been (mostly) flawless.

cheers,
-steve