[Dell Vostro 3500] suspend/resume failure

[Henri Coetzee]

cannot suspend/resume

ProblemType: KernelOops
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-18-generic 3.13.0-18.38
ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6
Uname: Linux 3.13.0-18-generic x86_64
Annotation: This occured during a previous suspend and prevented it from resuming properly.
ApportVersion: 2.13.3-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: henri 2043 F.... pulseaudio
Date: Sat Mar 22 16:52:59 2014
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: suspend/resume
HibernationDevice: RESUME=UUID=1c6d8279-b292-4118-8024-3df6cbea7728
InstallationDate: Installed on 2014-01-21 (59 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
InterpreterPath: /usr/bin/python3.4
MachineType: Dell Inc. Vostro 3500
ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-18-generic root=UUID=806668cf-b440-4beb-8f0d-9b701dc289bf ro quiet splash vt.handoff=7
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.13.0-18-generic N/A
 linux-backports-modules-3.13.0-18-generic N/A
 linux-firmware 1.126
SourcePackage: linux
Title: [Dell Inc. Vostro 3500] suspend/resume failure
UpgradeStatus: Upgraded to trusty on 2014-03-21 (1 days ago)
UserGroups:

dmi.bios.date: 08/04/2010
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A07
dmi.board.name: 0NVXFV
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias: dmi:bvnDellInc.:bvrA07:bd08/04/2010:svnDellInc.:pnVostro3500:pvrNotSpecified:rvnDellInc.:rn0NVXFV:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
dmi.product.name: Vostro 3500
dmi.product.version: Not Specified
dmi.sys.vendor: Dell Inc.

[Brad Figg (brad-figg)]

This change was made by a bot.

[Joseph Salisbury (jsalisbury)]

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

[Henri Coetzee (henricoetzee)]

Updating my BIOS didn't solve the issue. This issue wasn't present in earlier versions of Ubuntu.

When I click on suspend, the password screen appears (not lightdm, but the lockscreen) and then my computer hangs and I have to reboot. When I close the lid of the laptop, the screen turns off, but the computer doesn't.

henri@henri-Vostro-3500:~$ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
A10
10/25/2010
henri@henri-Vostro-3500:~$

[penalvch (penalvch)]

Henri Coetzee, could you please test the latest mainline kernel via http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.15-rc3-utopic/ and advise to the results?

[Henri Coetzee (henricoetzee)]

Suspend/resume works with mainline kernel 3.15.0-031500rc3-generic

[Henri Coetzee (henricoetzee)]

After some more testing, it seems that only the first suspend/resume action worked. Subsequent suspend/resume actions all failed, with the computer hanging most of the times, but not every time.

[penalvch (penalvch)]

Henri Coetzee, could you please test the latest mainline kernel 3.18-rc4 and advise to the results?

[Henri Coetzee (henricoetzee)]

Unfortunately, kernel 3.18-rc4 did not resolve the issue.

[penalvch (penalvch)]

Henri Coetzee, given this result, you are in a worked/broke/fixed/broke scenario. Hence, the next step is to fully commit bisect from kernel 3.15-rc3 to 3.18-rc4 in order to identify the last good kernel commit, followed immediately by the first bad one. This will allow for a more expedited analysis of the root cause of your issue. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection ? Please note, finding adjacent kernel versions is not fully commit bisecting.

Thank you for your understanding.

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

[Launchpad Janitor (janitor)]

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