8086:1502 [Lenovo ThinkPad W530] e1000e module sometimes prevents suspend to ram

This change was made by a bot.

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.11 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'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-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/v3.11-rc5-saucy/

Hi,
Unfortunately it doesn't look feasible for me to run with the mainline kernel for long as I can't get the nvidia driver working in it:

Setting up linux-headers-3.11.0-031100rc5-generic (3.11.0-031100rc5.201308112135) ...
Examining /etc/kernel/header_postinst.d.
run-parts: executing /etc/kernel/header_postinst.d/dkms 3.11.0-031100rc5-generic /boot/vmlinuz-3.11.0-031100rc5-generic
Traceback (most recent call last):
  File "/usr/share/apport/package-hooks/dkms_packages.py", line 22, in <module>
    import apport
ImportError: No module named apport
Error! Bad return status for module build on kernel: 3.11.0-031100rc5-generic (x86_64)
Consult /var/lib/dkms/nvidia-304-updates/304.88/build/make.log for more information.

The problem I see with the e1000e driver is too infrequent for me to test the kernel briefly, and without the nvidia drivers I cannot do my dayjob on this laptop. If I can find a way to trigger the problem on demand, then I am happy to attempt this again on a mainline kernel.

Hi, I updated to the new bios but still had the problem earlier today.
$ sudo dmidecode -s bios-version && sudo dmidecode -s -daterelease
G5ET93WW (2.53 )
05/24/2013

Anton Piatek, could you please confirm this issue exists with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ . If the issue remains, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

For reference I tried booting the latest mainline kernel, and apart from screwing up unity (see bug 1215828) it suspended once, then failed to resume. There was a reason I started using the nvidia driver, and that is because the nouveau one fails to resume. So testing on that won't be possible.
I am expecting that a live cd will have a similar problem, so don't know if testing it will be feasible.

It is not possible to test this on the latest development image as the nouveau driver does not resume (desktop completely locks up), and the e1000e problem is intermittent, so a full reboot between tests is infeasible.

Is there any debug info that I can gather to assist here? Any logs or trace?

Anton Piatek, did this problem not occur in Precise with the nvidia drivers?

I don't know. It is a new laptop and raring is the first thing I installed
on it.

There are many other people discussing this problem on other forums:

https://lkml.org/lkml/2013/7/15/69 (July 2013)
http://forums.fedoraforum.org/archive/index.php/t-293457.html (August 2013)

It's not easy to regression test this since rebooting fixes the problem. However, once the problem occurrs, I can easily debug things.

For instance, I know that "sudo rmmod e1000e" is a valid work-around for this problem.

I also have a W530, if that matters.

aporter, if you have a bug in Ubuntu, the Ubuntu Kernel team, Ubuntu Bug Control team, and Ubuntu Bug Squad would like you to please file a new report by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Please note, not filing a new report would delay your problem being addressed as quickly as possible.

No need exists to comment here at this time. After reading the above documentation in it's entirety, if you have further questions, you are welcome to redirect them to the appropriate mailing list or forum via http://www.ubuntu.com/support/community/mailinglists , or you may contact me directly.

Thank you for your understanding.

Are you sure? It's the same exact bug. Won't my bug be a duplicate?

I have the same log entries "Device 0000:00:19.0 failed to suspend async: error -2"

I have the same symptoms.

The same workaround works for me.

I even have the same exact hardware.

If you're sure, I'll do it, I just want to be sure you're sure.

thanks,

adrian

A duplicate actually counts for "heat" than reporting it "affects me too"

aporter, yes please file a new report as previously requested.

Ok, I will comply.

This is also happening to me on saucy:

Nov 12 12:08:38 pk0k4dr kernel: [33964.643792] PM: Syncing filesystems ... done.
Nov 12 12:08:38 pk0k4dr kernel: [33965.021021] PM: Preparing system for mem sleep
Nov 12 12:08:42 pk0k4dr kernel: [33965.134863] Freezing user space processes ... (elapsed 0.001 seconds) done.
Nov 12 12:08:42 pk0k4dr kernel: [33965.136441] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
Nov 12 12:08:42 pk0k4dr kernel: [33965.137766] PM: Entering mem sleep
Nov 12 12:08:42 pk0k4dr kernel: [33965.137838] Suspending console(s) (use no_console_suspend to debug)
Nov 12 12:08:42 pk0k4dr kernel: [33965.137889] xhci_hcd 0000:00:14.0: power state changed by ACPI to D0
Nov 12 12:08:42 pk0k4dr kernel: [33965.238268] xhci_hcd 0000:00:14.0: setting latency timer to 64
Nov 12 12:08:42 pk0k4dr kernel: [33965.238338] ehci-pci 0000:00:1a.0: power state changed by ACPI to D0
Nov 12 12:08:42 pk0k4dr kernel: [33965.342280] ehci-pci 0000:00:1a.0: setting latency timer to 64
Nov 12 12:08:42 pk0k4dr kernel: [33965.342306] ehci-pci 0000:00:1d.0: power state changed by ACPI to D0
Nov 12 12:08:42 pk0k4dr kernel: [33965.446254] ehci-pci 0000:00:1d.0: setting latency timer to 64
Nov 12 12:08:42 pk0k4dr kernel: [33965.578114] sd 0:0:0:0: [sda] Synchronizing SCSI cache
Nov 12 12:08:42 pk0k4dr kernel: [33965.578476] sd 0:0:0:0: [sda] Stopping disk
Nov 12 12:08:42 pk0k4dr kernel: [33965.802057] nouveau [ DRM] suspending fbcon...
Nov 12 12:08:42 pk0k4dr kernel: [33965.802061] nouveau [ DRM] suspending display...
Nov 12 12:08:42 pk0k4dr kernel: [33965.802087] nouveau [ DRM] unpinning framebuffer(s)...
Nov 12 12:08:42 pk0k4dr kernel: [33965.802480] mei_me 0000:00:16.0: suspend
Nov 12 12:08:42 pk0k4dr kernel: [33965.803108] nouveau [ DRM] evicting buffers...
Nov 12 12:08:42 pk0k4dr kernel: [33965.827282] nouveau [ DRM] waiting for kernel channels to go idle...
Nov 12 12:08:42 pk0k4dr kernel: [33965.827309] nouveau [ DRM] suspending client object trees...
Nov 12 12:08:42 pk0k4dr kernel: [33965.835924] nouveau [ DRM] suspending kernel object tree...
Nov 12 12:08:42 pk0k4dr kernel: [33966.209804] i915 0000:00:02.0: power state changed by ACPI to D3cold
Nov 12 12:08:42 pk0k4dr kernel: [33966.429324] pci_pm_suspend(): e1000_suspend+0x0/0x20 [e1000e] returns -2
Nov 12 12:08:42 pk0k4dr kernel: [33966.429328] dpm_run_callback(): pci_pm_suspend+0x0/0x150 returns -2
Nov 12 12:08:42 pk0k4dr kernel: [33966.429330] PM: Device 0000:00:19.0 failed to suspend async: error -2
Nov 12 12:08:42 pk0k4dr kernel: [33967.221549] nouveau 0000:01:00.0: power state changed by ACPI to D3cold
Nov 12 12:08:42 pk0k4dr kernel: [33967.221613] PM: Some devices failed to suspend, or early wake event detected
Nov 12 12:08:42 pk0k4dr kernel: [33967.221661] i915 0000:00:02.0: power state changed by ACPI to D0
Nov 12 12:08:42 pk0k4dr kernel: [33967.221684] xhci_hcd 0000:00:14.0: setting latency timer to 64
Nov 12 12:08:42 pk0k4dr kernel: [33967.221737] mei_me 0000:00:16.0: irq 45 for MSI/MSI-X

I haven't seen it in saucy yet, but then I haven't been on saucy all that long

Just seen this on saucy with kernel 3.11.0-13-generic
[32026.365726] PM: Entering mem sleep
[32026.365783] Suspending console(s) (use no_console_suspend to debug)
[32026.491757] sd 0:0:0:0: [sda] Synchronizing SCSI cache
[32026.491946] sd 0:0:0:0: [sda] Stopping disk
[32026.724207] mei_me 0000:00:16.0: suspend
[32027.346674] pci_pm_suspend(): e1000_suspend+0x0/0x20 [e1000e] returns -2
[32027.346678] dpm_run_callback(): pci_pm_suspend+0x0/0x150 returns -2
[32027.346681] PM: Device 0000:00:19.0 failed to suspend async: error -2
[32027.346722] PM: Some devices failed to suspend, or early wake event detected

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

Bios upgrade didn't help

$sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
G5ET96WW (2.56 )
11/27/2013

Anton Piatek, could you please confirm this issue exists with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ . If the issue remains, please just make a comment to this.

Just adding a note for a possible cause: I have a Lenovo T430s running Ubuntu Quantal with this same problem, and it only seems to occur just after undocking the laptop. I wonder if this puts the ethernet driver in a bad state. (The workaround also works for me.)

Hi Christopher @penalvch, thanks for the update. Given the intermittent nature of the bug (not every suspend is prevented from succeeding) it is going to be incredibly difficult for me to reproduce on a livecd. Has anything changed in this driver that makes you think it will be better for me? It hasn't changed between raring and saucy.

Is there a possibility of trying only a newer kernel from trusty perhaps, then I could use it for a week as normal and see if the issue still presents itself?

Perhaps there is some debug output I could gather that might point to a cause? This might help determine if undocking is involved as Tim mentions

Tim McCormack, thank you for your comment. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

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

I am still being affected by this

This change was made by a bot.

I can confirm this bug exists in trusty. Would be nice to fix on an LTS release.

I had not been using ethernet (only wireless) for some time, but recently started using wired and this bug very consistently prevents suspend. I think the occurrance is around 100% of the time if I suspend after ethernet has been used.

"sudo rmmod e1000e; sudo modprobe e1000e" is an easy enough workaround, but it continues to be an annoyance.

up-to-date ubuntu 14.04 with "Linux zem 3.13.0-29-generic #53-Ubuntu SMP Wed Jun 4 21:00:20 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux" kernel.