From: bugzilla-daemon@kernel.org
To: linuxppc-dev@lists.ozlabs.org
Subject: [Bug 216238] New: Kernel 5.10.129 fails to boot on a Talos 2 with HASH MMU (PPC_RADIX_MMU not set) with CONFIG_PAGE_POISONING=y
Date: Mon, 11 Jul 2022 17:56:06 +0000 [thread overview]
Message-ID: <bug-216238-206035@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=216238
Bug ID: 216238
Summary: Kernel 5.10.129 fails to boot on a Talos 2 with HASH
MMU (PPC_RADIX_MMU not set) with
CONFIG_PAGE_POISONING=y
Product: Platform Specific/Hardware
Version: 2.5
Kernel Version: 5.10.129
Hardware: PPC-64
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: PPC-64
Assignee: platform_ppc-64@kernel-bugs.osdl.org
Reporter: erhard_f@mailbox.org
Regression: No
Created attachment 301393
--> https://bugzilla.kernel.org/attachment.cgi?id=301393&action=edit
kernel dmesg (kernel 5.19-rc4, without PAGE_POISONING, Talos II)
Found that out during investigating bug #216183 closer.
On kernel 5.10.x LTS the Talos 2 boots fine with HASH MMU used. But the same
kernel .config fails to boot when CONFIG_PAGE_POISONING=y is set and used. I
get no netconsole output then, only a reboot after a while.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2022-07-11 17:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-11 17:56 bugzilla-daemon [this message]
2022-07-11 17:57 ` [Bug 216238] Kernel 5.10.129 fails to boot on a Talos 2 with HASH MMU (PPC_RADIX_MMU not set) with CONFIG_PAGE_POISONING=y bugzilla-daemon
2022-07-11 18:00 ` bugzilla-daemon
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=bug-216238-206035@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.