From: "H. Peter Anvin" <hpa@zytor.com>
To: Yinghai Lu <yhlu.kernel@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Ingo Molnar <mingo@elte.hu>, Christoph Lameter <clameter@sgi.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: /initrd.img
Date: Tue, 12 Feb 2008 09:53:58 -0800 [thread overview]
Message-ID: <47B1DD36.6090401@zytor.com> (raw)
In-Reply-To: <86802c440802120328i2e60ba3brbe7fdec87d4cce4a@mail.gmail.com>
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
next prev parent reply other threads:[~2008-02-12 18:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-12 11:28 /initrd.img Yinghai Lu
2008-02-12 17:53 ` H. Peter Anvin [this message]
2008-02-13 5:55 ` /initrd.img Yinghai Lu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=47B1DD36.6090401@zytor.com \
--to=hpa@zytor.com \
--cc=akpm@linux-foundation.org \
--cc=clameter@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=yhlu.kernel@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.