Red Hat Bugzilla – Bug 195002
RHEL4 U4 i386 partner beta will not install on ES7000/one
Last modified: 2007-11-30 17:07:25 EST
Description of problem:
When attempting to install the RHEL4 U4 partner beta (i386) on an ES7000/one,
the uniprocessor installation kernel panics. We have found that the system will
install when using the "noapic" parameter, but are unsure if this is an general
work-around or if it only works in a particular hardware configuration.
This is a regression from RHEL4 U3. In RHEL4 U3, no kernel parameters were
required to install i386.
Version-Release number of selected component (if applicable):
Boot from the RHEL4 U4 i386 partner beta CD1 and attempt the install.
Kernel will panic.
Kernel does not panic.
RHEL4 U3 installation kernel did not require any kernel parameters in order to
install i386 on ES7000/one.
Created attachment 130841 [details]
Kernel panic with apic=debug
We are also unable to boot the default uniprocessor kernel even after
installation is complete.
Does 'apic=bigsmp' work?
Does 'apic=bigsmp' work? Also, can you post the result of running dmidecode on
In regards to " but are unsure if this is an general
work-around or if it only works in a particular hardware configuration." it is a
general work-around introduced in RHEL4 U4 kernel due to APIC being turned on in
the uni-processor kernel. There are two parameters to revert to RHEL4 U3
behaviour: "nolapic" and "noapic". Just curious, what happends if "nolapic" is used?
apic=bigsmp does not change the panic. We see this error in the console:
APIC Verbosity level bigsmp not recognised use apic=verbose or apic=debug.
We will try nolapic shortly.
The nolapic option also did not help the panic.
I will boot into the x86_64 install CD and retrieve the dmidecode output.
Created attachment 130912 [details]
Output of dmidecode
Created attachment 131080 [details]
A proposed patch.
This a proposed patch that would automaticly supply the 'noapic' parameter when
the UP kernel would be executed on a UNISYS ES/7000 ONE box.
Try this kernel, pls:
without adding the 'noapic' paramter.
The kernel you supplied booted successfully.
Patch posted on internal reflector for review and submission in 2.6.9 kernel.
Just to be sure - is this the same kernel that will be used to boot from the
> Just to be sure - is this the same kernel that will be used to boot from the
> installation media?
Yes. Thought a bit updated. The 2.6.9-39 kernel has a three-line patch for a
kABI symbol breakage (nothing that affects the installation stage). The i386 UP
kernel is the one used the installation media.
committed in stream U4 build 39.2. A test kernel with this patch is available
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 the 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.