Comment 89 for bug 1700373

On Tue, 29 Aug 2017, Robie Basak wrote:
> Regression report in bug 1713532. Please could someone familiar with
> these microcode updates take a look?

First, we should check for the possibility of a kernel or userspace
issue that is getting in the way of the bluetooth firmware loading when
a microcode update is available to be applied...

Hopefully, this should be easy enough to do: intel-microcode package
3.20151106.1 is reported to work, so it is just a matter of testing
successive intel-microcode packages, and looking at the full logs of the
attempts.

Please report the contents of /proc/cpuinfo with the latest
intel-microcode package that works, and /proc/cpuinfo with the package
that doesn't (3.20170707.1~ubuntu16.04.0).

Also, please report the output of "dmesg" or from "journalctl -k -b"
(i.e. the kernel logs) in the failure case, so that we can search for
some sort of kernel message by the bluetooth stack, etc.

You could test when the breakage happened using the Debian packages,
They should be 100% compatible with the Ubuntu OS, as far as I know.

Packages to test (in order, you can stop when the breakage disappears):

http://snapshot.debian.org/package/intel-microcode/3.20170707.1/
http://snapshot.debian.org/package/intel-microcode/3.20170511.1/
http://snapshot.debian.org/package/intel-microcode/3.20161104.1/
http://snapshot.debian.org/package/intel-microcode/3.20160607.2/

Thanks.

--
  Henrique Holschuh