[Dell Inc. Latitude E6420] suspend/resume failure [non-free: nvidia]

[Robin-garner-u]

apport detected this error on a fresh boot.

ProblemType: KernelOops
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-19-generic 3.13.0-19.40
ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6
Uname: Linux 3.13.0-19-generic x86_64
NonfreeKernelModules: nvidia
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/controlC1: rgarner 2756 F.... pulseaudio
 /dev/snd/pcmC1D0c: rgarner 2756 F...m pulseaudio
 /dev/snd/controlC2: rgarner 2756 F.... pulseaudio
 /dev/snd/controlC0: rgarner 2756 F.... pulseaudio
Date: Tue Mar 25 10:20:28 2014
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: suspend/resume
HibernationDevice: RESUME=UUID=c7ef60d1-697d-4495-bb69-10665128efd3
InstallationDate: Installed on 2014-01-27 (55 days ago)
InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140121.1)
InterpreterPath: /usr/bin/python3.4
MachineType: Dell Inc. Latitude E6420
ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
ProcFB:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-19-generic root=UUID=e960e3c7-aa3d-43d3-9178-7719d9023e08 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.13.0-19-generic N/A
 linux-backports-modules-3.13.0-19-generic N/A
 linux-firmware 1.126
SourcePackage: linux
Title: [Dell Inc. Latitude E6420] suspend/resume failure [non-free: nvidia]
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 01/01/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A16
dmi.board.name: 032T9K
dmi.board.vendor: Dell Inc.
dmi.board.version: A02
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA16:bd01/01/2013:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn032T9K:rvrA02:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E6420
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.

[Brad Figg (brad-figg)]

This change was made by a bot.

[Alberto Salvia Novella (es20490446e)]

It renders the system temporarily or permanently unusable.

[Ian Ozsvald (ian-x88)]

Note I removed the duplicate link (to #1275621) as the other link doesn't mention NVIDIA and it isn't a Dell machine, I suspect that the NVIDIA chipset is the problem.

For the 4 years I've owned my E6420 I've failed to get reliable suspend/hibernate behaviour, I always turn the laptop off when I want to change location. Sometimes it'll suspend once or twice, sometimes it fails the first time. A failure can mean that it tries to suspend and then wakes up (sometimes having completely shut down - power light off, no activity...then a few seconds later it wakes up) or it'll start to suspend and then freeze on the console screen (having shut down Cinnamon).

After a suspend it is hit or miss whether wifi is working. On occasion the Suspend does work correctly but I can't narrow down the conditions that make it work, it can fail (either re-awakening or freezing) if I try to Suspend just from a fresh boot.

A year back I changed the behaviour so it'll only Suspend if I hit the power button and click Suspend (if I close the lid it'll just keep running), that way I can't accidentally close it thinking it might suspend correctly. Since it only Suspends if I click a button I'm confident that there's no odd hardware interactions (e.g. a laptop-closed sensor that's dodgy), as after I click Suspend I wait to see what happens without trying to close the lid.

I'm using E6420 Bios A19 (from late 2013). This bug affects me right now (I tried Suspend again last week - same problems occurred). I'm running Linux Mint 17.1 (I've been using Mint for 2.5 years). I started with the official Ubuntu 10.10 Dell installation from 2011 when I bought the machine, that never successfully Hibernated or Suspended either.

I've never used apport or other crash report tools, I'd be happy to do so if this might help?

[Ian Ozsvald (ian-x88)]

Further notes - the A19 bios was from approx June 2013, there is an A21 bios released in 2014 but the few fixes don't seem relevant.

I would *very much* like to have a way of getting some sort of kernel log dump after a failure on the next boot, so I can even diagnose if it is failing the same way each time. Can anyone please direct me to how I should do this?

[Ian Ozsvald (ian-x88)]

Further note - when I made comment #4 I was using the NVIDIA driver 331.113 and kernel 3.13.0-24. I've just updated from Mint 17.1 to Mint 17.2 (with a new nvidia driver and kernel), I'll try suspend & hibernate over the coming days and report back.

[penalvch (penalvch)]

Robin-garner-u, thank you for reporting this and helping make Ubuntu better. As per http://www.dell.com/support/home/us/en/19/product-support/product/latitude-e6420/drivers/advanced an update to your computer's buggy and outdated BIOS is available (A22). 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

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

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.

Once the BIOS is updated, if the problem is still reproducible, and the information above is provided, then please mark this report Status Confirmed. Otherwise, please mark this as Invalid.

Thank you for your understanding.

[Robin-garner-u (robin-garner-u)]

I'm now running 15.04, so the bug no longer applies. I've marked it as invalid.