[Bug 1713532] Re: Intel-8260 not init'd by intel-microcode=3.20170707.1~ubuntu16.04.0

Robie Basak 1713532 at bugs.launchpad.net
Tue Aug 29 09:10:20 UTC 2017


Thank you for the report. For reference, bug 1700373 was the SRU
tracking bug for the intel-microcode update.

** Tags added: regression-update

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to intel-microcode in Ubuntu.
https://bugs.launchpad.net/bugs/1713532

Title:
  Intel-8260 not init'd by intel-microcode=3.20170707.1~ubuntu16.04.0

Status in intel-microcode package in Ubuntu:
  New

Bug description:
  I'm running:

  LSB Version:	core-9.20160110ubuntu0.2-amd64:core-9.20160110ubuntu0.2-noarch:printing-9.20160110ubuntu0.2-amd64:printing-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-amd64:security-9.20160110ubuntu0.2-noarch
  Distributor ID:	Ubuntu
  Description:	Ubuntu 16.04.3 LTS
  Release:	16.04
  Codename:	xenial

  On a NUC6i5SYH, with 32G RAM, and BIOS 0061

  Recently, the following package update happened:
  intel-microcode=3.20170707.1~ubuntu16.04.0

  Upon reboot, bluetooth was unavailable / uninitialized.
  Poking around w/ various tools, I think the insightful bit came from:
  `service bluetooth status -l` which showed multiple lines of
  `not enough free handles to register service` (see attached image).

  Rolling back to:
  `intel-microcode=3.20151106.1`

  and rebooting restored bluetooth function (I use a bluetooth
  keyboard).

  I did try (and leave) changing /etc/bluetooth/main.conf as follows:
  `Autoenable=true`

  It didn't help under the new intel-micorcode, and seems to have no
  noticable deleterious effect under the old intel-microcode.

  Let me know if there's any other / more information I can provide to
  help.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1713532/+subscriptions



More information about the foundations-bugs mailing list