Bug 1317962 - kernel 4.4.4-301 fails to boot on my system
Summary: kernel 4.4.4-301 fails to boot on my system
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 23
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-15 15:43 UTC by Bruno Antunes
Modified: 2016-03-15 21:21 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-03-15 21:20:39 UTC
Type: Bug

Attachments (Terms of Use)
the error (4.20 MB, image/jpeg)
2016-03-15 15:43 UTC, Bruno Antunes 		no flags Details
new error (2.43 MB, image/jpeg)
2016-03-15 16:22 UTC, Bruno Antunes 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Bruno Antunes 2016-03-15 15:43:09 UTC 
Created attachment 1136649 [details]
the error

Description of problem:

Kernel 4.4.4-301 does not boot on my machine.

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

4.4.4-301

How reproducible:

Always

Steps to Reproduce:
1. select 4.4.4-301 on GRUB
2. press enter

Actual results:

Kernel hangs with a failure message "Failed to start Load Kernel Modules." (see photo)

Expected results:

Kernel should boot

Additional info:

Crypto LUKS setup on main disk. Currently running 4.4.3 just fine.
Comment 1 Josh Boyer 2016-03-15 15:51:10 UTC 
Are you using virtualbox modules on this machine?
Comment 2 Bruno Antunes 2016-03-15 15:59:11 UTC 
Yes, I am!
Comment 3 Josh Boyer 2016-03-15 16:07:02 UTC 
Boot into an older kernel and remove them.  They are likely what is causing your boot hang.  Nothing in Fedora itself uses the systemd module loading service.
Comment 4 Bruno Antunes 2016-03-15 16:22:53 UTC 
Created attachment 1136666 [details]
new error

What happens now (this is usually what I get on the current kernel, before the unlock disk dialog shows up, but now it just hangs here)
Comment 5 Bruno Antunes 2016-03-15 16:23:31 UTC 
Also, I removed VirtualBox and reinstalled the kernel packages.
Comment 6 Bruno Antunes 2016-03-15 16:40:28 UTC 
I've managed to boot by adding "nomodeset" to my kernel on GRUB. Do I need to reinstall the AMDGPU driver? How can I fix this?
Comment 7 Laura Abbott 2016-03-15 18:51:53 UTC 
If you have a radeon chip please test http://koji.fedoraproject.org/koji/taskinfo?taskID=13356645
Comment 8 Bruno Antunes 2016-03-15 21:06:10 UTC 
How can I do that? Can't find a download :/
Comment 9 Bruno Antunes 2016-03-15 21:20:39 UTC 
Well, nevermind - from that link, I got to http://koji.fedoraproject.org/koji/buildinfo?buildID=743760 and this package works! On kernel 4.4.5-300 now, no modesetting issues! Thanks for the (indirect) pointer :D
Note You need to log in before you can comment on or make changes to this bug.