Booting kernel failed: Invalid argument

Bug #1564740 reported by Seth Arnold on 2016-04-01
28
This bug affects 5 people
Affects Status Importance Assigned to Milestone
memtest86+ (Ubuntu)
High
Unassigned

Bug Description

I cannot run the Memory Test using the Xenial beta2 server image via a USB memory stick.

The "verify disc" option ran to completion and reported no errors -- is the memory test included in this verification?

The error message on screen reads:

Loading /install/mt86plus... ok
Booting kernel failed: Invalid argument

The system is dual e5-2630v3, 128 gigs ram, supermicro 6038r-e1cr16L.

Thanks

tags: added: xenial
japi (x-launchpad-ziqu-de) wrote :

I can confirm this issue with the following configuration:

ISO: ubuntu-16.10-desktop-amd64 (mounted as emulated drive / console redirection)
MB: Supermicro X10DRi
CPU: 2x Intel E5-2620v4
RAM: 128 GB

In BIOS/Legacy mode I get the same error:

Loading /install/mt86plus... ok
Booting kernel failed: Invalid argument

In UEFI mode memtest is not listed in the boot options.

Ubuntu itself starts without issues on the same hardware.
The iso file is not corrupt. Memtest runs fine from the same iso file in an VM.

Sidenote: The Windows memory test seems to have issues on this plattform too in BIOS mode:
It was finished as fast as if it would only check a small part of the RAM compared to the same test in UEFI mode. Maybe something is wrong with PAE and they check only 4GB...

Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in memtest86+ (Ubuntu):
status: New → Confirmed
Changed in memtest86+ (Ubuntu):
importance: Undecided → High
Hans Meier (herrmeier) wrote :

I can confirm this issue with the following configuration:
ISO: ubuntu-16.04.2-server-amd64.iso
MB: X9DRL-IF
CPU: 2x Intel Xeon E5-2630 2.3Ghz Six Core
RAM: 8x4gb = 32GB RAM 1Rx4 PC3L M393B5270DH0 - YH9 SAMSUNG
IPMI-Firmware: SMT_X9_339.bin
BIOS: AMI 3.0 X9DRL5.922

ISO booted via virtual storage IPMI.
Thank you!

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers