[Dell Latitude E7440] suspend/resume failure

Bug #1364539 reported by Michael
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned

Bug Description

If relevant, I docked the laptop between suspending and resuming.

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.6-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: michael 2707 F.... pulseaudio
 /dev/snd/controlC0: michael 2707 F.... pulseaudio
Date: Tue Sep 2 19:58:10 2014
DuplicateSignature: suspend/resume:Dell Inc. Latitude E7440:A10
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: suspend/resume
HibernationDevice: RESUME=UUID=6d651e5a-075d-4911-a5ce-6710f7246853
InstallationDate: Installed on 2014-08-01 (32 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
InterpreterPath: /usr/bin/python3.4
MachineType: Dell Inc. Latitude E7440
ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-11-generic root=/dev/mapper/ubuntu--vg-root 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.16.0-11-generic N/A
 linux-backports-modules-3.16.0-11-generic N/A
 linux-firmware 1.132
SourcePackage: linux
Title: [Dell Inc. Latitude E7440] suspend/resume failure
UpgradeStatus: Upgraded to utopic on 2014-08-28 (5 days ago)
UserGroups:

dmi.bios.date: 06/26/2014
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A10
dmi.board.name: 0RYCC9
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA10:bd06/26/2014:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn0RYCC9:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E7440
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.

Revision history for this message
Michael (michaeljt) 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: latest-bios-a10
Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
summary: - [Dell Inc. Latitude E7440] suspend/resume failure
+ [Dell Latitude E7440] suspend/resume failure
Revision history for this message
Michael (michaeljt) wrote :

I'm afraid that this is not reproducible on demand (it was reported automatically). I will have to observe it before I can do any sensible testing.

Revision history for this message
Daniel Christian Henter (mr-ghettoblaster) wrote :

I'm also affected but in my case it's reproducable every time I suspend

Revision history for this message
Bryan Quigley (bryanquigley) wrote :

@mr-ghettoblaster
In that case, please do try with a mainline kernel and see if it's still the case (see Christopher's instructions).

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
Michael Thayer (michael-thayer) wrote :

Just seen this again with Vivid.

Changed in linux (Ubuntu):
status: Expired → Confirmed
penalvch (penalvch)
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Michael Thayer (michael-thayer) wrote :

For information, I am the original reporter. I set this to "confirmed" because I am still seeing the problem (not reproducible on demand, in fact only extremely sporadic) and one other person (mr-ghettoblaster) confirmed it. Is a new bug report still useful? If so, for my help in filing it, what advantages does it bring?

Revision history for this message
penalvch (penalvch) wrote :

Michael Thayer, it's a little confusing as you are logging into a different account then the one that originally reported the issue:
Original Reporter account -> https://launchpad.net/~michaeljt
Your second account -> https://launchpad.net/~michael-thayer

Revision history for this message
Michael Thayer (michael-thayer) wrote :

Sorry about that. This was one of about twenty automatic reports by Apport when I upgraded to Vivid.

Revision history for this message
penalvch (penalvch) wrote :

Michael Thayer, could you please test the latest upstream kernel available from the very top line at the top of the page (the release names are irrelevant for testing, and please do not test the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue.

If the test did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to 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 by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description:
kernel-fixed-upstream
kernel-fixed-upstream-3.XY-rcZ

Where XY and Z are numbers corresponding to the kernel version.

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-3.XY-rcZ

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: vivid
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.