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
