[Inter 7260] Very slow and unstable WIFI

[BruceWouaigne]

Using an Asus Zenbook UX303L, with the last kernel, wifi is almost unusable. The connection is VERY slow and keeps dropping.

There was absolutely no problem with the linux-image-3.13.0-40-generic kernel.

Tried turning off the power management of wlan0 without any changes.

lspci -knn | grep Net -A2

02:00.0 Network controller [0280]: Intel Corporation Wireless 7260 [8086:08b1] (rev 6b)
    Subsystem: Intel Corporation Dual Band Wireless-N 7260 [8086:c160]
    Kernel driver in use: iwlwifi

Here is the speedtest output with the last kernel:

☺ ~⮀ speedtest
Retrieving speedtest.net configuration...
Retrieving speedtest.net server list...
Testing from Orange (***)...
Selecting best server based on latency...
Hosted by iperf.fr (Rouen) [315.45 km]: 15.149 ms
Testing download speed........................................
Download: 19.17 Mbits/s
Testing upload speed..................................................
Upload: 30.53 Mbits/s

And after a rollback on the 3.13

☺ ~⮀ speedtest
Retrieving speedtest.net configuration...
Retrieving speedtest.net server list...
Testing from Orange (***)...
Selecting best server based on latency...
Hosted by TestDebit.info (Limoges) [264.48 km]: 13.848 ms
Testing download speed........................................
Download: 61.95 Mbits/s
Testing upload speed..................................................
Upload: 71.33 Mbits/s

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.16.0-25-generic 3.16.0-25.33~14.04.2
ProcVersionSignature: Ubuntu 3.16.0-25.33~14.04.2-generic 3.16.7
Uname: Linux 3.16.0-25-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.5
Architecture: amd64
CurrentDesktop: GNOME
Date: Tue Dec 2 22:39:01 2014
InstallationDate: Installed on 2014-11-20 (12 days ago)
InstallationMedia: Ubuntu-GNOME 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SourcePackage: linux-lts-utopic
UpgradeStatus: No upgrade log present (probably fresh install)
---
ApportVersion: 2.14.1-0ubuntu3.5
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: bruce 2241 F.... pulseaudio
 /dev/snd/pcmC1D0p: bruce 2241 F...m pulseaudio
 /dev/snd/controlC1: bruce 2241 F.... pulseaudio
CurrentDesktop: GNOME
DistroRelease: Ubuntu 14.04
HibernationDevice: RESUME=UUID=8a3f827c-19e2-473a-aeef-d988e7b1be88
InstallationDate: Installed on 2014-11-20 (12 days ago)
InstallationMedia: Ubuntu-GNOME 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
MachineType: ASUSTeK COMPUTER INC. UX303LN
Package: linux (not installed)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-25-generic root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash acpi_osi= vt.handoff=7
ProcVersionSignature: Ubuntu 3.16.0-25.33~14.04.2-generic 3.16.7
RelatedPackageVersions:
 linux-restricted-modules-3.16.0-25-generic N/A
 linux-backports-modules-3.16.0-25-generic N/A
 linux-firmware 1.127.8
Tags: trusty
Uname: Linux 3.16.0-25-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 06/23/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX303LN.203
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX303LN
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX303LN.203:bd06/23/2014:svnASUSTeKCOMPUTERINC.:pnUX303LN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX303LN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: UX303LN
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

[penalvch (penalvch)]

BruceWouaigne, thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command, as it will automatically gather debugging information, in a terminal:
apport-collect 1398585

[BruceWouaigne (charrier-denis)]

apport information

[BruceWouaigne (charrier-denis)]

apport information

[BruceWouaigne (charrier-denis)]

apport information

[BruceWouaigne (charrier-denis)]

apport information

[BruceWouaigne (charrier-denis)]

apport information

[BruceWouaigne (charrier-denis)]

apport information

[BruceWouaigne (charrier-denis)]

apport information

[BruceWouaigne (charrier-denis)]

apport information

[BruceWouaigne (charrier-denis)]

apport information

[BruceWouaigne (charrier-denis)]

apport information

[BruceWouaigne (charrier-denis)]

apport information

[BruceWouaigne (charrier-denis)]

apport information

[BruceWouaigne (charrier-denis)]

apport information

[BruceWouaigne (charrier-denis)]

apport information

[BruceWouaigne (charrier-denis)]

apport information

[Joseph Salisbury (jsalisbury)]

I'd like to perform a reverse bisect to figure out which commit upstream fixes this regression. It would be very helpful to know the last upstream kernel that had this issue and the first kernel that did not.

Can you test the following kernels and report back?

v3.13.11.10: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.13.11.10-trusty/
v3.13.11.11: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.13.11.11-trusty/

linux-image-3.13.0-40-generic was based on the upstream 3.13.11.10 kernel, so that upstream kernel should not have the bug. If it doesn't, we can bisect betwee 3.13.11.10 and 3.13.11.11.

[Joseph Salisbury (jsalisbury)]

Some commits added in 3.13.0-41 that could be related:

464cb89 Revert "iwlwifi: mvm: treat EAPOLs like mgmt frames wrt rate"
156627a iwlwifi: dvm: drop non VO frames when flushing
46ad4b0 mac80211: add vif to flush call
ee7d9de iwlwifi: configure the LTR
006f959 mac80211: fix typo in starting baserate for rts_cts_rate_idx

[BruceWouaigne (charrier-denis)]

Ok so, same problem (wifi unstable and very slow) with the new BIOS. Here is the result of the command:

$ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
UX303LN.204
09/01/2014

Coming up next, the tests on the previous kernels!

[BruceWouaigne (charrier-denis)]

3.13.11.10 and 3.13.11.11 are working perfectly.

[Joseph Salisbury (jsalisbury)]

The v3.13.11.11 kernel does not have the bug?

http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.13.11.11-trusty/

[BruceWouaigne (charrier-denis)]

No, everything looks fine with both 3.13.11.10 and 3.13.11.11

[Pilot6 (hanipouspilot)]

@Christopher

What fixed the bug upstream?

@BruceWouaigne

Is this bug still there with 3.16.0-26.35 or 3.16.0-25.33?

[penalvch (penalvch)]

Pilot6, I added the tag with the meaning of the issue is not reproducible with the upstream kernel. However, the usage precedent of this tag is if both the problem is not reproducible in the upstream kernel, and the upstream kernel version is higher than the Ubuntu kernel after mapping. I'll remove it as it clearly caused confusion for folks, and update the definition of the tag at https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies so that this confusion is avoided in the future.

BruceWouaigne, could you please test the latest upstream kernel available from the very top line at the top of the page (the release names are irrelevant for testing, and please do not test the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue.

If the test did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested exactly shown as:
kernel-fixed-upstream-3.18-rc7

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description.

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

[BruceWouaigne (charrier-denis)]

Sorry for the delay guys, I've beed quite occupied these days...

So as you asked @Christopher, I've tried with the latest upstream kernel which is http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.18-rc7-vivid/ right?

Same problem, veeeery slow and unstable wireless.

[penalvch (penalvch)]

BruceWouaigne, the next step is to fully commit bisect from kernel 3.13.11.11 to 3.16 in order to identify the last good kernel commit, followed immediately by the first bad one. This will allow for a more expedited analysis of the root cause of your issue. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection ? Please note, finding adjacent kernel versions is not fully commit bisecting.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

[BruceWouaigne (charrier-denis)]

Ok folks, I don't know why but (before doing the commit bisect) I tried again a few kernels. And I guess I did something wrong last week because it looks like the problem is between 3.13.11.10 (which seems to work) and 3.13.11.11 (which don't)

I guess my test scenario can be the problem since I'm only doing some kind of a speed test by downloading http://cdimage.ubuntu.com/ubuntu-gnome/releases/14.10/release/ubuntu-gnome-14.10-desktop-amd64.iso

[BruceWouaigne (charrier-denis)]

Any idea why can't I find the rev Ubuntu-3.13.0-41.69 in the git://kernel.ubuntu.com/ubuntu/ubuntu-trusty.git

[Joseph Salisbury (jsalisbury)]

I started a kernel bisect between v3.13.11.10 and v3.13.11.11. The kernel bisect will require testing of about 7-10 test kernels.

I built the first test kernel, up to the following commit:
faabc0f89f64062c18fc047f0008b45556be1efd

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1398585

Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results.

Thanks in advance

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]