iwlwifi restarts randomly in xenial

[Chris Stratford]

Recently installed xenial on a Lenovo Yoga 2-13 (Intel 7260 wifi card). On wily it worked perfectly, on xenial it regularly appears to restart the wifi connection (the end result is that I lose any vpn connections, as they don't seem to notice the restart, but that's another issue).

In general use, I get periodic "wlp1s0: WPA: Group rekeying completed" messages in syslog (and used to get these in wily, too), but now, after a random amount of time (over the weekend it was several hours, this morning it was about 10 minutes, so it might be related to the amount of network traffic) I get "kernel: [13983.248157] wlp1s0: authenticate with 00:8a:ae:c9:9a:d8" (presumably my wifi router) and the usual wifi startup stuff including frequency lists, etc.

It also always logs "systemd-udevd[30319]: Process '/sbin/crda' failed with exit code 249." every time (I'm not sure if this is relevant)

After reading old, but similar bug reports, I've tried changing some of the module options: "11n_disable=1" and "11n_disable=8", but these had no effect. I've also tried the older firmware that wily used (/lib/firmware/iwlwifi-7260-13.ucode), but again, no improvement.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-18-generic 4.4.0-18.34
ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
Uname: Linux 4.4.0-18-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: chris 7058 F.... pulseaudio
 /dev/snd/controlC1: chris 7058 F.... pulseaudio
CurrentDesktop: Unity
Date: Mon Apr 18 09:01:26 2016
HibernationDevice: RESUME=UUID=f92d915f-d552-4e5b-989d-70e936ce4f74
InstallationDate: Installed on 2016-04-14 (3 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
MachineType: LENOVO 20344
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-18-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro noprompt quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-18-generic N/A
 linux-backports-modules-4.4.0-18-generic N/A
 linux-firmware 1.157
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/09/2014
dmi.bios.vendor: LENOVO
dmi.bios.version: 96CN25WW(V1.11)
dmi.board.asset.tag: 31900058WIN
dmi.board.name: INVALID
dmi.board.vendor: LENOVO
dmi.board.version: 31900058WIN
dmi.chassis.asset.tag: 31900058WIN
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo Yoga 2 13
dmi.modalias: dmi:bvnLENOVO:bvr96CN25WW(V1.11):bd07/09/2014:svnLENOVO:pn20344:pvrLenovoYoga213:rvnLENOVO:rnINVALID:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoYoga213:
dmi.product.name: 20344
dmi.product.version: Lenovo Yoga 2 13
dmi.sys.vendor: LENOVO

[Chris Stratford (chris-gondolin)]

In the attached WifiSyslog.txt an example of this problem starts at "Apr 18 08:17:42" (followed by a network restart to get the vpn working again)

[Brad Figg (brad-figg)]

This change was made by a bot.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.6 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.6-rc4-wily/

[Chris Stratford (chris-gondolin)]

No change with an upstream kernel, I'm afraid. It lasted about 30 mins.

$ uname -a
Linux anduin 4.6.0-040600rc4-generic #201604172330 SMP Mon Apr 18 03:32:32 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

It did log something that I hadn't seen before, this time:

Apr 19 10:01:27 anduin kernel: [ 23.775807] wlp1s0: authenticate with 00:8a:ae:c9:9a:d8
Apr 19 10:01:27 anduin NetworkManager[1023]: <info> [1461056487.0028] device (wlp1s0): supplicant interface state:
 inactive -> authenticating
Apr 19 10:01:27 anduin wpa_supplicant[1351]: wlp1s0: Trying to associate with 00:8a:ae:c9:9a:d8 (SSID='BTHub5-8KRS'
 freq=2437 MHz)

...

Apr 19 10:28:45 anduin wpa_supplicant[1351]: wlp1s0: SME: Trying to authenticate with 00:8a:ae:c9:9a:d9 (SSID='BTHub5-8KRS' freq=5240 MHz)
Apr 19 10:28:45 anduin kernel: [ 1662.238729] wlp1s0: disconnect from AP 00:8a:ae:c9:9a:d8 for new auth to 00:8a:ae:c9:9a:d9
Apr 19 10:28:45 anduin kernel: [ 1662.248214] wlp1s0: authenticate with 00:8a:ae:c9:9a:d9
Apr 19 10:28:45 anduin kernel: [ 1662.252410] wlp1s0: send auth to 00:8a:ae:c9:9a:d9 (try 1/3)
Apr 19 10:28:45 anduin wpa_supplicant[1351]: wlp1s0: Trying to associate with 00:8a:ae:c9:9a:d9 (SSID='BTHub5-8KRS' freq=5240 MHz)

So, it seems to be switching between the different network connections (first 2.4MHz then 5.2MHz) when it does this.

[Chris Stratford (chris-gondolin)]

While I'm not sure why this only appeared in xenial, I've told network manager to prefer 2.4MHz for now in the hope that will help.

[Chris Stratford (chris-gondolin)]

Having run with just the 2.4MHz network for a while, something still isn't right. Every so often the network just stops talking. NetworkManger still thinks its connected, but no traffic seems to pass. It logs nothing when this happens (I'm guessing it gets detected, though, as that would explain the 2.4 <-> 5 switching I was seeing before)

I would suspect the router at this point, but another machine (with a different Intel chipset - lspci says Centrino Wireless-N 1030) never has any issues and, as mentioned originally, this only started after installing xenial, wily was fine.

I'm out of ideas how how to try and debug this further. For reference I'm now using the 4.4.0-21-generic kernel.

[Launchpad Janitor (janitor)]

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

[Nick Moffitt (nick-moffitt)]

This inactivity is not Chris Stratford's fault.

[Isaac Wilder (cryptobiotik)]

I can also confirm this bug. Bug seems not to occur if interface is kept constantly active, via background mtr or similar.

[Michel-Ekimia (michel.ekimia)]

Is there a master BUg for this ? this is a major problem even in 16.04.1 with latest updates.