From: Abdul Haleem <abdhalee@linux.vnet.ibm.com>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-next <linux-next@vger.kernel.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
sachinp <sachinp@linux.vnet.ibm.com>,
benh@kernel.crashing.org, mikey@neuling.org
Subject: Re: [linux-next][bisected 1c0eaf0f] Today's next kernel fails to boot on ppc bare-metal
Date: Mon, 17 Jul 2017 11:37:06 +0530 [thread overview]
Message-ID: <1500271626.27017.3.camel@abdul.in.ibm.com> (raw)
In-Reply-To: <87mv8324p8.fsf@concordia.ellerman.id.au>
On Mon, 2017-07-17 at 12:10 +1000, Michael Ellerman wrote:
> Hi Abdul,
>
> Thanks for the bug report.
>
> Abdul Haleem <abdhalee@linux.vnet.ibm.com> writes:
> > Hi
> >
> > Today's linux-next fails to boot on ppc bare-metal
> >
> > Test: Boot
> > Machine: Power 8 bare-metal
> > kernel: 4.12.0-next-20170713
> > gcc: version 4.8.5
> > config : Tul-NV-config attached.
>
> [swearing redacted]
>
> Does this help?
Yes, it fixes the boot issue. Thanks for the fix.
With below patch, I was able to successfully boot
4.13.0-rc1-next-20170717 kernel on ppc bare-metal
Reported-and-tested-by: Abdul Haleem <abdhalee@linux.vnet.ibm.com>
>
> diff --git a/arch/powerpc/platforms/powernv/opal.c b/arch/powerpc/platforms/powernv/opal.c
> index 9b87abb178f0..cad6b57ce494 100644
> --- a/arch/powerpc/platforms/powernv/opal.c
> +++ b/arch/powerpc/platforms/powernv/opal.c
> @@ -78,7 +78,7 @@ void opal_configure_cores(void)
> * ie. Host hash supports hash guests
> * Host radix supports hash/radix guests
> */
> - if (cpu_has_feature(CPU_FTR_ARCH_300)) {
> + if (early_cpu_has_feature(CPU_FTR_ARCH_300)) {
> reinit_flags |= OPAL_REINIT_CPUS_MMU_HASH;
> if (early_radix_enabled())
> reinit_flags |= OPAL_REINIT_CPUS_MMU_RADIX;
>
--
Regard's
Abdul Haleem
IBM Linux Technology Centre
prev parent reply other threads:[~2017-07-17 6:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-14 9:42 [linux-next][bisected 1c0eaf0f] Today's next kernel fails to boot on ppc bare-metal Abdul Haleem
2017-07-17 2:10 ` Michael Ellerman
2017-07-17 6:07 ` Abdul Haleem [this message]
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=1500271626.27017.3.camel@abdul.in.ibm.com \
--to=abdhalee@linux.vnet.ibm.com \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mikey@neuling.org \
--cc=mpe@ellerman.id.au \
--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;
as well as URLs for NNTP newsgroup(s).