Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
My customer is using kexec to avoid the excessive amount of time it takes for the UEFI (IBM HS22V blade in this case) to get to the state that it will do a DHCP request (about 7 *minutes*). Essentially using kexec as outlined here: https://access.redhat.com/kb/docs/DOC-9797 (rebooting without rebooting)
Upon executing the following:
kexec -l /boot/vmlinuz-2.6.32-71.el6.x86_64 --initrd=/boot/initramfs-2.6.32-71.el6.x86_64.img
kexec -e
In the customer's case this operation works only sometimes, and when it does panic, they actually get a variety of different stack traces. Additionally there are other times when the system just hangs completely. I actually have managed to reproduce this issue on similar hardware (IBM HS21) in-house, and in every case the system appears to hang completely (no kernel panic, nada). Just for kicks I tried out the RHEL6.1 candidate kernel and still no change in behaviour.
Version-Release number of selected component (if applicable):
kernel-2.6.32-71.el6.x86_64
How reproducible:
*On customer's hardware, majority of the time.
*On in-house hardware, every time.
Steps to Reproduce:
1. kexec -l /boot/vmlinuz-2.6.32-71.el6.x86_64 --initrd=/boot/initramfs-2.6.32-71.el6.x86_64.img
2. kexec -e
Actual results:
System panics, or is hung completely.
Expected results:
Successfully load up the new kernel without issue.