Bug 1253814 - Latest kernel update causes kernel panic
Summary: Latest kernel update causes kernel panic
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 22
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-08-14 19:08 UTC by Diederik van Lierop
Modified: 2015-08-16 12:23 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-08-16 12:23:13 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Cellphone picture of call trace (346.80 KB, image/jpeg)
2015-08-14 19:08 UTC, Diederik van Lierop
no flags Details

Description Diederik van Lierop 2015-08-14 19:08:10 UTC
Created attachment 1063160 [details]
Cellphone picture of call trace

Description of problem:

Just updated to the latest kernel version 4.1.4-200.fc22.x86_64, but this panics on boot after only 1.6 seconds. Can't find any log files using journalctl, maybe because it's too early in the boot process?

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

4.1.4-200.fc22.x86_64

How reproducible:

Just booting my system and selecting the most recently installed kernel version causes this panic. When using the previously installed version (4.1.3-201) it works just fine

Steps to Reproduce:
1.
2.
3.

Additional info:

Shuttle barebone, SZ77
Intel® Core™ i5-3570K CPU @ 3.40GHz × 4 
Gallium 0.4 on AMD OLAND

I took a picture of the screen, please see the attached file

Just let me know what more information you would need. Also, where do I find the relevant logs of the panic and the call trace? "journalctl -k -l -b -1" doesn't show anything useful.

Comment 1 Laura Abbott 2015-08-14 21:27:21 UTC
This panic indicates it can't find the root file system. Can you try the 4.1.5 update in testing in bohdi and see if that works for you?

Comment 2 Diederik van Lierop 2015-08-15 06:57:53 UTC
Yes, 4.1.5 works again!

Thanks for looking into this.

Comment 3 Josh Boyer 2015-08-16 12:23:13 UTC
Thanks.  Typically that means that the initramfs wasn't created or loaded for some reason.  The new update likely didn't fix a kernel bug, but instead had the initramfs created properly.


Note You need to log in before you can comment on or make changes to this bug.