From: Cameron Berkenpas <cam@neo-zeon.de>
To: "Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: bugzilla-daemon@bugzilla.kernel.org, linuxppc-dev@lists.ozlabs.org
Subject: Re: [Bug 204789] New: Boot failure with more than 256G of memory
Date: Fri, 13 Sep 2019 10:28:26 -0700 [thread overview]
Message-ID: <e45ab4aa-202f-b98a-e9cf-8945ea9391a8@neo-zeon.de> (raw)
In-Reply-To: <28de8cb6-3213-56aa-8ed6-fbdb109ab3df@linux.ibm.com>
Running against the kernel I built against 0034d395f89d and the problem
is still there.
However, running against the kernel I built against the previous commit,
a35a3c6f6065, and the system boots.
This being due to 0034d395f89d confirmed.
Thanks!
On 9/13/19 9:13 AM, Aneesh Kumar K.V wrote:
> On 9/13/19 8:35 PM, Cameron Berkenpas wrote:
>> Yep, the box comes up now, but with 256G memory as expected.
>>
>> I'll get back to you on when I'll be able to bisect.
>>
>> Thanks!
>
> I am sure this is due to
>
> commit: 0034d395f89d ("powerpc/mm/hash64: Map all the kernel regions
> in the same 0xc range"),
>
> We reduced the linear map range for 4K page size to 16TB there.
>
>
> -aneesh
next prev parent reply other threads:[~2019-09-13 17:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-204789-27@https.bugzilla.kernel.org/>
2019-09-11 14:31 ` [Bug 204789] New: Boot failure with more than 256G of memory Andrew Morton
2019-09-11 15:34 ` Cameron Berkenpas
2019-09-13 4:53 ` Aneesh Kumar K.V
2019-09-13 14:21 ` Aneesh Kumar K.V
2019-09-13 15:05 ` Cameron Berkenpas
2019-09-13 16:13 ` Aneesh Kumar K.V
2019-09-13 17:28 ` Cameron Berkenpas [this message]
2019-09-18 3:15 ` Aneesh Kumar K.V
2019-09-18 15:38 ` Cameron Berkenpas
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=e45ab4aa-202f-b98a-e9cf-8945ea9391a8@neo-zeon.de \
--to=cam@neo-zeon.de \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.ibm.com \
--cc=bugzilla-daemon@bugzilla.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).