linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linuxppc-dev@lists.ozlabs.org
Subject: [Bug 216183] Kernel 5.19-rc4 boots ok with CONFIG_PPC_RADIX_MMU=y but fails to boot with CONFIG_PPC_HASH_MMU_NATIVE=y
Date: Mon, 11 Jul 2022 18:07:51 +0000	[thread overview]
Message-ID: <bug-216183-206035-qEl00WW4pz@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-216183-206035@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=216183

--- Comment #6 from Erhard F. (erhard_f@mailbox.org) ---
Created attachment 301395
  --> https://bugzilla.kernel.org/attachment.cgi?id=301395&action=edit
kernel .config (kernel 5.10.129, Talos II)

Tried some LTS kernels and with 5.10.x I got a .config working to boot the
Talos 2 with HASH MMU on my system.

Also I found out that selecting CONFIG_PAGE_POISONING=y in the working 5.10.x
config renders the kernel unbootable again. Though this seems a different
issue, as simply deselecting PAGE_POISONING in my 5.19-rc .config did not help.
So I opened bug #216238 for this issue.

5.11.x also boots with HASH MMU, but I got problems on 5.12.x again. 5.15 LTS
shows almost the same behaviour as described here for 5.19-rc.

At least I got a starting point now for a bisect.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2022-07-11 18:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-27 22:54 [Bug 216183] New: Kernel 5.19-rc4 boots ok with CONFIG_PPC_RADIX_MMU=y but fails to boot with CONFIG_PPC_HASH_MMU_NATIVE=y bugzilla-daemon
2022-06-27 22:56 ` [Bug 216183] " bugzilla-daemon
2022-06-29  6:35 ` bugzilla-daemon
2022-06-29 10:28 ` bugzilla-daemon
2022-07-10 10:29 ` bugzilla-daemon
2022-07-10 11:01 ` bugzilla-daemon
2022-07-11 18:07 ` bugzilla-daemon [this message]
2022-07-11 18:08 ` bugzilla-daemon
2022-07-14 12:57 ` [Bug 216183] [bisected] " bugzilla-daemon
2022-07-29  7:13 ` bugzilla-daemon
2022-07-30 13:15 ` 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-216183-206035-qEl00WW4pz@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 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).