Ubuntu
amd64-microcode package

[MIR] amd64-microcode (multiverse -> main)

Bug #1521174 reported by Alberto Salvia Novella
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
AMD
Fix Released
Undecided
Unassigned
amd64-microcode (Ubuntu)
Fix Released
High
Unassigned

Bug Description

**************
 AVAILABILITY
**************
Available in multiverse for the i386 and amd64 architectures. Automatically imported from the Debian non-free repository.

************
 RATIONALE
************
Fixes processor misbehaviours by patching its microcode early on boot. This removes the need of upgrading the BIOS for solving these issues.

***********
 SECURITY
***********
If the microcode is not reapplied on each boot, the processor simply behaves as it was when manufactured. This is inherently more riskier than patching it.

On the other hand the microcode is provided as a binary only, so nobody outside AMD can review it for issues.

**********************
 QUALITY ASSURANCE
**********************
The package just works after installation. The kernel automatically applies the microcode to the processor after each boot.

****************
 DEPENDENCIES
****************
None.

**************************
 STANDARD COMPLIANCE
**************************
The microcode is proprietary, so the kernel cannot carry it itself.

****************
 MAINTENANCE
****************
The maintainer of this package is the same as the intel-microcode, which is already in the restricted repository. Reading Debian change logs, we see that the frequency of upgrades for both packages is the same.

Alberto Salvia Novella (es20490446e)
Changed in amd:
status: New → Confirmed
Michael Terry (mterry)
Changed in amd64-microcode (Ubuntu):
assignee: nobody → Jamie Strandboge (jdstrand)
Revision history for this message
Dimitri John Ledkov (xnox) wrote :

Also see https://bugs.launchpad.net/ubuntu/+source/amd64-microcode/+bug/1386257 that ubuntu-drivers has had a plugin to detect and install amd64-microcode on amd cpus since at least xenial.

Revision history for this message
Tyler Hicks (tyhicks) wrote :

Unassigning this MIR from jdstrand so that it'll go back into the queue.

Changed in amd64-microcode (Ubuntu):
assignee: Jamie Strandboge (jdstrand) → nobody
Revision history for this message
Steve Langasek (vorlon) wrote :

This should go to main, not restricted, by analogy with LP: #1738272.

summary: - [MIR] amd64-microcode (multiverse -> restricted)
+ [MIR] amd64-microcode (multiverse -> main)
Revision history for this message
Matthias Klose (doko) wrote :

the only concern here is that we have a downstream package without any information about the upstream status. The URLs in the packaging all point to invalid pages.

Besides that it look ok to go to main

Revision history for this message
Matthias Klose (doko) wrote :

wait, missing bug subscriber ...

Changed in amd64-microcode (Ubuntu):
status: Triaged → Incomplete
Revision history for this message
Alberto Salvia Novella (es20490446e) wrote :

Sorry, but I don't understand the above statement and how it affects status.

Changed in amd64-microcode (Ubuntu):
status: Incomplete → Triaged
Revision history for this message
Matthias Klose (doko) wrote :

> Sorry, but I don't understand the above statement and how it affects status

well, if you don't understand it, why do you change it? The package needs a bugs subscriber.

Changed in amd64-microcode (Ubuntu):
status: Triaged → Incomplete
Revision history for this message
Dimitri John Ledkov (xnox) wrote :

foundations-bugs subscribed

Revision history for this message
Alberto Salvia Novella (es20490446e) wrote :

Saying a report is "incomplete" means that the reporters need to provide more info for the bug to be workable.

Setting it to "incomplete" in any other scenario effectively disuades people to help out on it.

Changed in amd64-microcode (Ubuntu):
status: Incomplete → Triaged
Revision history for this message
Matthias Klose (doko) wrote :

Alberto, you are wrong. Please abstain from modifying the status for bug reports handled by the MIR team. And yes, we needed to know who subscribes to the bug reports.

Revision history for this message
Alberto Salvia Novella (es20490446e) wrote :

This simple report is more than two years old, and the wiki clearly states what "incomplete" means:
(https://wiki.ubuntu.com/Bugs/Bug%20statuses)

You say the solution is to handle all by yourselves. But we actually see that it's quite the opposite.

Or I am mistaken, and MIR is been great success? Come on!

Revision history for this message
Matthias Klose (doko) wrote :

please see https://wiki.ubuntu.com/MainInclusionProcess for the description of MIR bug statuses.

Revision history for this message
Matthias Klose (doko) wrote :

Override component to main
amd64-microcode 3.20160316.3 in bionic: multiverse/admin -> main
amd64-microcode 3.20160316.3 in bionic amd64: multiverse/admin/extra/100% -> main
amd64-microcode 3.20160316.3 in bionic i386: multiverse/admin/extra/100% -> main
3 publications overridden.

Changed in amd64-microcode (Ubuntu):
status: Triaged → Fix Released
Revision history for this message
Alberto Salvia Novella (es20490446e) wrote :

You will want to make those two pages consistent with each other, with the scope of making users co-developers.

Anyway thanks for your help, and have a nice day. I'm unsubscribing now from this report, but feel free to call me back if you need anything.

Amr Ibrahim (amribrahim1987)
Changed in amd:
status: Confirmed → Fix Released
Francis Ginther (fginther)
tags: added: id-5a20305cc21096d164992af9
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.