Kernel Panic - I panic

This may be only of interest only to people who Dual Boot. Here is what I saw on my PC when I booted Mint sometimes.

Kernel Panic
Please reboot your computer
Fatal exception in interrupt

My panic was I had just install MX 25 a couple days ago, so I delete the MX 25 partition thinking it was the problem. I also have MX 23 on the PC.

What I found out.
The problem was intermittent.
It only occurred when I restarted (warm boot) the PC from MX to Mint.
Shutdown of PC and boot (cold boot) to Mint and there was never a panic from the Mint’s kernel.

I always thought a restart of the PC was the same as a shutdown (power off). AI help me resolve this problem and believe it to be correct.

1 Like

My guess is MX 25 during startup loads firmware into various motherboard components. The warm boot, I think , skips reloading firmware. So switching distros with a warm boot might try to run Mint on MX firmware.
That said… I do it all the time… ie switch distros with a warm boot …it does not usually give trouble.

I have MX25 controlling grub … to test it out. It gives a message about not finding EFI , but it continues into grub OK.
I think MX25 needs a couple more updates.

1 Like

That was the exactly opinion of the AI. It suggest the cold boot which force the reloading of everything. Power off / power on - I never saw a panic. I thought it was a little funny that MX did not seem to care about the warm restart. Did not see a panic from MX, going form Mint to MX.

1 Like

Reading about Howard s problems with mx 25 and given his level of computer knowledge why are others not jumping up and down about problems or is it just different things linked together hardware and op systems combinations causing this

I’d suggest playing around with GRUB_CMDLINE_LINUX instead …

1 Like

Yes, the AI suggest this change.

"#GRUB_CMDLINE_LINUX_DEFAULT=“quiet splash reboot=pci pci=nomsi acpi=force”

But I see two extra parameters. Maybe over kill. The above change cause Mint to crawl. The mouse moved slowly and apt update-grub took 3 to 5 minutes to complete.

When I backed out the change I commented the line. So just adding the reboot=pci fixed your problem?