Messages in this thread | | | Date | Tue, 12 Feb 2008 09:53:58 -0800 | From | "H. Peter Anvin" <> | Subject | Re: /initrd.img |
| |
Yinghai Lu wrote: > any limitation about size of > /initrd.img that saved by populate_rootfs ? > > i got > > RAMDISK: Compressed image found at block 0 > RAMDISK: incomplete write (-28 != 2048) 134217728 > crc error > VFS: Mounted root (ext2 filesystem). > Freeing unused kernel memory: 388k freed > init_special_inode: bogus i_mode (177777) > Warning: unable to open an initial console. > init_special_inode: bogus i_mode (177777) > init_special_inode: bogus i_mode (177777) > Kernel panic - not syncing: No init found. Try passing init= option to kernel. > > before that > checking if image is initramfs... it isn't (no cpio magic); looks like an initrd > Freeing initrd memory: 25735k freed. > > that only happen one system (64G RAM) and SLUB. > > if using SLAB, it works well. > > somewhere the ramdisk or /initrd.img get corrupted.. >
Assuming a 64-bit system, that's *supposed* to work. Doesn't mean anything that weird has been tested.
It could be a SLUB bug, or it could be memory not being properly defended.
-hpa
| |