Suspend-Resume freezes the computer completely

[flrtx]

I’m using HP 250 G3 notebook. When closing the screen and reopening it, the system should suspend and resume. However, when I reopen the computer, the system is completely frozen. I can’t move the mouse, keyboard strokes don’t get recongnized, not even Ctrl+Alt+F1 to get to the rescue terminal where I could at least reboot the computer. Instead, the only solution I found was to press the power button for several seconds.
Being able to suspend the computer is very important for me. What can I do about this?

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: linux-headers-4.2.0-30 4.2.0-30.35
ProcVersionSignature: Ubuntu 4.2.0-30.35-generic 4.2.8-ckt3
Uname: Linux 4.2.0-30-generic x86_64
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: babbl 1584 F.... pulseaudio
 /dev/snd/controlC1: babbl 1584 F.... pulseaudio
CurrentDesktop: MATE
Date: Tue Feb 23 15:28:30 2016
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=34ce0104-ddbf-4b6e-8f5b-2012550d55ef
InstallationDate: Installed on 2015-10-17 (129 days ago)
InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
Lsusb:
 Bus 003 Device 003: ID 064e:9320 Suyin Corp.
 Bus 003 Device 002: ID 8087:8000 Intel Corp.
 Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Hewlett-Packard HP 250 G3 Notebook PC
PackageArchitecture: all
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-30-generic.efi.signed root=UUID=ce32a0c7-c1c0-4a26-90c2-6466918c1e3d ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.2.0-30-generic N/A
 linux-backports-modules-4.2.0-30-generic N/A
 linux-firmware 1.149.3
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
UdevLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: '/var/log/udev'
UpgradeStatus: Upgraded to wily on 2016-02-23 (0 days ago)
dmi.bios.date: 10/23/2014
dmi.bios.vendor: Insyde
dmi.bios.version: F.31
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 2212
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 86.44
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.31:bd10/23/2014:svnHewlett-Packard:pnHP250G3NotebookPC:pvr0991100000000000000600087:rvnHewlett-Packard:rn2212:rvr86.44:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.name: HP 250 G3 Notebook PC
dmi.product.version: 0991100000000000000600087
dmi.sys.vendor: Hewlett-Packard

[Brad Figg (brad-figg)]

This change was made by a bot.

[Launchpad Janitor (janitor)]

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

[flrtx (fltrx)]

Thanks, Christopher, for advising the BIOS update.

However, it didn’t improve the situation. The system is still completely frozen when I reopen the display.

The output of 'sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date' is the following:
F.39
05/26/2015

[penalvch (penalvch)]

flrtx, 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.

[Launchpad Janitor (janitor)]

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