-
Notifications
You must be signed in to change notification settings - Fork 93
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rebuilding Kernel 4.15.0-23 Fails under certain conditions #196
Comments
Fixed in the latest build -- this failure happens due to microcode updates with the 'early' setting, which is the new default for L1FT and other mitigations. Thanks for your excellent report -- it was invaluable in tracking the issue down. https://github.com/kamilion/customizer/releases/tag/4.2.0-0 |
And I get that error too running 18.04 ... Starting Customizer with ('/usr/bin/python3', '/usr/sbin/customizer-gui')...
|
Attempting to rebuild kernel 4.15.0-23 fails, as was described in issue #191, however upon entering the chroot and purging the kernel image, then reinstalling the same kernel, the build will succeed. Although I haven't been able to determine a cause for this, I've put all the information I have below concerning the events and conditions, so it should be repeatable. I hope that this can be of some help.
Failing to build
Method:
Error Message
running file on initrd.img-4.15.0-23-generic inside chroot returns:
/boot/initrd.img-4.15.0-23-generic: ASCII cpio archive (SVR4 with no CRC)
Successful build
Method:
running file on initrd.img-4.15.0-23-generic inside chroot returns:
initrd.img-4.15.0-23-generic: gzip compressed data, last modified: Tue Jun 19 15:14:53 2018, from Unix
Extra Info:
Customizer version: 4.1.5
Host OS: Ubuntu 18.04 LTS
Host Kernel: 4.15.0-23-generic
Image being remastered: ubuntu-mate-18.04-desktop-amd64.iso
Image original kernel: 4.15.0.20-generic
image kernel after update: 4.15.0.23-generic
It should be noted that this issue does not occur with the 4.15.0-20 or 4.15.0.22 generic kernel.
Thanks,
Will
The text was updated successfully, but these errors were encountered: