Bug 1601407

Summary: Random crash on vmlinuz-4.17.5-100.fc27.x86_64
Product: [Fedora] Fedora Reporter: Rick Richardson <rickrich>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 27CC: airlied, avinash, bskeggs, ewk, hdegoede, ichavero, itamar, jarodwilson, jcline, jglisse, john.j5live, jonathan, josef, kernel-maint, linville, mchehab, mjg59, steved
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-07-16 18:01:27 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:
Embargoed:
Attachments:
Description Flags
Hardware Lister none

Description Rick Richardson 2018-07-16 11:13:38 UTC
Created attachment 1459127 [details]
Hardware Lister

Random crash on vmlinuz-4.17.5-100.fc27.x86_64.

Usually, its when I'm sleeping, but also I had it doing a VirtualBox.

The previous kernel, vmlinuz-4.17.3-100.fc27.x86_64, does not have this problem.

I am running the previous kernel until this is fixed!

Comment 1 Avinash Meetoo 2018-07-16 12:04:04 UTC
I have noticed the same thing. The latest kernel (4.17.5-100.fc27) has frozen twice: once on my Dell Inspiron laptop and once on a Dell Poweredge T20 server.

The previous kernel never froze.

When the computer freezes, nothing can be done apart from restarting using the power button and the log does not indicate anything (i.e. it only contains normal lines then nothing until, of course, -- Restarting --)

I have also booted in the previous kernel until a solution is found.

Comment 2 Jeremy Cline 2018-07-16 18:01:27 UTC
A fix for this should be in v4.17.7

*** This bug has been marked as a duplicate of bug 1598462 ***