@Uqbar The microcode update is fine and exactly as expected. 2018-01-08
is the release date of the microcode *bundle*, which contains 20
microcodes updated at various times around late November, mid-December
2017.
In the case of his 0x406e3 CPU, the microcode is from 2017-11-16, which
is exactly
@Marat I suspect your microcode is not as new as it seems: 2017-11-16 <
2018-01-08.
But I could be easily wrong.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1700373
Title:
intel-microcode is out
Today my manually installed 3.20151106.1+lp1700373b2 auto-updated to
3.20180108.0~ubuntu14.04.2 from repository, system booted successfully:
$ dmesg | grep microcode
[0.00] microcode: CPU0 microcode updated early to revision 0xc2, date =
2017-11-16
[0.110006] microcode: CPU1
This bug was fixed in the package intel-microcode -
3.20180108.0~ubuntu14.04.2
---
intel-microcode (3.20180108.0~ubuntu14.04.2) trusty-security; urgency=medium
* Sync package to xenial's latest update
* New upstream microcode datafile 20180108
+ New Microcodes:
sig
Regression report in bug 1713532. Please could someone familiar with
these microcode updates take a look?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1700373
Title:
intel-microcode is out of
This bug was fixed in the package intel-microcode -
3.20170707.1~ubuntu17.04.0
---
intel-microcode (3.20170707.1~ubuntu17.04.0) zesty; urgency=medium
* Sync of new upstream microcode release to address Kaby Lake
Hyper Threading bug. This is a sync of the dat files from artful
This bug was fixed in the package intel-microcode -
3.20170707.1~ubuntu16.04.0
---
intel-microcode (3.20170707.1~ubuntu16.04.0) xenial; urgency=medium
* Sync of new upstream microcode release to address Skylake, Kaby Lake
Hyper Threading bug. This is a sync of the dat files
On recent machine (88 cores + HT) running Xenial:
$ dpkg-query -W intel-microcode
intel-microcode 3.20170707.1~ubuntu16.04.0
$ grep -E 'model|stepping' /proc/cpuinfo | sort -u
model : 79
model name : Intel(R) Xeon(R) CPU E5-4669 v4 @ 2.20GHz
stepping: 1
$ journalctl -k |
Worked fine for me with Xenial on a laptop:
$ dpkg-query -W intel-microcode
intel-microcode 3.20170707.1~ubuntu16.04.0
$ grep -E 'model|stepping' /proc/cpuinfo | sort -u
model : 142
model name : Intel(R) Core(TM) i7-7500U CPU @ 2.70GHz
stepping: 9
$ journalctl -k | grep
> Just add the "dis_ucode_ldr" parameter to the kernel command line.
That's hardly a "just". Remember that Ubuntu is for everyone, not just
people who know how to tweak their bootloaders, or even understand how
to get to the grub boot menu. It's unreasonable for all Ubuntu desktop
users
Actually, it is not hard to bypass a boot-killer microcode update issue.
Just add the "dis_ucode_ldr" parameter to the kernel command line.
To make it trivial, add that to a "safe mode" grub menu entry...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
> 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
I just verified skylake + 20170707 on zesty. I did not rerun the
testcase, but I did do boot testing.
Marking verification-done.
** Tags removed: verification-needed verification-needed-zesty
** Tags added: verification-done verification-done-zesty
** Changed in: intel-microcode (Ubuntu
I have now killed my 4-simultaneous compilation loop tests after 20
hours. With the previous microcode, 2 of 3 loop threads died with a
segfault within 1 hour, so I consider this fixed.
@Others, Has anyone tested this with skylake/kabylake on zesty?
I have installed and boot tested using
Marking xenial-verification-done
I was able to reproduce the compilation crash as described on the ocaml
bug in about 30 minutes on my Skylake machine. After upgrading
firmware, I have been running for simultanous compilations loops for the
last 2 hours with no crash. I will let them continue
@Robie Basak
I updated the intel-microcode package ("3.20170707.1~ubuntu16.04.0") from
proposed.
This version is running fine so far on the "Intel(R) Core(TM) i5-6200U CPU @
2.30GHz"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
running on 17.04; no issues loading the new package:
[2.985314] microcode: sig=0x306c3, pf=0x10, revision=0x22
[3.013156] microcode: Microcode Update Driver: v2.2.
# on return from suspend:
[336419.388901] microcode: sig=0x306c3, pf=0x10, revision=0x12
[336419.389861] microcode: updated
Tested on my system:
Linux sxps 4.4.0-87-generic #110-Ubuntu SMP Tue Jul 18 12:55:35 UTC 2017
x86_64 x86_64 x86_64 GNU/Linux
Distributor ID: Ubuntu
Description:Ubuntu 16.04.2 LTS
Release:16.04
Codename: xenial
CPU:
Vendor ID: GenuineIntel
CPU family:6
> The minimum aging period is indeed 7 days, but I did say that I think
this particular update needs wider testing and aging due to the expected
severity of any regressions.
Debian distributed the update already if I am not mistaken. I haven’t
heard of any regression. Also I don’t recall anything
I have been running this on my kabylake laptop and skylake desktop under
X for quite some time now, and haven't hit any issues that I can
attribute to the microcode. I attempted to follow the reproducer here
https://caml.inria.fr/mantis/view.php?id=7452 , but some of the versions
of packages
@asgard2
Have you been able to test the proposed update please?
The minimum aging period is indeed 7 days, but I did say that I think
this particular update needs wider testing and aging due to the expected
severity of any regressions.
Thank you to Adrien for taking the time to test this
It was committed 3 days ago (the latest upload) and it is usually held
in proposed for at least 7 days.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1700373
Title:
intel-microcode is out of date,
when can we expect the xenial release, could not take long since the
status committed ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1700373
Title:
intel-microcode is out of date, version 20170707
Another test, this time on a NUC with a Pentium N3700 Braswell CPU under
Xenial.
$ uname -a
Linux 4.10.0-28-generic #32~16.04.2-Ubuntu SMP Thu Jul 20 10:19:48 UTC 2017
x86_64 x86_64 x86_64 GNU/Linux
$ cat /proc/cpuinfo
(...)vendor_id : GenuineIntel
cpu family : 6
model : 76
> @rbasak, The reason for the omission of "skylake" from the changelog
entry for zesty is because zesty already had 3.20170511.1~ubuntu17.04.0
in -updates which contained the fixes for the majority of Skylake
processors, but not Kaby Lake.
Ah. That makes sense. Sorry!
--
You received this bug
Here is a successful test of a Core i5-6600 Skylake CPU under Xenial.
$ uname -a
Linux 4.10.0-28-generic #32~16.04.2-Ubuntu SMP Thu Jul 20 10:19:48 UTC 2017
x86_64 x86_64 x86_64 GNU/Linux
$ cat /proc/cpuinfo
(...)
vendor_id : GenuineIntel
cpu family : 6
model : 94
model
@rbasak, The reason for the omission of "skylake" from the changelog
entry for zesty is because zesty already had 3.20170511.1~ubuntu17.04.0
in -updates which contained the fixes for the majority of Skylake
processors, but not Kaby Lake. So for zesty this release only fixes
kaby lake processors,
Additional SRU verification notes (also in bug description):
SRU verification needs to take care to consider CPUs actually tested. We
should have a representative sample of CPUs tested in SRU verification
reports before considering release to the updates pockets.
Given the potential severity of
I've reviewed Dave's updated upload. They look good - thanks!
One note: I think due to an omission debian/changelog for Zesty doesn't
mention that it fixes Skylake, whereas the Xenial debian/changelog does
state this. The binary blobs shipped between the two are identical, so
presumably the
Yakkety is EOL now.
** Changed in: intel-microcode (Ubuntu Yakkety)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1700373
Title:
intel-microcode is out of
Hi Dave,
Thank you for going through this. I think it's OK if you want to keep
the set of dat files available in sync with the set available in the
development release. But then the changelog entry should make this
clear.
I expected the changelog entry to match the diff that I was reviewing.
The changelog entry is there to match the artful changelog entry *(it
applies completely correctly for zesty).
As for the dat files. I guess my changelog entry would have been more
explicit had I said sync instead of backport.
" * Backport of new upstream microcode release to address Hyper
15:38 chiluk: around? Reviewing intel-microcode.
15:39 In principle the change seems OK, but I'm confused by
things mismatching the descriptions in debian/changelog
15:39 "source: remove unneeded intel-ucode/ directory" -
removed from where? I don't see this in the current packages for Xenial
Tested on 17.04 with a 4.13-rc1 kernel + a pinned microcode package from
artful:
➜ linux git:(5771a8c08880) ✗ apt policy intel-microcode
intel-microcode:
Installed: 3.20170707.1
Candidate: 3.20170707.1
Version table:
*** 3.20170707.1 500
500 http://ru.archive.ubuntu.com/ubuntu
Well, I tried intel-microcode_3.20151106.1+lp1700373b2_amd64.deb on
Trusty with 4.4 and it worked. Of course, in someone's case it may start
a thermonuclear war, so use this information with care.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
35 matches
Mail list logo
