Wifi non-functional after suspend (Intel 6205)

Bug #1590985 reported by James Ferguson
42
This bug affects 7 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Incomplete
High
Unassigned

Bug Description

Often, but not always, on resume from suspend my wifi does not connect. In the networking tray drop-down I can see one single wifi network listed (out of the many within range), and it can't reconnect to my network.

I clear it with the hammer of:

    sudo rmmod iwldvm && sudo modprobe iwldvm

I'm not sure what would be more appropriate, but that works. Then my laptop auto-connects to the right network, as expected.

Turning on/off the hardware wireless switch on the thinkpad does not clear the problem.

Just before running ubuntu-bug to submit this, I had the problem, then reloaded the iwldvm module.

----

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-22-generic 4.4.0-22.40
ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: james 1934 F.... pulseaudio
CurrentDesktop: Unity
Date: Thu Jun 9 18:57:10 2016
EcryptfsInUse: Yes
InstallationDate: Installed on 2016-05-21 (19 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: LENOVO 2325KZ5
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic root=UUID=72122534-7dd5-411b-9c56-c4844502e0ad ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-22-generic N/A
 linux-backports-modules-4.4.0-22-generic N/A
 linux-firmware 1.157
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/05/2013
dmi.bios.vendor: LENOVO
dmi.bios.version: G2ETA0WW (2.60 )
dmi.board.asset.tag: Not Available
dmi.board.name: 2325KZ5
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: 518896
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvrG2ETA0WW(2.60):bd03/05/2013:svnLENOVO:pn2325KZ5:pvrThinkPadX230:rvnLENOVO:rn2325KZ5:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 2325KZ5
dmi.product.version: ThinkPad X230
dmi.sys.vendor: LENOVO

Revision history for this message
James Ferguson (james-ferguson) wrote :
description: updated
Revision history for this message
Brad Figg (brad-figg) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Changed in linux (Ubuntu):
importance: Undecided → High
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.7-rc1 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.7-rc3-yakkety/

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
James Ferguson (james-ferguson) wrote :

Intalled. Will report back with results

$ uname -r
4.7.0-040700rc3-generic

tags: added: kernel-bug-exists-upstream
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
James Ferguson (james-ferguson) wrote :

Confirmed upstream - took about 4 suspend-resumes to reproduce with the 4.7.0 kernel

description: updated
description: updated
penalvch (penalvch)
tags: added: bios-outdated-2.66 kernel-bug-exists-upstream-4.7-rc3
Revision history for this message
penalvch (penalvch) wrote :

James Ferguson, as per http://support.lenovo.com/us/en/products/Laptops-and-netbooks/ThinkPad-X-Series-laptops/ThinkPad-X230?linkTrack=GPS%253ABody_Search%2BProducts&tabName=&beta=false an update to your computer's buggy, insecure, and outdated BIOS is available (2.66). When you update to this following https://help.ubuntu.com/community/BIOSUpdate how does this improve the situation?

For more on BIOS updates and linux, please see https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette .

Please note your current BIOS is already in the Bug Description, so posting this on the old BIOS would not be helpful.

Also, you don't have to create a new bug report.

Once the BIOS is updated, if the problem is still reproducible:
1) Please provide the output of the following terminal command (not perform an apport-collect):
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
2) Please make a comment specifically advising on if there was an improvement or not.
3) Please mark this report Status Confirmed.

If it's not reproducible, please mark this as Invalid.

Thank you for your help.

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
James Ferguson (james-ferguson) wrote :

I have been watching the Network Manager applet after suspend and seeing the problem a lot, but then I noticed that even though it's saying i have no connectivity (or available networks), I am actually connected. I have to assume this was always the case and I didn't notice!

So, I assume that makes it a network manager applet bug, and not a Linux kernel bug?

Revision history for this message
Juraj (ojura) wrote :

I can confirm same behavior as James Ferguson on a Thinkpad W520 with Intel Wireless Centrino 6205 Advanced-N. Network manager fails to display any signal strength and visible networks, but I am actually connected and internet works. This didn't happen on Ubuntu 14.04.

Revision history for this message
openfred (openfred) wrote :

[Solved] Validated on a Lenovo Thinkpad T520 using a 6205 wifi card

$ lspci | grep 6205
03:00.0 Network controller: Intel Corporation Centrino Advanced-N 6205 [Taylor Peak] (rev 34)

Just add a file for iwlwifi options in /etc/modprobe.d (1 line) - filename can be anything:

$ cat /etc/modprobe.d/fred.conf
options iwlwifi 11n_disable=1

Reboot after adding this file !

I prefer not to modify /etc/modprobe.d/iwlwifi.conf, as this file is owned by package kmod, and can be modified at anytime.

I tried many times, wifi connection is restored in a 1 second. wifi connection seems much stable.

Tried on Ubuntu Gnome 16.04 and Mint 18.

By the way, many posts are available on the internet about this issue, and a lot of options are suggested. I recall that "modinfo -p" gives the options available for a module:

$ sudo modinfo -p iwlwifi
swcrypto:using crypto in software (default 0 [hardware]) (int)
11n_disable:disable 11n functionality, bitmap: 1: full, 2: disable agg TX, 4: disable agg RX, 8 enable agg TX (uint)
amsdu_size_8K:enable 8K amsdu size (default 0) (int)
fw_restart:restart firmware in case of error (default true) (bool)
antenna_coupling:specify antenna coupling in dB (default: 0 dB) (int)
nvm_file:NVM file name (charp)
d0i3_disable:disable d0i3 functionality (default: Y) (bool)
lar_disable:disable LAR functionality (default: N) (bool)
uapsd_disable:disable U-APSD functionality (default: Y) (bool)
bt_coex_active:enable wifi/bt co-exist (default: enable) (bool)
led_mode:0=system default, 1=On(RF On)/Off(RF Off), 2=blinking, 3=Off (default: 0) (int)
power_save:enable WiFi power management (default: disable) (bool)
power_level:default power save level (range from 1 - 5, default: 1) (int)
fw_monitor:firmware monitor - to debug FW (default: false - needs lots of memory) (bool)

$ iwconfig wlp3s0
wlp3s0 IEEE 802.11abg ESSID:"freebox_CJBHVW"
          Mode:Managed Frequency:2.417 GHz Access Point: F4:CA:E5:88:30:DC
          Bit Rate=48 Mb/s Tx-Power=15 dBm
          Retry short limit:7 RTS thr:off Fragment thr:off
          Power Management:on
          Link Quality=48/70 Signal level=-62 dBm
          Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
          Tx excessive retries:0 Invalid misc:71 Missed beacon:0

Revision history for this message
Juraj (ojura) wrote :

Here's my dmidecode for a Thinkpad W520:

8BET62WW (1.42 )
07/26/2013

It has the newest available BIOS.

lspci:
03:00.0 Network controller: Intel Corporation Centrino Advanced-N 6205 [Taylor Peak] (rev 34)

Kernel:
Linux juraj 4.4.0-31-generic #50-Ubuntu SMP Wed Jul 13 00:07:12 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
penalvch (penalvch) wrote :

Juraj, it will help immensely if you filed a new report with the Ubuntu repository kernel (not mainline/upstream) via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

For more on why this is helpful, please see https://wiki.ubuntu.com/ReportingBugs.

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
openfred (openfred) wrote :

Believe me, disabling wifi 11n solves the issue, as explained in Post #9

However, the data transfert speed is now really slow with this option.
By disabling wifi 11n (between 72Mb/s and 152Mb/s), I was expecting wifi G speed (54Mb/s) but only get Wifi B (11Mb/s speed)...

Revision history for this message
penalvch (penalvch) wrote :

openfred, it will help immensely if you filed a new report with the Ubuntu repository kernel (not mainline/upstream) via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

For more on why this is helpful, please see https://wiki.ubuntu.com/ReportingBugs.

Revision history for this message
anarsoul (anarsoul) wrote :

Something's wrong with scan after resume. Not sure if it's NM or kernel bug, but doing 'sudo iw wlan0 scan' fixes the issue till next suspend/resume.

Revision history for this message
penalvch (penalvch) wrote :

anarsoul, it will help immensely if you filed a new report with the Ubuntu repository kernel (not mainline/upstream) via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

For more on why this is helpful, please see https://wiki.ubuntu.com/ReportingBugs.

Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in linux (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Tormod Volden (tormodvolden) wrote :

Seeing the same as OP with "Intel Corporation Centrino Advanced-N 6235 (rev 24)" on 16.04.2 with 4.8.0-34-generic.

Changed in linux (Ubuntu):
status: Expired → Confirmed
Revision history for this message
Tormod Volden (tormodvolden) wrote :
Revision history for this message
penalvch (penalvch) wrote :

Tormod Volden, to track your hardware, it will help immensely if you filed a new report with Ubuntu, using the default repository kernel (not mainline/upstream/3rd party) via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

For more on why this is helpful, please see https://wiki.ubuntu.com/ReportingBugs.

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Tormod Volden (tormodvolden) wrote :

There are possibly two independent issues here. In some cases the connection is lost after resume, and the module must be reloaded (or configured to be unloaded at suspend).

The other issue is that nm-applet shows no connection (or in my case it shows a wired connection and no wifi bar or networks, although it is connected to wifi). I can run "nmcli device" and "nmcli device wifi" which works fine, so this issue seems limited to nm-applet and not network-manager or drivers. In my case running "iw wlp3s0 scan" or "iwlist scanning" does not fix up nm-applet.

Reloading the module (for the first issue) also gives nm-applet a kick in the butt so that the second issue is remedied temporarily.

Revision history for this message
Tormod Volden (tormodvolden) wrote :

When I have the OP's original issue, lost connection after resume and only one network listed, simply running "sudo iw wlp3s0 scan" makes everything work again, without having to reload the module.

I am sure I have seen the lost connection after resume without any network listed too. I have not yet determined if a scan will fix this without reloading modules, otherwise I would believe I am actually experiencing 3 different issues.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.