Thanks Robie.
Only sense I can make of it (since I struggled for a while, before
trying downgrade of intel-microcode) --- downgrade flushed / did
something w/ some settings, somewhere (and that persisted).
I've upgraded to 4.4.0.93.98 kernel now, with latest intel-microcode,
and all continues to
Thank you for the report.
Based on that I think it's safe to say that this isn't caused by the
issued update of intel-microcode? So I'll mark the intel-microcode task
Invalid.
If you determine that the regression was caused by the kernel update,
then please add a bug task against the "linux" pack
With no more than intel-microcode (re-) upgraded to
3.20170707.1~ubuntu16.04.0, and booting - now bluetooth works.
I can say this: with initial dropout of bluetooth, I rebooted I think a total
of 3 times:
Once just reboot; Once complete power-down / power-up. Then, only
downgrading intel-mic
Ok - here's my starting point (now):
Bluetooth working.
-
attached archive has:
- installed version info for:
- intel-microcode
- linux-firmware
- linux-image
- cpuinfo
- kern.log (boot log: output of journctl -k -b)
** Attachment added: "installed versions, cpuinfo, kernal
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 (
@yarko, Please start by gathering the information @hmh requested. Those
include:
1. output of /proc/cpuinfo
2. /var/log/kern.log
Please provide both of these with both the working and newest microcode.
Also please reverify bluetooth in both cases, as we need to make sure
that the issue wasn't si
Good point, Simon:
I'm running: 4.4.0-92-generic
As I'm just getting ready to sit down to this, and see:
linux-image-generic/xenial-updates,xenial-security 4.4.0.93.98 amd64
[upgradable from: 4.4.0.92.97]
Perhaps I'll (?):
- upgrade kernel (and related files queued);
- upgrade to latest intel-
Could this be a duplicate of LP: #1705633? @yarko, could you please
provide which kernel you used?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1713532
Title:
Intel-8260 not init'd by intel-microco
A couple of quick responses:
@chiluk - linux-firmware installed is showing as:
(apt list --installed output):
linux-firmware/xenial-updates,xenial-updates,xenial-security,xenial-
security,now 1.157.11 all [installed,automatic]
--
You received this bug notification because you are a member of U
According to the bios changelog
https://downloadmirror.intel.com/26841/eng/SY_0061_ReleaseNotes.pdf
0061 of your bios should already include the microcode that is also
available in the intel-microcode package. As such, on boot I'd expect a
no-op when checking for newer microcode version. We defi
This may require escalating back to Intel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1713532
Title:
Intel-8260 not init'd by intel-microcode=3.20170707.1~ubuntu16.04.0
To manage notifications a
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1713532
Ti
12 matches
Mail list logo
