Return-path: Received: from mx.logic.tuwien.ac.at ([128.130.175.19]:45354 "EHLO mx.logic.tuwien.ac.at" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752965Ab2LQNtB (ORCPT ); Mon, 17 Dec 2012 08:49:01 -0500 Date: Mon, 17 Dec 2012 22:25:41 +0900 From: Norbert Preining To: Larry Finger Cc: linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org, Borislav Petkov Subject: Re: rtl8192se: ping router gives mdev of 25387.102??? Message-ID: <20121217132541.GA19386@gamma.logic.tuwien.ac.at> (sfid-20121217_144927_942986_2ECF9DA1) References: <505251FD.2090901@lwfinger.net> <5051EF3C.3020401@lwfinger.net> <20120913222850.GA438@gandalf.dynalias.org> <20120915041513.GF30623@gamma.logic.tuwien.ac.at> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <20120915041513.GF30623@gamma.logic.tuwien.ac.at> Sender: linux-wireless-owner@vger.kernel.org List-ID: There we go again, rtl is completely hosed ... $ ping 192.168.0.1 # this is my router!!! PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data. >From 192.168.0.6 icmp_seq=21 Destination Host Unreachable >From 192.168.0.6 icmp_seq=22 Destination Host Unreachable >From 192.168.0.6 icmp_seq=23 Destination Host Unreachable >From 192.168.0.6 icmp_seq=24 Destination Host Unreachable >From 192.168.0.6 icmp_seq=25 Destination Host Unreachable >From 192.168.0.6 icmp_seq=26 Destination Host Unreachable >From 192.168.0.6 icmp_seq=27 Destination Host Unreachable >From 192.168.0.6 icmp_seq=28 Destination Host Unreachable >From 192.168.0.6 icmp_seq=29 Destination Host Unreachable >From 192.168.0.6 icmp_seq=30 Destination Host Unreachable >From 192.168.0.6 icmp_seq=31 Destination Host Unreachable >From 192.168.0.6 icmp_seq=32 Destination Host Unreachable >From 192.168.0.6 icmp_seq=33 Destination Host Unreachable >From 192.168.0.6 icmp_seq=34 Destination Host Unreachable >From 192.168.0.6 icmp_seq=35 Destination Host Unreachable >From 192.168.0.6 icmp_seq=36 Destination Host Unreachable >From 192.168.0.6 icmp_seq=37 Destination Host Unreachable >From 192.168.0.6 icmp_seq=38 Destination Host Unreachable 64 bytes from 192.168.0.1: icmp_req=1 ttl=255 time=38455 ms 64 bytes from 192.168.0.1: icmp_req=2 ttl=255 time=37453 ms 64 bytes from 192.168.0.1: icmp_req=3 ttl=255 time=36445 ms 64 bytes from 192.168.0.1: icmp_req=4 ttl=255 time=35437 ms 64 bytes from 192.168.0.1: icmp_req=5 ttl=255 time=34429 ms 64 bytes from 192.168.0.1: icmp_req=6 ttl=255 time=33421 ms 64 bytes from 192.168.0.1: icmp_req=7 ttl=255 time=32413 ms 64 bytes from 192.168.0.1: icmp_req=8 ttl=255 time=31405 ms 64 bytes from 192.168.0.1: icmp_req=9 ttl=255 time=30397 ms 64 bytes from 192.168.0.1: icmp_req=10 ttl=255 time=29388 ms 64 bytes from 192.168.0.1: icmp_req=11 ttl=255 time=28381 ms 64 bytes from 192.168.0.1: icmp_req=12 ttl=255 time=27373 ms 64 bytes from 192.168.0.1: icmp_req=13 ttl=255 time=26365 ms 64 bytes from 192.168.0.1: icmp_req=14 ttl=255 time=25357 ms 64 bytes from 192.168.0.1: icmp_req=15 ttl=255 time=24349 ms 64 bytes from 192.168.0.1: icmp_req=16 ttl=255 time=23341 ms 64 bytes from 192.168.0.1: icmp_req=17 ttl=255 time=22333 ms 64 bytes from 192.168.0.1: icmp_req=18 ttl=255 time=21325 ms 64 bytes from 192.168.0.1: icmp_req=19 ttl=255 time=20317 ms 64 bytes from 192.168.0.1: icmp_req=20 ttl=255 time=19309 ms 64 bytes from 192.168.0.1: icmp_req=39 ttl=255 time=207 ms 64 bytes from 192.168.0.1: icmp_req=40 ttl=255 time=1.36 ms 64 bytes from 192.168.0.1: icmp_req=41 ttl=255 time=1.22 ms 64 bytes from 192.168.0.1: icmp_req=42 ttl=255 time=1.76 ms ^C --- 192.168.0.1 ping statistics --- 42 packets transmitted, 24 received, +18 errors, 42% packet loss, time 41261ms rtt min/avg/max/mdev = 1.229/24079.534/38455.055/11983.493 ms, pipe 39 $ Yeahhhhh..... we are talking about my router, and a stability that is below the quality of morse code ... On Sa, 15 Sep 2012, Norbert Preining wrote: > Hi Larry, hi all, > > On Fr, 14 Sep 2012, wrote: > > I am running on top of default kernel git, will try wireless-testing, too. > > I tried now with wireless-testing from yesterday, and had the same problem. > Actually, I got even *better* results: > 64 bytes from 192.168.0.1: icmp_req=75 ttl=255 time=137856 ms > 64 bytes from 192.168.0.1: icmp_req=76 ttl=255 time=136848 ms > 64 bytes from 192.168.0.1: icmp_req=78 ttl=255 time=134943 ms > > ... > rtt min/avg/max/mdev = 1.110/46967.879/137856.232/49666.671 ms, pipe 138 > > > So now we are mdev of 50secs sometimes ;-) > > > Another interesting things: > At home I have the problems with the NEC router, but I am now at > the university. I am writing this email over a very very stable > ssh link to another server. > > Here is the output iof ifconfig: > $ ifconfig > eth0 Link encap:Ethernet HWaddr 60:eb:69:c9:0c:ea > UP BROADCAST MULTICAST MTU:1500 Metric:1 > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) > > lo Link encap:Local Loopback > inet addr:127.0.0.1 Mask:255.0.0.0 > UP LOOPBACK RUNNING MTU:16436 Metric:1 > RX packets:20418 errors:0 dropped:0 overruns:0 frame:0 > TX packets:20418 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:1950587 (1.8 MiB) TX bytes:1950587 (1.8 MiB) > > wlan0 Link encap:Ethernet HWaddr 88:9f:fa:f9:07:28 > inet addr:150.65.206.200 Bcast:150.65.207.255 Mask:255.255.252.0 > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:232640 errors:0 dropped:1 overruns:0 frame:0 > TX packets:69798 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:85599897 (81.6 MiB) TX bytes:8925832 (8.5 MiB) > > > But the kernel is convinced that I am not connected ...: > $ iw dev wlan0 link > Not connected. > $ iwconfig wlan0 > wlan0 IEEE 802.11bgn ESSID:off/any > Mode:Managed Access Point: Not-Associated Tx-Power=20 dBm > Retry long limit:7 RTS thr=2347 B Fragment thr:off > Encryption key:off > Power Management:off > > > And no, I guarantee you there is no ethernet cable plugged in ;-) > > I can only assume that is a problem with iwconfig/iw being too old, > although according to the output of iwconfig it is fine: > # iw --version > iw version 3.4 > # iwconfig --version > iwconfig Wireless-Tools version 30 > Compatible with Wireless Extension v11 to v22. > > Kernel Currently compiled with Wireless Extension v22. > > wlan0 Recommend Wireless Extension v21 or later, > Currently compiled with Wireless Extension v22. > > # uname -a > Linux tofuschnitzel 3.6.0-rc5-wl+ #19 SMP PREEMPT Fri Sep 14 13:14:15 JST 2012 x86_64 GNU/Linux > > > Best wishes > > Norbert > ------------------------------------------------------------------------ > Norbert Preining preining@{jaist.ac.jp, logic.at, debian.org} > JAIST, Japan TeX Live & Debian Developer > DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094 > ------------------------------------------------------------------------ > CHICAGO (n.) > The foul-smelling wind which precedes an underground railway train. > --- Douglas Adams, The Meaning of Liff Best wishes Norbert ------------------------------------------------------------------------ Norbert Preining preining@{jaist.ac.jp, logic.at, debian.org} JAIST, Japan TeX Live & Debian Developer DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094 ------------------------------------------------------------------------ SPITTAL OF GLENSHEE (n.) That which has to be cleaned off castle floors in the morning after a bagpipe contest or vampire attack. --- Douglas Adams, The Meaning of Liff