| Summary: | Kernel panic in kernel-desktop-4.1.3-1 when is using more than 1 processor | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Piotr Mierzwinski <piotr.mierzwinski> |
| Component: | RPM Packages | Assignee: | Thomas Backlund <tmb> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | gm2.asp, marja11, thierry.vignaud |
| Version: | Cauldron | ||
| Target Milestone: | --- | ||
| Hardware: | i586 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | kernel-desktop-4.1.3-1.mga6-1-1.mga6 | CVE: | |
| Status comment: | |||
| Attachments: |
Kernel panic screen shot
VirtualBox 5.0 settings VirtualBox 5.0 settings for Windows host (Intel i5 in host) VirtualBox 5.0 settings for Linux host (Amd Phenom in host, no nested paging) Kernel panic screen shot (4.1.4-desktop) |
||
|
Description
Piotr Mierzwinski
2015-08-03 02:03:01 CEST
Created attachment 6888 [details]
Kernel panic screen shot
Do you get the kernel panic every time you try, or didn't you try again? If the latter, then please try whether you can reproduce it. CC:
(none) =>
marja11, tmb Can you test if disabling "nested paging" in vbox config (system) fixes it? I'd quite a lot of kernel oops & userspace segfaults once updating to virtualbox-5.0 on Windows that were solved by disabling "nested paging" CC:
(none) =>
thierry.vignaud #1, @Marja van Waes
I tried several times with several settings in VirtualBox. Result was always the same, so I decided to try with kernel server version where I didn't meet Kernel Panic. Additionally I was trying with VirtualBox package from Mageia 5.
Hence I suppose it's something wrong in kernel desktop configuration.
#2, @Thierry Vignaud
I was trying with disabled "nested paging". Didn't help.
I was trying with both type of chipsets (PIIX3 and ICH9).
I was trying with enabled and disabled PAE/NX.
I was trying with 1 CPU, 2 CPU and 3 CPU. Only on 1 CPU kernel is starting.
Paravirtualization interface has "Default" value (here this is KVM).
Always result is the same. Kernel Panic.
I'm testing Mageia 6 on configuration where host and guest is Linux. In this particular case it was:
Host: Mageia 5 32bit (virtualbox installed from package provided by Oracle)
I'm using AMD Phenom(tm) II X4 955 Processor (4 cores).
with kernel: 3.19.8-server-3.mga5
Guest Mageia 6 (Cauldron) 32 bit (updates on day 2015/08/02)
VirtualBox configuration is:
Processors: 3 (from 8 available)
Base Memory is "1251 MB"
Chipset: ICH9
Enable I/O APIC (on)
Enable EFI (off)
Enable PAE/NX (off)
Enable 3D acceleration (on)
Controller IDE: ICH9
Controller SATA: AHCI (Use Host I/O cache - off)
As I said before, kernel-server-4.1.3-1 is working fine with default settings in VirtualBox (nested paging is turned on).
Sorry I think that was paravirtualization that was the issue. I think I'd to set it to "kvm" + disable "nested pages" in order to get rid of those issues I was trying kvm (directly selecting KVM) + disabled "nested pages" and it doesn't work! Even if I turn off "paravirtualization" then I get Kernel Panic! Sorry, your were talking in previous post about Windows. Maybe there it will help. And by the way. I'm using VirtualBox 5.0.0 with Mageia 5 32bit, where Windows 7 is the host and all work fine. KVM is chose by default by virtual machine in my system, because I don't have installed in my system other Hypervisor (only KVM). Attached screen shot. I can say also that using older kernel: "kernel-desktop-3.19.0-0.rc.7.3.mga5" (comming from Mageia 5), the system starts up. How could you explain that Mageia Cauldron is starting with kernel dedicated for servers (using 3 cores from my processor, KVM and enabled "nested pages")? Did kernel-desktop-4.3.1 was tested on (running on Linux) VirtualBox 5.0 with more than 1 CPU (set in VBox)? From my point of view the issue is in configuration which was using to build kernel desktop. Created attachment 6894 [details]
VirtualBox 5.0 settings
Marja Van Waes
2015-08-03 20:40:09 CEST
CC:
tmb =>
(none) You didn't disabled "nested pages"! Thierry please. Yes. I did it. Trust me. On screen shot I only showed my default configuration of virtual machine where I run Mageia. Through this screen shot I would like to prove you that I have turned on KVM as default. Just look at where I put info about screen shot. If option "nested pages" helped you in Windows (I don't know what version), so this automatically not means that it will help everywhere. Did you ever test this kernel in similar configuration? If I will have some time then I try to do the test on Windows 7 host. Created attachment 6903 [details]
VirtualBox 5.0 settings for Windows host (Intel i5 in host)
Update. As I promised I performed test for Windows 7 as host. Virtual machine had 2 processors. Check screen shot for the other details of configuration referring to virtual machine. Host is based on Intel i5-3340 processor. VirtualBox in version 5.0.0. All works fine. Mageia Cauldron with kernel-desktop-4.1.3 is running. I was repeating last test on machine with AMD Phenom II processor where "nested paging" is disabled and set 3 processors. Result the same - Kernel Panic. I was also testing with Paravirtualization interface set as "legacy" and disabled "nested paging" (check screen shot). No change - Kernel Panic. Please notice, that on machine with AMD Phenom II processor where on virtual machine is available only 1 processor - Mageia Cauldron with kernel-desktop-4.1.3 kernel is starting. And I remind that for kernel-server-4.1.3 all work fine (with KVM and enabled "nested paging"). I'm confused and I don't know what is going on here. :-( Created attachment 6904 [details]
VirtualBox 5.0 settings for Linux host (Amd Phenom in host, no nested paging)
On version 4.1.4-desktop I meet the same situation - Kernel panic (attached screen shot). Version for servers works fine. Created attachment 6919 [details]
Kernel panic screen shot (4.1.4-desktop)
is 4.1.7 working any better ? Unfortunately no change :(. Server is working "desktop" not working. Please note that this is working on real machine (I've tested on Ivy Bridge). I've installed all updates till today (18/09/2015 23:30) If you havent done it yet... can you update virtualbox to 5.0.4 too Issue bears some similarities to this Manjaro issue: https://github.com/manjaro/packages-core/issues/14 which is traced back to an upstream regression. CC:
(none) =>
gm2.asp (In reply to Thomas Backlund from comment #17) > If you havent done it yet... can you update virtualbox to 5.0.4 too No change - server is working and "desktop" is not working. I've updated virtualbox to: VirtualBox-5.0.4-102546 (using self executable file - "Linux_x86.run") and immediately updated extension pack to Oracle_VM_VirtualBox_Extension_Pack-5.0.4-102546.vbox-extpack Virtualbox is running on Mageia 5 32bit with latest updates (kernel-3.19.8-server-3.mga5). (In reply to Arne Spiegelhauer from comment #18) > Issue bears some similarities to this Manjaro issue: > https://github.com/manjaro/packages-core/issues/14 > which is traced back to an upstream regression. Ah, indeed ... now I remember reading about this issue earlier... I will merge that fix in the next kernel there is now a 4.1.8-1 kernel in cauldron (and mga5 updates testing) that I have added the needed fix in It's working :). kernel-desktop-4.1.8-1.mga6-1-1.mga6 Tested with 3 processors on virtual machine running on VirtualBox-5.0.4-102546. Big thanks. Status:
NEW =>
RESOLVED Great :) And thanks to Arne for upstream regression reference |