[Dell Studio 1555] suspend/resume failure

Bug #1364583 reported by Mattias Evensson
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned

Bug Description

I closed the lid to suspend the computer, which worked fine. When I opened the lid the computer hanged during the resume. I got a black screen with a pointer that I couldn't move. I resolved the problem by poweing off the computer and then power it on again.

I've got the same behaviour several times since I upgrade to the Utopic repospitories. I can't remember having any supsend/resume problems in Ubuntu 14.04.

ProblemType: KernelOops
DistroRelease: Ubuntu 14.10
Package: linux-image-3.16.0-11-generic 3.16.0-11.16
ProcVersionSignature: Ubuntu 3.16.0-11.16-generic 3.16.1
Uname: Linux 3.16.0-11-generic x86_64
Annotation: This occured during a previous suspend and prevented it from resuming properly.
ApportVersion: 2.14.7-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: matte 2523 F.... pulseaudio
 /dev/snd/controlC0: matte 2523 F.... pulseaudio
Date: Sun Aug 31 21:53:00 2014
DuplicateSignature: suspend/resume:Dell Inc. Studio 1555:A07
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: suspend/resume
HibernationDevice: RESUME=UUID=9c6427da-c9b6-4874-b81a-772962fe1e83
InstallationDate: Installed on 2014-07-30 (34 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
InterpreterPath: /usr/bin/python3.4
MachineType: Dell Inc. Studio 1555
ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/@utopic-root/boot/vmlinuz-3.16.0-11-generic root=UUID=5b80c34a-7c49-426f-b918-4f34e49f9eba ro rootflags=subvol=@utopic-root 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.16.0-11-generic N/A
 linux-backports-modules-3.16.0-11-generic N/A
 linux-firmware 1.133
SourcePackage: linux
Title: [Dell Inc. Studio 1555] suspend/resume failure
UpgradeStatus: Upgraded to utopic on 2014-08-07 (26 days ago)
UserGroups:

dmi.bios.date: 07/03/2009
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A07
dmi.board.name: 0C234M
dmi.board.vendor: Dell Inc.
dmi.board.version: A07
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A07
dmi.modalias: dmi:bvnDellInc.:bvrA07:bd07/03/2009:svnDellInc.:pnStudio1555:pvrA07:rvnDellInc.:rn0C234M:rvrA07:cvnDellInc.:ct8:cvrA07:
dmi.product.name: Studio 1555
dmi.product.version: A07
dmi.sys.vendor: Dell Inc.

Revision history for this message
Mattias Evensson (mevensson) 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
penalvch (penalvch)
tags: added: bios-outdated-a13
Changed in linux (Ubuntu):
importance: Undecided → Low
status: Confirmed → Incomplete
summary: - [Dell Inc. Studio 1555] suspend/resume failure
+ [Dell Studio 1555] suspend/resume failure
Revision history for this message
Mattias Evensson (mevensson) wrote :

I have updated the BIOS, output from the terminal command is:

$ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
A13
04/02/2011

I have also updated to the new 3.6.0-12 kernel. After that I tried to reproduce the hang by doing suspend resume about 10 times in a row, but it worked fine. Now however after having the computer asleep for a couple of days it hanged when I woke it up. I got a black screen with a white mousepointer. The first few seconds I could move the pointer but it was very choppy. Then it froze completely and I was unable to do anything except power off the computer.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
penalvch (penalvch) wrote :

Mattias Evensson, could you please test the latest upstream kernel available from the very top line at the top of the page (not the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. 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 exactly shown as:
kernel-fixed-upstream-3.17-rc3

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.

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

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.

tags: added: latest-bios-a13
removed: bios-outdated-a13
Changed in linux (Ubuntu):
importance: Low → Medium
status: Confirmed → 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
Revision history for this message
Mattias Evensson (mevensson) wrote :

Now I've tested linux-image-3.17.0-031700-generic for more than a month and the bug seems to be fixed in it. It has woken up from sleep as it should every time.

Changed in linux (Ubuntu):
status: Expired → Confirmed
tags: added: kernel-fixed-upstream kernel-fixed-upstream-3.17.0
Revision history for this message
Mattias Evensson (mevensson) wrote :

Also I tried out the 3.16.2, 3.17-rc1, and 3.17-rc2 and got the hang on all of them. Then I tried out 3.17-rc6 for a about a week before the 3.17.0 was released and didn't get the crash, but I can't say for sure it's bug free as the hang doesn't come very time.

Revision history for this message
penalvch (penalvch) wrote :

Mattias Evensson, the next step is to fully reverse commit bisect from kernel 3.17-rc2 to 3.17 in order to identify the last bad commit, followed immediately by the first good one. Once this commit has been identified, then it may be reviewed as a candidate for backporting into your release. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection#How_do_I_reverse_bisect_the_upstream_kernel.3F ? 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

tags: added: kernel-fixed-upstream-3.17 needs-reverse-bisect
removed: kernel-fixed-upstream-3.17.0
Changed in linux (Ubuntu):
status: Confirmed → 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.