10ec:818b [Lenovo ThinkPad T440] WiFi does not reconnect after resuming from sleep in Ubuntu 14.10

[Mahsa Mohammadkhani]

After resuming from suspend via closing the lid, my wireless doesn't work. It finds the wireless network and tries to reconnect but fails. The only I can solve it now is by restarting. This happens with both my home and university AP. I do not have any other problem with these APs with my other laptop.

I tried to re-initialize the kernel module but it doesn't work as per dmesg:
modprobe -r r8192ee && modprobe r8192ee
[ 125.586281] wlan0: deauthenticating from f4:7f:35:cc:f6:71 by local choice (Reason: 3=DEAUTH_LEAVING)
[ 125.622205] cfg80211: Calling CRDA to update world regulatory domain
[ 125.630473] cfg80211: World regulatory domain updated:
[ 125.630476] cfg80211: DFS Master region: unset
[ 125.630478] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
[ 125.630480] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm), (N/A)
[ 125.630482] cfg80211: (2457000 KHz - 2482000 KHz @ 40000 KHz), (300 mBi, 2000 mBm), (N/A)
[ 125.630484] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm), (N/A)
[ 125.630485] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm), (N/A)
[ 125.630487] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm), (N/A)
[ 138.859714] cfg80211: Calling CRDA to update world regulatory domain
[ 138.872238] cfg80211: World regulatory domain updated:
[ 138.872240] cfg80211: DFS Master region: unset
[ 138.872241] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
[ 138.872243] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm), (N/A)
[ 138.872244] cfg80211: (2457000 KHz - 2482000 KHz @ 40000 KHz), (300 mBi, 2000 mBm), (N/A)
[ 138.872245] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm), (N/A)
[ 138.872246] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm), (N/A)
[ 138.872247] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm), (N/A)
[ 138.878321] r8192ee: module is from the staging directory, the quality is unknown, you have been warned.
[ 138.879407] mem mapped space: start: 0xf0400000 len:00004000 flags:00140204, after map:0xffffc90004ff8000
[ 138.879418] Pci Bridge Vendor is found index: 0
[ 138.879420] pcidev busnumber:devnumber:funcnumber:vendor:link_ctl 3:0:0:10ec:0
[ 138.879421] pci_bridge busnumber:devnumber:funcnumber:vendor:pcie_cap:link_ctl_reg:amd 0:28:1:8086:40:40:0
[ 138.879441] Boot from EFUSE
[ 138.886730] dev_addr: 38:b1:db:00:1b:9b
[ 138.886735] RT Customized ID: 0x12
[ 138.887501] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
[ 138.887743] cfg80211: Calling CRDA for country: EC
[ 138.887777] rtlwifi: wireless switch is on
[ 138.888325] r8192ee 0000:03:00.0: irq 64 for MSI/MSI-X
[ 139.587122] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 139.587167] cfg80211: Regulatory domain changed to country: EC
[ 139.587169] cfg80211: DFS Master region: unset
[ 139.587170] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
[ 139.587172] cfg80211: (2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
[ 139.587173] cfg80211: (5170000 KHz - 5250000 KHz @ 20000 KHz), (300 mBi, 1700 mBm), (N/A)
[ 139.587175] cfg80211: (5250000 KHz - 5330000 KHz @ 20000 KHz), (300 mBi, 2300 mBm), (0 s)
[ 139.587175] cfg80211: (5735000 KHz - 5835000 KHz @ 20000 KHz), (300 mBi, 3000 mBm), (N/A)
[ 149.723735] wlan0: authenticate with f4:7f:35:dd:e1:c1
[ 150.390674] wlan0: direct probe to f4:7f:35:dd:e1:c1 (try 1/3)
[ 150.593636] wlan0: direct probe to f4:7f:35:dd:e1:c1 (try 2/3)
[ 150.797653] wlan0: direct probe to f4:7f:35:dd:e1:c1 (try 3/3)
[ 151.001675] wlan0: authentication with f4:7f:35:dd:e1:c1 timed out
[ 166.155577] wlan0: authenticate with f4:7f:35:f7:29:d1
[ 166.823724] wlan0: direct probe to f4:7f:35:f7:29:d1 (try 1/3)
[ 167.027908] wlan0: direct probe to f4:7f:35:f7:29:d1 (try 2/3)
[ 167.231945] wlan0: direct probe to f4:7f:35:f7:29:d1 (try 3/3)
[ 167.435952] wlan0: authentication with f4:7f:35:f7:29:d1 timed out
[ 182.580710] wlan0: authenticate with f4:7f:35:f6:9e:d1
[ 183.248770] wlan0: direct probe to f4:7f:35:f6:9e:d1 (try 1/3)
[ 183.450239] wlan0: direct probe to f4:7f:35:f6:9e:d1 (try 2/3)
[ 183.654202] wlan0: direct probe to f4:7f:35:f6:9e:d1 (try 3/3)
[ 183.858252] wlan0: authentication with f4:7f:35:f6:9e:d1 timed out
[ 199.016228] wlan0: authenticate with f4:7f:35:cc:f6:71
[ 199.683511] wlan0: direct probe to f4:7f:35:cc:f6:71 (try 1/3)
[ 199.884523] wlan0: direct probe to f4:7f:35:cc:f6:71 (try 2/3)
[ 200.088554] wlan0: direct probe to f4:7f:35:cc:f6:71 (try 3/3)
[ 200.292604] wlan0: authentication with f4:7f:35:cc:f6:71 timed out

---
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: mahsa 2186 F.... pulseaudio
 /dev/snd/controlC1: mahsa 2186 F.... pulseaudio
CRDA:
 country EC: DFS-UNSET
  (2402 - 2482 @ 40), (N/A, 20)
  (5170 - 5250 @ 20), (3, 17)
  (5250 - 5330 @ 20), (3, 23), DFS
  (5735 - 5835 @ 20), (3, 30)
DistroRelease: Ubuntu 14.10
HibernationDevice: RESUME=UUID=ddd1312b-78c0-4393-949e-8507904afc64
InstallationDate: Installed on 2014-10-26 (13 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
MachineType: LENOVO 20B6CTO1WW
Package: linux (not installed)
ProcEnviron:
 LANGUAGE=en_CA:en
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic.efi.signed root=UUID=74eb8dd9-80ed-4d4b-bacd-d0c8e0749a36 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
PulseList:
 Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied
 No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-3.16.0-24-generic N/A
 linux-backports-modules-3.16.0-24-generic N/A
 linux-firmware 1.138
StagingDrivers: r8192ee
Tags: utopic staging
Uname: Linux 3.16.0-24-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

_MarkForUpload: True
dmi.bios.date: 07/29/2014
dmi.bios.vendor: LENOVO
dmi.bios.version: GJET78WW (2.28 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20B6CTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0E50512 STD
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvrGJET78WW(2.28):bd07/29/2014:svnLENOVO:pn20B6CTO1WW:pvrThinkPadT440:rvnLENOVO:rn20B6CTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 20B6CTO1WW
dmi.product.version: ThinkPad T440
dmi.sys.vendor: LENOVO

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[penalvch (penalvch)]

Mahsa Mohammadkhani, 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 1386863
When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

[Mahsa Mohammadkhani (mahsa2)]

apport information

[Mahsa Mohammadkhani (mahsa2)]

apport information

[Mahsa Mohammadkhani (mahsa2)]

apport information

[Mahsa Mohammadkhani (mahsa2)]

apport information

[Mahsa Mohammadkhani (mahsa2)]

apport information

[Mahsa Mohammadkhani (mahsa2)]

apport information

[Mahsa Mohammadkhani (mahsa2)]

apport information

[Mahsa Mohammadkhani (mahsa2)]

apport information

[Mahsa Mohammadkhani (mahsa2)]

apport information

[Mahsa Mohammadkhani (mahsa2)]

apport information

[Mahsa Mohammadkhani (mahsa2)]

apport information

[Mahsa Mohammadkhani (mahsa2)]

apport information

[Mahsa Mohammadkhani (mahsa2)]

apport information

[penalvch (penalvch)]

Mahsa Mohammadkhani, 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 in your release) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine 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-rc3

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.

[Mahsa Mohammadkhani (mahsa2)]

I have tried the latest upstream kernel mainline with the following tests in this order:

1. Closing and opening the lid (Sleep mode) --> Working
2. Switching off and on the wireless --> Working
3. modprobe -r rtl8192ee && modprobe rtl8192ee --> Not Working

After the modprobe, nothing else such as sleep mode and wireless switch could fix the issue except restarting the system. I have attached the dmesg of this process.

[penalvch (penalvch)]

Mahsa Mohammadkhani, just to clarify, this bug report is only scoped to WiFi not working after resume from suspend.

With this in mind, is there a reason you would be modprobe'ing if the WiFi works after resuming from suspend?

Despite this, the next step is to fully reverse commit bisect from kernel 3.16 to 3.18-rc3 in order to identify the last bad commit, followed immediately by the first good one. Once this commit has been identified, then it may be reviewed as a candidate for backporting into your release. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection#How_do_I_reverse_bisect_the_upstream_kernel.3F ? 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

[Mahsa Mohammadkhani (mahsa2)]

To answer your first question, No, I was just testing modprobe to see if it is working too or not.

For your second task, I have tried it into different APs. With one of them ALL the versions were working. With the other one, not all but a few were working:

v3.18-rc2-vivid and above --> Working (Good)
v3.18-rc2-utopic --> Ubuntu did not come up. (Bad)
v3.18-rc1 --> Did not detect any WiFi (Bad)

Because with one of the rc2 releases Ubuntu did not run on my machine, I did not know how to do the last step of reverse commite bisection, because it only has version number and the release name (i.e. utopic, or vivid) is not included. Should I ignore the release names as you mentioned it ealier for the last step or not? Thank you.

[Mahsa Mohammadkhani (mahsa2)]

I have done the last part of bisect (reverse commit bisecting) by ignoring the release names and I received this comment:

Bisecting: 233 revisions left to test after this (roughly 8 steps)
[3f6f1480d86bf9fc16c160d803ab1d006e3058d5] KVM: x86: PREFETCH and HINT_NOP should have SrcMem flag

[penalvch (penalvch)]

The following git output would indicate that you would have at most an additional 8 kernel bisection points to further test in order to find the fix commit:

Bisecting: 233 revisions left to test after this (roughly 8 steps)
[3f6f1480d86bf9fc16c160d803ab1d006e3058d5] KVM: x86: PREFETCH and HINT_NOP should have SrcMem flag

[Mahsa Mohammadkhani (mahsa2)]

So, I have tried to build the new kernel using the description in the guide you provided me, however, after building the kernel, the wireless was not working/detected in any of them using the defualt config even on the ones I built manually and my wireless issue was solved on. I asked this question in
http://askubuntu.com/questions/553094/no-wireless-drive-detection-in-new-built-kernel-for-reverse-bisecting
but no one gave me any answer. I am wondering if you or any of your collegue can reply to the question I provided in the above url.
Thanks.

[penalvch (penalvch)]

Mahsa Mohammadkhani, just skip that commit and build against another one.

[Mahsa Mohammadkhani (mahsa2)]

I think I was not clear. The wireless module is not detected when I build even a kernel version that detects wireless when I download the pre-built and install it.
1. I downloaded the pre-built kernel version v3.18-rc2, installed it, and the wireless worked as desired.
2. I checked out the same version v3.18-rc2 of the kernel, built it*, installed it, and the wireless was not detected at all.

*I built it using this link: https://wiki.ubuntu.com/KernelTeam/GitKernelBuild and also https://wiki.ubuntu.com/Kernel/KernelBisection#Bisecting_upstream_kernel_versions_to_single_commit_using_mainline-build-one. Both had the same problem.

[penalvch (penalvch)]

Mahsa Mohammadkhani, which build instructions precisely did you use? There are two different ones mentioned.

[Mahsa Mohammadkhani (mahsa2)]

As in my previous comment, BOTH build instructions had the issue I explained, i.e. the wireless module was not detected in either of them. (Number 2 in previous comment).
However, by building the same kernel with the same version manually, using pre-built (provided http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D), the wireless module was detected. (Number 1 in the previous comment).

[penalvch (penalvch)]

Mahsa Mohammadkhani, just to advise, I asked to you specify which of the two build instructions you used because you never advised explicitly if you only used one or both, nor did you give a click for click on both of these. Quoting previous comments is unhelpful here as I already read all your comments, and the answer to my question isn't found in them, hence my question.

Despite this, given this is a downstream issue, and the commit is not able to be identified so far, this will have to be addressed by the Ubuntu Kernel Team.

[Peter Ullinger (upthere)]

Similar error messages¹ are filed in both bugs 1408963 and 1390709. In both cases, there were workarounds to network-manager and wpa-supplicant. So, there seems no kernel issue in all three cases.

¹wlan0: deauthenticating from ... by local choice (Reason: 3=DEAUTH_LEAVING)