On Tue, Jan 21, 2014 at 12:55:53PM -0500, Boris Ostrovsky wrote:
> cat $(AMD_UCODE_PATH)/* >
> ucode_initrd/kernel/x86/microcode/AuthenticAMD.bin
> (cd ucode_initrd;find . | cpio -o -H newc >
> ../$(DISTDIR)/common/ucode_initrd.cpio)
> ...
> cat $(DISTDIR)/common/ucode_initrd.cpio \
> $(DISTDIR)/common/_initramfs.cpio.gz > \
> $(DISTDIR)/common/initramfs.cpio.gz
>
> and as I just discovered, with a little twist: apparently
> AMD_UCODE_PATH points to Intel microcode.
LOL!
@hpa: in case you were wondering whether Intel ucode works on AMD - it
doesn't! :-)
> So we clearly screwed up on our end but I'd think that we shouldn't
> crash when this happens.
Yes, we shouldn't. I'll try to reproduce it here.
Thanks.
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
