Bug 77604 - kernel 2.4.18-17.7.x decomprimation hangs
kernel 2.4.18-17.7.x decomprimation hangs
Status: CLOSED CURRENTRELEASE
Product: Red Hat Linux
Classification: Retired
Component: kernel (Show other bugs)
7.3
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Arjan van de Ven
Brian Brock
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2002-11-10 11:06 EST by Need Real Name
Modified: 2008-08-01 12:22 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2004-09-30 11:40:11 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)

  None (edit)
Description Need Real Name 2002-11-10 11:06:57 EST
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.01; Windows 98)

Description of problem:
kernel write uncompressing linux.... and then hangs with message
'ran out of input data'
  - System halted

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


How reproducible:
Always

Steps to Reproduce:
1.installed kernel kernel-2.4.18-17.7.x.i386.rpm by rpm -ivh
2.copy vmlinuz-2.4.18-17.7.x to dos partition or to fd0
3.boot from diskete in fd0 or loadlin vmlinuz from dos part.
	

Actual Results:  loading ...........
uncompresing linux ...

  ran out of input data

 - System halted


Expected Results:  normal linux dekompression a then ramdisk dekompression ..

Additional info:

If I use lilo or make bootdisk by mkbootdisk then kernel load is OK
I make bzImage from the kernel source kernel-source-2.4.18-17.7.x.i386.rpm and 
boot bzImage - the error is the same. In RH8.0
is the same problem in new kernel. Previous version of RH kernels
were OK. I download Linus kernel 2.4.19 and make bzImage and no error
appear. I reproduce this bug on P-100, PII-400, PIII-500
Comment 1 Bugzilla owner 2004-09-30 11:40:11 EDT
Thanks for the bug report. However, Red Hat no longer maintains this version of
the product. Please upgrade to the latest version and open a new bug if the problem
persists.

The Fedora Legacy project (http://fedoralegacy.org/) maintains some older releases, 
and if you believe this bug is interesting to them, please report the problem in
the bug tracker at: http://bugzilla.fedora.us/

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