[HP ZBook 14 Mobile Workstation] Hard freeze upon resuming from hibernate and logging in

[Vadim Peretokin]

After I resume from hibernate and log in, the desktop freezes completely. Even using alt+sysreq+b does not reboot it.

This started happening recently.

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: linux-image-3.16.0-29-generic 3.16.0-29.39
ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2
Uname: Linux 3.16.0-29-generic x86_64
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: vadi 2981 F.... pulseaudio
 /dev/snd/controlC0: vadi 2981 F.... pulseaudio
CRDA:
 country AU: DFS-UNSET
  (2402 - 2482 @ 40), (N/A, 20)
  (5170 - 5250 @ 40), (3, 23)
  (5250 - 5330 @ 40), (3, 23), DFS
  (5735 - 5835 @ 40), (3, 30)
CurrentDesktop: Unity
Date: Mon Jan 19 08:05:47 2015
HibernationDevice: RESUME=UUID=745d185e-0cf7-47d5-8900-9f89f21b1af8
InstallationDate: Installed on 2014-06-26 (205 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
MachineType: Hewlett-Packard HP ZBook 14
ProcFB:
 0 inteldrmfb
 1 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-29-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
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
SourcePackage: linux
UpgradeStatus: Upgraded to utopic on 2014-10-27 (83 days ago)
dmi.bios.date: 04/29/2014
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: L71 Ver. 01.11
dmi.board.name: 198F
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 15.54
dmi.chassis.asset.tag: CNU424B3ZZ
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-Packard:bvrL71Ver.01.11:bd04/29/2014:svnHewlett-Packard:pnHPZBook14:pvrA3009DD10303:rvnHewlett-Packard:rn198F:rvrKBCVersion15.54:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP ZBook 14
dmi.product.version: A3009DD10303
dmi.sys.vendor: Hewlett-Packard

[Brad Figg (brad-figg)]

This change was made by a bot.

[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/

[Vadim Peretokin (vperetokin)]

That one is more disastrous - where the previous one allowed me to put in the disk password and unlock the computer, this one does not bring the lock screen up after the disk password and goes completely black.

I have been submitting the 'apportcheckresume' crash reports daily a while back, I'd get at least 3 of them upon resuming - I'm not sure if anyone actually pays attention to them.

[Joseph Salisbury (jsalisbury)]

This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report[0]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug.

Please follow the instructions on the wiki page[0]. The first step is to email the appropriate mailing list. If no response is received, then a bug may be opened on bugzilla.kernel.org.

Once this bug is reported upstream, please add the tag: 'kernel-bug-reported-upstream'.

[0] https://wiki.ubuntu.com/Bugs/Upstream/kernel

[penalvch (penalvch)]

Vadim Peretokin, could you please advise which prior kernel version you were using specifically where this issue did not occur?

[Vadim Peretokin (vperetokin)]

I don't recall, I've had it for a while. The version of the kernel I was
using when I reported the issue locked up after I logged in, the latest one
from mainline doesn't even let me log in and just shows a black screen.

There is a lot to do in those upstream reporting instructions so it'll take
me a bit.

On Tue, Jan 27, 2015 at 10:40 AM, Christopher M. Penalver <
<email address hidden>> wrote:

> Vadim Peretokin, could you please advise which prior kernel version you
> were using specifically where this issue did not occur?
>
> ** Changed in: linux (Ubuntu)
> Status: Confirmed => Incomplete
>
> ** Changed in: linux (Ubuntu)
> Importance: High => Medium
>
> ** Tags added: bios-outdated-1.12
>
> ** Tags added: hibernate resume
>
> ** Summary changed:
>
> - Hard freeze upon resuming from hibernate and logging in
> + [HP ZBook 14 Mobile Workstation] Hard freeze upon resuming from
> hibernate and logging in
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1412257
>
> Title:
> [HP ZBook 14 Mobile Workstation] Hard freeze upon resuming from
> hibernate and logging in
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1412257/+subscriptions
>

[Launchpad Janitor (janitor)]

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

[penalvch (penalvch)]

Vadim Peretokin, as per http://h20564.www2.hp.com/hpsc/swd/public/readIndex?sp4ts.oid=5428311&swLangOid=8&swEnvOid=4158 an update to your computer's buggy and outdated BIOS is available (1.30). 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.

[Launchpad Janitor (janitor)]

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