From: Serge Belyshev <belyshev@depni.sinp.msu.ru>
To: Christophe Leroy <crhistophe.leroy@c-s.fr>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: BUG: crash in __tlb_remove_page_size with STRICT_KERNEL_RWX on BOOK3S_32
Date: Fri, 26 Apr 2019 07:54:06 +0300 [thread overview]
Message-ID: <87pnp9mknl.fsf@depni.sinp.msu.ru> (raw)
Hi! Commit 63b2bc61956 aka "powerpc/mm/32s: Use BATs for STRICT_KERNEL_RWX"
caused my old powerbook to crash under I/O. After "dd if=/dev/hda of=/null"
the crash happens in seconds. Reverting the commit helps, as well as
disabling STRICT_KERNEL_RWX. Unfortunately, I was unable to capture the oops
via the usb serial console, as it stuck right after the first "BUG: Unable to
handle kernel data access at 0xe0c29000" message. Oops screenshot:
http://aargh.no-ip.org/oops.jpg
next reply other threads:[~2019-04-26 5:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-26 4:54 Serge Belyshev [this message]
2019-04-26 7:27 ` BUG: crash in __tlb_remove_page_size with STRICT_KERNEL_RWX on BOOK3S_32 Christophe Leroy
2019-04-26 14:38 ` Serge Belyshev
2019-04-26 17:07 ` Segher Boessenkool
2019-04-27 9:05 ` christophe leroy
2019-04-29 7:31 ` Christophe Leroy
2019-04-29 8:20 ` Serge Belyshev
2019-04-29 8:49 ` 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=87pnp9mknl.fsf@depni.sinp.msu.ru \
--to=belyshev@depni.sinp.msu.ru \
--cc=crhistophe.leroy@c-s.fr \
--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).