Bug 196720

Summary: RHEL4 U4 i386 partner beta will not install on Dylan systems
Product: Red Hat Enterprise Linux 4 Reporter: Larry Newitt <lawrence.newitt>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED DUPLICATE QA Contact: Brian Brock <bbrock>
Severity: high Docs Contact:
Priority: medium    
Version: 4.0   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-06-26 19:15:02 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
serial-debug print none

Description Larry Newitt 2006-06-26 17:57:35 UTC 
Description of problem:
When attempting to install the RHEL4 U4 partner beta (i386) on a Unisys Dylan 
system, the uniprocessor installation kernel panics.  We found that the system 
will install when using the "noapic" parameter.

This is a regression from RHEL4 U3.  There were no kernel parameters rquired 
to install RHEL4 U3

Version-Release number of selected component (if applicable):
2.6.9-39.EL


How reproducible:
Can be reproduced anytime install is attempted without the nopic parameter.

Steps to Reproduce:
1. Boot from the RHEL4 U4 i386 partner beta CD1 and attempt to install.
2.
3.
  
Actual results:
Kernel panics.

Expected results:
Kernel does not panic.

Additional info:

This problem appears to be similar to the problem reported in Bugzilla Bug 
195002.  The patch that corrected that problem will not corrct this one 
because the dmidecode values are different for the Dylan systems.  If you want 
to make a similar patch for the Dylan systems we can provide the dmidecode 
product names for the Dylan systems.
Comment 1 Larry Newitt 2006-06-26 17:57:35 UTC 
Created attachment 131554 [details]
serial-debug print
Comment 2 Larry Newitt 2006-06-26 18:17:35 UTC 
This is duplicate of Bug 196723.  I get errors when I try to mark it as a 
duplicate.
Comment 3 Konrad Rzeszutek 2006-06-26 19:15:02 UTC 

*** This bug has been marked as a duplicate of 196723 ***