Network does not work after restart from Windows 10

Bug #1904895 reported by Fred
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

I got a Intel I217-V integrated on the motherboard, it is an Ethernet NIC.

$ lspci
00:19.0 Ethernet controller: Intel Corporation Ethernet Connection I217-V (rev 04)

Before this worked good, but yesterday it stopped working after restarting the computer from Windows 10. I suspect there might have been some Windows update maybe.

It seems to work again after I went into the Device Manager in Windows and turned off power management settings.

Under the "Advanced" tab, I selected the "Enable PME" option and changed it from "Enabled" to "Disabled".

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: linux-image-generic 5.8.0.29.34
ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14
Uname: Linux 5.8.0-29-generic x86_64
ApportVersion: 2.20.11-0ubuntu50.1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: shockzor 1889 F.... pulseaudio
 /dev/snd/controlC0: shockzor 1889 F.... pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: GNOME
Date: Thu Nov 19 17:23:08 2020
HibernationDevice: RESUME=UUID=9f2a3e60-3444-415f-b930-aa1f0beffaf9
InstallationDate: Installed on 2013-12-26 (2519 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.
MachineType: ASUS All Series
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-29-generic root=UUID=31dc4488-28d4-4d2a-aa51-6733e237d5f8 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.8.0-29-generic N/A
 linux-backports-modules-5.8.0-29-generic N/A
 linux-firmware 1.190.1
RfKill:

SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/18/2014
dmi.bios.release: 4.6
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-PRO
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2103:bd08/18/2014:br4.6:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-PRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: ASUS MB
dmi.product.name: All Series
dmi.product.sku: All
dmi.product.version: System Version
dmi.sys.vendor: ASUS

Revision history for this message
Fred (eldmannen+launchpad) wrote :
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Alex Hung (alexhung) wrote :

When you reboot from Windows, i.e. network is unusable, does lspci show the NIC?

It might be possible that Windows powers off the NIC and motherboard does not power it on and therefore the NIC is no visible to Linux.

Revision history for this message
Fred (eldmannen+launchpad) wrote :

I think so, but that it is in some sleeping state. Because it worked to do "ethtool eth0" and "ifconfig".
I read on the web that someone had success with reset it by doing:
$ echo 1 > /sys/devices/pci0000\:00/0000:00:19.0/reset
But I never tried that.

I think Windows does not power it off, but puts it into some sleep state.

Revision history for this message
Fred (eldmannen+launchpad) wrote :

2020-11-18 15:37:54
Device PCI\VEN_8086&DEV_153B&SUBSYS_859F1043&REV_04\3&11583659&0&C8 was configured.

Driver Name: oem24.inf
Class Guid: {4d36e972-e325-11ce-bfc1-08002be10318}
Driver Date: 09/29/2020
Driver Version: 12.19.0.16
Driver Provider: Intel
Driver Section: E153B.10.0.1.19H1
Driver Rank: 0xFF2001
Matching Device Id: PCI\VEN_8086&DEV_153B
Outranked Drivers: net1ic64.inf:PCI\VEN_8086&DEV_153B:00FF2001
Device Updated: true
Parent Device: ACPI\PNP0A08\0

--

2020-11-18 15:37:54
Device PCI\VEN_8086&DEV_153B&SUBSYS_859F1043&REV_04\3&11583659&0&C8 had a problem starting.

Driver Name: oem24.inf
Class Guid: {4d36e972-e325-11ce-bfc1-08002be10318}
Service: e1dexpress
Lower Filters:
Upper Filters:
Problem: 0x15
Problem Status: 0x0

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

The log shows it's working:
[ 40.650463] e1000e 0000:00:19.0 eth0: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None

Can you please collect the log when it's not working?

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Fred (eldmannen+launchpad) wrote :

Alex Hung (alexhung), yes lspci shows the NIC.

This is from "lspci -vvv":

00:19.0 Ethernet controller: Intel Corporation Ethernet Connection I217-V (rev 04)
 DeviceName: Onboard LAN
 Subsystem: ASUSTeK Computer Inc. Ethernet Connection I217-V
 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
 Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
 Latency: 0
 Interrupt: pin A routed to IRQ 27
 Region 0: Memory at efc00000 (32-bit, non-prefetchable) [size=128K]
 Region 1: Memory at efc3d000 (32-bit, non-prefetchable) [size=4K]
 Region 2: I/O ports at f080 [size=32]
 Capabilities: <access denied>
 Kernel driver in use: e1000e
 Kernel modules: e1000e

description: updated
Revision history for this message
Fred (eldmannen+launchpad) wrote :

Kai-Heng Feng (kaihengfeng), yes but when I reported this bug it was after I had fixed it. I could not report this bug when I had no internet connectivity.

However, now that I run dmesg when after enabled the "Enable PME" setting on the NIC driver on Windows and restarted again, it still says "e1000e 0000:00:19.0 eth0: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None" despite not working.

[ 0.199867] pci 0000:00:19.0: [8086:153b] type 00 class 0x020000
[ 0.199881] pci 0000:00:19.0: reg 0x10: [mem 0xefc00000-0xefc1ffff]
[ 0.199886] pci 0000:00:19.0: reg 0x14: [mem 0xefc3d000-0xefc3dfff]
[ 0.199892] pci 0000:00:19.0: reg 0x18: [io 0xf080-0xf09f]
[ 0.199937] pci 0000:00:19.0: PME# supported from D0 D3hot D3cold
...
[ 0.852959] e1000e 0000:00:19.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode
...
[ 0.943948] e1000e 0000:00:19.0 0000:00:19.0 (uninitialized): registered PHC clock
[ 1.022272] e1000e 0000:00:19.0 eth0: (PCI Express:2.5GT/s:Width x1) 74:d0:2b:9e:e9:58
[ 1.022274] e1000e 0000:00:19.0 eth0: Intel(R) PRO/1000 Network Connection
[ 1.022314] e1000e 0000:00:19.0 eth0: MAC: 11, PHY: 12, PBA No: FFFFFF-0FF
...
[ 40.746594] e1000e 0000:00:19.0 eth0: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.