Asus ROG GL553VE Shutdown/Restart freeze in kernel 4.14

Bug #1734805 reported by Md Kowsar Hossain
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

I'm usung Asus ROG GL553VE. If I use an updated kernel I can't shutdown/restart, it just freezes.

First I updated my linux kernel into v4.10 and experienced the issue. Then again I updated my kernel into v4.14 and this issue still exists. However If I go back to kernel v4.4 this issue seems to be resolved. So seems like it's a kernel issue(v4.14).
---
ApportVersion: 2.20.1-0ubuntu2.13
Architecture: amd64
CurrentDesktop: Unity
DistroRelease: Ubuntu 16.04
InstallationDate: Installed on 2017-11-19 (11 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
Package: linux (not installed)
Tags: xenial
Uname: Linux 4.15.0-041500rc1-generic x86_64
UnreportableReason: The running kernel is not an Ubuntu kernel
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
---
ApportVersion: 2.20.1-0ubuntu2.13
Architecture: amd64
CurrentDesktop: Unity
DistroRelease: Ubuntu 16.04
InstallationDate: Installed on 2017-11-19 (11 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
Package: linux (not installed)
Tags: xenial
Uname: Linux 4.15.0-041500rc1-generic x86_64
UnreportableReason: The running kernel is not an Ubuntu kernel
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True

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 1734805

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 :

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

Changed in linux (Ubuntu):
importance: Undecided → Medium
Revision history for this message
Md Kowsar Hossain (kowsar89) wrote : JournalErrors.txt

apport information

tags: added: apport-collected xenial
description: updated
Revision history for this message
Md Kowsar Hossain (kowsar89) wrote : ProcCpuinfoMinimal.txt

apport information

Revision history for this message
Md Kowsar Hossain (kowsar89) wrote : ProcEnviron.txt

apport information

description: updated
Revision history for this message
Md Kowsar Hossain (kowsar89) wrote : JournalErrors.txt

apport information

Revision history for this message
Md Kowsar Hossain (kowsar89) wrote : ProcCpuinfoMinimal.txt

apport information

Revision history for this message
Md Kowsar Hossain (kowsar89) wrote : ProcEnviron.txt

apport information

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
tags: added: kernel-bug-exists-upstream
Revision history for this message
Md Kowsar Hossain (kowsar89) wrote :

Just tested, this issue exists in v4.15.0-041500rc1-generic too

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Does blacklist nouveau helps?

Add `blacklist=nouveau modprobe.blacklist=nouveau` to your kernel parameter.

Revision history for this message
Md Kowsar Hossain (kowsar89) wrote :

Where i have to add it?

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.