From: Michael Ellerman <mpe@ellerman.id.au>
To: Abdul Haleem <abdhalee@linux.vnet.ibm.com>,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
linux-input@vger.kernel.org, Jiri Kosina <jikos@kernel.org>,
Benjamin Tissoires <benjamin.tissoires@redhat.com>,
sachinp <sachinp@linux.vnet.ibm.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Rob Landley <rob@landley.net>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [linux-next] PPC Lpar fail to boot with error hid: module verification failed: signature and/or required key missing - tainting kernel
Date: Thu, 25 May 2017 23:02:06 +1000 [thread overview]
Message-ID: <8760gp9jjl.fsf@concordia.ellerman.id.au> (raw)
In-Reply-To: <1495700957.9020.43.camel@abdul.in.ibm.com>
Abdul Haleem <abdhalee@linux.vnet.ibm.com> writes:
> Hi,
>
> Test : boot
> Machine : Power 8 PowerVM LPAR
> Kernel version : 4.12.0-rc2-next-20170524
> Toolchain : gcc version 5.2.1
> Config : attached
>
> next-20170517 was last good version where we did not see the failure.
> from next-20170519 to today's next-20170524, we see the problem
> everyday.
>
> Kernels fails to boot on PowerVM LPAR with these errors;
>
> Freeing unused kernel memory: 4416K
> This architecture does not have kernel memory protection.
> Loading, please wait...
> mount: mounting udev on /dev failed: Device or resource busy
> W: devtmpfs not available, falling back to tmpfs for /dev
It'll be:
ee35011fd032 ("initramfs: make initramfs honor CONFIG_DEVTMPFS_MOUNT")
cheers
next prev parent reply other threads:[~2017-05-25 13:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1495700957.9020.43.camel@abdul.in.ibm.com>
2017-05-25 9:08 ` Jiri Kosina
2017-05-25 13:02 ` Michael Ellerman [this message]
2017-05-25 21:24 ` Stephen Rothwell
2017-05-26 6:24 ` Rob Landley
2017-05-29 5:06 ` Michael Ellerman
2017-09-13 23:51 ` [PATCH v3] Make initramfs honor CONFIG_DEVTMPFS_MOUNT Rob Landley
2017-09-14 9:17 ` Christophe LEROY
2017-09-17 4:03 ` Rob Landley
2017-09-17 13:51 ` Henrique de Moraes Holschuh
2017-09-20 3:29 ` Rob Landley
2017-09-21 10:13 ` Michael Ellerman
2017-09-14 17:45 ` Greg KH
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=8760gp9jjl.fsf@concordia.ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=abdhalee@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=benjamin.tissoires@redhat.com \
--cc=jikos@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=rob@landley.net \
--cc=sachinp@linux.vnet.ibm.com \
--cc=sfr@canb.auug.org.au \
/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
all inboxes | Powered by JetHome®