From: Christophe LEROY <christophe.leroy@c-s.fr>
To: David Gounaris <David.Gounaris@infinera.com>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Cc: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
Mathias Thore <Mathias.Thore@infinera.com>
Subject: Re: MPC8321 boot failure
Date: Wed, 17 Oct 2018 18:36:39 +0200 [thread overview]
Message-ID: <0cbfec90-0e58-e267-71ae-c5fc8a8e0640@c-s.fr> (raw)
In-Reply-To: <CY1PR10MB020424967E404E0B1BBE1E82EFFF0@CY1PR10MB0204.namprd10.prod.outlook.com>
Hi,
Yes I discovered the same issue today on MPC8321E, I plan to look at it
more closely tomorrow morning (Paris Time).
I think we are missing commit 8183d99f4a22c2abbc543847a588df3666ef0c0c ,
I didn't realise it when we applied the serie to 4.14,
patch_instruction() is called too early without that patch.
If you have opportunity to test now, you are welcome, otherwise I'll
test it tomorrow.
Christophe
Le 17/10/2018 à 17:18, David Gounaris a écrit :
> Hello, I got into troubles when I upgraded to Linux kernel 4.14.76 on
> boards with MPC8321.
>
>
> The symptom that I see is that the boot process gets cyclic, and no
> printouts are seen from the Linux kernel. It seems like it resets.
>
>
> When I revert the following commits it works again.
>
> af1a8101794dfea897290e057f61086dabfe6c91, powerpc/lib: fix book3s/32
> boot failure due to code patching
> 609fbeddb24c4035d24fc32d82dc08b30ae3dfc0, powerpc: Avoid code patching
> freed init sections
>
> Any ideas of how to continue?
>
> BR / David Gounaris
>
>
>
next parent reply other threads:[~2018-10-17 16:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CY1PR10MB020424967E404E0B1BBE1E82EFFF0@CY1PR10MB0204.namprd10.prod.outlook.com>
2018-10-17 16:36 ` Christophe LEROY [this message]
2018-10-18 4:49 ` MPC8321 boot failure Christophe LEROY
[not found] ` <CY1PR10MB0204796CBD711EBA4F5286A4EFF80@CY1PR10MB0204.namprd10.prod.outlook.com>
2018-10-18 9:34 ` SV: " gregkh
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=0cbfec90-0e58-e267-71ae-c5fc8a8e0640@c-s.fr \
--to=christophe.leroy@c-s.fr \
--cc=David.Gounaris@infinera.com \
--cc=Mathias.Thore@infinera.com \
--cc=gregkh@linuxfoundation.org \
--cc=linuxppc-dev@lists.ozlabs.org \
/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