From: Richard Henderson <rth@twiddle.net>
To: Laszlo Ersek <lersek@redhat.com>,
Stefan Hajnoczi <stefanha@gmail.com>,
Dennis Luehring <dl.soluz@gmx.net>
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: Fri, 4 Nov 2016 15:08:12 -0600 [thread overview]
Message-ID: <b0eca829-4008-53b1-669f-54d82f98c657@twiddle.net> (raw)
In-Reply-To: <e798b637-073c-0256-4a3d-b1bd9a5341b1@redhat.com>
On 11/04/2016 01:40 PM, Laszlo Ersek wrote:
>> For the 4.7 kernel, we had enough ram to unpack the (large) initrd; with
>> the 4.8 kernel, we ran out. The 4.8 kernel did in fact print an
>> (obscure) error message to that effect, which had not been noticed.
>
> Was it
>
> Unpacking initramfs...
> Initramfs unpacking failed: junk in compressed archive
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.
r~
next prev parent reply other threads:[~2016-11-04 21:08 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 [this message]
2016-11-07 7:37 ` Dennis Luehring
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=b0eca829-4008-53b1-669f-54d82f98c657@twiddle.net \
--to=rth@twiddle.net \
--cc=dl.soluz@gmx.net \
--cc=lersek@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rjones@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).