Bug 18888 - Fresh install of Mageia 6 sta1-x86_64 on virtualbox does not boot ("bug unable to handle kernel null pointer dereference at")
Summary: Fresh install of Mageia 6 sta1-x86_64 on virtualbox does not boot ("bug unabl...
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal major
Target Milestone: ---
Assignee: Kernel and Drivers maintainers
QA Contact:
URL:
Whiteboard:
Keywords: NEEDINFO
Depends on:
Blocks:
 
Reported: 2016-07-07 16:42 CEST by Alejandro Vargas
Modified: 2021-02-09 16:01 CET (History)
4 users (show)

See Also:
Source RPM: kernel
CVE:
Status comment:

Attachments
Screenshot after boot (25.21 KB, image/png)
2016-07-14 15:57 CEST, Alejandro Vargas 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Alejandro Vargas 2016-07-07 16:42:19 CEST 
I just installed Mageia 6 64 bits sta1 on virtualbox. I created only one partition for data (btrfs filesystem) and one for swap. I let the installer to download all available updates.

When reboot, I receive a message from grub2 (reported on another bug) but the system bots ok.

When booting I press escape for removing the Mageia logo and see the boot log. When booting I see a "kernel null pointer error" and the system hangs.

This is a capture of the part when the problem starts:

http://imgur.com/TEB6g5K
Thierry Vignaud 2016-07-07 23:01:14 CEST

CC: (none) => tmb
Summary: Fresh install of Mageia 6 sta1-x86_64, btrfs on virtualbox does not boot => Fresh install of Mageia 6 sta1-x86_64, btrfs on virtualbox does not boot ("bug unable to handle kernel null pointer dereference at")
Component: Release (media or process) => RPM Packages
Source RPM: (none) => kernel

Comment 1 Alejandro Vargas 2016-07-08 08:54:19 CEST 
Same problem using EXT4 filesystem
Alejandro Vargas 2016-07-08 08:54:35 CEST

Summary: Fresh install of Mageia 6 sta1-x86_64, btrfs on virtualbox does not boot ("bug unable to handle kernel null pointer dereference at") => Fresh install of Mageia 6 sta1-x86_64 on virtualbox does not boot ("bug unable to handle kernel null pointer dereference at")

Comment 2 Alejandro Vargas 2016-07-08 09:33:34 CEST 
Installed with no updates and it boots OK but. Then updated and it failed again, then the problem is with kernel 4.7.0. With 4.6.3 it boots ok.
Comment 3 Marja Van Waes 2016-07-09 12:41:52 CEST 
(In reply to Alejandro Vargas from comment #2)
> Installed with no updates and it boots OK but. Then updated and it failed
> again, then the problem is with kernel 4.7.0. With 4.6.3 it boots ok.

Can you please try again?

I see you had updated at the end of install to kernel-desktop-4.7.0-0.rc6.1.mga6-1-1.mga6.

About 11 hours ago 4.7.0-0.rc6.3.mga6, with even more fixes than already available in 4.7.0-0.rc6.2.mga6, was pushed to the mirrors.

Thanks :-)

CC: (none) => marja11
Assignee: bugsquad => tmb
Keywords: (none) => NEEDINFO

Comment 4 Alejandro Vargas 2016-07-14 15:56:40 CEST 
Yes. I love the virtual machines: I have a snapshot just at the end screen of the installation. Tested updates from there. Some popus asking for  dependencies needed (I think it should be automatic "yes").

The system starts but boot sequence never ends. Check the screenshot attached.
Comment 5 Alejandro Vargas 2016-07-14 15:57:09 CEST 
Created attachment 8177 [details]
Screenshot after boot
Comment 6 Marja Van Waes 2016-08-26 11:42:37 CEST 
Mass-reassigning all bugs with "kernel" in the Source RPM field that are assigned to tmb, to the kernel packagers group, because tmb is currently MIA.

Assignee: tmb => kernel

Comment 7 Aurelien Oudelet 2021-02-09 16:01:36 CET 
Hi, thanks for reporting this bug.
We are sorry, but we no longer maintains this version of Mageia. Please upgrade to the latest version and reopen this bug against that version if this bug exists there.
As a result we are setting this bug to CLOSED:OLD

CC: (none) => ouaurelien
Status: NEW => RESOLVED
Resolution: (none) => OLD
Note You need to log in before you can comment on or make changes to this bug.