[HP 14-d004tx Notebook PC] Can't resume from suspend state

[Lars Hansson]

In Utopic my laptop can suspend but upon resume all that is seen is a black screen with an underline cursor in the top left corner. While it is possible to switch to VT1, switching back to VT7 causes the laptop to stop responding to input. With nouveau, while on resume you get the graphical login screen, it does not accept any keyboard or mouse input.

Suspend worked fine in 13.10.

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: linux-image-3.16.0-24-generic 3.16.0-24.32
ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
Uname: Linux 3.16.0-24-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: lars 2398 F.... pulseaudio
CurrentDesktop: Unity
Date: Wed Nov 12 14:26:57 2014
HibernationDevice: RESUME=UUID=5a554079-ba87-4a30-95af-c2c9b60ed506
InstallationDate: Installed on 2014-11-09 (2 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
MachineType: Hewlett-Packard HP 14 Notebook PC
ProcEnviron:
 LANGUAGE=en_PH:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_PH.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic.efi.signed root=UUID=0c322239-684b-4a1e-b2b5-d5ce8fe0cedd ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.16.0-24-generic N/A
 linux-backports-modules-3.16.0-24-generic N/A
 linux-firmware 1.138
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/28/2013
dmi.bios.vendor: Insyde
dmi.bios.version: F.08
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 21BB
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 39.15
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnInsyde:bvrF.08:bd11/28/2013:svnHewlett-Packard:pnHP14NotebookPC:pvr0976100000405F10000610180:rvnHewlett-Packard:rn21BB:rvr39.15:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.name: HP 14 Notebook PC
dmi.product.version: 0976100000405F10000610180
dmi.sys.vendor: Hewlett-Packard

[Brad Figg (brad-figg)]

This change was made by a bot.

[Lars Hansson (romabysen)]

Model number: 14-d004TX

[Lars Hansson (romabysen)]

Hi Christopher,
I updated the BIOS to F.18 but it doesn't change anything. Suspend/resume still behaves as stated above. I also tried with the Nouveau driver but the result is similar; on resume you get the graphical login screen (at least) but it does not accept any input (keyboard or mouse) and it's not possible to switch to VT1.

The output of sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date is:
F.18
09/04/2014

[Lars Hansson (romabysen)]

I should probably add that suspend/resume worked just fine in 13.10 with this laptop.

[penalvch (penalvch)]

Lars Hansson, 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:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested exactly shown as:
kernel-fixed-upstream-3.18-rc4

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description.

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

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.

[Lars Hansson (romabysen)]

Hi,
I tried 3.18-rc4 and 3.17.1 and they both have this problem.

[penalvch (penalvch)]

Lars Hansson, the next step is to fully commit bisect from kernel Saucy to Trusty in order to identify the last good kernel commit, followed immediately by the first bad one. This will allow for a more expedited analysis of the root cause of your issue. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection ? Please note, finding adjacent kernel versions is not fully commit bisecting.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

[Launchpad Janitor (janitor)]

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