[ASUSTeK Computer Inc. hostname] hibernate/resume failure

[Tomasz Kazimierczak]

pm-hibernate does not work

ProblemType: KernelOops
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-11-generic 4.4.0-11.26
ProcVersionSignature: Ubuntu 4.4.0-11.26-generic 4.4.4
Uname: Linux 4.4.0-11-generic x86_64
Annotation: This occurred during a previous hibernation, and prevented the system from resuming properly.
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: gdm 1146 F.... pulseaudio
                      tomasz 1680 F.... pulseaudio
Date: Sun Mar 13 10:50:26 2016
DuplicateSignature: hibernate/resume:ASUSTeK Computer Inc. U36SD:U36SD.205
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: hibernate/resume
InstallationDate: Installed on 2016-02-24 (17 days ago)
InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021)
InterpreterPath: /usr/bin/python3.5
MachineType: ASUSTeK Computer Inc. U36SD
ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
ProcEnviron:
 PATH=(custom, no user)
 LANG=pl_PL.UTF-8
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-11-generic root=UUID=a638f00b-30bc-492b-b280-8240260e63d8 ro quiet splash pcie_aspm=force elevator=noop 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-11-generic N/A
 linux-backports-modules-4.4.0-11-generic N/A
 linux-firmware 1.156
SourcePackage: linux
Title: [ASUSTeK Computer Inc. hostname] hibernate/resume failure
UpgradeStatus: Upgraded to xenial on 2016-03-02 (11 days ago)
UserGroups:

dmi.bios.date: 07/12/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: U36SD.205
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: U36SD
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrU36SD.205:bd07/12/2011:svnASUSTeKComputerInc.:pnU36SD:pvr1.0:rvnASUSTeKComputerInc.:rnU36SD:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
dmi.product.name: U36SD
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer Inc.

[Brad Figg (brad-figg)]

This change was made by a bot.

[Tomasz Kazimierczak (faithlesstomas)]

I had no swap turned on when the bug occurred. After "swapon" hibernation kind of work but not fully, i.e. pm-hibernate does not shut down (even after waiting some time). However after "hard kill" (with power button) it did resume. But i still consider this as a bug.

[Tomasz Kazimierczak (faithlesstomas)]

After updating BiOS sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date gives this
U36SD.206
09/26/2011

which I suppose it should since i've updated it exactly to this (i presume the latest) version.

But now pm-hibernate literally do nothing, or at least I do not observe that anything happens,
except this record in /var/log/syslog:
Mar 14 21:34:44 U36SD systemd[1]: Stopped Run anacron jobs.

An that's it! no hibernation, no crush, even no screen blink. Swap also stays untouched.

[penalvch (penalvch)]

Tomasz Kazimierczak, 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.

[Tomasz Kazimierczak (faithlesstomas)]

unfortunately I won't have time to play with instaling kernels until mid April - urgent work sorry...
but after that time i would be happy to check upstream kernel, if bug still not fixed

Bests,
Tomasz

[Launchpad Janitor (janitor)]

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