From: Christophe Leroy <christophe.leroy@csgroup.eu>
To: Eddie James <eajames@linux.ibm.com>, linuxppc-dev@lists.ozlabs.org
Cc: linux-kernel@vger.kernel.org, benh@kernel.crashing.org,
paulus@samba.org, mpe@ellerman.id.au, npiggin@gmail.com,
miltonm@us.ibm.com
Subject: Re: PPC476 hangs during tlb flush after calling /init in crash kernel with linux 5.4+
Date: Tue, 27 Apr 2021 19:26:07 +0200 [thread overview]
Message-ID: <a24e9e0d-1d4f-506b-9303-4b995815d3c4@csgroup.eu> (raw)
In-Reply-To: <b973fa4768140021719e7cc3123ee873d8b2a3f1.camel@linux.ibm.com>
Hi Eddies,
Le 27/04/2021 à 19:03, Eddie James a écrit :
> Hi all,
>
> I'm having a problem in simulation and hardware where my PPC476
> processor stops executing instructions after callling /init. In my case
> this is a bash script. The code descends to flush the TLB, and
> somewhere in the loop in _tlbil_pid, the PC goes to
> InstructionTLBError47x but does not go any further. This only occurs in
> the crash kernel environment, which is using the same kernel,
> initramfs, and init script as the main kernel, which executed fine. I
> do not see this problem with linux 4.19 or 3.10. I do see it with 5.4
> and 5.10. I see a fair amount of refactoring in the PPC memory
> management area between 4.19 and 5.4. Can anyone point me in a
> direction to debug this further? My stack trace is below as I can run
> gdb in simulation.
Can you bisect to pin point the culprit commit ?
Assuming the problem is in arch/powerpc/ , you should get the result in approx 10 steps:
[root@po15610vm linux-powerpc]# git bisect start -- arch/powerpc/
[root@po15610vm linux-powerpc]# git bisect bad v5.4
[root@po15610vm linux-powerpc]# git bisect good v4.19
Bisecting: 964 revisions left to test after this (roughly 10 steps)
Christophe
next prev parent reply other threads:[~2021-04-27 17:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-27 17:03 PPC476 hangs during tlb flush after calling /init in crash kernel with linux 5.4+ Eddie James
2021-04-27 17:26 ` Christophe Leroy [this message]
2021-04-27 22:42 ` Eddie James
2021-04-28 6:08 ` Christophe Leroy
2021-04-28 13:56 ` Eddie James
2021-04-28 14:18 ` Eddie James
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=a24e9e0d-1d4f-506b-9303-4b995815d3c4@csgroup.eu \
--to=christophe.leroy@csgroup.eu \
--cc=benh@kernel.crashing.org \
--cc=eajames@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=miltonm@us.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
--cc=paulus@samba.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;
as well as URLs for NNTP newsgroup(s).