Ilya Smirnov

ok to test

ok to test

ok to test

The BOOTKERNEL PNOR section is too big, so the PNOR build actually fails: ERROR: PnorUtils::checkSpaceConstraints: Image provided (/tmp/hostboot-jenkins.swg-devops/jenkins-agent/workspace/Hostboot/OpenPower/GHPR/build-p10-public-github-292/CONFIG/p10ebmc/OS/rhel7/build/op-build/output/host/powerpc64le-buildroot-linux-gnu/sysroot/openpower_pnor_scratch.EVEREST_XML/zImage.epapr) has size (33546240) which is greater than allocated space (16773120) for section=BOOTKERNEL....

> 33546240 = 16773120 * 2. I wonder what's going on there? > > On p10, we have no real pnor size constraints. Can we simply make the bootkernel partition...

Have been trying to recreate this with op-build level cf83faa745f652b7f9cb7e9e5e606ba2bcf7f2c7. Replacing PAYLOAD with the skiboot.lid.xz generated by the above build produces the following errors: ```45.99376|ISTEP 20. 1 - host_load_payload 46.01959|System...

I was trying to recreate on Witherspoon originally. I switched to Boston and saw the same error as you posted. Below are some findings.

--The PAYLOAD image in this case (skiboot.lid.xz) doesn't have any kind of secure header since even the fake header didn't get added to it during op-build. --The code path with...

After some discussion, we agreed on a fix that will check the partition header even in non-secure boot if the partition is marked with sha512 flag in the xml layout....

Changes were merged to hb master today.