Closing this . Since it is becoming clear that Linux is abandoning it's
original fan base of older hardware and moving on, as it should, I don't
love it enough to go out and buy new hardware since Windows stills run
fine on my old stuff.
--
You received this bug notification because you are a
Additional information
** Attachment added: "kernel-4.11_dmidecode.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1778222/+attachment/5158334/+files/kernel-4.11_dmidecode.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Additional info
** Attachment added: "kernel-4.11_lspci.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1778222/+attachment/5158335/+files/kernel-4.11_lspci.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
Additional information
** Attachment added: "kernel-4.11_kernel-log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1778222/+attachment/5158336/+files/kernel-4.11_kernel-log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
I went back and installed kernel 4.12.14 and it works fine so something
definitely changed in kernel 4.13 that keeps my machine from booting.
Attached is my CPU information,
** Attachment added: "Cpu info"
Upgraded to kernel 4.17.3 using ukuu. System still fails to boot. Gets
the same kernel panic and locks up.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
Comparing differences between kernels.
There are differences in the way kernel 4.11 and kernel 4.15 handle 'ACPI'.
Wonder if this could be the cause of the kernel panic in kernel version
4.15?
** Attachment added: "kernel diff.odt"
Today I installed VirtualBox 5.2.12 on windows 7 pro.
I found that both Ubuntu 18.04 LiveCD and Linux Mint 19.0 LiveCD will
boot and load in the virtual machine with no kernel panic message. Same
physical machine, same bios.
Neither disk will boot standalone on my system without the kernel panic
When this problem occurs you cannot get to the terminal or anything
else. everything is locked up. You have to power the machine down. If
anything is logged I don't know how to get to it with the system locked
up.
It will boot with 'noacpi' option. But under that condition no errors
are apparent.
Public bug reported:
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
10 matches
Mail list logo
