I’ve encounter a problem, not sure if it’s a bug or an intentional change to the Linux kernel. I normally don’t mess with the kernel as suggested by many on the Internet. But with new releases of Linux Mint 19.0 or Ubuntu 18.04 out, I decided to try them with the new LiveCD’s. With Ubuntu now using Gnome, I decided to give the LiveCD for 18.04 a try since I haven’t used Ubuntu since Unity, but then ‘Bamm’ the boot of the LiveCD locks up with a kernel panic.
So I tried the Linux Mint 19.0 LiveCD and had the same failure. Looking further at the problem I started installing different kernels in my Linux Mint 18.3 system. I found that my system will operate with different kernels up to an including 4.11. When I tried kernels 4.13 or 4.15 both failed to boot with the same kernel panic. Everything locks up and I have to do a power off, power on operation to recover. So kernel 4.11 is the last one I can use. I found that the LiveCD’s both use kernel 4.15 which does not work on my system.
I have included a picture of the screen when the boot fails. Would like to use the latest versions but the kernel problem prevents me from doing so.
This is my uname data: uname -a
Linux 4.11.0-14-generic #20~16.04.1-Ubuntu SMP Wed Aug 9 09:06:22 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
I have the dmidecode data and the lspci data if needed for kernel 4.11.(From a good boot)
With further testing I have found that, Linux Mint 19.0 LiveCD (in compatibility mode) or Ubuntu 18.04 LiveCD with the ‘noacpi’ option, will both boot into a usable live operating system. I’m afraid though that if I installed either to my hard drive that neither would boot. I would like to have help resolving this problem so I can continue to use Linux. Thanks!
Ps.there are no newer bios updates for my computer.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
apport-collect 1778222
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the Ubuntu Kernel Team.