Bug 196720 - RHEL4 U4 i386 partner beta will not install on Dylan systems
Summary: RHEL4 U4 i386 partner beta will not install on Dylan systems
Status: CLOSED DUPLICATE of bug 196723
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: kernel
Version: 4.0
Hardware: i386
OS: Linux
Target Milestone: ---
: ---
Assignee: Kernel Maintainer List
QA Contact: Brian Brock
Depends On:
TreeView+ depends on / blocked
Reported: 2006-06-26 17:57 UTC by Larry Newitt
Modified: 2007-11-30 22:07 UTC (History)
0 users

Clone Of:
Last Closed: 2006-06-26 19:15:02 UTC

Attachments (Terms of Use)
serial-debug print (10.65 KB, text/plain)
2006-06-26 17:57 UTC, Larry Newitt
no flags Details

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):

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.
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 

Comment 3 Konrad Rzeszutek 2006-06-26 19:15:02 UTC

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

Note You need to log in before you can comment on or make changes to this bug.