[Dell Alienware 15 R2] WiFi + wired ethernet broken after suspend

[Andy Barry]

With Ubuntu 14.04, and 15.10, using my Alienware 15 R2 the Intel 7265 WiFi is broken on resume from suspend. However, after suspend, it is gone from network manager ("No network devices available"), from ifconfig, and from lshw -class Network. It works fine prior to suspend.

I have tried removing the kernel module iwlwifi,before suspend and modprobe-ing it after, but that results in no change. I also have disabled wifi via the keyboard key, then suspended, then resumed, but still no luck. No change after installing intel-microcode either.

Wifi does come back after resume in Windows.

As additional data points:
This also happens with WiFi cards Killer 1535, and Intel 8260.
Also, the exact same thing happens to my wired ethernet connection as well (it disappears from lshw -class Network) after suspend.

WORKAROUND: cat /etc/pm/sleep.d/alienware_pci_rescan
#! /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 in
     resume|thaw)
        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

---
ApportVersion: 2.19.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: abarry 1585 F.... pulseaudio
CurrentDesktop: Unity
DistroRelease: Ubuntu 15.10
InstallationDate: Installed on 2016-03-10 (0 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 1bcf:2b8c Sunplus Innovation Technology Inc.
 Bus 001 Device 003: ID 8087:0a2a Intel Corp.
 Bus 001 Device 002: ID 187c:0528 Alienware Corporation
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Alienware Alienware 15 R2
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-30-generic.efi.signed root=UUID=115dc7cd-b190-4872-94bd-685ec9695732 ro noprompt persistent quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 4.2.0-30.36-generic 4.2.8-ckt3
RelatedPackageVersions:
 linux-restricted-modules-4.2.0-30-generic N/A
 linux-backports-modules-4.2.0-30-generic N/A
 linux-firmware 1.149
Tags: wily
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
Uname: Linux 4.2.0-30-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 01/29/2016
dmi.bios.vendor: Alienware
dmi.bios.version: 1.2.8
dmi.board.name: Alienware 15 R2
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.8:bd01/29/2016:svnAlienware:pnAlienware15R2:pvr1.2.8:rvnAlienware:rnAlienware15R2:rvrA00:cvnAlienware:ct10:cvrNotSpecified:
dmi.product.name: Alienware 15 R2
dmi.product.version: 1.2.8
dmi.sys.vendor: Alienware

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1555775

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Joseph Salisbury (jsalisbury)]

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.5 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.5-rc7-wily/

[Andy Barry (abarry-gmail)]

apport information

[Andy Barry (abarry-gmail)]

apport information

[Andy Barry (abarry-gmail)]

apport information

[Andy Barry (abarry-gmail)]

apport information

[Andy Barry (abarry-gmail)]

apport information

[Andy Barry (abarry-gmail)]

apport information

[Andy Barry (abarry-gmail)]

apport information

[Andy Barry (abarry-gmail)]

apport information

[Andy Barry (abarry-gmail)]

apport information

[Andy Barry (abarry-gmail)]

apport information

[Andy Barry (abarry-gmail)]

apport information

[Andy Barry (abarry-gmail)]

apport information

[Andy Barry (abarry-gmail)]

apport information

[Andy Barry (abarry-gmail)]

apport information

[Andy Barry (abarry-gmail)]

No this issue has happened on every linux installation I have tried.

I'll upgrade to 4.5.x and will report back.

[Andy Barry (abarry-gmail)]

Upgraded to the 4.5.0 kernel, rebooted, and attempted suspend/resume cycle. Same result, network adapters are offline and do not appear in lshw.

[penalvch (penalvch)]

Andy Barry, to advise, it would be most helpful if simply one card is tested and advised to (not 3) so that this report may be precisely scoped, and dealt with.

Hence, to clarify https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1555775/comments/18 :
1) Which card did you test with specifically?
2) Did you test http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.5-rc7-wily/ or something else?

[Andy Barry (abarry-gmail)]

> Andy Barry, to advise, it would be most helpful if simply one card is tested and advised to (not 3) so that this report may be precisely scoped, and dealt with.

The reason I wrote about the 3 different cards is that I think it indicates the bug is likely *not* in the wifi drivers for the cards, but in the driver for the motherboard / BIOS. For the purposes of this report, I'm happy to focus on the Intel 7265 which is the most well supported of the 3.

> Hence, to clarify https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1555775/comments/18 :
> 1) Which card did you test with specifically?
> 2) Did you test http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.5-rc7-wily/ or something else?

I tested Intel 7265 with v4.5-rc7-wily, yes. Exactly that link with the amd64 packages.

I'll change the status back to Confirmed since I've answered your questions, but please let me know if that's inappropriate and something you or someone else is supposed to do (I'm relatively new to bugs on launchpad).

[penalvch (penalvch)]

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

[Andy Barry (abarry-gmail)]

Ok, I've attached the resume traces from the various levels of suspend debug. All were done running the rc7 kernel as above.

[penalvch (penalvch)]

Andy Barry, to clarify, which of those files attached was the issue reproducible with?

Also, as of March 14, the latest mainline kernel is now 4.5 (not 4.5-rc7).

[Andy Barry (abarry-gmail)]

Hi Christopher,

Good catch. I've redone everything after upgrading to 4.5.0:

abarry@AAAZZZL15:~$ uname -a
Linux AAAZZZL15 4.5.0-040500-generic #201603140130 SMP Mon Mar 14 05:32:22 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

Wifi breaks after executing the platform suspend run. I've added that to the filenames so hopefully it is much more clear.

[Andy Barry (abarry-gmail)]

(and to further clarify, I rebooted after each suspend iteration where wifi failed, so that it was operational before each suspend attempt.)

[penalvch (penalvch)]

Andy Barry, to clarify, did both WiFi and ethernet break after resuming from suspend?

[Andy Barry (abarry-gmail)]

Yes. Perhaps the most informative thing yet is lspci before and after:

Before suspend:

$ lspci -vtnnQ

-[0000:00]-+-00.0 Intel Corporation Skylake Host Bridge/DRAM Registers [8086:1910]
           +-01.0-[01]----00.0 NVIDIA Corporation GM204M [GeForce GTX 970M] [10de:13d8]
           +-02.0 Intel Corporation Skylake Integrated Graphics [8086:191b]
           +-04.0 Intel Corporation Skylake Processor Thermal Subsystem [8086:1903]
           +-14.0 Intel Corporation Sunrise Point-H USB 3.0 xHCI Controller [8086:a12f]
           +-14.2 Intel Corporation Sunrise Point-H Thermal subsystem [8086:a131]
           +-16.0 Intel Corporation Sunrise Point-H CSME HECI #1 [8086:a13a]
           +-17.0 Intel Corporation 82801 Mobile SATA Controller [RAID mode] [8086:282a]
           +-1c.0-[02-3a]--
           +-1c.4-[3b]----00.0 Qualcomm Atheros Killer E2400 Gigabit Ethernet Controller [1969:e0a1]
           +-1c.5-[3c]----00.0 Intel Corporation Wireless 7265 [8086:095a]
           +-1c.6-[3d]----00.0 Realtek Semiconductor Co., Ltd. RTS5227 PCI Express Card Reader [10ec:5227]
           +-1f.0 Intel Corporation Sunrise Point-H LPC Controller [8086:a14e]
           +-1f.2 Intel Corporation Sunrise Point-H PMC [8086:a121]
           +-1f.3 Intel Corporation Sunrise Point-H HD Audio [8086:a170]
           \-1f.4 Intel Corporation Sunrise Point-H SMBus [8086:a123]

After suspend:

-[0000:00]-+-00.0 Intel Corporation Skylake Host Bridge/DRAM Registers [8086:1910]
           +-01.0-[01]----00.0 NVIDIA Corporation GM204M [GeForce GTX 970M] [10de:13d8]
           +-02.0 Intel Corporation Skylake Integrated Graphics [8086:191b]
           +-04.0 Intel Corporation Skylake Processor Thermal Subsystem [8086:1903]
           +-14.0 Intel Corporation Sunrise Point-H USB 3.0 xHCI Controller [8086:a12f]
           +-14.2 Intel Corporation Sunrise Point-H Thermal subsystem [8086:a131]
           +-16.0 Intel Corporation Sunrise Point-H CSME HECI #1 [8086:a13a]
           +-17.0 Intel Corporation 82801 Mobile SATA Controller [RAID mode] [8086:282a]
           +-1c.0-[02-3a]--
           +-1c.4-[3b]--
           +-1c.5-[3c]--
           +-1c.6-[3d]--
           +-1f.0 Intel Corporation Sunrise Point-H LPC Controller [8086:a14e]
           +-1f.2 Intel Corporation Sunrise Point-H PMC [8086:a121]
           +-1f.3 Intel Corporation Sunrise Point-H HD Audio [8086:a170]
           \-1f.4 Intel Corporation Sunrise Point-H SMBus [8086:a123]

So you can see the wifi, wired ethernet, and the PCI express card reader are gone. I'll attach more verbose versions of lspci below.

[penalvch (penalvch)]

Andy Barry, to clarify, the next thing to do here is pin down which module is responsible for this behavior.

Hence:
1) If you remove the kernel module for only the ethernet card what happens?
2) If you remove the kernel module for only the PCI express card reader, what are the results then?

[Andy Barry (abarry-gmail)]

Confirmed that the problem still exists in 4.6.0-rc1. I'll try removing the other kernel modules tomorrow and will report back. Thanks for your continued help.

[Andy Barry (abarry-gmail)]

Removing the kernel modules for the card reader:

sudo rmmod rtsx_pci_sdmmc
sudo rmmod rtsx_pci_ms
sudo rmmod rtsx_pci

It still appears in lspci (but as unassigned)
After a suspend cycle, it is gone just like before, along with the wired and wireless ethernet.

Removing the kernel module for the wired ethernet:

sudo rmmod alx

Same as above: wired ethernet still appears in lspci. After a suspend cycle, it is gone along with the other two items, just as before.

[penalvch (penalvch)]

Andy Barry, given how wide spread the effects are (both wired and wireless) a more lower level cause may be the culprit here. However, given you have tested the latest mainline kernel, and provided verbose suspend debug logs, another pair of eyes to root cause would be helpful.

[Andy Barry (abarry-gmail)]

Great, thanks for the help. Standing by if more info is needed.

[penalvch (penalvch)]

Andy Barry, consulting https://www.kernel.org/doc/Documentation/power/basic-pm-debugging.txt (which is the basis for the Ubuntu support article) the issue is correlated to ACPI firmware, given how suspend does not work on the platform setting, it affects multiple hardware devices, and as per https://launchpadlibrarian.net/249705631/dmesg_platform_wifi_broken.txt :
[ 213.797247] ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20160108/nsarguments-95)
[ 213.798037] ACPI: \_SB_.PCI0.PEG0.PEGP: failed to evaluate _DSM
[ 213.798044] ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20160108/nsarguments-95)
...
[ 269.799208] ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20160108/nsarguments-95)
[ 269.800160] ACPI: \_SB_.PCI0.PEG0.PEGP: failed to evaluate _DSM
[ 269.800170] ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20160108/nsarguments-95)

Hence, it wouldn't hurt to confirm this by running it by the linux-acpi mailing list via https://wiki.ubuntu.com/Bugs/Upstream/kernel .

[Andy Barry (abarry-gmail)]

I was about to post to linux-acpi when I tried:

sudo su
echo 1 > /sys/bus/pci/rescan

which successfully brings back the wifi, wired ethernet, and card reader! Should I still post to the mailing list, or does this open up alternatives for us?

[Andy Barry (abarry-gmail)]

This script now solves the problem (although does cause a delay before wifi connection):

$ cat /etc/pm/sleep.d/alienware_pci_rescan
#! /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 in
     resume|thaw)
        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

[penalvch (penalvch)]

Andy Barry, identifying a WORKAROUND wouldn't preempt sending a message about this bug to developers.

[Vesa Suontama (vesa-suontama)]

I have also the same issue, but I have a Realtek card. Running ubuntu 15.10 and after suspend or restart it is saying network cable unplugged very often. And network seems to go down everytime you suspend.

 Unpluggin and plugging it sometimes help, but you may need to do it multiple times.

Here is my network card information:

   *-network
                description: Ethernet interface
                product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
                vendor: Realtek Semiconductor Co., Ltd.
                physical id: 0
                bus info: pci@0000:06:00.0
                logical name: enp6s0
                version: 02
                serial: e0:cb:4e:70:1c:91
                size: 100Mbit/s
                capacity: 1Gbit/s
                width: 64 bits
                clock: 33MHz
                capabilities: bus_master cap_list rom ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation
                configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=2.3LK-NAPI duplex=full ip=192.168.1.70 latency=0 link=yes multicast=yes port=MII speed=100Mbit/s
                resources: irq:28 ioport:e800(size=256) memory:fbeff000-fbefffff memory:f8ef0000-f8efffff memory:fbec0000-fbedffff

And I am having this kind of messages in dmesg:

r8169 0000:06:00.0 enp6s0: link down
[ 812.236808] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
[ 1065.789186] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
[ 1065.789313] Failed to recover vector for irq 28
[ 1065.799353] r8169 0000:06:00.0 enp6s0: link down
[ 1065.799395] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
[ 1174.573575] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
[ 1174.573708] Failed to recover vector for irq 28
[ 1174.584636] r8169 0000:06:00.0 enp6s0: link down
[ 1174.584676] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
[ 1196.290919] r8169 0000:06:00.0 enp6s0: link up
[ 1196.290931] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
[ 1288.122309] r8169 0000:06:00.0 enp6s0: link down
[ 1292.840986] r8169 0000:06:00.0 enp6s0: link up
[ 1293.086834] r8169 0000:06:00.0 enp6s0: link down
[ 1295.367146] r8169 0000:06:00.0 enp6s0: link up
[ 1349.102757] r8169 0000:06:00.0 enp6s0: link down
[ 1354.569764] r8169 0000:06:00.0 enp6s0: link up
[ 1496.447962] r8169 0000:06:00.0 enp6s0: link down
[ 1517.072913] r8169 0000:06:00.0 enp6s0: link up
[ 2528.507279] lpc_ich 0000:00:1f.0: BAR 13: [io size 0x0080] has bogus alignment
[ 2528.507288] pci 0000:00:1e.0: PCI bridge to [bus 08]
[ 2557.675540] lpc_ich 0000:00:1f.0: BAR 13: [io size 0x0080] has bogus alignment
[ 2557.675551] pci 0000:00:1e.0: PCI bridge to [bus 08]
[ 3003.140722] r8169 0000:06:00.0 enp6s0: link down
[ 3021.111219] r8169 0000:06:00.0 enp6s0: link up

(Note I removed my network card multiple times, and I was trying to restart the network sometimes with sudo /etc/init.d/network-manager restart)

I read somewhere this may be a buggy Realtek driver. Or some other issue, but seems to be very similar symptomps than the OP had.

Any advice? File a separate bug report?

[Vesa Suontama (vesa-suontama)]

FYI: I had to update the driver from http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=13&PFid=5&Level=5&Conn=4&DownTypeID=3&GetDown=false#2 and got my problem solved.

[penalvch (penalvch)]

Vesa Suontama, 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.

[penalvch (penalvch)]

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

[Andy Barry (abarry-gmail)]

I'm afraid I don't have access to that hardware anymore. Perhaps Vesa can provide an update?

[penalvch (penalvch)]

Andy Barry, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1555775/comments/58 regarding you no longer have the hardware. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.

[jason (dimensionaltravel)]

I tried kernel 4.18-rc4 after I saw your post, Christopher, and this bug is fixed. Wifi, ethernet, and nvme drive all work after suspend/resume now. I haven't tried any kernels between this and 4.13.0, so I can't say which version fixed it.

Kernel 4.18-rc4
Kubuntu 18.04 with the latest package updates
Alienware 15 R2
BIOS 1.4.4 01/08/2018

Thanks for fixing it! This makes a big difference in my productivity and decision to not buy a new laptop.