From: Dennis Luehring <dl.soluz@gmx.net>
To: Richard Henderson <rth@twiddle.net>,
Laszlo Ersek <lersek@redhat.com>,
Stefan Hajnoczi <stefanha@gmail.com>
Cc: qemu-devel <qemu-devel@nongnu.org>,
"Richard W.M. Jones" <rjones@redhat.com>
Subject: Re: [Qemu-devel] alpha platform is missing files after initrd load
Date: Mon, 7 Nov 2016 08:37:32 +0100 [thread overview]
Message-ID: <238afa75-0263-9314-caec-05ffeb46fe6e@gmx.net> (raw)
In-Reply-To: <b0eca829-4008-53b1-669f-54d82f98c657@twiddle.net>
Am 04.11.2016 um 22:08 schrieb Richard Henderson:
> No, it was less specific than that. Something like "unpacking failed: error".
>
>> >And, apparently, it used to be handled with a panic() call, but then that
>> >was deemed "policy", and downgraded to a KERN_EMERG message:
> Ouch. A silly decision, but definitely an uphill fight to get it changed.
using a big(~370MB) initrd.cpio with not enough ram (1GB) in qemu i get
this kernel message
"Initramfs unpacking failed: write error"
using a small(~14MB) initrd.cpio with just a staticaly linked c based
init for the kernel also with 1GB ram (more then enough) gives me this
kernel message:
"Initramfs unpacking failed: junk in compressed archive"
and i currently can't say if only the first is evil or both
both cpios created with "find . | cpio -H newc -o initrd.cpio"
next prev parent reply other threads:[~2016-11-07 7:37 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-20 10:45 [Qemu-devel] alpha platform is missing files after initrd load Dennis Luehring
2016-11-04 11:08 ` Stefan Hajnoczi
2016-11-04 16:37 ` Richard Henderson
2016-11-04 19:40 ` Laszlo Ersek
2016-11-04 21:08 ` Richard Henderson
2016-11-07 7:37 ` Dennis Luehring [this message]
2016-11-07 14:12 ` Laszlo Ersek
2016-11-07 14:38 ` Dennis Luehring
2016-11-07 15:56 ` Laszlo Ersek
2016-11-07 16:11 ` Dennis Luehring
2016-11-07 17:21 ` Laszlo Ersek
2016-11-09 6:34 ` Dennis Luehring
2016-11-11 6:49 ` Dennis Luehring
2016-11-07 7:35 ` Dennis Luehring
2016-11-07 14:15 ` Laszlo Ersek
2016-11-07 14:18 ` Laszlo Ersek
2016-11-07 15:16 ` Dennis Luehring
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=238afa75-0263-9314-caec-05ffeb46fe6e@gmx.net \
--to=dl.soluz@gmx.net \
--cc=lersek@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rjones@redhat.com \
--cc=rth@twiddle.net \
--cc=stefanha@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.