Skip to contentSkip to conversation

N900, wl1251: wifi is now slow, even with powersave off

DISCUSSION Pavel Machek 1 participant 3 messages Jun 18, 2016

lore
Share & tools
lore
#0 lore 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

Signature · 2 lines
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
#1 lore raw

Hi!

Quoted 13 lines

Ping to N900:

64 bytes from maemo (10.0.0.8): icmp_seq=187 ttl=64 time=124 ms 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:

Quoted 7 lines
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
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?

v4.4: works ok, rtt min/avg/max/mdev = 2.111/2.243/2.524/0.150 ms v4.5-rc0: can't get wifi to work.
v4.6: slow as described.
v4.7-rc3: slow as described.

Even confirming you see same problem would help :-).

Thanks,
Pavel

Signature · 2 lines
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
#2 lore raw
Quoted 21 lines · Pavel Machek

Hi!

Quoted 19 lines

Ping to N900:

64 bytes from maemo (10.0.0.8): icmp_seq=187 ttl=64 time=124 ms 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
rtt min/avg/max/mdev = 18.298/68.025/118.223/30.756 ms
root@duo:/data/pavel#
Quoted 4 lines
Quoted 1 line

Any ideas what is going on there?

v4.4: works ok, rtt min/avg/max/mdev = 2.111/2.243/2.524/0.150 ms v4.5-rc0: can't get wifi to work.

v4.5: slow as described.

Quoted 2 lines

v4.6: slow as described.
v4.7-rc3: slow as described.

Hmm. If wifi is truly broken in -rc0, I'm looking for some fun bisect :-(.

Pavel

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