Suspend/Resume does not fully work on 14.10

[Lepaffe Philippe]

I am using an Asus Zenbook UX301LA and it often doesn't suspend properly on 14.10.

When the bug occurs, the fans keep going faintly even after the lid has been closed, and when I try to resume by opening the lid, the laptop is unresponsive to any input, the screen stays black nothing happens until I shut the machine down by holding the power key.

I have recently tried to switch to the mainline kernel (3.19 stable), and couldn't reproduce this issue after about 20 suspend/resume (before the switch I could resume once every two tries at best), but unfortunately this particular release seemed to make my laptop overheat and I'm generally not too confortable running something else than the default Ubuntu Kernel so I switched back to 3.16.0-30-generic.

I'm not the most knowledgeable Ubuntu user but if more information is need I could try to provide it.

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: linux-image-3.16.0-30-generic 3.16.0-30.40
ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3
Uname: Linux 3.16.0-30-generic x86_64
ApportVersion: 2.14.7-0ubuntu8.1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: elmagio 2503 F.... pulseaudio
 /dev/snd/controlC0: elmagio 2503 F.... pulseaudio
CurrentDesktop: Unity
Date: Sun Feb 22 16:38:23 2015
HibernationDevice: RESUME=UUID=d088c44e-dfc5-4708-9624-fac5ea539328
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 03eb:8a0c Atmel Corp.
 Bus 001 Device 003: ID 1bcf:2987 Sunplus Innovation Technology Inc.
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. UX301LAA
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-30-generic.efi.signed root=UUID=022477ea-14c8-4b51-8546-fa0fa2c6084f ro quiet acpi_osi= quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.16.0-30-generic N/A
 linux-backports-modules-3.16.0-30-generic N/A
 linux-firmware 1.138.1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/11/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX301LAA.204
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX301LAA
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.:bvrUX301LAA.204:bd09/11/2013:svnASUSTeKCOMPUTERINC.:pnUX301LAA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX301LAA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: UX301LAA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

[Brad Figg (brad-figg)]

This change was made by a bot.

[penalvch (penalvch)]

Lepaffe Philippe, thank you for reporting this and helping make Ubuntu better. As per http://www.asus.com/Notebooks_Ultrabooks/ASUS_ZENBOOK_UX301LA/HelpDesk_Download/ an update to your computer's buggy and outdated BIOS is available (209). 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, and the information above is provided, then please mark this report Status Confirmed.

Thank you for your understanding.

[Lepaffe Philippe (mistermagio)]

I have updated the BIOS, and haven't been able to reproduce the issue since after about 10 suspends, so if not fixed the issue was largely diminished by the BIOS upgrade. I will update this bug report again should the issue reappear.

I am sorry for the inconvenience, I hadn't looked up the bug reporting etiquette and updating the BIOS hadn't come to mind, and I was convinced it had to do with Linux/Ubuntu as updating to 3.19 seemed to have fixed it. But apparently the issue lay in the outdated BIOS. Is there something I need to do to close the bug report?

[Lepaffe Philippe (mistermagio)]

The latest BIOS hasn't fixed it after all.

The bug seems to appear randomly, and it just happened to not occur for the 15 times I suspended-resumed after the BIOS upgrade, but it has since reappeared at the same frequency as before. It does seem to occur more frequently after long sessions of usage without interruption.

It's still the exact same symptoms.

The output of sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date is:

UX301LAA.209
05/08/2014

I have also updated to the latest Ubuntu kernel, 3.16.0-31-generic, with the same results. I will try a full day on a later version of the Linux kernel (3.18.6 or 3.19) tomorrow.

[penalvch (penalvch)]

Lepaffe Philippe, 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.

[Launchpad Janitor (janitor)]

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