Red Hat Bugzilla – Bug 444132
Kernel panic - Unable to mount rootfs
Last modified: 2008-04-28 09:11:46 EDT
Description of problem:
automated test cases for ia64 fail due to the following error:
RAMDISK: Compressed image found at block 0
RAMDISK: incomplete write (-28 != 32768) 12582912
VFS: Cannot open root device "<NULL>" or unknown-block(8,2)
Please append a correct "root=" boot option
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(8,2)
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Boot the installer (need more details here, will investigate how out test
cases run the installer)
* prior to that I have RHEL4-U6 on one machine and 5.2 on another
* seeing this on different machines/different test cases (although they should
start the install in the same manner)
* see full console log attached
Created attachment 303767 [details]
full log from rebooting the system to kernel panic
Sounds like HP box, adding Doug...
Is it able to be reproduced on other ia64 boxes?
I thought we determined this was a problem with KATE and not an OS bug.
However, since I can't see the private comments there is more to this than I
know. Could someone enlighten me?
Sorry for the noise once again:
This commit didn't make it into the 88-1 build of anaconda. This is 2/2 patch
that's needed to fix bug #443373 (it is changing the default value for
ramdisk_size in the boot images). According to jgranado that's why we've been
seeing the kernel panic with 0424.0 tree.
the bug was reopened due to seeing the same behavior with Xen but comment #10
explains it all.