linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Pali Rohár" <pali@kernel.org>
To: Christophe Leroy <christophe.leroy@csgroup.eu>,
	Michael Ellerman <mpe@ellerman.id.au>,
	linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Regression: Linux v5.15+ does not boot on Freescale P2020
Date: Fri, 22 Jul 2022 11:09:29 +0200	[thread overview]
Message-ID: <20220722090929.mwhmxxdd7yioxqpz@pali> (raw)

Hello!

Trying to boot mainline Linux kernel v5.15+, including current version
from master branch, on Freescale P2020 does not work. Kernel does not
print anything to serial console, seems that it does not work and after
timeout watchdog reset the board.

I run git bisect and it found following commit:

9401f4e46cf6965e23738f70e149172344a01eef is the first bad commit
commit 9401f4e46cf6965e23738f70e149172344a01eef
Author: Christophe Leroy <christophe.leroy@csgroup.eu>
Date:   Tue Mar 2 08:48:11 2021 +0000

    powerpc: Use lwarx/ldarx directly instead of PPC_LWARX/LDARX macros

    Force the eh flag at 0 on PPC32.

    Signed-off-by: Christophe Leroy <christophe.leroy@csgroup.eu>
    Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
    Link: https://lore.kernel.org/r/1fc81f07cabebb875b963e295408cc3dd38c8d85.1614674882.git.christophe.leroy@csgroup.eu

:040000 040000 fe6747e45736dfcba74914a9445e5f70f5120600 96358d08b65d3200928a973efb5b969b3d45f2b0 M      arch


If I revert this commit then kernel boots correctly. It also boots fine
if I revert this commit on top of master branch.

Freescale P2020 has two 32-bit e500 powerpc cores.

Any idea why above commit is causing crash of the kernel? And why it is
needed? Could eh flag set to 0 cause deadlock?

I have looked into e500 Reference Manual for lwarx instruction (page 562)
https://www.nxp.com/files-static/32bit/doc/ref_manual/EREF_RM.pdf and
both 0 and 1 values for EH flag should be supported.

             reply	other threads:[~2022-07-22  9:10 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-22  9:09 Pali Rohár [this message]
2022-07-23 14:42 ` Regression: Linux v5.15+ does not boot on Freescale P2020 Christophe Leroy
2022-07-23 15:07   ` Pali Rohár
2022-07-25  8:20     ` Michael Ellerman
2022-07-25 12:52       ` Pali Rohár
2022-07-25 16:20         ` Christophe Leroy
2022-07-25 20:10           ` Pali Rohár
2022-07-25 21:54             ` Segher Boessenkool
2022-07-26  8:34               ` Pali Rohár
2022-07-26  9:02                 ` Arnd Bergmann
2022-07-26 13:44                   ` Segher Boessenkool
2022-07-26 14:01                     ` Pali Rohár
2022-07-26 14:14                       ` Segher Boessenkool
2022-08-02  6:47                     ` Christophe Leroy
2022-08-02  8:28                       ` Arnd Bergmann
2022-07-26 14:30                 ` Christophe Leroy

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=20220722090929.mwhmxxdd7yioxqpz@pali \
    --to=pali@kernel.org \
    --cc=christophe.leroy@csgroup.eu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mpe@ellerman.id.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).