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

[yarko]

I'm glad, then, I waited until someone reacted to my "plan".

Checking /var/log/kern.log, I have the log from when I first booted w/ the failing situation.
I know this, because I shutdown (rare) in anticipation of a coming Hurricane Harvey, and tweeted the next day when weather was stable.

The (attached) log - the interesting starting point, first boot w/
intel-microcode 3.2017.07.07.1 is "Aug 26 12:52"  (shutdown was "Aug 26
00:10").

In the meantime, I'll upgrade just the intel-microcode to the Ubuntu
release, and shortly provide that associated kern.log and /proc/cpuinfo,
then cycle thru the various debian releases @hmh listed, and (finally)
end with Ubuntu upgrades, including intel-microcode and kernel.

Let's see what happens...

** Attachment added: "kern.log from initial discovery/ report here"
   https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1713532/+attachment/4941067/+files/kern.log.2017.08.26.gz

-- 
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