Comment 81 for bug 1700373

> So I don’t see the high caution is justified compared to any other package.

Because: a) Unlike regular software updates, testing on one CPU model/stepping doesn't test on any other CPU model/stepping; and b) if the updates does regress, unlike most other updates this may render systems unbootable, meaning that fixing any regression isn't as simple as just releasing another update.

Thanks for the testing so far everyone. Here's mine on Xenial:

robie@mal:~$ dpkg-query -W intel-microcode
intel-microcode 3.20170707.1~ubuntu16.04.0
robie@mal:~$ grep -E 'model|stepping' /proc/cpuinfo | sort -u
model : 94
model name : Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz
stepping : 3
robie@mal:~$ journalctl -k | grep microcode
Aug 03 13:35:16 mal kernel: microcode: CPU0 microcode updated early to revision 0xba, date = 2017-04-09
Aug 03 13:35:16 mal kernel: microcode: CPU1 microcode updated early to revision 0xba, date = 2017-04-09
Aug 03 13:35:16 mal kernel: microcode: CPU2 microcode updated early to revision 0xba, date = 2017-04-09
Aug 03 13:35:16 mal kernel: microcode: CPU3 microcode updated early to revision 0xba, date = 2017-04-09
Aug 03 13:35:16 mal kernel: microcode: CPU0 sig=0x506e3, pf=0x2, revision=0xba
Aug 03 13:35:16 mal kernel: microcode: CPU1 sig=0x506e3, pf=0x2, revision=0xba
Aug 03 13:35:16 mal kernel: microcode: CPU2 sig=0x506e3, pf=0x2, revision=0xba
Aug 03 13:35:16 mal kernel: microcode: CPU3 sig=0x506e3, pf=0x2, revision=0xba
Aug 03 13:35:16 mal kernel: microcode: CPU4 sig=0x506e3, pf=0x2, revision=0xba
Aug 03 13:35:16 mal kernel: microcode: CPU5 sig=0x506e3, pf=0x2, revision=0xba
Aug 03 13:35:16 mal kernel: microcode: CPU6 sig=0x506e3, pf=0x2, revision=0xba
Aug 03 13:35:16 mal kernel: microcode: CPU7 sig=0x506e3, pf=0x2, revision=0xba
Aug 03 13:35:16 mal kernel: microcode: Microcode Update Driver: v2.01 <email address hidden>, Peter Oruba
robie@mal:~$ dpkg-query -W intel-microcode
intel-microcode 3.20170707.1~ubuntu16.04.0