Suspend crashes and causing the computer shut down on Dell XPS 15

[Gyula Gubacsi]

Ubuntu 14.10: After updating ubuntu around the 8th of January, suspending causing system crash. I tried with different kernel versions and reinstalling the nvidia driver, and also using the open source nvidia driver, but got the same problem. It is crippling as I can't close my laptop lid.
---
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/pcmC1D0p: gyula.gubacsi 2871 F...m pulseaudio
 /dev/snd/controlC1: gyula.gubacsi 2871 F.... pulseaudio
 /dev/snd/controlC0: gyula.gubacsi 2871 F.... pulseaudio
CurrentDesktop: Unity
DistroRelease: Ubuntu 14.10
HibernationDevice: RESUME=UUID=ba60a536-e5db-4152-9b2e-e70a0af1ec3f
InstallationDate: Installed on 2014-11-06 (75 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
MachineType: Dell Inc. XPS 15 9530
NonfreeKernelModules: pax nvidia
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-29-generic.efi.signed root=UUID=412601a6-f086-40cc-8bd2-f1ea9a2fa66c ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2
RelatedPackageVersions:
 linux-restricted-modules-3.16.0-29-generic N/A
 linux-backports-modules-3.16.0-29-generic N/A
 linux-firmware 1.138.1
Tags: utopic
Uname: Linux 3.16.0-29-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm lpadmin sambashare sudo
_MarkForUpload: True
dmi.bios.date: 07/16/2014
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A06
dmi.board.name: XPS 15 9530
dmi.board.vendor: Dell Inc.
dmi.board.version: A06
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias: dmi:bvnDellInc.:bvrA06:bd07/16/2014:svnDellInc.:pnXPS159530:pvrA06:rvnDellInc.:rnXPS159530:rvrA06:cvnDellInc.:ct8:cvrNotSpecified:
dmi.product.name: XPS 15 9530
dmi.product.version: A06
dmi.sys.vendor: Dell Inc.

[Gyula Gubacsi (gyula-gubacsi)]

This is the crash report I get.

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1412748/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1412748

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Gyula Gubacsi (gyula-gubacsi)]

apport information

[Gyula Gubacsi (gyula-gubacsi)]

apport information

[Gyula Gubacsi (gyula-gubacsi)]

apport information

[Gyula Gubacsi (gyula-gubacsi)]

apport information

[Gyula Gubacsi (gyula-gubacsi)]

apport information

[Gyula Gubacsi (gyula-gubacsi)]

apport information

[Gyula Gubacsi (gyula-gubacsi)]

apport information

[Gyula Gubacsi (gyula-gubacsi)]

apport information

[Gyula Gubacsi (gyula-gubacsi)]

apport information

[Gyula Gubacsi (gyula-gubacsi)]

apport information

[Gyula Gubacsi (gyula-gubacsi)]

apport information

[Gyula Gubacsi (gyula-gubacsi)]

apport information

[Gyula Gubacsi (gyula-gubacsi)]

apport information

[Gyula Gubacsi (gyula-gubacsi)]

apport information

[Gyula Gubacsi (gyula-gubacsi)]

apport information

[Gyula Gubacsi (gyula-gubacsi)]

apport information

[Gyula Gubacsi (gyula-gubacsi)]

While running the apport script I had a warning message stating that "linux" package was not found. I set the package name as such as per the wiki page describing what package name should be used for the suspend/resume problems (kernel->linux). I hope the logs are still useful.

[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.19 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.19-rc5-vivid/

[Gyula Gubacsi (gyula-gubacsi)]

I'm sorry, but I have no time to update the kernel just now. Perhaps sometimes later. This is the laptop I'm working on, and I don't want to make it useless.

[Gyula Gubacsi (gyula-gubacsi)]

Hi Christopher,

I updated my BIOS through Windows, as it seemed the easiest solution. Now I have A07 BIOS (I used to have A06), but the bug persist. The output of the commands you asked me to post is:

A07
10/15/2014

I would like to emphasize, that the suspend mode was working up until the very beginning of January. I'm going to give a try with the upstream kernel, but the weird thing is that even with the older kernels it seems to be broken now.

[Gyula Gubacsi (gyula-gubacsi)]

Joseph Salisbury: I experience the same issue with the 3.19.0rc5 kernel. Basically, calling pm-suspend or choosing the suspend in the menu leave me a completely shut down computer. This makes me think that the actual bug doesn't have anything to do with the kernel, or the BIOS. Now I tried multiple different kernels, old and upcoming, and found no changes in the behaviour.

Anything I can do to help? I was wondering if there was a log of updates, it would be worth to look at it. How can I find such thing?

[Gyula Gubacsi (gyula-gubacsi)]

Oh, and by the way, I'm getting a tons of crash reports when booting up, but whenever I try to report it, it's the same as if I've just pressed the cancel button. There's no crash report form anymore for a while.

[penalvch (penalvch)]

Gyula Gubacsi, could you please test the latest mainline kernel (3.19-rc6) and advise to the results?

[Gyula Gubacsi (gyula-gubacsi)]

Christopher M. Penalver:

I've installed today the 3.19-rc6 but hittin suspend results in a shut down nevertheless. Was there any specific change in the kernel that might have fixed this issue, or are we still trying to nail down the source of this issue?

[penalvch (penalvch)]

Gyula Gubacsi, could you please provide the missing information following https://wiki.ubuntu.com/DebuggingKernelSuspend ?

[Gyula Gubacsi (gyula-gubacsi)]

Christopher M. Penalver:

I'm attaching the wakup from the /proc/acpi/wakeup. I'm not entirely sure if I have to go through the next bit of the wiki recommendation becaue it refers to debugging the resume, and as it is, I don't resume the computer: it boots up clean. Let me know what to do next.

[Gyula Gubacsi (gyula-gubacsi)]

This is attachement was created after booting with the 3.19rc6 kernel.

[Gyula Gubacsi (gyula-gubacsi)]

Sorry, I forgot to add that I used the "sudo pm-suspend" command this time, but the same outcome if I close the lid, if I select the Suspend in the menu too.

[penalvch (penalvch)]

Fyula Gubacsi:
>" I'm not entirely sure if I have to go through the next bit of the wiki"

While an expectation of you debugging it isn't expected, the dmesg capture is.

As well, could you please clarify what update specifically happened in January that afterwards demonstrates this problem?

[Craig Setera (craigjunk)]

I believe that this issue is also affecting me. I've uploaded error reports via the error reporter, but I'm unsure how to associate them with this bug report.

I have followed the directions to use a newer mainline kernel and it *seems* to have resolved the issue for me. What are the issues with me staying on a mainline kernel? I'm seeing some complaints from Virtualbox not being able to install the modules.

The kernel I have installed that seems to be working is:

╰─➤ uname -a
Linux xps15 3.17.1-031701-generic #201410150735 SMP Wed Oct 15 11:36:31 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

Please advise on how I can help move this forward.

[penalvch (penalvch)]

Craig Setera:

"Please advise on how I can help move this forward."

It would help immensely if you filed a new report via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

[Craig Setera (craigjunk)]

Christopher - my information was attached to bug https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1431629

[Launchpad Janitor (janitor)]

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