T550 crashed during attempted suspend: e1000e hardware error

Bug #1435073 reported by Shevek
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Running X. Nothing exciting.
Locked the screen and shut the lid.
Red LED took longer than normal to turn "off".
Then it went off, and didn't blink like in sleep mode.
Damnit, it's crashed, hasn't it.
Reboot, read log files. We got something this time. Here it is.

Mar 22 13:36:41 raven NetworkManager[1894]: <info> NetworkManager state is now ASLEEP
Mar 22 13:36:42 raven NetworkManager[1894]: <info> (cdc-wdm0): device state change: unavailable -> unmanaged (reason 'sleeping') [20 10 37]
Mar 22 13:36:42 raven dbus[1842]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'
Mar 22 13:36:42 raven systemd[1]: Starting Network Manager Script Dispatcher Service...
Mar 22 13:36:42 raven dbus[1842]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Mar 22 13:36:42 raven nm-dispatcher: Dispatching action 'down' for wlan0
Mar 22 13:36:42 raven systemd[1]: Started Network Manager Script Dispatcher Service.
Mar 22 13:36:43 raven systemd[1]: Reached target Sleep.
Mar 22 13:36:43 raven systemd[1]: Starting Sleep.
Mar 22 13:36:43 raven systemd[1]: Starting Suspend...
Mar 22 13:36:43 raven systemd-sleep[26355]: Suspending system...
Mar 22 13:36:43 raven NetworkManager[1894]: <info> wake requested (sleeping: yes enabled: yes)
Mar 22 13:36:43 raven NetworkManager[1894]: <info> waking up...
Mar 22 13:36:43 raven NetworkManager[1894]: <info> (eth0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Mar 22 13:37:03 raven kernel: [ 2906.011617] PM: Syncing filesystems ... done.
Mar 22 13:37:03 raven kernel: [ 2906.114788] PM: Preparing system for mem sleep
Mar 22 13:37:03 raven kernel: [ 2906.115270] Freezing user space processes ...
Mar 22 13:37:03 raven kernel: [ 2915.266916] e1000e 0000:00:19.0 eth0: Hardware Error
Mar 22 13:37:03 raven kernel: [ 2916.261811] e1000e 0000:00:19.0: EEE advertisement - unable to acquire PHY
Mar 22 13:37:03 raven kernel: [ 2926.137012]
Mar 22 13:37:03 raven kernel: [ 2926.137018] Freezing of tasks failed after 20.010 seconds (1 tasks refusing to freeze, wq_busy=0):
Mar 22 13:37:03 raven kernel: [ 2926.137038] NetworkManager R running task 0 1894 1 0x00000004
Mar 22 13:37:03 raven kernel: [ 2926.137043] ffffffffffffff10 ffffffff8101e1bc 0000000000000010 0000000000000206
Mar 22 13:37:03 raven kernel: [ 2926.137047] ffff880417253480 0000000000000018 ffff8804172534a8 ffffffff813c151b
Mar 22 13:37:03 raven kernel: [ 2926.137051] 0000000000000001 ffff880414c3ce38 0000000000000000 ffff880417253530
Mar 22 13:37:03 raven kernel: [ 2926.137055] Call Trace:
Mar 22 13:37:03 raven kernel: [ 2926.137064] [<ffffffff8101e1bc>] ? native_read_tsc+0xc/0x20
Mar 22 13:37:03 raven kernel: [ 2926.137070] [<ffffffff813c151b>] ? delay_tsc+0x3b/0x80
Mar 22 13:37:03 raven kernel: [ 2926.137075] [<ffffffff813c1526>] ? delay_tsc+0x46/0x80
Mar 22 13:37:03 raven kernel: [ 2926.137079] [<ffffffff813c151b>] ? delay_tsc+0x3b/0x80
Mar 22 13:37:03 raven kernel: [ 2926.137084] [<ffffffff813c145b>] ? __const_udelay+0x2b/0x30
Mar 22 13:37:03 raven kernel: [ 2926.137111] [<ffffffffc033fc1a>] ? e1000_acquire_swflag_ich8lan+0x7a/0x180 [e1000e]
Mar 22 13:37:03 raven kernel: [ 2926.137122] [<ffffffffc03401c9>] ? e1000_clear_hw_cntrs_ich8lan+0xa9/0x1e0 [e1000e]
Mar 22 13:37:03 raven kernel: [ 2926.137133] [<ffffffffc0342c46>] ? e1000_init_hw_ich8lan+0x236/0x340 [e1000e]
Mar 22 13:37:03 raven kernel: [ 2926.137147] [<ffffffffc035c4aa>] ? e1000e_reset+0x23a/0x620 [e1000e]
Mar 22 13:37:03 raven kernel: [ 2926.137161] [<ffffffffc035a1c3>] ? e1000e_setup_rx_resources+0x103/0x140 [e1000e]
Mar 22 13:37:03 raven kernel: [ 2926.137173] [<ffffffffc035dd70>] ? e1000_open+0x3a0/0x4b0 [e1000e]
Mar 22 13:37:03 raven kernel: [ 2926.137179] [<ffffffff81095756>] ? raw_notifier_call_chain+0x16/0x20
Mar 22 13:37:03 raven kernel: [ 2926.137186] [<ffffffff816bfbe6>] ? __dev_open+0xb6/0x130
Mar 22 13:37:03 raven kernel: [ 2926.137190] [<ffffffff816bff11>] ? __dev_change_flags+0xa1/0x170
Mar 22 13:37:03 raven kernel: [ 2926.137193] [<ffffffff816c0009>] ? dev_change_flags+0x29/0x70
Mar 22 13:37:03 raven kernel: [ 2926.137197] [<ffffffff816cf787>] ? do_setlink+0x3a7/0xb80
Mar 22 13:37:03 raven kernel: [ 2926.137204] [<ffffffff811989d0>] ? zone_statistics+0x80/0xa0
Mar 22 13:37:03 raven kernel: [ 2926.137209] [<ffffffff813dedd2>] ? nla_parse+0x32/0x120
Mar 22 13:37:03 raven kernel: [ 2926.137213] [<ffffffff816d069d>] ? rtnl_newlink+0x5fd/0x760
Mar 22 13:37:03 raven kernel: [ 2926.137218] [<ffffffff81312268>] ? security_capable+0x18/0x20
Mar 22 13:37:03 raven kernel: [ 2926.137223] [<ffffffff8107e64d>] ? ns_capable+0x2d/0x60
Mar 22 13:37:03 raven kernel: [ 2926.137226] [<ffffffff816cc7f2>] ? rtnetlink_rcv_msg+0x92/0x260
Mar 22 13:37:03 raven kernel: [ 2926.137231] [<ffffffff813c9436>] ? rhashtable_lookup_compare+0x36/0x70
Mar 22 13:37:03 raven kernel: [ 2926.137235] [<ffffffff816e9d7e>] ? __netlink_lookup+0x3e/0x50
Mar 22 13:37:03 raven kernel: [ 2926.137238] [<ffffffff816cc760>] ? rtnetlink_rcv+0x40/0x40
Mar 22 13:37:03 raven kernel: [ 2926.137242] [<ffffffff816edc89>] ? netlink_rcv_skb+0xb9/0xe0
Mar 22 13:37:03 raven kernel: [ 2926.137245] [<ffffffff816cc74c>] ? rtnetlink_rcv+0x2c/0x40
Mar 22 13:37:03 raven kernel: [ 2926.137248] [<ffffffff816ed3c1>] ? netlink_unicast+0x111/0x1b0
Mar 22 13:37:03 raven kernel: [ 2926.137252] [<ffffffff816ed767>] ? netlink_sendmsg+0x307/0x650
Mar 22 13:37:03 raven kernel: [ 2926.137256] [<ffffffff8135e2f0>] ? aa_sk_perm.isra.4+0x70/0x170
Mar 22 13:37:03 raven kernel: [ 2926.137260] [<ffffffff816a1e5c>] ? do_sock_sendmsg+0x8c/0x100
Mar 22 13:37:03 raven kernel: [ 2926.137264] [<ffffffff816a181c>] ? copy_msghdr_from_user+0x15c/0x210
Mar 22 13:37:03 raven kernel: [ 2926.137268] [<ffffffff816a2478>] ? ___sys_sendmsg+0x348/0x360
Mar 22 13:37:03 raven kernel: [ 2926.137273] [<ffffffff81180f67>] ? __free_pages+0x27/0x30
Mar 22 13:37:03 raven kernel: [ 2926.137277] [<ffffffff81180fd3>] ? free_pages+0x13/0x20
Mar 22 13:37:03 raven kernel: [ 2926.137281] [<ffffffff8107cea6>] ? __do_proc_dointvec+0x346/0x420
Mar 22 13:37:03 raven kernel: [ 2926.137286] [<ffffffff8123321e>] ? fsnotify+0x37e/0x530
Mar 22 13:37:03 raven kernel: [ 2926.137290] [<ffffffff813c2c38>] ? lockref_put_or_lock+0x58/0x90
Mar 22 13:37:03 raven kernel: [ 2926.137294] [<ffffffff8120b166>] ? dput+0x56/0x1c0
Mar 22 13:37:03 raven kernel: [ 2926.137298] [<ffffffff812143e4>] ? mntput+0x24/0x40
Mar 22 13:37:03 raven kernel: [ 2926.137302] [<ffffffff816a2b92>] ? __sys_sendmsg+0x42/0x80
Mar 22 13:37:03 raven kernel: [ 2926.137306] [<ffffffff816a2be2>] ? SyS_sendmsg+0x12/0x20
Mar 22 13:37:03 raven kernel: [ 2926.137311] [<ffffffff817c7aed>] ? system_call_fastpath+0x16/0x1b
Mar 22 13:37:03 raven kernel: [ 2926.137352]
Mar 22 13:37:03 raven kernel: [ 2926.137353] Restarting tasks ... done.
Mar 22 13:37:03 raven rtkit-daemon[2151]: The canary thread is apparently starving. Taking action.
Mar 22 13:37:03 raven rtkit-daemon[2151]: Demoting known real-time threads.
Mar 22 13:37:03 raven rtkit-daemon[2151]: Successfully demoted thread 2740 of process 2697 (n/a).
Mar 22 13:37:03 raven rtkit-daemon[2151]: Successfully demoted thread 2738 of process 2697 (n/a).
Mar 22 13:37:03 raven rtkit-daemon[2151]: Successfully demoted thread 2736 of process 2697 (n/a).
Mar 22 13:37:03 raven rtkit-daemon[2151]: Successfully demoted thread 2697 of process 2697 (n/a).
Mar 22 13:37:03 raven rtkit-daemon[2151]: Demoted 4 threads.

Then the machine abruptly powered off. ARGH! AAAAAAAAAAAAAARGH!!!!!

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: linux-image-3.19.0-9-generic 3.19.0-9.9
ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
Uname: Linux 3.19.0-9-generic x86_64
ApportVersion: 2.16.2-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: shevek 2677 F.... pulseaudio
 /dev/snd/controlC0: shevek 2677 F.... pulseaudio
CurrentDesktop: XFCE
Date: Sun Mar 22 13:47:36 2015
HibernationDevice: RESUME=UUID=cd97b65a-0d29-4887-a0e6-7c9eea8707b0
InstallationDate: Installed on 2015-03-05 (17 days ago)
InstallationMedia: Xubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
MachineType: LENOVO 20CKCTO1WW
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-9-generic.efi.signed root=/dev/mapper/xubuntu--vg-root ro quiet splash crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.19.0-9-generic N/A
 linux-backports-modules-3.19.0-9-generic N/A
 linux-firmware 1.143
SourcePackage: linux
UpgradeStatus: Upgraded to vivid on 2015-03-19 (3 days ago)
dmi.bios.date: 12/26/2014
dmi.bios.vendor: LENOVO
dmi.bios.version: N11ET29W (1.05 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20CKCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0E50512 STD
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: dmi:bvnLENOVO:bvrN11ET29W(1.05):bd12/26/2014:svnLENOVO:pn20CKCTO1WW:pvrThinkPadT550:rvnLENOVO:rn20CKCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone:
dmi.product.name: 20CKCTO1WW
dmi.product.version: ThinkPad T550
dmi.sys.vendor: LENOVO

Revision history for this message
Shevek (r-launchpad-anarres-org) wrote :
Revision history for this message
Shevek (r-launchpad-anarres-org) wrote :

Also, why didn't it just fail to suspend? Why power the entire machine off? That's the most frustrating possible behaviour, as I lose my work. :-(

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
Joseph Salisbury (jsalisbury) wrote :

Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?

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

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
tags: added: kernel-unable-to-test-upstream
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Shevek (r-launchpad-anarres-org) wrote :

Workaround (unfortunately):

shevek@raven:~$ cat /etc/modprobe.d/local.conf
blacklist e1000e

Revision history for this message
Shevek (r-launchpad-anarres-org) wrote :

After a week, still reliable with e1000e blacklisted. Strong correlation now established?

Revision history for this message
Shevek (r-launchpad-anarres-org) wrote :

Bug not observed in 4.2.0.

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.