Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 160359 - Kernel compiled with CONFIG_BLK_DEV_RAM_SIZE too small
Summary: Kernel compiled with CONFIG_BLK_DEV_RAM_SIZE too small
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: kernel
Version: 4.0
Hardware: powerpc
OS: Linux
Target Milestone: ---
: ---
Assignee: Jason Baron
QA Contact: Brian Brock
Depends On:
TreeView+ depends on / blocked
Reported: 2005-06-14 17:28 UTC by David Huffman
Modified: 2013-03-06 05:58 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Last Closed: 2012-06-20 13:33:36 UTC
Target Upstream Version:

Attachments (Terms of Use)

Description David Huffman 2005-06-14 17:28:17 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.6) Gecko/20050302 Firefox/1.0.1 Fedora/1.0.1-1.3.2

Description of problem:
In order to provide a way to concatenate a kernel and initrd image into a single 32-bit binary for network boot, the ramdisk_size for the kernel must be large enough for the initrd. I am recommended increasing the ramdisk size above 65536 to allow for larger initrd images that are at least 65536.

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

How reproducible:

Steps to Reproduce:
1. Create a concatenated kernel + initrd image using distro supplied kernel.

Actual Results:  Received kernel panic while loading initrd image.
errors "attempting to access beyond end of device"

Additional info:

Using yaboot to network boot rs6K systems in not a working solution because it does not support network boot of kernel images larger than 6MB. This solution would allow the ability to create the zImage.initrd images needed to network boot a system without the yaboot bootloader.

Comment 1 Jason Baron 2005-06-20 19:53:17 UTC
you can pass kernel command line:'ramdisk_size=#', where # is the size of the
ramdisk in K. Does that solve this issue?

Comment 2 David Huffman 2005-06-21 15:52:03 UTC
(In reply to comment #1) 
> you can pass kernel command line:'ramdisk_size=#', where # is the size of 
> ramdisk in K. Does that solve this issue? 
Not really. When using a kerenl+initrd (zImage.initrd) I boot directly from 
openfirmware without a bootloader, so I cannot pass that info. I can pass 
ramdisk_size= at the OF prompt, but that would be required at every boot. I 
would assume most admins would rather configure the IPL within SMS rather than 
boot using OF commands. Is there a particular reason the ramdisk size is so 

Comment 3 Arjan van de Ven 2005-08-19 18:23:34 UTC
Note that we don't use ramdisks for initrd's anymore, but initramfs... that has
no limit at all...

Comment 5 Jiri Pallich 2012-06-20 13:33:36 UTC
Thank you for submitting this issue for consideration in Red Hat Enterprise Linux. The release for which you requested us to review is now End of Life. 
Please See

If you would like Red Hat to re-consider your feature request for an active release, please re-open the request via appropriate support channels and provide additional supporting details about the importance of this issue.

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