Bug 450438 - System Hang in installation process.
Summary: System Hang in installation process.
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: anaconda
Version: 5.2
Hardware: ppc64
OS: Linux
low
low
Target Milestone: rc
: ---
Assignee: Anaconda Maintenance Team
QA Contact: Brock Organ
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-06-08 13:40 UTC by umed
Modified: 2011-06-29 14:32 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-12-11 21:36:32 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description umed 2008-06-08 13:40:00 UTC
Description of problem:
System Hang at "Select Language" screnn of installation process.

Version-Release number of selected component (if applicable):
RHEL5 server 5.2 ppc64

How reproducible:
Allways

Steps to Reproduce:
Install from RHEL52ppc64 Installation CD-ROM #1 or netboot
CD-ROM(/images/boot.iso in Installation CD-ROM).
  
Actual results:
Hang at "Select Language" screen.

Expected results:
Proceed installation process.

Additional info:
on IBM RS/6000 7044-170(44P-170).
CPU: POWER3 (630+) 400MHz * 1
Mem: 1GB

Comment 1 Chris Lumens 2008-08-26 21:29:57 UTC
The system is completely unresponsive?  Can you hit alt-f3 and alt-f4 and see if there are any obvious error messages?  Is this a reproducable error?  Thanks.

Comment 2 Denise Dumas 2008-12-11 21:36:32 UTC
The information we've requested above is required in order to review this
problem report further and diagnose or fix the issue if it is still present. 
Since it has been thirty days or more since we first requested additional
information, we're assuming the problem is either no longer present in the
current RHEL release, or that there is no longer any interest in tracking the
problem.

Setting status to "CLOSED: INSUFFICIENT_DATA".  If you still experience this
problem after updating to our latest RHEL release and can provide the
information previously requested, please feel free to reopen the bug report.

In addition, if you test this again to attach the needed information, it's
worth testing with the latest snapshot of 5.3 to verify whether it's still
broken there.


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