Bug 92731 - High latency with Intel wireless 7260
Summary: High latency with Intel wireless 7260
Status: CLOSED WILL_NOT_FIX
Alias: None
Product: Networking
Classification: Unclassified
Component: Wireless (show other bugs)
Hardware: Intel Linux
: P1 normal
Assignee: networking_wireless@kernel-bugs.osdl.org
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-02-04 22:03 UTC by anuppari
Modified: 2015-02-10 18:32 UTC (History)
1 user (show)

See Also:
Kernel Version: 3.18.3-031803-generic
Subsystem:
Regression: No
Bisected commit-id:


Attachments
dmesg output (81.08 KB, text/plain)
2015-02-05 17:49 UTC, anuppari
Details
dmesg output with new firmware (77.74 KB, text/plain)
2015-02-10 15:25 UTC, anuppari
Details
link info (229 bytes, text/plain)
2015-02-10 15:25 UTC, anuppari
Details
ping with power save off (904 bytes, text/plain)
2015-02-10 16:12 UTC, anuppari
Details
ping with power save on (902 bytes, text/plain)
2015-02-10 16:12 UTC, anuppari
Details
ping local server with power save off (1.28 KB, text/plain)
2015-02-10 16:15 UTC, anuppari
Details
ping local server with power save on (1.27 KB, text/plain)
2015-02-10 16:16 UTC, anuppari
Details

Description anuppari 2015-02-04 22:03:59 UTC
I'm getting high and variable latency with this wifi. If I plug in a usb wifi dongle, I get ~15 +/- 0.1 ms ping to 8.8.8.8. With the in built wifi, I get anywhere from 50 to 1000+ ms latency. I'm running Ubuntu 14.04. Based on others issues with this wifi card, I updated to an upstream kernel, version 3.18.3, which enabled wifi, but still high latency.
Comment 1 anuppari 2015-02-04 22:04:55 UTC
Let me know if any additional information is needed.
Comment 2 Emmanuel Grumbach 2015-02-05 16:57:39 UTC
Please attach dmesg output.
Comment 3 anuppari 2015-02-05 17:49:17 UTC
Created attachment 165941 [details]
dmesg output
Comment 4 Emmanuel Grumbach 2015-02-09 06:57:38 UTC
please try to disable power save.

sudo iw wlan0 set power_save off
Comment 5 anuppari 2015-02-09 13:52:11 UTC
That has worked!

Is there a way to permanently disable power save, or do I need to turn it off at every boot? Also, will this change be pushed into the upstream kernel, at least for this wifi card?
Comment 6 Emmanuel Grumbach 2015-02-09 13:54:29 UTC
disabling power save should not be pushed to upstream kernel. If power save causes high latency in Tx, then there is a bug. Power save can cause issues in Rx, not in Tx.

You can add a module parameter for iwlmvm:

options iwlmvm power_scheme=1
Comment 7 anuppari 2015-02-09 13:58:13 UTC
The only way I have been able to reproducibly test high latency is via ping, both pinging from this problem machine to other machines and pinging from other machines to this machine. From my understanding, either way uses both Tx and Rx. Is there a way to check only one or the other?

And even if power save is causing issues in only Rx, isn't that also a bug?
Comment 8 Emmanuel Grumbach 2015-02-09 14:03:36 UTC
(In reply to anuppari from comment #7)
> The only way I have been able to reproducibly test high latency is via ping,
> both pinging from this problem machine to other machines and pinging from
> other machines to this machine. From my understanding, either way uses both
> Tx and Rx. Is there a way to check only one or the other?
> 

The question here is where you do your ping command.
You need to ping from the machine that has the 7260.

> And even if power save is causing issues in only Rx, isn't that also a bug?

No - that's the way WiFi works
Comment 9 anuppari 2015-02-09 14:07:38 UTC
If I ping from the machine with the 7260, I get latency issues (without power save off). I also get high ping time if I ping the 7260 machine from another machine. So it seems to be a problem both ways, at least with power save on. With power save off, it works fine both ways.

How do I set that module parameter? I tried running that command in the terminal but there is no options command. Does that line need to be added to a file?
Comment 10 Emmanuel Grumbach 2015-02-10 06:35:17 UTC
can you a more recent firmware?

curl https://git.kernel.org/cgit/linux/kernel/git/iwlwifi/linux-firmware.git/plain/iwlwifi-7260-10.ucode?id=c3d350ee05a8cf15c119af0fd1a60cd8595379c2 > iwlwifi-7260-10.ucode
sudo cp iwlwifi-7260-10.ucode /lib/firmware/

reboot

I'd like to know if this firmware will solve your latency problems with power save enabled.
Comment 11 anuppari 2015-02-10 14:04:17 UTC
Latency is still present with the new firmware.
Comment 12 Emmanuel Grumbach 2015-02-10 14:39:23 UTC
can you please share your dmesg with the new firmware?
Also - I'd like to see the output of

iw wlan0 link
Comment 13 anuppari 2015-02-10 15:25:17 UTC
Created attachment 166281 [details]
dmesg output with new firmware
Comment 14 anuppari 2015-02-10 15:25:38 UTC
Created attachment 166291 [details]
link info
Comment 15 Emmanuel Grumbach 2015-02-10 15:50:01 UTC
all seems fine here...

please paste the output of ping when it is run from the 7260. Thanks.
Comment 16 anuppari 2015-02-10 16:12:32 UTC
Created attachment 166301 [details]
ping with power save off
Comment 17 anuppari 2015-02-10 16:12:53 UTC
Created attachment 166311 [details]
ping with power save on
Comment 18 anuppari 2015-02-10 16:15:40 UTC
Created attachment 166321 [details]
ping local server with power save off
Comment 19 anuppari 2015-02-10 16:16:03 UTC
Created attachment 166331 [details]
ping local server with power save on
Comment 20 anuppari 2015-02-10 16:17:01 UTC
I added pinging a local server. This really shows the difference with/without power management
Comment 21 Emmanuel Grumbach 2015-02-10 17:35:28 UTC
you were talking about 1000ms, here I can ~60ms... It is not the same...
I can't say that these number are great but for sure, no real bug here.
That can also be related to the AP.

Closing this bug.
Comment 22 anuppari 2015-02-10 18:32:01 UTC
I think the new firmware helped a little with the latency. But you can see when pinging the local server, there is an order of magnitude difference between with and without power management (~1 ms to ~60). That is not insignificant.

Note You need to log in before you can comment on or make changes to this bug.