Ask Your Question

Fedora 27: Kernel Panic at Boot w/ Fresh Install

asked 2018-01-12 18:15:41 -0500

thatrandomguy gravatar image

updated 2018-03-25 18:01:36 -0500

I'm relatively new to Linux and I haven't a clue as to how to diagnose the issue I've been receiving.

The setup that I currently have consists of a KVM switch that allows me to use a single keyboard and mouse for two machines—one running Windows and the other running Fedora.

I installed Fedora before I introduced the new hardware arrangement and hadn't used it until after it was done.

Today, I decided to play around with it after a while and noticed it took a while to boot. All of the sudden, I'm greeted by these error messages during boot and I hadn't understood why it was doing so. Thinking it was doing something behind the scenes, I left it for an hour. Coming back, the thing was still stuck; so I decided to manually force a shutdown and restart the machine. The same error messages popped up and lacking resources online to diagnose the problem with a working solution, I decided to reinstall Fedora.

I just recently installed it but had misplaced the live disc I used to install. I had to use Fedora Media Writer to get another ISO to install. After which, I proceeded to install Fedora again. It ran its course and I was able to run it normally for that brief period. Thinking the worst had been evaded, I decided to run some updates from the Gnome Software app. It rebooted, updates, and rebooted again. On that last reboot (after having applied the updates), I am yet again met with this weird kernel panic message—impeding me from using Fedora normally.


After burning the new ISO to a spare DVD, I booted the live system and started looking for logs to diagnose the problem. AFAIK, I wasn't able to see anything concerning the issue that caused the error shown in the picture.

Additionally, I ran fsck on the larger partition for the machine holding Fedora and it returned with a status of 0. After reading the man page, I can assume that's a good thing. I attempted to check the root file system but I couldn't get access to it because it was mounted.

I honestly don't know what to do at this point.

I have Kali on a USB which I can use to do tasks not possible with a live system (if necessary).

The processor and video card for the system are both Intel. The system itself is pretty old I'd imagine and from what I've read online about this issue, the possibility of it being a hardware problem is plausible.

What steps do I take to better understand this random issue?

I will provide more info on request.


EDIT: Proper fix has been included in chosen answer. Please see below.

edit retag flag offensive close merge delete


@bitwiseoperator I agree. I ran the grml live-DVD and used the tips to see if there was anything I could use to run tests on the hardware. I ran some smartctl tests and they seemed to have come back positive. I noticed that grml has the potential to run memtest86 but requires some special config for grub? Incidentally, I had to use memtest86 not too long ago and have a spare DVD to run it. I'll report back on my findings. Considering the age of this PC, I think faulty hardware is a likely cause.

thatrandomguy gravatar imagethatrandomguy ( 2018-01-13 12:51:10 -0500 )edit

Cool. If you don't want to mess with memtest, I believe the GRML program has a memory stressing program (like Prime95 or something); if your RAM is faulty, smashing it for a few minutes (or seconds) usually results in kernel panic, so you could try that, too.

bitwiseoperator gravatar imagebitwiseoperator ( 2018-01-13 13:31:45 -0500 )edit

@bitwiseoperator Before I read your recent message, I remembered something I did right before the kernel panic incidents arose. I recalled running updates for Fedora and so I actually just reinstalled Fedora again. This time, however, I didn't update anything. I rebooted a couple of time to verify if it was something else, but I've been running it fine since I reinstalled. I've even managed to recover all my previous settings and whatnot (after manually doing so). It might be premature to say this, but I'm starting to think there might be an update that's causing my kernel panics.

thatrandomguy gravatar imagethatrandomguy ( 2018-01-13 18:22:26 -0500 )edit

Well, that's possible, but I would definitely put some stress on that hardware before going too far; you don't want to lose your configuration again (though if it's RAM, you should be able to recover with, y'know, new RAM).

bitwiseoperator gravatar imagebitwiseoperator ( 2018-01-14 04:26:42 -0500 )edit

@bitwiseoperator To update: I ran memtest86+ and received no errors on the ram. I decided to run the updates again and I've been left with the same kernel panic on start up. Something I think I should point out is that I haven't attempted to use a previous kernel from the grub menu. I hadn't attempted it due to my keyboard not registering during boot. I've ordered a PS/2 adapter so that I can see if there's anything in the BIOS that needs updating or readjusting. Hopefully, I'll be able to use an earlier kernel and get myself logged in. I'll keep you posted.

thatrandomguy gravatar imagethatrandomguy ( 2018-01-23 12:13:36 -0500 )edit

3 Answers

Sort by » oldest newest most voted

answered 2018-01-25 10:33:58 -0500

thatrandomguy gravatar image

updated 2018-03-25 18:04:40 -0500

The issue with my HP microtower was that my BIOS was out of date. I confirmed with the wrong version before but after updating it, I can now run Fedora 27 with the latest kernels.

Again, my system was a HP eq5600. Intel core duo processor with Intel graphics.

If you've also been suffering from kernel panics from the new kernels, I'd suggest taking a look at your BIOS version.

edit flag offensive delete link more

answered 2018-01-12 20:14:34 -0500

The first thing you want to rule out is a hardware problem. Given the panic you're seeing, the first suspect I'd consider in that domain would be faulty RAM. What kind of hardware is this? Often times, manufacturers include built-in diagnostics options from the boot menu which you may want to execute if available. If not, you could try using a toolkit designed for that purpose, such as GRML ( ).

Rule that out, and then we'll see what's next, but repeated OS failures from fresh installations with kernel panics at memory I/O functions sounds like hardware to me.

edit flag offensive delete link more

answered 2018-02-26 19:17:59 -0500

ulatekh gravatar image

Are you running an Intel processor, by chance?

One of my Intel boxes started having this problem with all the 4.14 and 4.15 kernels. It didn't seem to be a hardware issue, since I could boot a Live CD just fine, and I could still boot into Windows 10.

This bug report suggested adding "nopti" to my kernel command line. Now my Intel box boots.

Guess they still have some bugs to work out.

edit flag offensive delete link more

Question Tools

1 follower


Asked: 2018-01-12 18:15:41 -0500

Seen: 1,795 times

Last updated: Mar 25 '18