@tyhicks
I can also confirm that the issue appears to be resolved with linux-image-4.13.0-38-generic_4.13.0-38.43+lp1759920.1
Below is the requested information.
$ uname -a Linux mercury 4.13.0-38-generic #43+lp1759920.1 SMP Tue Apr 3 22:59:23 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
$ cat /proc/version_signature Ubuntu 4.13.0-38.43+lp1759920.1-generic 4.13.16
$ cat /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-4.13.0-38-generic root=UUID=5dd1c110-663e-4cf0-9a63-45815590a186 ro quiet splash vt.handoff=7
$ dmesg -t | grep -i microcode microcode: microcode updated early to revision 0x84, date = 2018-01-21 microcode: sig=0x906e9, pf=0x20, revision=0x84 microcode: Microcode Update Driver: v2.2.
@tyhicks
I can also confirm that the issue appears to be resolved with linux-image- 4.13.0- 38-generic_ 4.13.0- 38.43+lp1759920 .1
Below is the requested information.
$ uname -a
Linux mercury 4.13.0-38-generic #43+lp1759920.1 SMP Tue Apr 3 22:59:23 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
$ cat /proc/version_ signature 38.43+lp1759920 .1-generic 4.13.16
Ubuntu 4.13.0-
$ cat /proc/cmdline /boot/vmlinuz- 4.13.0- 38-generic root=UUID= 5dd1c110- 663e-4cf0- 9a63-45815590a1 86 ro quiet splash vt.handoff=7
BOOT_IMAGE=
$ dmesg -t | grep -i microcode
microcode: microcode updated early to revision 0x84, date = 2018-01-21
microcode: sig=0x906e9, pf=0x20, revision=0x84
microcode: Microcode Update Driver: v2.2.