Bug 58687 - Installer crashes at random points in the installation process
Summary: Installer crashes at random points in the installation process
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: anaconda
Version: 7.2
Hardware: athlon
OS: Linux
medium
high
Target Milestone: ---
Assignee: Jeremy Katz
QA Contact: Brock Organ
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-01-23 01:38 UTC by mthayer
Modified: 2007-04-18 16:39 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2006-02-21 18:48:22 UTC
Embargoed:


Attachments (Terms of Use)

Description mthayer 2002-01-23 01:38:51 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows 98; AT&T WNS5.0)

Description of problem:
This is one of several errors that occur with every attempt at installation.  
The installation process terminates abnormally and with different errors at 
random points during the instatllation process, but more frequently during the 
package installation phase.

Version-Release number of selected component (if applicable):


How reproducible:
Sometimes

Steps to Reproduce:
1.Just run through the default workstation installation process.
2.
3.
	

Actual Results:  Installer aborts, shuts down, and I have to reboot the system.

Expected Results:  Would prefer a clean install.

Additional info:

Running dual Athlon 1.2Ghz cpu's on a Tyan Tiger MP motherboard.

Comment 1 Michael Fulbright 2002-01-23 16:18:01 UTC
Just a few questions so I can better help you:

Do you have MP rated processors in the board? This can cause problems if not?

Could you try an install with 'noathlon' on the install boot commandline?  This
is known to help with some Athlon problems.

Could you attach any errors messages you see when the install fails?

Thank You.

Comment 2 Michael Fulbright 2002-02-27 19:50:51 UTC
Closing due to inactivity, please reopen this report if you continue to have
problems.

Comment 3 Red Hat Bugzilla 2006-02-21 18:48:22 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.


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