Bug 1394546 - "Try to free Memory without Signature" on HP Proliant BL460c/DL380 G8 (iPXE)
Summary: "Try to free Memory without Signature" on HP Proliant BL460c/DL380 G8 (iPXE)
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: ipxe
Version: 7.2
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: pre-dev-freeze
: ---
Assignee: Neil Horman
QA Contact: Raviv Bar-Tal
URL: https://bugzilla.redhat.com/show_bug....
Whiteboard:
Depends On:
Blocks: 1401400 1420851 1442258
TreeView+ depends on / blocked
 
Reported: 2016-11-13 10:54 UTC by Mihir Lele
Modified: 2021-09-09 12:00 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-02-26 12:31:01 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Mihir Lele 2016-11-13 10:54:29 UTC 
Description of problem:

Getting "Try to free Memory without Signature" error while pxe provision the system

Version-Release number of selected component (if applicable): 6.2.x


How reproducible:

Everytime

Steps to Reproduce:

1. Create a bootdisk for host on Satellite.
2. Try to boot using it on  HP Proliant BL460c Gen8 and HP DL380 Gen8 hardware
3. It fails with error "Try to free Memory without Signature"


Actual results:

Fails to boot.

Expected results:

Should be able to boot.

Additional Info:

System is getting provisioned with the workaround given the article for DHCP less provisioning

https://access.redhat.com/solutions/2143291
Comment 8 Lenny Szubowicz 2017-08-16 19:16:09 UTC 
Can you provide be with some more specific information about how to reproduce this problem given that I'm not familiar with Satellite?

In the mean time, a serial console log showing the failure would be helpful.

                              -Lenny.
Comment 12 Neil Horman 2018-02-06 21:53:27 UTC 
This isn't going to be fixable by us.  I presume this is a Broadcom card involved here?  And you are likely attempted to boot the ipxe undi image?  The error you are seeing is generated internally from the UNDI driver on the broadcom NIC rom, and there is no way for us to fix it.  You will need to contact broadcom to fix this
Note You need to log in before you can comment on or make changes to this bug.