Bug 65125

Summary:	Installer crashes when upgrading from skipjack to 7.3
Product:	[Retired] Red Hat Linux	Reporter:	Alex Deucher <agd5f>
Component:	anaconda	Assignee:	Michael Fulbright <msf>
Status:	CLOSED NOTABUG	QA Contact:	Brock Organ <borgan>
Severity:	high	Docs Contact:
Priority:	medium
Version:	7.3
Target Milestone:	---
Target Release:	---
Hardware:	i686
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2002-05-17 22:48:10 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:

Description Alex Deucher 2002-05-17 21:29:50 UTC

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:0.9.9) Gecko/20020311

Description of problem:
When upgrading from skipjack to 7.3 on an IBM thinkpad t20 using iso images on
the hard drive (checked MD5SUMS -everything is correct, also using text install)
or via FTP install, the installer will crash at the same point every time.  I
choose upgrade and it scans for files to be upgraded and then prepares to
upgrade and then as it's about to start loading rpms (glibc-common is the first
one listed) all of a sudden  something "signal 11", "sending kill signal"
appears on the screen followed by "disabling swap..." "unmounting
filesystems..." etc. till it finally gets to "you may safely reboot your system"
 VT4 shows the following repeated over and over:

<4>Error -3 while decompressing!
<4>c02a4684(260)->c1c8e000(4096)
<4>Error -3 while decompressing!
<4>c02a4684(-2216)->c25cb000(4096)

it repeats over and over with different numbers

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


How reproducible:
Always

Steps to Reproduce:
1.boot install program
2.choose upgrade
3.installer crashes
	

Actual Results:  installer crashes

Expected Results:  7.3 should have installed

Additional info:

iso from harddrive and FTP based install produced the exact same problem

Comment 1 Jeremy Katz 2002-05-17 22:08:53 UTC

How are you booting the install?  Sounds like you're missing the
'ramdisk_size=8192' parameter to the kernel.

Comment 2 Alex Deucher 2002-05-17 22:48:04 UTC

I was booting the installer from grub since I didn't have my floppy drive with
me.  I just tried the installer with 'ramdisk_size=8192' and it now works fine.

Thanks!