ethernet card can not resume

Bug #1534985 reported by Yuan Song
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

I have two network cards on my desktop. Both failed to resume from S3. Both cards are intel cards. The driver I am using is e1000e-3.2.4.2 . I did some driver debug and found the watchdog event in the driver was not triggered. The watchdog event is used to check if the card is ready. I also tried Ubuntu 15.10 on the same machine. The cards can wake up from S3 under linux kernel 4.2 . Here is the configuration I have on my machine

Motherboard ASRock H170 Pro4 Bios p1.8
CPU: Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz
Memory : G.Skill Ripjaws V Series 8G DDR4
Ethernet cards: Intel PRO/1000 PT and Intel® Ethernet Connection I219-V (built-in)
Ubuntu 14.04
Kernel : 3.13.0-74-generic
driver: e1000e-3.2.4.2

00:1f.6 Ethernet controller: Intel Corporation Device 15b8 (rev 31)
        Subsystem: ASRock Incorporation Device 15b8
        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 146
        Region 0: Memory at df300000 (32-bit, non-prefetchable) [size=128K]
        Capabilities: <access denied>
        Kernel driver in use: e1000e

03:00.0 Ethernet controller: Intel Corporation 82572EI Gigabit Ethernet Controller (Copper) (rev 06)
        Subsystem: Intel Corporation PRO/1000 PT Server Adapter
        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 147
        Region 0: Memory at df240000 (32-bit, non-prefetchable) [size=128K]
        Region 1: Memory at df220000 (32-bit, non-prefetchable) [size=128K]
        Region 2: I/O ports at d000 [size=32]
        Expansion ROM at df200000 [disabled] [size=128K]
        Capabilities: <access denied>
        Kernel driver in use: e1000e

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-74-generic 3.13.0-74.118 [modified: lib/modules/3.13.0-74-generic/kernel/drivers/net/ethernet/intel/e1000e/e1000e.ko]
ProcVersionSignature: Ubuntu 3.13.0-74.118-generic 3.13.11-ckt30
Uname: Linux 3.13.0-74-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC2: yuan 3396 F.... pulseaudio
 /dev/snd/controlC1: yuan 3396 F.... pulseaudio
 /dev/snd/controlC0: yuan 3396 F.... pulseaudio
CurrentDesktop: Unity
Date: Sat Jan 16 13:51:21 2016
HibernationDevice: RESUME=UUID=f8281216-c26a-4a26-9279-ed9fa58388c8
InstallationDate: Installed on 2013-04-02 (1019 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcFB:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-74-generic root=UUID=f630d0df-facb-47b4-b39a-be87a1252e93 ro crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-74-generic N/A
 linux-backports-modules-3.13.0-74-generic N/A
 linux-firmware 1.127.19
RfKill:
 0: hci0: Bluetooth
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
UpgradeStatus: Upgraded to trusty on 2014-04-19 (637 days ago)
dmi.bios.date: 11/10/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.80
dmi.board.name: H170M Pro4
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.80:bd11/10/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH170MPro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.

Revision history for this message
Yuan Song (ysong) wrote :
Revision history for this message
Yuan Song (ysong) wrote :
Revision history for this message
Brad Figg (brad-figg) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Yuan Song (ysong) wrote :

I also tried kernel 4.2 and 3.19 in ubuntu 14.04. The same problem happened. It is pretty strange. It works in Ubuntu 15.10

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.4 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4-wily

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
tags: added: needs-bisect regression-release
Revision history for this message
Yuan Song (ysong) wrote :

kernel-bug-exists-upstream

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
penalvch (penalvch) wrote :

Yuan Song, could you please advise if the latest mainline kernel (4.5-rc1) changes anything?

tags: added: latest-bios-1.80
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Yuan Song (ysong) wrote :

4.5-rc1 makes no difference. But, as I said, 15.10 works fine. May not be pure kernel issue.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Yuan Song (ysong) wrote :

the problem does not happen in 16.04

Revision history for this message
Yuan Song (ysong) wrote :

After using 16.04 for several months, I found the same problem can also happen in 16.04. It just happens much less frequently. Do not see any pattern when it can happen.

Revision history for this message
Yuan Song (ysong) wrote :

looks like it is related to scheduler timer. I got a different issue with another device. After spending some time debugging the driver, I found the timeout was not scheduled correctly. Even though the timeout value was set to 3 minutes, timeout happened within 100ms

Revision history for this message
Yuan Song (ysong) wrote :

I was wrong. The timestamp in the printk output is not quite accurate. Looks like timestamp is added asynchronously.

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.