Bug 75818 - Installer crashes when loading packages
Installer crashes when loading packages
Status: CLOSED NOTABUG
Product: Red Hat Linux
Classification: Retired
Component: anaconda (Show other bugs)
7.2
i586 Linux
medium Severity high
: ---
: ---
Assigned To: Michael Fulbright
Brock Organ
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2002-10-12 21:34 EDT by Need Real Name
Modified: 2007-04-18 12:47 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2002-10-12 21:38:33 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
dump file generated by installer (60.02 KB, text/plain)
2002-10-12 21:38 EDT, Need Real Name
no flags Details

  None (edit)
Description Need Real Name 2002-10-12 21:34:37 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.0; Windows 98; DigExt)

Description of problem:
when trying to install Red Hat 7.2 I get over 1 gig into the install and it 
crashes-says to report the bug.

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


How reproducible:
Always

Steps to Reproduce:
1.boot from install disk- install all packages- wait
2.
3.
	

Expected Results:  install should have completed

Additional info:
Comment 1 Need Real Name 2002-10-12 21:38:27 EDT
Created attachment 80164 [details]
dump file generated by installer
Comment 2 Jeremy Katz 2002-10-14 05:27:58 EDT
These errors in the anaconda dump

<4>hdb: irq timeout: status=0xd0 { Busy }
<4>hdb: ATAPI reset complete
<4>hdb: irq timeout: status=0xd0 { Busy }
<4>hdb: ATAPI reset complete

implies that there were errors in reading from the CD that were not correctable.
 Please verify the integrity of the media.  Newer releases of Red Hat Linux have
additional code to try to work around these cases.
Comment 3 Need Real Name 2002-10-15 01:08:51 EDT
installed in text mode...worked like a champ!

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