Red Hat Bugzilla – Bug 439116
POWER 6 systems cannot boot without manual intervention
Last modified: 2014-01-12 19:07:03 EST
Description of problem:
POWER 6 systems cannot boot without manual intervention after installing and
booting a >= 2.6.20-rc1 kernel. Kernel 2.6.20-rc1 introduces support for
"ibm,dynamic-reconfiguration-memory nodes", and when this feature is used (ie,
kernel 2.6.20-rc1+ is booted) subsequent boots will not be automatic: the kernel
label must be manual entered at yaboot.
If RHEL 5 is installed on a system and a >= 2.6.20-rc1 kernel is installed then
subsequent boots of RHEL 5 will not occur automatically -- the label must be
Version-Release number of selected component (if applicable):
Machine Type = 9117-MMA
Steps to Reproduce:
1. Load any variant of RHEL 5 on a POWER6 system.
2. Download, build and install the mainline kernel.
The boot process begins, the firmware detects a CAS change and reboots the
system. To correctly boot the system you need to manually enter the kernel label
Yaboot should automatically boot the last kernel attempted.
This problem will be seen in upgrades from RHEL 5.x to RHEL 6, when released.
A patch from IBM against yaboot (to fix unattended reboot on POWER 6) is attached.
Created attachment 299255 [details]
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release. Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products. This request is not yet committed for inclusion in an Update
I wanted to get our email correspondence out there so people would understand
that you were pushing this bug. Hope you don't mind!
> Is there anything I need to do to ensure this patch makes RHEL 5.3? Is there
> any testing that needs to be done, or perhaps a mailing list I should to post
> to in order to get the patch reviewed?
there is special process for this called errata. Don't deal with this bug. I
will do everything needed.
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.