FS#42560 - [intel-ucode]: Probably outdated package

Attached to Project: Arch Linux
Opened by Martin Schnitkemper (Martin-MS) - Sunday, 26 October 2014, 09:18 GMT
Last edited by Thomas Bächler (brain0) - Sunday, 26 October 2014, 10:29 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Thomas Bächler (brain0)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
~~~~~~~~~~~
Microcode-Update on boot reports revision 0x1b from 2014-05-29 while Intel offers an update 2014-09-13. The current packages has been build on 2014-10-12.

Additional info:
~~~~~~~~~~~~~~~
On boot I get

| [ 0.000000] CPU0 microcode updated early to revision 0x1b, date = 2014-05-29
| [ 0.082057] CPU1 microcode updated early to revision 0x1b, date = 2014-05-29
| [ 0.317017] microcode: CPU0 sig=0x306a9, pf=0x2, revision=0x1b
| [ 0.317021] microcode: CPU1 sig=0x306a9, pf=0x2, revision=0x1b
| [ 0.317027] microcode: CPU2 sig=0x306a9, pf=0x2, revision=0x1b
| [ 0.317032] microcode: CPU3 sig=0x306a9, pf=0x2, revision=0x1b
| [ 0.317072] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba

but after I rebuild the package again from source I got, inter alia, these messages

| signature: 0x306a9
| flags: 0x12
| revision: 0x1b
| date: 2014-05-29
| size: 12288
|
| signature: 0x306f2
| flags: 0x6f
| revision: 0x29
| date: 2014-09-03
| size: 28672

Steps to reproduce:
~~~~~~~~~~~~~~~~~~
Compare intel-ucode.img against the current file and that you got after rebuilding the package.

I am not sure if just the wrong revision and date is reported or if we are just on an outdated microcode.
This task depends upon

Closed by  Thomas Bächler (brain0)
Sunday, 26 October 2014, 10:29 GMT
Reason for closing:  Not a bug
Comment by Andreas Radke (AndyRTR) - Sunday, 26 October 2014, 10:14 GMT
If it's really outdated please flag the pkg out-of-date.

Loading...