[LENOVO 3000 Y410] suspend/resume failure

[Essa J Permana]

suddenly i got this error after entered the desktop after login

ProblemType: KernelOops
DistroRelease: Ubuntu 13.10
Package: linux-image-3.11.0-7-generic 3.11.0-7.13
ProcVersionSignature: Ubuntu 3.11.0-7.13-generic 3.11.0
Uname: Linux 3.11.0-7-generic i686
Annotation: This occured during a previous suspend and prevented it from resuming properly.
ApportVersion: 2.12.1-0ubuntu4
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: essajiwa 2183 F.... pulseaudio
Date: Sat Sep 14 01:27:30 2013
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: suspend/resume
HibernationDevice: RESUME=UUID=da679f1b-70ac-42e0-a4e5-fe541510ce53
InstallationDate: Installed on 2013-02-25 (199 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2)
InterpreterPath: /usr/bin/python3.3
MachineType: LENOVO LENOVO3000 Y410
MarkForUpload: True
ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-7-generic root=UUID=797bbdac-7bb0-4e34-9b50-7fe5114e9f05 ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not responding.
RelatedPackageVersions:
 linux-restricted-modules-3.11.0-7-generic N/A
 linux-backports-modules-3.11.0-7-generic N/A
 linux-firmware 1.114
SourcePackage: linux
Title: [LENOVO LENOVO3000 Y410] suspend/resume failure
UpgradeStatus: Upgraded to saucy on 2013-08-11 (33 days ago)
UserGroups:

dmi.bios.date: 03/26/2008
dmi.bios.vendor: LENOVO
dmi.bios.version: 05CN63WW(V3.05)
dmi.board.name: IGT30
dmi.board.vendor: LENOVO
dmi.board.version: 05CN63WW
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnLENOVO:bvr05CN63WW(V3.05):bd03/26/2008:svnLENOVO:pnLENOVO3000Y410:pvr:rvnLENOVO:rnIGT30:rvr05CN63WW:cvnNoEnclosure:ct10:cvrN/A:
dmi.product.name: LENOVO3000 Y410
dmi.sys.vendor: LENOVO

[Brad Figg (brad-figg)]

This change was made by a bot.

[penalvch (penalvch)]

Essa J Permana, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily kernel folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.11.1

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

[Essa J Permana (essa-jp)]

I don't know how, but on my laptop now the bug doesn't exist anymore. I haven't using the latest upstream kernel yet. So should I change the status and tag as you mentioned above? Thanks.

[penalvch (penalvch)]

Essa J Permana, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1225138/comments/4 regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.