[Dell Inc. Inspiron 7559] suspend/resume failure

[Jimmy Pan]

When using command of pm-suspend, the machine might be suspended, but cannot be waken either by clicking the keyboard or power button.

Sometimes the suspension will fail too.

ProblemType: KernelOops
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-8-generic 4.4.0-8.23
ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2
Uname: Linux 4.4.0-8-generic x86_64
Annotation: This occurred during a previous suspend, and prevented the system from resuming properly.
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/pcmC0D0p: pjm 2439 F...m pulseaudio
 /dev/snd/controlC0: pjm 2439 F.... pulseaudio
Date: Sun Feb 28 15:30:13 2016
DuplicateSignature: suspend/resume:Dell Inc. Inspiron 7559:1.1.3
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: suspend/resume
HibernationDevice: RESUME=UUID=447ec3f7-71bc-498d-ba0f-03ed68deccf2
InstallationDate: Installed on 2016-02-27 (0 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160225)
InterpreterPath: /usr/bin/python3.5
MachineType: Dell Inc. Inspiron 7559
ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-8-generic.efi.signed root=UUID=d19074ca-3e53-4e29-b6ba-95daa56f7da0 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-4.4.0-8-generic N/A
 linux-backports-modules-4.4.0-8-generic N/A
 linux-firmware 1.156
SourcePackage: linux
Title: [Dell Inc. Inspiron 7559] suspend/resume failure
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 11/05/2015
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.1.3
dmi.board.name: 0H87XC
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.:bvr1.1.3:bd11/05/2015:svnDellInc.:pnInspiron7559:pvr1.1.3:rvnDellInc.:rn0H87XC:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
dmi.product.name: Inspiron 7559
dmi.product.version: 1.1.3
dmi.sys.vendor: Dell Inc.

[Brad Figg (brad-figg)]

This change was made by a bot.

[Jimmy Pan (dspjmr)]

But actually, suspend and resume doesn't work. Not sure if the bug provided useful info.

[Brad Figg (brad-figg)]

This change was made by a bot.

[Jimmy Pan (dspjmr)]

After updating bios, my machine still cannot suspend. I saw nothing in syslog or kern.log, though I want to provide some more logs.

[Jimmy Pan (dspjmr)]

$ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
1.1.5
01/14/2016

[Jimmy Pan (dspjmr)]

Sorry, forgot about the command

[penalvch (penalvch)]

Jimmy Pan, in order to allow additional upstream developers to examine the issue, at your earliest convenience, could you please test the latest upstream kernel available from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D ? Please keep in mind the following:
1) The one to test is at the very top line at the top of the page (not the daily folder).
2) The release names are irrelevant.
3) The folder time stamps aren't indicative of when the kernel actually was released upstream.
4) Install instructions are available at https://wiki.ubuntu.com/Kernel/MainlineBuilds .

If testing on your main install would be inconvenient, one may:
1) Install Ubuntu to a different partition and then test this there.
2) Backup, or clone the primary install.

If the latest kernel 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 issue 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-X.Y-rcZ

Where X, and Y are the first two numbers of the kernel version, and Z is the release candidate number if it exists.

If the mainline kernel does not fix the issue, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

Please note, an error to install the kernel does not fit the criteria of kernel-bug-exists-upstream.

Also, you don't need to apport-collect further unless specifically requested to do so.

Once testing of the latest upstream kernel is complete, please mark this report Status Confirmed. Please let us know your results.

Thank you for your understanding.

[Jimmy Pan (dspjmr)]

The bug still exists using:
kernel 4.5.0-040500rc7

[penalvch (penalvch)]

Jimmy Pan, to clarify, did this issue not occur in a release prior to 16.04?

[Jimmy Pan (dspjmr)]

No, I tested it several times on 14.04 LTS, it did succeeded for once, but other times, it doesn't work, behaving the same as 16.04.

[penalvch (penalvch)]

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

[Jimmy Pan (dspjmr)]

Do I just need to execute the tests and append the content of /sys/kernel/debug/suspend_stats?

I tried the tests on another computer, looks like there's no output and the content of the file didn't change at all.

[Jimmy Pan (dspjmr)]

the output of pm test

[Jimmy Pan (dspjmr)]

 cat /proc/acpi/wakeup
Device S-state Status Sysfs node
PEG2 S4 *disabled
PEGP S4 *disabled
RP09 S4 *disabled
PXSX S4 *disabled
RP10 S4 *disabled
PXSX S4 *disabled
RP11 S4 *disabled
PXSX S4 *disabled
RP12 S4 *disabled
PXSX S4 *disabled
RP13 S4 *disabled
PXSX S4 *disabled
RP01 S4 *disabled pci:0000:00:1c.0
PXSX S4 *disabled
RP02 S4 *disabled
PXSX S4 *disabled
RP03 S4 *disabled
PXSX S4 *disabled
RP04 S4 *disabled
PXSX S4 *disabled
RP05 S4 *disabled pci:0000:00:1c.4
PXSX S4 *enabled pci:0000:04:00.0
RP06 S4 *disabled pci:0000:00:1c.5
PXSX S4 *disabled pci:0000:05:00.0
RP07 S4 *disabled pci:0000:00:1c.6
PXSX S4 *disabled pci:0000:06:00.0
                *disabled platform:rtsx_pci_sdmmc.0
                *disabled platform:rtsx_pci_ms.0
RP08 S4 *disabled
PXSX S4 *disabled
RP17 S4 *disabled
PXSX S4 *disabled
RP18 S4 *disabled
PXSX S4 *disabled
RP19 S4 *disabled
PXSX S4 *disabled
RP20 S4 *disabled
PXSX S4 *disabled
RP14 S4 *disabled
PXSX S4 *disabled
RP15 S4 *disabled
PXSX S4 *disabled
RP16 S4 *disabled
PXSX S4 *disabled
PEG1 S4 *disabled pci:0000:00:01.0
PEGP S4 *disabled
PEG0 S4 *disabled pci:0000:00:01.1
PEGP S4 *disabled pci:0000:02:00.0
XHC S3 *enabled pci:0000:00:14.0
XDCI S4 *disabled
HDAS S4 *disabled pci:0000:00:1f.3
LID0 S3 *enabled platform:PNP0C0D:00

[Jimmy Pan (dspjmr)]

suspension failed in any way, first clipping my laptop screen doesn't work, executing pm-suspend or clicking the suspend button in gnome don't work either.

[penalvch (penalvch)]

Still missing most of the information.

[Jimmy Pan (dspjmr)]

Which part?

[Jimmy Pan (dspjmr)]

Can you please which information I am missing but not just changing the bug status?

[penalvch (penalvch)]

Jimmy Pan, as is noticed, the article has been significantly updated. Hence, you are missing all the information.

[Jimmy Pan (dspjmr)]

I did all the tests, which part is missing?

[Jimmy Pan (dspjmr)]

Can you see comment 16, 17 and 18?

[penalvch (penalvch)]

Jimmy Pan, please see https://wiki.ubuntu.com/DebuggingKernelSuspend#Debugging_information_to_provide_in_your_bug_report . You are missing all 11 items. When you actually have attached them to this report, then please mark this Confirmed.

[Jimmy Pan (dspjmr)]

1. All those information has been provided in the comments, I don't understand what you mean. Anyway, I will answer those questions one by one.

Which part of the process does the issue occur with, the suspend to ram, or resuming from?
suspend to ram

2. Please advise how you suspended specifically. For example:

suspension failed in any way, first clipping my laptop screen doesn't work, executing pm-suspend or clicking the suspend button in gnome don't work either.

3. While booted into the latest non-daily mainline kernel, execute at a terminal:
cat /proc/acpi/wakeup > wakeup

content:
Device S-state Status Sysfs node
PEG2 S4 *disabled
PEGP S4 *disabled
RP09 S4 *disabled
PXSX S4 *disabled
RP10 S4 *disabled
PXSX S4 *disabled
RP11 S4 *disabled
PXSX S4 *disabled
RP12 S4 *disabled
PXSX S4 *disabled
RP13 S4 *disabled
PXSX S4 *disabled
RP01 S4 *disabled pci:0000:00:1c.0
PXSX S4 *disabled
RP02 S4 *disabled
PXSX S4 *disabled
RP03 S4 *disabled
PXSX S4 *disabled
RP04 S4 *disabled
PXSX S4 *disabled
RP05 S4 *disabled pci:0000:00:1c.4
PXSX S4 *enabled pci:0000:04:00.0
RP06 S4 *disabled pci:0000:00:1c.5
PXSX S4 *disabled pci:0000:05:00.0
RP07 S4 *disabled pci:0000:00:1c.6
PXSX S4 *disabled pci:0000:06:00.0
                *disabled platform:rtsx_pci_sdmmc.0
                *disabled platform:rtsx_pci_ms.0
RP08 S4 *disabled
PXSX S4 *disabled
RP17 S4 *disabled
PXSX S4 *disabled
RP18 S4 *disabled
PXSX S4 *disabled
RP19 S4 *disabled
PXSX S4 *disabled
RP20 S4 *disabled
PXSX S4 *disabled
RP14 S4 *disabled
PXSX S4 *disabled
RP15 S4 *disabled
PXSX S4 *disabled
RP16 S4 *disabled
PXSX S4 *disabled
PEG1 S4 *disabled pci:0000:00:01.0
PEGP S4 *disabled
PEG0 S4 *disabled pci:0000:00:01.1
PEGP S4 *disabled pci:0000:02:00.0
XHC S3 *enabled pci:0000:00:14.0
XDCI S4 *disabled
HDAS S4 *disabled pci:0000:00:1f.3
LID0 S3 *enabled platform:PNP0C0D:00

3. While booted into the latest non-daily mainline kernel, execute at a terminal:

sudo su
echo freezer > /sys/power/pm_test
exit

Please attach to your report the resume trace mentioned below.

While booted into the latest non-daily mainline kernel, execute at a terminal:

sudo su
echo devices > /sys/power/pm_test
exit

Please attach to your report the resume trace mentioned below.

While booted into the latest non-daily mainline kernel, execute at a terminal:

sudo su
echo platform > /sys/power/pm_test
exit

Please attach to your report the resume trace mentioned below.

While booted into the latest non-daily mainline kernel, execute at a terminal:

sudo su
echo processors > /sys/power/pm_test
exit

Please attach to your report the resume trace mentioned below.

While booted into the latest non-daily mainline kernel, execute at a terminal:

sudo su
echo core > /sys/power/pm_test
exit

Please attach to your report the resume trace mentioned below.

While booted into the latest non-daily mainline kernel, execute at a terminal:

sudo su
echo none > /sys/power/pm_test
exit

Please attach to your report the resume trace mentioned below.

Please provide the output of the following terminal command:

cat /sys/kernel/debug/suspend_stats

I ran those tests in a script, the commands and output can be find in the attachment of comment ...

[penalvch (penalvch)]

Jimmy Pan, to advise, no comment in this report provides all of the requested information.

To clarify, for steps 5-11 you need to provide a separate attachment for each step, following the resume trace method mentioned.

[Launchpad Janitor (janitor)]

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

[Insanity (ivan-d-may)]

Hi

I initially had this issue and when I changed my Nvidia drivers to Nvidia binary driver 361.45.18 the problem does not occur while the power is plugged in. Ie I can wake from sleep if the machine was suspended with external power plugged in.

Let me know if you need any info that can help in solving this issue

[Insanity (ivan-d-may)]

I should possibly add that I cannot wake if the machine was suspended without external power

[penalvch (penalvch)]

Insanity (ivan-d-may), it will help immensely if you filed a new report with the Ubuntu repository kernel (not mainline/upstream) via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

For more on why this is helpful, please see https://wiki.ubuntu.com/ReportingBugs.