All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: pali.rohar@gmail.com, sre@kernel.org,
	kernel list <linux-kernel@vger.kernel.org>,
	aaro.koskinen@iki.fi, ivo.g.dimitrov.75@gmail.com,
	patrikbachan@gmail.com, serge@hallyn.com,
	linux-wireless@vger.kernel.org
Subject: N900, wl1251: wifi is now slow, even with powersave off
Date: Sat, 18 Jun 2016 17:59:46 +0200	[thread overview]
Message-ID: <20160618155946.GA16792@amd> (raw)

Hi!

Ping to N900:

64 bytes from maemo (10.0.0.8): icmp_seq=187 ttl=64 time=124 ms
64 bytes from maemo (10.0.0.8): icmp_seq=188 ttl=64 time=131 ms
64 bytes from maemo (10.0.0.8): icmp_seq=189 ttl=64 time=66.7 ms
^C
--- maemo ping statistics ---
189 packets transmitted, 189 received, 0% packet loss, time 188742ms
rtt min/avg/max/mdev = 4.382/101.866/453.145/42.395 ms
root@duo:/data/pavel#

Now on n900:

pavel@n900:/my/tui/ofone$ sudo iw dev wlan0 set power_save off
pavel@n900:/my/tui/ofone$

That should bring ping back to < 2 msec range, but nothing changes:

root@duo:/data/pavel# ping maemo
PING maemo (10.0.0.8) 56(84) bytes of data.
64 bytes from maemo (10.0.0.8): icmp_seq=1 ttl=64 time=78.5 ms
64 bytes from maemo (10.0.0.8): icmp_seq=2 ttl=64 time=101 ms
64 bytes from maemo (10.0.0.8): icmp_seq=3 ttl=64 time=18.2 ms
64 bytes from maemo (10.0.0.8): icmp_seq=4 ttl=64 time=37.5 ms
64 bytes from maemo (10.0.0.8): icmp_seq=5 ttl=64 time=58.2 ms
64 bytes from maemo (10.0.0.8): icmp_seq=6 ttl=64 time=77.6 ms
64 bytes from maemo (10.0.0.8): icmp_seq=7 ttl=64 time=98.3 ms
64 bytes from maemo (10.0.0.8): icmp_seq=8 ttl=64 time=118 ms
64 bytes from maemo (10.0.0.8): icmp_seq=9 ttl=64 time=35.8 ms
64 bytes from maemo (10.0.0.8): icmp_seq=10 ttl=64 time=55.7 ms
^C
--- maemo ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9034ms
rtt min/avg/max/mdev = 18.298/68.025/118.223/30.756 ms
root@duo:/data/pavel#

Any ideas what is going on there?

Best regards,
									Pavel


-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

             reply	other threads:[~2016-06-18 15:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-18 15:59 Pavel Machek [this message]
2016-06-18 22:55 ` N900, wl1251: wifi is now slow, even with powersave off Pavel Machek
2016-06-18 23:36   ` Pavel Machek

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160618155946.GA16792@amd \
    --to=pavel@ucw.cz \
    --cc=aaro.koskinen@iki.fi \
    --cc=ivo.g.dimitrov.75@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=pali.rohar@gmail.com \
    --cc=patrikbachan@gmail.com \
    --cc=serge@hallyn.com \
    --cc=sre@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.