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 1827427
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
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1827427
Title:
DHCP IP not obtainable if booting into Linux from
suspended/hibernated/rebooted Windows
Status in linux package in Ubuntu:
Incomplete
Bug description:
Steps to reproduce: boot into Windows, obtain DHCP IP. either
hibernate PC or reboot then boot into Linux; a DHCP IP is not
obtainable even if I power cycle my router.
To obtain a DHCP IP in Linux on the PC, I must either fully shutdown
Windows then cold boot into Linux, or manually reset the ethernet
adapter with
echo 1 > /sys/bus/pci/devices/0000:00:19.0/reset
The connection then comes good.
I can see various DHCPDISCOVER and network-related traffic in journalctl -f
during the time the machine is attempting to set an address on the interface,
periodically the "activation of network connection failed" error message
displays.
Other discussion online suggests setting a spoofed, different MAC on
the interface
I am using Ubuntu 19 and Mint Cinnamon 19.1 to test and can reproduce
this over multiple boots. It has apparently been a longstanding bug,
perhaps due to how Windows is setting some aspect of the ethernet
controller for a WOL or other boot-related operation. Either way, it's
entirely confusing. Perhaps resetting the adapter should occur if this
situation arises, particularly in LiveUSB/LiveCD scenarios.
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: network-manager 1.16.0-0ubuntu2
ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
Uname: Linux 5.0.0-13-generic x86_64
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
CasperVersion: 1.405
CurrentDesktop: ubuntu:GNOME
Date: Thu May 2 22:06:00 2019
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
IpRoute:
IwConfig:
lo no wireless extensions.
eno1 no wireless extensions.
LiveMediaBuild: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
NetworkManager.state:
[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=true
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=C.UTF-8
SHELL=/bin/bash
RfKill:
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-con:
NAME UUID TYPE TIMESTAMP
TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY
DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH
SLAVE FILENAME
lan1 cbe6c8b2-dab9-347f-8a1d-613294b87483 ethernet 1556833444 Thu May 2
21:44:04 2019 yes -999 no
/org/freedesktop/NetworkManager/Settings/1 no -- -- --
-- /etc/NetworkManager/system-connections/lan1.nmconnection
nmcli-dev:
DEVICE TYPE STATE IP4-CONNECTIVITY IP6-CONNECTIVITY
DBUS-PATH CONNECTION CON-UUID CON-PATH
eno1 ethernet disconnected limited limited
/org/freedesktop/NetworkManager/Devices/2 -- -- --
lo loopback unmanaged unknown unknown
/org/freedesktop/NetworkManager/Devices/1 -- -- --
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW
WIFI WWAN-HW WWAN
running 1.16.0 disconnected started limited enabled enabled
enabled enabled enabled
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1827427/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
