[IBM 184348M] suspend/resume failure

Bug #1362660 reported by Stephen Angelico
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned

Bug Description

My laptop is an old Thinkpad R51e for which suspending does not work, with or without linux-firmware-nonfree. Without, calling a suspend would cause the laptop to fade the screen to black, flash the sleep light for a while, then be asleep for one second before waking up again without any trigger such as opening the lid or pressing a key. With linux-firmware-nonfree, calling a suspend causes a fade of the screen and the sleep light flashing as before, but the light keeps flashing and the fan keeps going for more time than I waited (at least 30 seconds), such that I did a hard shutdown.
Ubuntu version: 14.10 Utopic Unicorn (development branch) - UbuntuMATE Alpha 2
linux-firmware-non-free version: 1.16 (latest packaged at time of writing)

ProblemType: KernelOops
DistroRelease: Ubuntu 14.10
Package: linux-image-3.16.0-10-generic 3.16.0-10.15
ProcVersionSignature: Ubuntu 3.16.0-10.15-generic 3.16.1
Uname: Linux 3.16.0-10-generic i686
Annotation: This occured during a previous suspend and prevented it from resuming properly.
ApportVersion: 2.14.6-0ubuntu2
Architecture: i386
CRDA:
 country AU: DFS-UNSET
  (2402 - 2482 @ 40), (N/A, 20)
  (5170 - 5250 @ 40), (3, 23)
  (5250 - 5330 @ 40), (3, 23), DFS
  (5735 - 5835 @ 40), (3, 30)
Date: Fri Aug 29 00:55:44 2014
DuplicateSignature: suspend/resume:IBM 184348M:78ET36WW (1.07 )
ExecutablePath: /usr/share/apport/apportcheckresume
ExecutableTimestamp: 1408437800
Failure: suspend/resume
HibernationDevice: RESUME=UUID=4d358988-246f-4712-afdf-d358ff67643c
InstallationDate: Installed on 2014-08-27 (1 days ago)
InstallationMedia: Ubuntu MATE 14.10 "Utopic Unicorn" - Alpha i386 (20140731)
InterpreterPath: /usr/bin/python3.4
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: IBM 184348M
ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
ProcCwd: /
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-10-generic root=UUID=dfec0088-7f1e-4ac6-a114-e68f5f95a911 ro quiet splash
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-3.16.0-10-generic N/A
 linux-backports-modules-3.16.0-10-generic N/A
 linux-firmware 1.132
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
Title: [IBM 184348M] suspend/resume failure
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 10/31/2005
dmi.bios.vendor: IBM
dmi.bios.version: 78ET36WW (1.07 )
dmi.board.name: 184348M
dmi.board.vendor: IBM
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: IBM
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnIBM:bvr78ET36WW(1.07):bd10/31/2005:svnIBM:pn184348M:pvrThinkPadR51e:rvnIBM:rn184348M:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
dmi.product.name: 184348M
dmi.product.version: ThinkPad R51e
dmi.sys.vendor: IBM

Revision history for this message
Stephen Angelico (raaff35lightning) wrote :
tags: removed: need-duplicate-check
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 :

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

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
penalvch (penalvch)
tags: added: bios-outdated-1.61
Revision history for this message
Stephen Angelico (raaff35lightning) wrote :

This bug can now be closed - I upgraded to kernel 3.16.0-11-generic after installing 3.17-rc2 but before rebooting. Due to my Debian-Ubuntu dual-boot system, I had to boot into Debian to update-grub, after which I booted into the default Ubuntu kernel, which was now 3.16.0-11-generic. In the nature of experimentation, I ordered a suspend, which worked just fine, though it takes a while. It doesn't take as long as I waited on kernel 3.16.0-10-generic, but it is a little bit annoying. Also, Hibernating works, but after suspending, instead of shutting down, it appears to reboot. This is probably a separate bug though, and I am happy to have this one closed and to open a new one.

Changed in linux (Ubuntu):
status: Incomplete → Fix Released
Revision history for this message
Stephen Angelico (raaff35lightning) wrote :

It seems I spoke in haste. Suspending seems to work when on power, but on battery, it immediately un-suspends after suspending, exactly like the previous kernel without linux-firmware-nonfree.
I am mobile at the moment but when I get home I will try the 3.17-rc2 kernel.

Revision history for this message
Stephen Angelico (raaff35lightning) wrote :

I dint know what is going on here - I just rebooted, logged in and suspended, which worked as it did 7 hours ago. What happened was:
Settings: Lid closed - on power, blank screen; on battery, suspend.
The lid was closed while the laptop was on power (that's how I leave it at night). I had to take it in a hurry, with its power cord, so I unplugged the cord, and saw the sleep light start flashing. While I was packing the power cord into his case, I heard a beep for suspending, then 1 second later, another beep for unsuspending. I rebooted when I had time, suspended and it succeeded.
I haven't tested whether there is a difference between closing the lid and pressing Fn-F4 (Thinkpad suspend trigger, seems to be the sleep button mentioned on the General tab in mate-power-preferences).

Revision history for this message
Stephen Angelico (raaff35lightning) wrote :

Initial experimentation - only the first suspend works. The second time, it suspends and then un-suspends immediately. The third time, it blanks the screen and flashes the sleep light until I run out of patience and do a hard shutdown. I don't know if the attached log was attached initially, but it may have more info now.

Revision history for this message
Stephen Angelico (raaff35lightning) wrote :
Revision history for this message
Stephen Angelico (raaff35lightning) wrote :
Revision history for this message
penalvch (penalvch) wrote :

Stephen Angelico, as per http://download.lenovo.com/express/ddfm.html an update to your BIOS is available (1.61). If you update to this following https://help.ubuntu.com/community/BiosUpdate does it change anything? If it doesn't, could you please both specify what happened, and provide the output of the following terminal command:
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date

Please note your current BIOS is already in the Bug Description, so posting this on the old BIOS would not be helpful. As well, you don't have to create a new bug report. As well, you don't have to create a new bug report.

For more on BIOS updates and linux, please see https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette .

Once the BIOS is updated, then please mark this report Status Confirmed.

Thank you for your understanding.

Changed in linux (Ubuntu):
status: Fix Released → Incomplete
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.