From: Doug Crawford <doug.crawford@intelight-its.com>
To: linuxppc-dev@lists.ozlabs.org
Subject: Freeze on ppc32 MPC8248 board with 5.2 kernel
Date: Thu, 25 Jul 2019 15:30:26 -0700 [thread overview]
Message-ID: <CAESxVDiyXu+=6+YmLej3K=i55h3=Z9JLA8JgrDn3fEQGUuSq7Q@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 555 bytes --]
We have a ppc32 MPC8248 board that is working perfectly with the 4.19
kernel.
We have noticed two issues with the 5.2 kernel:
1) If the new CONFIG_PPC_KUAP (kernel userspace access protection) is
enabled the kernel freezes right after initializing all the drivers and
just before starting /sbin/init.
2) If CONFIG_PPC_KUAP is disabled the system starts up, but any user space
program will hang indefinitely after calling the GCC atomic
"__sync_bool_compare_and_swap". This happens when nginx starts. The same
nginx binary works fine on a 4.19 kernel.
[-- Attachment #2: Type: text/html, Size: 647 bytes --]
next reply other threads:[~2019-07-25 22:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-25 22:30 Doug Crawford [this message]
2019-08-13 4:41 ` Freeze on ppc32 MPC8248 board with 5.2 kernel 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='CAESxVDiyXu+=6+YmLej3K=i55h3=Z9JLA8JgrDn3fEQGUuSq7Q@mail.gmail.com' \
--to=doug.crawford@intelight-its.com \
--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;
as well as URLs for NNTP newsgroup(s).