Bugzilla – Bug 1172886
Kernel 4.12.14-lp151.28.52-default is unable to start on some hardware
Last modified: 2020-06-15 10:20:19 UTC
Created attachment 838763 [details]
Screenshot of Kernelpanic
Kernelpanic with Linux mail 4.12.14-lp151.28.52-default #1 SMP Wed Jun 10 15:32:08 UTC 2020 (464fb5f) x86_64 x86_64 x86_64 GNU/Linux
Kernel Linux mail 4.12.14-lp151.28.48-default #1 SMP Fri Apr 17 05:38:36 UTC 2020 (18849d1) x86_64 x86_64 x86_64 GNU/Linux works fine.
I can only add a picture from the root server.
This might be rather the latest ucode-intel firmware update.
Could you try to boot with dis_ucode_ldr boot option?
I hope i did i right.
Created attachment 838765 [details]
Screenshot of Kernelpanic with BootOptions
Created attachment 838766 [details]
Screenshot of BootOptions
Thanks for the quick test.
Then it's not about the firmware upgrade, but the regression in the kernel indeed.
Could you boot again with the old kernel, run hwinfo and attach the output to Bugzilla? The bug is very likely specific to the hardware, and we need details.
Reassigned to Boris.
It's too long for pasting here:
This are VServers with Dedicated Harddisks. I never had such issue with these servers.
2b:* 0f 01 c9 mwait %eax,%ecx <-- trapping instruction
provided I've typed the Code: line right.
* this box worked before with previous kernels?
* if so, pls boot it in a working kernel and upload full dmesg by doing
# dmesg > dmesg.log
* also, get the cpuid tool (leap should have it) and do
# cpuid -r > cpuid.log
and upload that log too pls.
That should be for now.
Created attachment 838767 [details]
Created attachment 838768 [details]
Wait a minute. Is that kernel running as a guest on some parallels hypervisor which says it is KVM?!?
[ 0.000000] DMI: Parallels Software International Inc. Parallels Virtual Platform/Parallels Virtual Platform, BIOS 6.12.26096.1233688 08/07/2019
[ 0.000000] Hypervisor detected: KVM
In any case, try booting with "idle=nomwait".
After updating to the *.52 I was also no longer able to boot. The previous kernel (*.48) wouldn't boot anymore either until I added the dis_ucode_ldr boot option, as recommended by Takashi Iwai.
I don't get any error messages when the boot fails. The system just hangs. Is there a boot option I should specify, that would produce log messages that could be helpful here?
(In reply to Simon Wood from comment #11)
> After updating to the *.52 I was also no longer able to boot.
Please open a separate bug and upload dmesg from a booting kernel there.
Created attachment 838778 [details]
hwinfo of a hardware setup that does not start with kernel 4.12.14-lp151.28.52-default
This is the output of hwinfo. After downgrading intel-ucode to version 20191115-lp126.96.36.199 I can boot kernel 4.12.14-lp151.28.52-default.
(In reply to Simon Wood from comment #13)
> Created attachment 838778 [details]
> hwinfo of a hardware setup that does not start with kernel
I asked you to open a *separate* bug instead of hijacking this one.
> This is the output of hwinfo. After downgrading intel-ucode to version
> 20191115-lp188.8.131.52 I can boot kernel 4.12.14-lp151.28.52-default.
And yes, you're the next one affected by faulty microcode. There's nothing we can do about that.
Ok, this solved the issue:
Linux dyndns 4.12.14-lp151.28.52-default #1 SMP Wed Jun 10 15:32:08 UTC 2020 (464fb5f) x86_64 x86_64 x86_64 GNU/Linux
Should i keep this Option always? Or can i remove this Option, if a new Kernel is available?
(In reply to Andreas Ernst from comment #15)
> Ok, this solved the issue:
> Linux dyndns 4.12.14-lp151.28.52-default #1 SMP Wed Jun 10 15:32:08 UTC 2020
> (464fb5f) x86_64 x86_64 x86_64 GNU/Linux
> Should i keep this Option always? Or can i remove this Option, if a new
> Kernel is available?
Keep it always as long as you're using parallels and they haven't fixed it. It looks like they're reporting CPUID(5).ECX=0x3 and the kernel tries to use it but it #GPs because, well, virtualization. And kvm is probably fine...
(Clear stale NEEDINFO.)