ubuntu freezes on suspend after upgrade to 4.10.0-27

Bug #1705859 reported by jas mann
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Immediately after upgrading to 4.10.0-27, system unresponsive after suspend. This did not occur previously with 4.8.0-56. HP Z820, XEON ES-2669, Nvidia Quadro K2000.
---
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: jld 1750 F.... pulseaudio
 /dev/snd/controlC0: jld 1750 F.... pulseaudio
CurrentDesktop: Unity
DistroRelease: Ubuntu 16.04
HibernationDevice: RESUME=UUID=c205dd4d-b915-4bad-aadb-1887e7e4e95c
InstallationDate: Installed on 2017-04-05 (114 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2)
IwConfig:
 eno1 no wireless extensions.

 enp1s0 no wireless extensions.

 lo no wireless extensions.
MachineType: Hewlett-Packard HP Z820 Workstation
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
Package: linux (not installed)
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-58-generic.efi.signed root=UUID=cba6eb44-edf8-4971-a53e-b86d347e720c ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 4.8.0-58.63~16.04.1-generic 4.8.17
RelatedPackageVersions:
 linux-restricted-modules-4.8.0-58-generic N/A
 linux-backports-modules-4.8.0-58-generic N/A
 linux-firmware 1.157.11
RfKill:

Tags: xenial
Uname: Linux 4.8.0-58-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 05/27/2015
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: J63 v03.88
dmi.board.asset.tag: 2UA2271NB2
dmi.board.name: 158B
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 0.00
dmi.chassis.asset.tag: 2UA2271NB2
dmi.chassis.type: 6
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-Packard:bvrJ63v03.88:bd05/27/2015:svnHewlett-Packard:pnHPZ820Workstation:pvr:rvnHewlett-Packard:rn158B:rvr0.00:cvnHewlett-Packard:ct6:cvr:
dmi.product.name: HP Z820 Workstation
dmi.sys.vendor: Hewlett-Packard

Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1705859

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Does this issue go away if you boot back into the prior kernel?

Changed in linux (Ubuntu):
importance: Undecided → Medium
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.13 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'.

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/v4.13-rc2

Revision history for this message
jas mann (dotmarker) wrote :

> Does this issue go away if you boot back into the prior kernel?
  Yes

> Would it be possible for you to test the latest upstream kernel?
  I'll have a go at it. Thanks.

Revision history for this message
jas mann (dotmarker) wrote :

We are not able to test the upstream kernel at this time. The consensus is that the risk, however unlikely, of extended downtime is too great at this point in our development cycle. It must wait for a break in the action, my apologies.

Revision history for this message
jas mann (dotmarker) wrote : AlsaInfo.txt

apport information

tags: added: apport-collected xenial
description: updated
Revision history for this message
jas mann (dotmarker) wrote : CRDA.txt

apport information

Revision history for this message
jas mann (dotmarker) wrote : CurrentDmesg.txt

apport information

Revision history for this message
jas mann (dotmarker) wrote : JournalErrors.txt

apport information

Revision history for this message
jas mann (dotmarker) wrote : Lspci.txt

apport information

Revision history for this message
jas mann (dotmarker) wrote : Lsusb.txt

apport information

Revision history for this message
jas mann (dotmarker) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
jas mann (dotmarker) wrote : ProcCpuinfoMinimal.txt

apport information

Revision history for this message
jas mann (dotmarker) wrote : ProcEnviron.txt

apport information

Revision history for this message
jas mann (dotmarker) wrote : ProcInterrupts.txt

apport information

Revision history for this message
jas mann (dotmarker) wrote : ProcModules.txt

apport information

Revision history for this message
jas mann (dotmarker) wrote : PulseList.txt

apport information

Revision history for this message
jas mann (dotmarker) wrote : UdevDb.txt

apport information

Revision history for this message
jas mann (dotmarker) wrote : WifiSyslog.txt

apport information

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
jas mann (dotmarker) wrote :

Bug persists after upgrade to 4.10.0-30.

It continues to be necessary to boot a 4.8 kernel to avoid catastrophic work loss.

Surely this regression merits higher priority attention.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.