[Dell Alienware 17 R3] No network devices after suspend and resume

Bug #1607571 reported by adin
26
This bug affects 5 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Low
Unassigned

Bug Description

I'm on an Alienware 17R3 on Ubuntu 16.04.

The wifi stops working after resume. The problem seems related to https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1422143, but the solutions proposed there doesn't work. Other seems to have a problem related with the network-manager stop working (like http://askubuntu.com/questions/761180/wifi-doesnt-work-after-suspend-after-16-04-upgrade).

However, in my case the network-manager restarts and stops after the resume. However, there is no device, and thus there is no list of available networks to join.

For example, doing

$ iwconfig
lo no wireless extensions.

while in a normal reboot the wireless card information is printed

$ iwconfig
wlp60s0 IEEE 802.11abgn ESSID:"Chapinlandia"
          Mode:Managed Frequency:2.412 GHz Access Point: 8C:04:FF:F6:90:9E
          Bit Rate=1 Mb/s Tx-Power=20 dBm
          Retry short limit:7 RTS thr:off Fragment thr:off
          Power Management:on
          Link Quality=51/70 Signal level=-59 dBm
          Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
          Tx excessive retries:36 Invalid misc:39 Missed beacon:0

lo no wireless extensions.

enp59s0 no wireless extensions.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-31-generic 4.4.0-31.50
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: adin 3934 F.... pulseaudio
CurrentDesktop: Unity
Date: Thu Jul 28 21:05:44 2016
HibernationDevice: RESUME=UUID=c0bba13c-6fa5-4545-a7ee-cd58b1e6e3bd
InstallationDate: Installed on 2016-07-03 (25 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: Alienware Alienware 17 R3
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed root=UUID=dc6d8cac-eff1-4dce-97fd-949d7268d2d9 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-31-generic N/A
 linux-backports-modules-4.4.0-31-generic N/A
 linux-firmware 1.157.2
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/11/2015
dmi.bios.vendor: Alienware
dmi.bios.version: 1.2.3
dmi.board.name: Alienware 17 R3
dmi.board.vendor: Alienware
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Alienware
dmi.chassis.version: Not Specified
dmi.modalias: dmi:bvnAlienware:bvr1.2.3:bd11/11/2015:svnAlienware:pnAlienware17R3:pvr1.2.3:rvnAlienware:rnAlienware17R3:rvrA00:cvnAlienware:ct10:cvrNotSpecified:
dmi.product.name: Alienware 17 R3
dmi.product.version: 1.2.3
dmi.sys.vendor: Alienware

Revision history for this message
adin (adin-rivera) wrote :
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
Revision history for this message
Joseph Salisbury (jsalisbury) wrote : Re: No network devices after suspend and resume

Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?

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 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

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Revision history for this message
adin (adin-rivera) wrote :

I haven't done an upgrade. I tested on the 4.7 kernel and the problem remains.

tags: added: bug-exists-upstream
Revision history for this message
penalvch (penalvch) wrote :

adin, to confirm a WORKAROUND, after resume are you able to recover the WiFi if you execute at a terminal:
sudo rmmod ath10k_pci ; sudo modprobe ath10k_pci

tags: added: bios-outdated-1.2.15
tags: added: kernel-bug-exists-upstream kernel-bug-exists-upstream-4.7
removed: bug-exists-upstream
Revision history for this message
adin (adin-rivera) wrote :

It doesn't work. The network manager is working, but there is still no card.

Revision history for this message
adin (adin-rivera) wrote :

1)

$ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
1.2.15
07/07/2016

2) I don't notice any change on the situation. Tested previous suggestions with the new bios but the problem remains.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
penalvch (penalvch)
tags: added: latest-bios-1.2.15
removed: bios-outdated-1.2.15
Revision history for this message
penalvch (penalvch) wrote :

adin, to confirm, if you stop network manager, then unload your driver, then load your driver, and then start network manager as per https://wiki.ubuntu.com/DebuggingNetworkManager does this allow it work after resume?

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

I can confirm: it doesn't work either.

I needed to do a small change though:

sudo service network-manager stop/start

as

$ sudo stop network-manager
stop: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused

I guess the intention is the same. If I tested it incorrectly please advice.

Revision history for this message
penalvch (penalvch) wrote :

adin, could you please provide the missing information from https://wiki.ubuntu.com/DebuggingKernelSuspend ?

Revision history for this message
adin (adin-rivera) wrote :

I'm completing the log report:

Which part of the process does the issue occur with, the suspend to ram, or resuming from?
The network interface is not showing, thus no networks appear in the network manager. Consequently, there is no internet.

Please advise how you suspended specifically. For example:

    Shutting the lid of the laptop, which is set to suspend on close.

Please advise how you resumed specifically. For example:

    Lifted the lid

I'm going to attach the log files in the next posts (the interface allows one attachment and the instructions ask for not compressed files)

Revision history for this message
adin (adin-rivera) wrote :
Revision history for this message
adin (adin-rivera) wrote :
Revision history for this message
adin (adin-rivera) wrote :
Revision history for this message
adin (adin-rivera) wrote :
Revision history for this message
adin (adin-rivera) wrote :
Revision history for this message
adin (adin-rivera) wrote :
Revision history for this message
adin (adin-rivera) wrote :
Revision history for this message
penalvch (penalvch) wrote :

adin, it looks like you didn't attach the files while using the latest mainline kernel (which is now 4.7), as the article advises.

Revision history for this message
adin (adin-rivera) wrote :

I installed http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.7/ generic amd64

However, there is no /sys/power/pm_trace. Do I need to do something else? From the article, it seems that the kernel should have that already.

Any advice on how to turn it on? or install it? My google-fu didn't return any pointers on how to achieve it.

penalvch (penalvch)
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
penalvch (penalvch)
tags: added: bios-outdated-1.3.6
removed: latest-bios-1.2.15
Revision history for this message
GhiOm (subtenante) wrote :

Related problem and non working solutions: https://ubuntuforums.org/archive/index.php/t-2315928.html

Revision history for this message
adin (adin-rivera) wrote :

Updated to Ubuntu 16.10, and the problem persists.

penalvch (penalvch)
tags: added: yakkety
Revision history for this message
ALan (alanxiaoyi) wrote :

Same here. With ubuntu 14.04 upgraded to 16.04.

Revision history for this message
ALan (alanxiaoyi) wrote :

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1555775 #52
has a workaround

put

#! /bin/sh

# This script rescans the PCI bus after resume from suspend to fix
# broken WiFi, wired ethernet, and the card reader on the Alienware 15 R2.
case $1/$2 in
  pre/*)
    echo "Going to $2..."
    # Place your pre suspend commands here, or `exit 0` if no pre suspend action required
    ;;
  post/*)
    echo "Waking up from $2..."
    # Place your post suspend (resume) commands here, or `exit 0` if no post suspend action required
        echo 1 > /sys/bus/pci/devices/0000\:00\:1c.4/rescan
 echo 1 > /sys/bus/pci/devices/0000\:00\:1c.5/rescan
 echo 1 > /sys/bus/pci/devices/0000\:00\:1c.6/rescan

esac

in file

/lib/systemd/system-sleep/aw_pci_rescan

change permission by

chmod +x

Working for me tested on 16.04 with kernel 4.9

Revision history for this message
Derrick (gallifrey2017) wrote :

Finally!!! After 2 plus years of having this issue with no solutions, this worked!!!! Thank you so very much! I have not been able to enjoy running Linux on this expensive Alienware laptop since I bought it. I am curious why this is still an issue.. this has been an issue since at least Ubuntu 16.04.. still an issue in 18.04. In any case, I can confirm this script fixed my issue!! Many thanks!

penalvch (penalvch)
tags: added: bios-outdated-1.3.12 needs-upstream-testing
removed: bios-outdated-1.3.6 kernel-bug-exists-upstream
summary: - No network devices after suspend and resume
+ [Dell Alienware 17 R3] No network devices after suspend and resume
Revision history for this message
penalvch (penalvch) wrote :

adin:

1) To keep this relevant to upstream, one will want to continue to test the latest mainline release (now 4.18-rc3) as it is released. Could you please advise?

2) Could you please advise if https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1607571/comments/25 provides a WORKAROUND?

Changed in linux (Ubuntu):
importance: Medium → Low
status: Confirmed → Incomplete
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
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.