No network from suspend resume

Bug #1760073 reported by Kev Bowring on 2018-03-30
68
This bug affects 14 people
Affects Status Importance Assigned to Milestone
Linux
Unknown
Unknown
linux (Ubuntu)
Undecided
Unassigned

Bug Description

Following a resume from suspend - no network available on machine.

Originally reported when using 4.15.0-10-generic, recent update to kernel 4.15.0-15-generic

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: lightdm 1.25.2-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: XFCE
Date: Fri Mar 30 11:53:22 2018
InstallationDate: Installed on 2018-03-08 (21 days ago)
InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180306.1)
SourcePackage: lightdm
UpgradeStatus: No upgrade log present (probably fresh install)
---
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: XFCE
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2018-03-08 (23 days ago)
InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180306.1)
Package: linux
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Tags: bionic third-party-packages
Uname: Linux 4.15.0-10-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
---
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: XFCE
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2018-03-08 (23 days ago)
InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180306.1)
Package: linux
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Tags: bionic third-party-packages
Uname: Linux 4.15.0-10-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
---
ApportVersion: 2.20.9-0ubuntu2
Architecture: amd64
CurrentDesktop: XFCE
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2018-03-08 (23 days ago)
InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180306.1)
Package: linux
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Tags: bionic
Uname: Linux 4.15.0-10-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True

Kev Bowring (flocculant) wrote :
Sean Davis (bluesabre) wrote :

Not seeing this on my machine, so it may be kernel related.

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1760073

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.

Changed in linux (Ubuntu):
status: New → Incomplete

apport information

tags: added: apport-collected
description: updated

apport information

apport information

apport information

apport information

apport information

apport information

apport information

description: updated

apport information

apport information

apport information

apport information

apport information

apport information

description: updated

apport information

apport information

apport information

apport information

apport information

apport information

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
TJ (tj) wrote :

Network issue is either kernel or Network Manager.

After the issue occurs we need to see the current 'dmesg' log (which will show if devices resumed successfully) and /var/log/syslog (where Network Manager is very verbose).

We also need to know which devices the system has:

lspci -nnk
lsusb

Kev Bowring (flocculant) wrote :
Download full text (4.4 KiB)

dmesg from suspend time:

[ 2652.902975] PM: suspend entry (deep)
[ 2652.902986] PM: Syncing filesystems ... done.
[ 2652.946758] Freezing user space processes ... (elapsed 0.001 seconds) done.
[ 2652.948257] OOM killer disabled.
[ 2652.948257] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
[ 2652.949367] Suspending console(s) (use no_console_suspend to debug)
[ 2652.961982] sd 5:0:0:0: [sdd] Synchronizing SCSI cache
[ 2652.962004] sd 4:0:0:0: [sdc] Synchronizing SCSI cache
[ 2652.962008] sd 0:0:0:0: [sda] Synchronizing SCSI cache
[ 2652.962029] sd 1:0:0:0: [sdb] Synchronizing SCSI cache
[ 2652.962128] sd 5:0:0:0: [sdd] Stopping disk
[ 2652.962140] sd 4:0:0:0: [sdc] Stopping disk
[ 2652.965477] sd 1:0:0:0: [sdb] Stopping disk
[ 2652.970202] sd 0:0:0:0: [sda] Stopping disk
[ 2654.390345] ACPI: Preparing to enter system sleep state S3
[ 2654.390953] PM: Saving platform NVS memory
[ 2654.390962] Disabling non-boot CPUs ...
[ 2654.406234] IRQ 28: no longer affine to CPU1
[ 2654.407248] smpboot: CPU 1 is now offline
[ 2654.430405] IRQ 27: no longer affine to CPU2
[ 2654.431426] smpboot: CPU 2 is now offline
[ 2654.454490] IRQ 16: no longer affine to CPU3
[ 2654.455514] smpboot: CPU 3 is now offline
[ 2654.459304] ACPI: Low-level resume complete
[ 2654.459391] PM: Restoring platform NVS memory
[ 2654.465534] Enabling non-boot CPUs ...
[ 2654.465611] x86: Booting SMP configuration:
[ 2654.465613] smpboot: Booting Node 0 Processor 1 APIC 0x2
[ 2654.470330] cache: parent cpu1 should not be sleeping
[ 2654.470456] CPU1 is up
[ 2654.470484] smpboot: Booting Node 0 Processor 2 APIC 0x4
[ 2654.471797] cache: parent cpu2 should not be sleeping
[ 2654.471936] CPU2 is up
[ 2654.471957] smpboot: Booting Node 0 Processor 3 APIC 0x6
[ 2654.473274] cache: parent cpu3 should not be sleeping
[ 2654.473419] CPU3 is up
[ 2654.476073] ACPI: Waking up from system sleep state S3
[ 2654.509979] sd 0:0:0:0: [sda] Starting disk
[ 2654.517656] sd 1:0:0:0: [sdb] Starting disk
[ 2654.517666] sd 4:0:0:0: [sdc] Starting disk
[ 2654.517681] sd 5:0:0:0: [sdd] Starting disk
[ 2654.848705] ata6: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 2654.848853] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 2654.851137] ata2.00: supports DRM functions and may not be fully accessible
[ 2654.851634] ata2.00: NCQ Send/Recv Log not supported
[ 2654.852853] ata2.00: supports DRM functions and may not be fully accessible
[ 2654.853344] ata2.00: NCQ Send/Recv Log not supported
[ 2654.853939] ata2.00: configured for UDMA/133
[ 2654.858934] ata6.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
[ 2654.858936] ata6.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
[ 2654.858937] ata6.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
[ 2654.894948] ata6.00: NCQ Send/Recv Log not supported
[ 2654.927088] ata6.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
[ 2654.927091] ata6.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
[ 2654.927093] ata6.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
[ 2654.963078] ata6.00: NCQ Send/Recv Log not support...

Read more...

Kev Bowring (flocculant) wrote :
Download full text (3.4 KiB)

lspci -nnk
00:00.0 Host bridge [0600]: Intel Corporation 4th Gen Core Processor DRAM Controller [8086:0c00] (rev 06)
 Subsystem: Gigabyte Technology Co., Ltd 4th Gen Core Processor DRAM Controller [1458:5000]
 Kernel driver in use: hsw_uncore
00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller [8086:0c01] (rev 06)
 Kernel driver in use: pcieport
 Kernel modules: shpchp
00:14.0 USB controller [0c03]: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI [8086:8c31] (rev 05)
 Subsystem: Gigabyte Technology Co., Ltd 8 Series/C220 Series Chipset Family USB xHCI [1458:5007]
 Kernel driver in use: xhci_hcd
00:16.0 Communication controller [0780]: Intel Corporation 8 Series/C220 Series Chipset Family MEI Controller #1 [8086:8c3a] (rev 04)
 Subsystem: Gigabyte Technology Co., Ltd 8 Series/C220 Series Chipset Family MEI Controller [1458:1c3a]
 Kernel driver in use: mei_me
 Kernel modules: mei_me
00:1a.0 USB controller [0c03]: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2 [8086:8c2d] (rev 05)
 Subsystem: Gigabyte Technology Co., Ltd 8 Series/C220 Series Chipset Family USB EHCI [1458:5006]
 Kernel driver in use: ehci-pci
00:1c.0 PCI bridge [0604]: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #1 [8086:8c10] (rev d5)
 Kernel driver in use: pcieport
 Kernel modules: shpchp
00:1c.2 PCI bridge [0604]: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #3 [8086:8c14] (rev d5)
 Kernel driver in use: pcieport
 Kernel modules: shpchp
00:1d.0 USB controller [0c03]: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #1 [8086:8c26] (rev 05)
 Subsystem: Gigabyte Technology Co., Ltd 8 Series/C220 Series Chipset Family USB EHCI [1458:5006]
 Kernel driver in use: ehci-pci
00:1f.0 ISA bridge [0601]: Intel Corporation C220 Series Chipset Family H81 Express LPC Controller [8086:8c5c] (rev 05)
 Subsystem: Gigabyte Technology Co., Ltd C220 Series Chipset Family H81 Express LPC Controller [1458:5001]
 Kernel driver in use: lpc_ich
 Kernel modules: lpc_ich
00:1f.2 SATA controller [0106]: Intel Corporation 8 Series/C220 Series Chipset Family 6-port SATA Controller 1 [AHCI mode] [8086:8c02] (rev 05)
 Subsystem: Gigabyte Technology Co., Ltd 8 Series/C220 Series Chipset Family 6-port SATA Controller 1 [AHCI mode] [1458:b005]
 Kernel driver in use: ahci
 Kernel modules: ahci
00:1f.3 SMBus [0c05]: Intel Corporation 8 Series/C220 Series Chipset Family SMBus Controller [8086:8c22] (rev 05)
 Subsystem: Gigabyte Technology Co., Ltd 8 Series/C220 Series Chipset Family SMBus Controller [1458:5001]
 Kernel modules: i2c_i801
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GT218 [GeForce 210] [10de:0a65] (rev a2)
 Subsystem: ZOTAC International (MCO) Ltd. GT218 [GeForce 210] [19da:1160]
 Kernel driver in use: nouveau
 Kernel modules: nvidiafb, nouveau
01:00.1 Audio device [0403]: NVIDIA Corporation High Definition Audio Controller [10de:0be3] (rev a1)
 Subsystem: ZOTAC International (MCO) Ltd. High Definition Audio Controller [19da:1160]
 Kernel driver in use: snd_hda_intel
 Kernel modules: snd_hda_intel
03:00.0 Ethernet con...

Read more...

Kev Bowring (flocculant) wrote :

lsusb:

Bus 002 Device 002: ID 8087:8000 Intel Corp.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:8008 Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 002: ID 2109:0812 VIA Labs, Inc. VL812 Hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 006: ID 046d:c077 Logitech, Inc. M105 Optical Mouse
Bus 003 Device 005: ID 046d:c31c Logitech, Inc. Keyboard K120
Bus 003 Device 003: ID 22e8:dac4
Bus 003 Device 002: ID 2109:2812 VIA Labs, Inc. VL812 Hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

description: updated
Kev Bowring (flocculant) wrote :

added a file to /lib/systemd/system-sleep with

#!/bin/sh

set -e

if [ "$2" = "suspend" ] || [ "$2" = "hybrid-sleep" ]; then
    case "$1" in
        pre) true ;;
        post) sleep 1 && service network-manager restart ;;
    esac
fi

and network coming out of suspend works ok.

Kev Bowring (flocculant) wrote :

then it didn't

Kai-Heng Feng (kaihengfeng) wrote :

How did you suspend the machine?

Kev Bowring (flocculant) wrote :

From the shutdown menu we use.

On 13/04/18 08:05, Kai-Heng Feng wrote:
> How did you suspend the machine?
>
This prompted me to see if there was a difference using systemctl
suspend - there wasn't.

Kai-Heng Feng (kaihengfeng) wrote :

It's because this:
[ 2663.907630] r8169 0000:03:00.0 enp3s0: link down
[ 2663.907639] do_IRQ: 3.34 No irq handler for vector

no longer affects: lightdm (Ubuntu)
Florian W. (florian-will) wrote :

Since updating to bionic, I notice the same symptoms (network not working after suspend).

I'm adding this comment to note that this makes my network come up again, I'll try to add this as a post-suspend script as described above:
$ sudo modprobe -r r8169
$ sudo modprobe r8169
(Suggested in https://ubuntuforums.org/showthread.php?t=2386503 )

My journalctl looks a very little bit different, but I guess it's simply because we don't use exactly the same mainboards, so the IRQs differ:

Apr 28 11:00:17 flo-desktop NetworkManager[733]: <info> [1524906017.6262] manager: sleep: wake requested (sleeping: yes enabled: yes)
Apr 28 11:00:17 flo-desktop NetworkManager[733]: <info> [1524906017.6263] device (eth0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'managed')
Apr 28 11:00:17 flo-desktop kernel: r8169 0000:02:00.0 eth0: link down
Apr 28 11:00:17 flo-desktop kernel: IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Apr 28 11:00:17 flo-desktop NetworkManager[733]: <info> [1524906017.6566] manager: NetworkManager state is now DISCONNECTED
Apr 28 11:00:20 flo-desktop ModemManager[693]: <info> Couldn't check support for device at '/sys/devices/pci0000:00/0000:00:0a.0/0000:02:00.0': not supported by any plugin
Apr 28 11:00:20 flo-desktop kernel: do_IRQ: 3.36 No irq handler for vector

Florian W. (florian-will) wrote :

I have added a link to the upstream kernel.org bugzilla, I believe it's the same bug.

Kostas Vekrakis.com (kosvek-k) wrote :

I have a SONY VAIO laptop model VPCEB3M1E. After upgrade from kubuntu 17.10 to kubuntu 18.04 i have this problem: Ethernet disconnect after suspend. My ethernet controller is: Marvell Technology Group Ltd. Yukon Optima 88E8059 [PCIe Gigabit Ethernet Controller with AVB] (rev 11) and the kernel module is sky2.

I try: sudo modprobe -r sky2 and then: sudo modprobe -i sky2 and the ethernet working since the computer goes in sleep mode. After suspend the problem again exists.

The linux kernel is 4.15.0-20-generic

To post a comment you must log in.