[Bug 1827427] Re: DHCP IP not obtainable if booting into Linux from suspended/hibernated/rebooted Windows

2019-07-23 Thread Launchpad Bug Tracker
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

** Changed in: linux (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1827427

Title:
  DHCP IP not obtainable if booting into Linux from
  suspended/hibernated/rebooted Windows

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1827427/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1827427] Re: DHCP IP not obtainable if booting into Linux from suspended/hibernated/rebooted Windows

2019-05-24 Thread Kai-Heng Feng
Please test mainline kernel and see if it helps:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.2-rc1/

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1827427

Title:
  DHCP IP not obtainable if booting into Linux from
  suspended/hibernated/rebooted Windows

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1827427/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1827427] Re: DHCP IP not obtainable if booting into Linux from suspended/hibernated/rebooted Windows

2019-05-24 Thread Kai-Heng Feng
[  668.026515] NETDEV WATCHDOG: eno1 (e1000e): transmit queue 0 timed
out

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1827427

Title:
  DHCP IP not obtainable if booting into Linux from
  suspended/hibernated/rebooted Windows

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1827427/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1827427] Re: DHCP IP not obtainable if booting into Linux from suspended/hibernated/rebooted Windows

2019-05-02 Thread Christopher Woods
apport information

** Tags added: apport-collected

** Description changed:

  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/: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:
   lono 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=
   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-REALAUTOCONNECT  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 
   eno1ethernet  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
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.10-0ubuntu27
+ Architecture: amd64
+ CasperVersion: 1.405
+ DistroRelease: Ubuntu 19.04
+ IwConfig:
+  lono wireless extensions.
+  
+  eno1  no wireless extensions.
+ LiveMediaBuild: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
+ MachineType: ASUS All Series
+ Package: linux (not installed)
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  LANG=C.UTF-8
+  SHELL=/bin/bash
+ ProcFB: 0 nouveaufb
+ ProcKernelCmdLine: file=/cdrom/preseed/ubuntu.seed noprompt persistent 
boot=casper 
iso-scan/filename=/multiboot/ubuntu-19.04-desktop-amd64/ubuntu-19.04-desktop-amd64.iso
 quiet --
+ ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
+ PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
+ RelatedPackageVersions:
+  linux-restricted-modules-5.0.0-13-generic N/A
+  linux-backports-modules-5.0.0-13-generic  N/A
+  linux-firmware1.178
+ RfKill:
+  
+ Tags:  disco
+ Uname: Linux 5.0.0-13-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups:
+  
+ _MarkForUpload: True
+ dmi.bios.date: 08/15/2014
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: 2103
+ dmi.board.asset.tag: To be filled by O.E.M.
+ dmi.board.name: Z87-PLUS
+ dmi.board.vendor: ASUSTeK COMPUTER INC.
+ dmi.board.version: Rev 1.xx
+ dmi.chassis.asset.tag: Asset-1234567890
+ dmi.chassis.type: 3
+ 

[Bug 1827427] Re: DHCP IP not obtainable if booting into Linux from suspended/hibernated/rebooted Windows

2019-05-02 Thread Sebastien Bacher
Thank you for your bug report. It does look like rather an
hardware/driver/kernel issue than a network-manager one though,
reassigning

** Package changed: network-manager (Ubuntu) => linux (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1827427

Title:
  DHCP IP not obtainable if booting into Linux from
  suspended/hibernated/rebooted Windows

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1827427/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs