TSC_DEADLINE disabled error even after updating microcode
I got the following error:
So, I logged into root shell and installed the intel-microcode package:
sudo apt-get install microcode.ctl intel-microcode
But I still receive the error after rebooting. I logged into root shell again and checked the version of microcode:
As you see I have version 0xb000021 which is newer than0xb000020 but I still get the same error and can't boot normally.
Any ideas?
16.04 intel microcode
edited Jan 10 at 14:39
karel
57.8k12128146
asked Apr 1 '18 at 19:29
CuriousGuyCuriousGuy
1213
add a comment |
I got the following error:
So, I logged into root shell and installed the intel-microcode package:
sudo apt-get install microcode.ctl intel-microcode
But I still receive the error after rebooting. I logged into root shell again and checked the version of microcode:
As you see I have version 0xb000021 which is newer than0xb000020 but I still get the same error and can't boot normally.
Any ideas?
16.04 intel microcode
edited Jan 10 at 14:39
karel
57.8k12128146
asked Apr 1 '18 at 19:29
CuriousGuyCuriousGuy
1213
Did you forget to update initrams withsudo update-initramfs -u -k all? Then reboot.
– N0rbert
Apr 1 '18 at 19:34
@N0rbert yes, should I have done it? Do you think this is the problem?
– CuriousGuy
Apr 1 '18 at 19:34
I think it should help. Current initramfs may not contain new ucode.
– N0rbert
Apr 1 '18 at 19:35
@N0rbert will try tomorrow and let you know, thanks.
– CuriousGuy
Apr 1 '18 at 19:36
@N0rbert doesn't work. Still getting the first error...
– CuriousGuy
Apr 2 '18 at 18:00
add a comment |
I got the following error:
So, I logged into root shell and installed the intel-microcode package:
sudo apt-get install microcode.ctl intel-microcode
But I still receive the error after rebooting. I logged into root shell again and checked the version of microcode:
As you see I have version 0xb000021 which is newer than0xb000020 but I still get the same error and can't boot normally.
Any ideas?
16.04 intel microcode
edited Jan 10 at 14:39
karel
57.8k12128146
asked Apr 1 '18 at 19:29
CuriousGuyCuriousGuy
1213
I got the following error:
So, I logged into root shell and installed the intel-microcode package:
sudo apt-get install microcode.ctl intel-microcode
But I still receive the error after rebooting. I logged into root shell again and checked the version of microcode:
As you see I have version 0xb000021 which is newer than0xb000020 but I still get the same error and can't boot normally.
Any ideas?
16.04 intel microcode
16.04 intel microcode
edited Jan 10 at 14:39
karel
57.8k12128146
asked Apr 1 '18 at 19:29
CuriousGuyCuriousGuy
1213
edited Jan 10 at 14:39
karel
57.8k12128146
asked Apr 1 '18 at 19:29
CuriousGuyCuriousGuy
1213
edited Jan 10 at 14:39
karel
57.8k12128146
edited Jan 10 at 14:39
karel
57.8k12128146
edited Jan 10 at 14:39
karel
57.8k12128146
57.8k12128146
asked Apr 1 '18 at 19:29
CuriousGuyCuriousGuy
1213
asked Apr 1 '18 at 19:29
CuriousGuyCuriousGuy
1213
asked Apr 1 '18 at 19:29
CuriousGuyCuriousGuy
1213
1213
Did you forget to update initrams withsudo update-initramfs -u -k all? Then reboot.
– N0rbert
Apr 1 '18 at 19:34
@N0rbert yes, should I have done it? Do you think this is the problem?
– CuriousGuy
Apr 1 '18 at 19:34
I think it should help. Current initramfs may not contain new ucode.
– N0rbert
Apr 1 '18 at 19:35
@N0rbert will try tomorrow and let you know, thanks.
– CuriousGuy
Apr 1 '18 at 19:36
@N0rbert doesn't work. Still getting the first error...
– CuriousGuy
Apr 2 '18 at 18:00
add a comment |
Did you forget to update initrams withsudo update-initramfs -u -k all? Then reboot.
– N0rbert
Apr 1 '18 at 19:34
@N0rbert yes, should I have done it? Do you think this is the problem?
– CuriousGuy
Apr 1 '18 at 19:34
I think it should help. Current initramfs may not contain new ucode.
– N0rbert
Apr 1 '18 at 19:35
@N0rbert will try tomorrow and let you know, thanks.
– CuriousGuy
Apr 1 '18 at 19:36
@N0rbert doesn't work. Still getting the first error...
– CuriousGuy
Apr 2 '18 at 18:00
Did you forget to update initrams with
sudo update-initramfs -u -k all ? Then reboot.– N0rbert
Apr 1 '18 at 19:34
Did you forget to update initrams with
sudo update-initramfs -u -k all ? Then reboot.– N0rbert
Apr 1 '18 at 19:34
@N0rbert yes, should I have done it? Do you think this is the problem?
– CuriousGuy
Apr 1 '18 at 19:34
@N0rbert yes, should I have done it? Do you think this is the problem?
– CuriousGuy
Apr 1 '18 at 19:34
I think it should help. Current initramfs may not contain new ucode.
– N0rbert
Apr 1 '18 at 19:35
I think it should help. Current initramfs may not contain new ucode.
– N0rbert
Apr 1 '18 at 19:35
@N0rbert will try tomorrow and let you know, thanks.
– CuriousGuy
Apr 1 '18 at 19:36
@N0rbert will try tomorrow and let you know, thanks.
– CuriousGuy
Apr 1 '18 at 19:36
@N0rbert doesn't work. Still getting the first error...
– CuriousGuy
Apr 2 '18 at 18:00
@N0rbert doesn't work. Still getting the first error...
– CuriousGuy
Apr 2 '18 at 18:00
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1021134%2ftsc-deadline-disabled-error-even-after-updating-microcode%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1021134%2ftsc-deadline-disabled-error-even-after-updating-microcode%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
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
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Did you forget to update initrams with
sudo update-initramfs -u -k all? Then reboot.– N0rbert
Apr 1 '18 at 19:34
@N0rbert yes, should I have done it? Do you think this is the problem?
– CuriousGuy
Apr 1 '18 at 19:34
I think it should help. Current initramfs may not contain new ucode.
– N0rbert
Apr 1 '18 at 19:35
@N0rbert will try tomorrow and let you know, thanks.
– CuriousGuy
Apr 1 '18 at 19:36
@N0rbert doesn't work. Still getting the first error...
– CuriousGuy
Apr 2 '18 at 18:00