in Kubuntu Bionic oem install, after installer finishes, it won't shut down to allow reboot

[Valorie Zimmerman]

it flashes a message about updating microcode, will not start a virtual term, and must be shut down with the power button.

Otherwise the install seems successful, although I've not completed the second reboot called for yet.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubiquity 18.04.9
ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
Uname: Linux 4.15.0-15-generic x86_64
ApportVersion: 2.20.9-0ubuntu6
Architecture: amd64
CurrentDesktop: KDE
Date: Sun Apr 22 00:20:13 2018
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/kubuntu.seed boot=casper only-ubiquity quiet splash oem-config/enable=true ---
InstallationDate: Installed on 2018-04-22 (0 days ago)
InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180421.1)
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

[Ubuntu QA Website (ubuntuqa)]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1766056

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Valorie Zimmerman (valorie-zimmerman)]

I've been hit by this one again, testing the second spin of the kubuntu bionic final ISO. This time I got a photo of the error message, which I will transcribe below and attach if possible.
[ 0.0000000] [Firmware Bug]: TSC_DEADLINE disabled due to Errata; please update microcode to version: 0x20 (or later)
[ 0.040000] mce: [Hardware Error]: CPU 0: Machine Check: 0 Bank 6: ae0000000040110a
[ 0.040000] mce: [Hardware Error]: TSC 0 ADDR fef86f00 MISC 38a0000086
[ 0.040000] mce: [Hardware Error]: PROCESSOR 0:40651 TIME 1524542899 SOCKET 0 APIC 0 microcode 1c
[ 0.045483] ipmi:dmi:Invalid offset: 0

[Phillip Susi (psusi)]

If you are unable to install the new microcode that may be a kernel problem. Certainly doesn't have anything to do with ubiquity.