shutdown/restart/suspend freezes laptop on intel graphics

Bug #1690512 reported by Thiru
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
intel-microcode (Ubuntu)
Invalid
Undecided
Unassigned
linux (Ubuntu)
Invalid
Undecided
Unassigned
xorg (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

I'm not sure where to report this under, so please bear with me. Reporting this bug using ubuntu-bug just crashes my system if im using intel graphics, I had to switch to nvidia graphics just to file this bug report so the automatically attached log files may not be a good representation of the problem.

I've attached the syslog and kern.log files below.

PROBLEM:

When using intel graphics:

Whenever I close the laptop lid or restart / shutdown using GUI or terminal commands, it goes into a black screen with a single "_" at the top left corner, and hangs. Only long-pressing (hard reset) the power button would shut down the computer.

However, when I use sudo prime-select nvidia to switch over to nvidia, everything works fine.log

I have tried many things, and all do not work. I have attached the logs for /var/log/syslog and /var/log/kern.log below.

Attempts so far:

1)Tried installing new intel drivers from Updated kernel to 4.8 now missing firmware warnings --> Did not work. Issue persists

2) Tried upgrading kernel from 4.8 to 4.10.15 --> Did not work. Problem got worse. Instead of the normal login screen, it gives a terminal login screen and hangs.

3) Tried the fix to nvidia-prime https://askubuntu.com/a/884506/547039, but both the poweron.sh and poweroff.sh script hangs my laptop instead.

4) Tried sudo swapoff -a && systemctl poweroff as a workaround, no avail.

5) Tried changing GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" to GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi=force" Does not work either.

Additional note:
'sudo lshw -C display' on intel graphics outputs PCI(sysfs) then laptop freezes.

LOG FILES:
/var/log/syslog
https://codeshare.io/5XOPwM

/var/log/kern.log
https://codeshare.io/aJp6nq

specs:

Intel 7700HQ, NVIDIA 1060GTX, kernel 4.8, Ubuntu 16.04

Would really appreciate your help. Thank you!

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.8.0-51.54~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-51-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
.proc.driver.nvidia.gpus.0000.01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0000:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module 381.22 Thu May 4 00:55:03 PDT 2017
 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4)
.tmp.unity_support_test.0:

ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Sat May 13 17:06:20 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus:
 bbswitch, 0.8, 4.4.0-77-generic, x86_64: installed
 bbswitch, 0.8, 4.8.0-49-generic, x86_64: installed
 bbswitch, 0.8, 4.8.0-51-generic, x86_64: installed
 nvidia-381, 381.22, 4.8.0-51-generic, x86_64: installed
EcryptfsInUse: Yes
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller])
   Subsystem: CLEVO/KAPOK Computer Device [1558:65a1]
 NVIDIA Corporation Device [10de:1c20] (rev a1) (prog-if 00 [VGA controller])
   Subsystem: CLEVO/KAPOK Computer Device [1558:65a1]
InstallationDate: Installed on 2017-03-30 (43 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 04f2:b5a7 Chicony Electronics Co., Ltd
 Bus 001 Device 003: ID 8087:0a2b Intel Corp.
 Bus 001 Device 002: ID 0483:374b STMicroelectronics ST-LINK/V2.1 (Nucleo-F103RB)
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Aftershock P65xHP
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-51-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash acpi=force vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/06/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.05.04
dmi.board.asset.tag: Tag 12345
dmi.board.name: P65xHP
dmi.board.vendor: Aftershock
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Aftershock
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.04:bd02/06/2017:svnAftershock:pnP65xHP:pvrNotApplicable:rvnAftershock:rnP65xHP:rvrNotApplicable:cvnAftershock:ct10:cvrN/A:
dmi.product.name: P65xHP
dmi.product.version: Not Applicable
dmi.sys.vendor: Aftershock
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Sat May 13 17:04:14 2017
xserver.configfile: /etc/X11/xorg.conf
xserver.errors:

xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.4-1ubuntu6.1~16.04.1

Revision history for this message
Thiru (waffleboy) wrote :
description: updated
Revision history for this message
Brad Figg (brad-figg) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Henrique de Moraes Holschuh (hmh) wrote :

This is a Kabilake system, the intel-microcode does not support it as of 20161104 or 20170511 (upcoming release, to be uploaded in the next few days).

Please ensure your BIOS/UEFI is up-to-date, latest known-to-be-available microcode is revision 0x58, so it is not impossible that there are available fixes through a vendor BIOS/UEFI update.

Revision history for this message
Thiru (waffleboy) wrote :

Hey Henrique, Thanks for your reply!

I thought kernel 4.10 supported kaby lake CPU's? As I mentioned in the post, I tried it and it gave even worse results (couldn't get past login screen)

Revision history for this message
Dave Chiluk (chiluk) wrote :

Please try the latest hwe stack by. I'm using kabylake + the hwe stack without issue at the moment.

sudo apt install --install-recommends linux-generic-hwe-16.04 xserver-xorg-hwe-16.04

More info is available here.
https://wiki.ubuntu.com/Kernel/LTSEnablementStack

I'm also closing the intel-microcode track of this bug as at the moment this does not appear to be hwe related.

Thank you,

Changed in intel-microcode (Ubuntu):
status: New → Invalid
Revision history for this message
Paul White (paulw2u) wrote :

We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. You reported this bug some time ago and there have been many changes in Ubuntu since that time.

Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021.

Do you still see a problem related to the one that you reported when using a currently supported version of Ubuntu? Please let us know if you do otherwise this report can be left to expire in approximately 60 days time.

Thank you for helping make Ubuntu better.

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Changed in xorg (Ubuntu):
status: New → Incomplete
Revision history for this message
Paul White (paulw2u) wrote :

I'm closing this issue earlier than normal as I'm moving away from reviewing bug reports that have received little or no attention in recent times and there have been no comments to suggest that the reported problem is still an issue when using a currently supported release of Ubuntu.

Please feel to revert the status of this bug report to a previous status if this is still an issue while using a currently supported release of Ubuntu.

Changed in linux (Ubuntu):
status: Incomplete → Invalid
Changed in xorg (Ubuntu):
status: Incomplete → Invalid
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.