Hello,
Unfortunately, this patch set has made things quite a bit worse for me.
Appending mem=256G doesn't fix it either. in all cases, the system at
least gets past early boot and then I will probably get a panic and
eventual reboot, or occasionally it just locks up entirely.
Here's my very first attempt at booting the kernel where I didn't even
get a panic:
https://pastebin.com/a3TVZcVB
Here's another attempt where I get a panic:
https://pastebin.com/QsJjyC2v
Finally here's an attempt with mem=256G:
https://pastebin.com/swgLYie9
I don't know that these results are substantially different from each
other, but perhaps there's something helpful.
Sometimes (but not in any of the above), the host gets to the point that
systemd starts up, but ultimately it seems I got the same stacktrace.
At one point, I ended up with a CPU guarded 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, a35a3c6f6065, and the system boots.
This being due to 0034d395f89d confirmed.
https://lore.kernel.org/linuxppc-dev/20190917145702.9214-1-aneesh.ku...@linux.ibm.com
This series should help you.
-aneesh
