Joel Stanley

This work depends on - Enable CONFIG_KEXEC_FILE and CONFIG_LOCK_DOWN_KERNEL_FORCE_INTEGRITY - Bump kexec-lite to latest, for kexec_file_load support - Add support to petitboot for the `-s` option (https://patchwork.ozlabs.org/patch/1185931/)

https://github.com/open-power/op-build/pull/3408 will be updated to include the KEXEC_FILE option, however this must be done after petitboot and kexec-lite are updated. I have a kexec-lite change to fix the install path...

The kexec-lite change has been merged, and the version used by op-build bumped. I amended the kernel config PR to not set FORCE_INTEGRITY, and to set KEXEC_FILE. This means we...

This is the same as https://github.com/open-power/op-build/pull/4616, but for the master-p10 branch.

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 larger?

I like the idea of initialising nvram at build time. Even if the user has not chosen any defaults, this would save us time on the first boot where we...

``` --- a/import/tools/imageProcs/ipl_image_tool.C +++ b/import/tools/imageProcs/ipl_image_tool.C @@ -939,7 +939,7 @@ dumpHeader(void* i_image, image_section_type_t i_imageSectionType) printf(" %04d ", val); //Get service bit vector - val64 = (uint64_t*)(malloc(sizeof(8 * numOf64BitsSet))); + val64 =...

I put the fix up internally: https://rchgit01.rchland.ibm.com/gerrit1/129328

What distro is this? Which verison? Are you running it inside docker? Can you reproduce using the latest `master-next`?

I think it's related to the permissions your container has (or in this case, does not have). `fakeroot` uses `CAP_IPC_LOCK`, so try adding `--cap-add IPC_LOCK` to your `docker run` line.