Updated amd microcode do not load after reboot
Clash Royale CLAN TAG#URR8PPP up vote
0
down vote
favorite
After install of updated microcode "sudo apt install amd64-microcode" on ubuntu 16.04, after reboot microcode do not load. Its needed to patch spectre v2 and without it the computer is vulnerable.
[1.702088]microcode: CPU0: patch_level=0x07030105
[1.702099]microcode: CPU1: patch_level=0x07030105
[1.702111]microcode: CPU2: patch_level=0x07030105
[1.702121]microcode: CPU3: patch_level=0x07030105
[1.702181]microcode: Microcode Update Driver: v2.2.
64-bit amd-processor microcode
asked Apr 12 at 11:42
José Almeida
262
 |Â
show 3 more comments
up vote
0
down vote
favorite
After install of updated microcode "sudo apt install amd64-microcode" on ubuntu 16.04, after reboot microcode do not load. Its needed to patch spectre v2 and without it the computer is vulnerable.
[1.702088]microcode: CPU0: patch_level=0x07030105
[1.702099]microcode: CPU1: patch_level=0x07030105
[1.702111]microcode: CPU2: patch_level=0x07030105
[1.702121]microcode: CPU3: patch_level=0x07030105
[1.702181]microcode: Microcode Update Driver: v2.2.
64-bit amd-processor microcode
asked Apr 12 at 11:42
José Almeida
262
How did you determine that "after reboot microcode do not load"?
– Byte Commander
Apr 12 at 11:48
by doing "dmesg | grep microcode"
– José Almeida
Apr 12 at 11:50
it show the same version off microcode that it had before update
– José Almeida
Apr 12 at 11:52
See askubuntu.com/questions/1016971/…
– Panther
Apr 12 at 15:16
@Panther OP has AMD, not Intel.
– heynnema
Apr 12 at 15:52
 |Â
show 3 more comments
up vote
0
down vote
favorite
up vote
0
down vote
favorite
After install of updated microcode "sudo apt install amd64-microcode" on ubuntu 16.04, after reboot microcode do not load. Its needed to patch spectre v2 and without it the computer is vulnerable.
[1.702088]microcode: CPU0: patch_level=0x07030105
[1.702099]microcode: CPU1: patch_level=0x07030105
[1.702111]microcode: CPU2: patch_level=0x07030105
[1.702121]microcode: CPU3: patch_level=0x07030105
[1.702181]microcode: Microcode Update Driver: v2.2.
64-bit amd-processor microcode
asked Apr 12 at 11:42
José Almeida
262
After install of updated microcode "sudo apt install amd64-microcode" on ubuntu 16.04, after reboot microcode do not load. Its needed to patch spectre v2 and without it the computer is vulnerable.
[1.702088]microcode: CPU0: patch_level=0x07030105
[1.702099]microcode: CPU1: patch_level=0x07030105
[1.702111]microcode: CPU2: patch_level=0x07030105
[1.702121]microcode: CPU3: patch_level=0x07030105
[1.702181]microcode: Microcode Update Driver: v2.2.
64-bit amd-processor microcode
64-bit amd-processor microcode
asked Apr 12 at 11:42
José Almeida
262
asked Apr 12 at 11:42
José Almeida
262
edited Apr 12 at 13:55
asked Apr 12 at 11:42
José Almeida
262
asked Apr 12 at 11:42
José Almeida
262
asked Apr 12 at 11:42
José Almeida
262
262
How did you determine that "after reboot microcode do not load"?
– Byte Commander
Apr 12 at 11:48
by doing "dmesg | grep microcode"
– José Almeida
Apr 12 at 11:50
it show the same version off microcode that it had before update
– José Almeida
Apr 12 at 11:52
See askubuntu.com/questions/1016971/…
– Panther
Apr 12 at 15:16
@Panther OP has AMD, not Intel.
– heynnema
Apr 12 at 15:52
 |Â
show 3 more comments
How did you determine that "after reboot microcode do not load"?
– Byte Commander
Apr 12 at 11:48
by doing "dmesg | grep microcode"
– José Almeida
Apr 12 at 11:50
it show the same version off microcode that it had before update
– José Almeida
Apr 12 at 11:52
See askubuntu.com/questions/1016971/…
– Panther
Apr 12 at 15:16
@Panther OP has AMD, not Intel.
– heynnema
Apr 12 at 15:52
How did you determine that "after reboot microcode do not load"?
– Byte Commander
Apr 12 at 11:48
How did you determine that "after reboot microcode do not load"?
– Byte Commander
Apr 12 at 11:48
by doing "dmesg | grep microcode"
– José Almeida
Apr 12 at 11:50
by doing "dmesg | grep microcode"
– José Almeida
Apr 12 at 11:50
it show the same version off microcode that it had before update
– José Almeida
Apr 12 at 11:52
it show the same version off microcode that it had before update
– José Almeida
Apr 12 at 11:52
See askubuntu.com/questions/1016971/…
– Panther
Apr 12 at 15:16
See askubuntu.com/questions/1016971/…
– Panther
Apr 12 at 15:16
@Panther OP has AMD, not Intel.
– heynnema
Apr 12 at 15:52
@Panther OP has AMD, not Intel.
– heynnema
Apr 12 at 15:52
 |Â
show 3 more comments
1 Answer
1
active
oldest
votes
up vote
0
down vote
Here, it did not load either, but apt wanted to autoremove it - just to install it again afterwards (on apt-get update). Turns out an "apt-get dist-upgrade" was needed to upgrade the linux-generic. Afterwards, the amd-microcode was uptodate again (and the autoremove issue went away).
answered Jun 20 at 9:16
Ingo
1
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
Here, it did not load either, but apt wanted to autoremove it - just to install it again afterwards (on apt-get update). Turns out an "apt-get dist-upgrade" was needed to upgrade the linux-generic. Afterwards, the amd-microcode was uptodate again (and the autoremove issue went away).
answered Jun 20 at 9:16
Ingo
1
add a comment |Â
up vote
0
down vote
Here, it did not load either, but apt wanted to autoremove it - just to install it again afterwards (on apt-get update). Turns out an "apt-get dist-upgrade" was needed to upgrade the linux-generic. Afterwards, the amd-microcode was uptodate again (and the autoremove issue went away).
answered Jun 20 at 9:16
Ingo
1
add a comment |Â
up vote
0
down vote
up vote
0
down vote
Here, it did not load either, but apt wanted to autoremove it - just to install it again afterwards (on apt-get update). Turns out an "apt-get dist-upgrade" was needed to upgrade the linux-generic. Afterwards, the amd-microcode was uptodate again (and the autoremove issue went away).
answered Jun 20 at 9:16
Ingo
1
Here, it did not load either, but apt wanted to autoremove it - just to install it again afterwards (on apt-get update). Turns out an "apt-get dist-upgrade" was needed to upgrade the linux-generic. Afterwards, the amd-microcode was uptodate again (and the autoremove issue went away).
answered Jun 20 at 9:16
Ingo
1
answered Jun 20 at 9:16
Ingo
1
answered Jun 20 at 9:16
Ingo
1
answered Jun 20 at 9:16
Ingo
1
1
add a comment |Â
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1024334%2fupdated-amd-microcode-do-not-load-after-reboot%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
How did you determine that "after reboot microcode do not load"?
– Byte Commander
Apr 12 at 11:48
by doing "dmesg | grep microcode"
– José Almeida
Apr 12 at 11:50
it show the same version off microcode that it had before update
– José Almeida
Apr 12 at 11:52
See askubuntu.com/questions/1016971/…
– Panther
Apr 12 at 15:16
@Panther OP has AMD, not Intel.
– heynnema
Apr 12 at 15:52