Bug 23104 - Kernel Panic on booting into kernel-4.14.44-desktop-2.mga6
Summary: Kernel Panic on booting into kernel-4.14.44-desktop-2.mga6
Status: RESOLVED WORKSFORME
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 6
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Kernel and Drivers maintainers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-06-01 10:23 CEST by Doug Laidlaw
Modified: 2018-06-03 05:33 CEST (History)
3 users (show)

See Also:
Source RPM: Kernel-4.14.44-desktop-2.mga6
CVE:
Status comment:

Attachments
/sbin/tune2fs -l /dev/sda5 (1.78 KB, text/plain)
2018-06-01 17:38 CEST, Doug Laidlaw 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Doug Laidlaw 2018-06-01 10:23:35 CEST 
Description of problem:
Kernel Panic on booting

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


How reproducible:
On booting into the latest kernel, I see "Kernel Panic, Unable to sync."
I can't get a screenshot, but the critical line seems to be:

"/dev/sda5: Unable to mount Ext4 filesystem as ext3 due to feature incompatibilities."

/dev/sda5 is my / partition.

Steps to Reproduce:
1.Any attempt to boot.
2.
3.
journalctl shows nothing except "partition busy" on a hardware reboot.  I assume that this is normal?
I am at present running happily on the previous kernel.
Bit Twister 2018-06-01 12:52:13 CEST

CC: (none) => bittwister2

Morgan Leijström 2018-06-01 13:56:19 CEST

CC: (none) => fri
Assignee: bugsquad => kernel

Comment 1 Dave Hodgins 2018-06-01 17:19:30 CEST 
Please attach the output of "/sbin/tune2fs -l /dev/sda5"

CC: (none) => davidwhodgins

Comment 2 Doug Laidlaw 2018-06-01 17:38:13 CEST 
Created attachment 10213 [details]
/sbin/tune2fs -l /dev/sda5

Output of command as requested.
Times are in my timezone:  UTC+10
Comment 3 Doug Laidlaw 2018-06-01 18:13:56 CEST 
I rebooted into Mint (so that /dev/sda5 would not be mounted) and ran fsck on /dev/sda5.  The output was a perfectly clean drive.

Because "tune2fs" might have fixed something, I tried booting into the new kernel again.  Nothing had changed.
Comment 4 Doug Laidlaw 2018-06-03 05:33:49 CEST 
I uninstalled and reinstalled kernel-4.14.44 and its dependencies.  Now everything is fine.

Status: NEW => RESOLVED
Resolution: (none) => WORKSFORME
Note You need to log in before you can comment on or make changes to this bug.