Hello,
Regression set to "yes". Not sure how I missed that. :)
Will report future PPC issues to that I come across to this list as well.
Thanks!
-Cameron
On 9/11/19 7:31 AM, Andrew Morton wrote:
(switched to email. Please respond via emailed reply-to-all, not via the
bugzilla web interface)
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!
On 9/13/19 7:21 AM, Aneesh Kumar K.V wrote:
Aneesh Kumar K.V writes:
Andrew Morton writes:
(switched to email. Please respond via emailed reply-to-all, not via the
b
:
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 0x
out, but it was simple to
recover.
-Cameron
On 9/17/19 8:15 PM, Aneesh Kumar K.V wrote:
On 9/13/19 10:58 PM, Cameron Berkenpas wrote:
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,
ear and vmemmap range is of 64TB size each and is mapped respectively
using 0xc and 0xf top nibble.
Fixes: 0034d395f89d ("powerpc/mm/hash64: Map all the kernel regions in the same 0xc
range")
Reported-by: Cameron Berkenpas
Signed-off-by: Aneesh Kumar K.V
---
arch/powerpc/include/asm/
