Bug 1401619

Summary: Fedora fails to shutdown or reboot in kernel 4.8.15 then graphics card crashes / interface breaks and computer hangs
Product: [Fedora] Fedora Reporter: Eric Remigino <eric.remigino>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 25CC: cz172638, eric.remigino, gansalmon, ichavero, itamar, jonathan, kernel-maint, labbott, madhu.chinakonda, mchehab, richjames11
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: 4.9.4 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-01-24 16:13:13 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
right before the gui breaks
none
Another shot of the full output right before the gui breaks
none
camera shot of the broken gui
none
another camera shot of the broken gui
none
journalctl log of final outputs that take place while trying to shutdown or reboot none

Description Eric Remigino 2016-12-05 17:37:46 UTC
Description of problem:

Fedora fails to shutdown or reboot, than graphic interface breaks and computer hangs.

Version-Release number of selected component (if applicable):

Kernel 4.8.10

How reproducible:

After computer bootsup, reboot the computer with sudo reboot now or sudo shutdown now.


Steps to Reproduce:
1.
2.
3.

Actual results:

Computer hangs and graphic interface breaks, refer to screenshot.


Expected results:

Fedora should reboot or shutdown cleanly and safely.


Additional info:

Comment 1 Eric Remigino 2016-12-05 17:39:03 UTC
Created attachment 1228115 [details]
right before the gui breaks

Here's a camera shot of the output right before the gui breaks

Comment 2 Eric Remigino 2016-12-05 17:40:29 UTC
Created attachment 1228116 [details]
Another shot of the full output right before the gui breaks

Here's another shot of the full output right before the gui camera breaks.

Comment 3 Eric Remigino 2016-12-05 17:41:04 UTC
Created attachment 1228117 [details]
camera shot of the broken gui

Comment 4 Eric Remigino 2016-12-05 17:41:38 UTC
Created attachment 1228118 [details]
another camera shot of the broken gui

Comment 5 Eric Remigino 2016-12-05 17:43:11 UTC
This all took place on the New Razer Blade Stealth (late 2016).

SPECS:

Kaby lake i7-7500U Dual Core Processor
Intel HD Graphics 620

Comment 6 Eric Remigino 2016-12-05 19:15:42 UTC
This bug also occurs now when trying to boot from Kernel 4.8.8 and Kernel 4.8.6  However, I don't occur before the install of Kernel 4.8.10, only afterwards.

Comment 7 Eric Remigino 2016-12-06 15:43:16 UTC
problem persists in 4.8.11

Comment 8 Eric Remigino 2016-12-10 18:40:05 UTC
Problem persists in 4.8.12 but with some peculiar changes.

If I reboot from the login screen and haven't logged in yet, the computer reboots just fine.

Rebooting from the GNOME Menu puts the computer in to a suspend loop.

Rebooting the computer from terminal using command `sudo reboot now` causes the Reboot to fail, and has the same output as shown from the picture attachments, and sometimes it puts it into a suspend loop.

Shutdown always fails and causes GUI to break.

Comment 9 Eric Remigino 2016-12-17 03:03:49 UTC
Problem persists in 4.8.14

When rebooting or shutting down from the login screen and haven't logged in yet, commands behave as expected (tested twice with each command)

When rebooting or shutting down the computer after logging in, the graphics card crashes and the computer locks as shown in the pictures.

Comment 10 Eric Remigino 2016-12-22 15:20:39 UTC
I was able to catch at the end that the last line before the graphics card crashes and makes it not legible is 

"Failed to reboot, no parameter file or directory"

Comment 11 Eric Remigino 2016-12-29 16:58:43 UTC
Created attachment 1235903 [details]
journalctl log of final outputs that take place while trying to shutdown or reboot

I believe watchdog is the issue after seeing that its the last command that fails before i have to hold down the power button to finish.

Comment 12 Eric Remigino 2017-01-13 05:55:21 UTC
I'm pretty sure this has been fixed now.  I did a clean install and fully updated fedora. Did multiple restarts / power downs.  I also installed multiple third party packages and dependencies a to try and track if one of them was causing it and so far the machine powers down and reboots as expected.

Comment 13 Laura Abbott 2017-01-17 01:13:04 UTC
*********** MASS BUG UPDATE **************
We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 25 kernel bugs.
 
Fedora 25 has now been rebased to 4.9.3-200.fc25.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.
 
If you have moved on to Fedora 26, and are still experiencing this issue, please change the version to Fedora 26.
 
If you experience different issues, please open a new bug report for those.

Comment 14 Eric Remigino 2017-01-21 04:33:49 UTC
seems to be fixed in 4.9.4

Comment 15 Laura Abbott 2017-01-24 16:13:13 UTC
Thanks for letting us know. I'm going to close the bug, please reopen if the problem shows up again.

Comment 16 Richard James 2017-02-17 12:03:16 UTC
Hi,

I know this is listed as fixed but I'm having the same issue on a Razer Blade Stealth running kernel 4.9.9-200 in Fedora 25. When shutting down/rebooting or connecting/disconnecting power I get the graphical corruption from earlier on in this thread, and I also get the same issue when pressing CAPS lock/NUM lock.

Should I raise this as a separate bug or reopen this one?

uname -r
4.9.9-200.fc25.x86_64

Richard

Comment 17 Laura Abbott 2017-02-17 17:07:30 UTC
Go ahead and open a separate bug.