RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 607006 - x86_64: memtest86+ grub entry fails to boot
Summary: x86_64: memtest86+ grub entry fails to boot
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: memtest86+
Version: 6.1
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Jaroslav Škarvada
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-06-22 22:52 UTC by Sunil
Modified: 2018-11-14 17:33 UTC (History)
10 users (show)

Fixed In Version: memtest86+-4.10-2.el6
Doc Type: Bug Fix
Doc Text:
The memtest86+ tool failed to start on AMD64 and Intel 64 computers with the "--type=netbsd /elf-memtest86+-4.00" kernel parameter, and the "Error 13: Invalid or unsupported executable format" error message was given. This option now works as expected, and no error message is displayed.
Clone Of:
Environment:
Last Closed: 2011-05-19 14:02:09 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Set max-page-size to 4kB (376 bytes, patch)
2011-01-18 10:15 UTC, Jaroslav Škarvada 		no flags Details | Diff
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2011:0683 0 normal SHIPPED_LIVE memtest86+ bug fix and enhancement update 2011-05-18 18:10:32 UTC

Description Sunil 2010-06-22 22:52:31 UTC 
Description of problem:memtest fails in x86_64 arch error says " Error 13: Unsupported or invalid executable file ". however it succeeds if the kernel parameter is changed from 

kernel --type=netbsd /elf-memtest86+-4.00

to 

kernel /memtest86+-4.00


Version-Release number of selected component (if applicable):memtest86+-4.00-2.el6.x86_64



How reproducible:


Steps to Reproduce:
1.Install memtest on 
2.setup the memtest
3.boot with memtest option 
  
Actual results:It fails with default parameter


Expected results: It should start the memtest with default parameter.


Additional info:
Comment 2 RHEL Program Management 2010-06-22 23:13:52 UTC 
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
inclusion.
Comment 3 Anton Arapov 2010-06-24 08:34:08 UTC 
  This problem is known and arise in this bugzilla from time to time. So far, we decided to leave this as is, iow WONTFIX. Majority of the x86_64 systems doesn't have this problem, and some does.
  The issue is due to really odd loader, that should be rewritten, but there are no people wishing to re-write it.

Anton.
Comment 4 Bill Nottingham 2010-06-24 16:17:42 UTC 
OK, clearing.
Comment 7 RHEL Program Management 2010-07-15 14:58:15 UTC 
This issue has been proposed when we are only considering blocker
issues in the current Red Hat Enterprise Linux release. It has
been denied for the current Red Hat Enterprise Linux release.

** If you would still like this issue considered for the current
release, ask your support representative to file as a blocker on
your behalf. Otherwise ask that it be considered for the next
Red Hat Enterprise Linux release. **
Comment 8 Anton Arapov 2010-08-10 17:00:39 UTC 
*** Bug 622667 has been marked as a duplicate of this bug. ***
Comment 9 Anton Arapov 2010-08-10 17:00:55 UTC 
*** Bug 622666 has been marked as a duplicate of this bug. ***
Comment 10 Nate Straz 2010-09-10 21:59:00 UTC 
Hit this while trying to start memtest86+ on a Dell PowerEdge R710 system.
Comment 11 Jaroslav Škarvada 2011-01-18 10:15:06 UTC 
Created attachment 474014 [details]
Set max-page-size to 4kB

Lowering the max-page-size to 4kB make it boot again on x86_64, fedora bug #620846.
Comment 14 Jaroslav Škarvada 2011-01-25 15:22:14 UTC 
Fixed in: memtest86+-4.10-2.el6
Comment 16 Alexander Todorov 2011-04-06 17:00:39 UTC 
Verified with memtest86+-4.10-2.el6.x86_64 on 6.1 beta. I'm able to boot into memtest and run the tests.
Comment 17 Tomas Capek 2011-05-12 13:44:56 UTC 
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
The memtest86+ tool failed to start on AMD64 and Intel 64 computers with the "--type=netbsd /elf-memtest86+-4.00" kernel parameter, and the "Error 13: Invalid or unsupported executable format" error message was given. This option now works as expected, and no error message is displayed.
Comment 18 errata-xmlrpc 2011-05-19 14:02:09 UTC 
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2011-0683.html
Note You need to log in before you can comment on or make changes to this bug.