It's because this:
[ 2663.907630] r8169 :03:00.0 enp3s0: link down
[ 2663.907639] do_IRQ: 3.34 No irq handler for vector
** No longer affects: lightdm (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in
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.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm
>From the shutdown menu we use.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1760073
Title:
No network from suspend resume
Status in lightdm package in Ubuntu:
New
How did you suspend the machine?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1760073
Title:
No network from suspend resume
Status in lightdm package in Ubuntu:
New
then it didn't
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1760073
Title:
No network from suspend resume
Status in lightdm package in Ubuntu:
New
Status in linux
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.
--
You received
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
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
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
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
--
apport information
** Description changed:
Following a resume from suspend - no network available on machine.
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
apport information
** Tags added: apport-collected
** Description changed:
Following a resume from suspend - no network available on machine.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: lightdm 1.25.2-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Not seeing this on my machine, so it may be kernel related.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
13 matches
Mail list logo
