From: han_mao at c-sky.com <han_mao@c-sky.com>
To: buildroot@busybox.net
Subject: [Buildroot] qemu_riscv64_virt can't boot up with large cpio initial RAM filesystem
Date: Wed, 9 Oct 2019 15:46:09 +0800 [thread overview]
Message-ID: <2019100915460909560126@c-sky.com> (raw)
Hi,
I've got some troble when I tried to use init ram fs on riscv64 virt.
The default ext2 fs works fine. If I use cpio and init ram fs to
replace that. The kernel can boot up with small ram fs, but
a big ram fs(>100M) doesn't work.
kernel got into panic and report "junk within compressed archive"
static long __init flush_buffer(void *bufv, unsigned long len)
{
char *buf = (char *) bufv;
long written;
long origLen = len;
if (message)
return -1;
while ((written = write_buffer(buf, len)) < len && !message) {
char c = buf[written];
if (c == '0') {
buf += written;
len -= written;
state = Start;
} else if (c == 0) {
buf += written;
len -= written;
state = Reset;
} else
error("junk within compressed archive");
This check failed.
Someone knows how to solve this problem?
Thanks,
Mao Han
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20191009/f88a9d62/attachment.html>
next reply other threads:[~2019-10-09 7:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-09 7:46 han_mao at c-sky.com [this message]
2019-10-09 22:59 ` [Buildroot] qemu_riscv64_virt can't boot up with large cpio initial RAM filesystem Arnout Vandecappelle
2019-10-10 1:41 ` Mao Han
[not found] <2019100915262320629523@c-sky.com>
2019-10-15 0:53 ` Alistair Francis
2019-10-16 10:48 ` Mao Han
2019-10-17 17:30 ` Alistair Francis
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=2019100915460909560126@c-sky.com \
--to=han_mao@c-sky.com \
--cc=buildroot@busybox.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox