Ubuntu 18.04 having kernel panic on boot
I tried to boot into Ubuntu 18.04 today, but when it was starting up and all the output was running by it declared a kernel error and froze. The only way I could get out was by holding the power button down for about ten seconds to shut the computer down. I think I might be able to fix the problem if I can get on Ubuntu or even into recovery mode, but I can't do either. I have had Ubuntu for almost nine months and have never had this problem before.
The last time I was on the system it worked normally and I didn't do anything major. The only change I have made to any system that is even related to boot since I was last on was to change the default boot value in the Grub menu. I have a dual boot of Kali Linux (I am using the Kali Grub menu) and Windows 10 (which I am currently on) on the same system, but they have both been working fine.
Before the kernel error the output said something like:
[Firmware Bug]: TSC_DEADLINE disabled due to Errata; please update microcode to version: 0x22 (or later)
The system also kept talking about the VFS but I don't know why because in BIOS the VFS tab is blanked out and it has never had a problem before.
My problem is not a duplicate of this issue because I am stuck outside of my system, not just reading the logs through: [Firmware Bug]: TSC_DEADLINE disabled due to Errata - what should I do about this?
Image of my screen during kernel panic
boot kernel
asked Jan 8 at 13:17
HansHans
14
add a comment |
I tried to boot into Ubuntu 18.04 today, but when it was starting up and all the output was running by it declared a kernel error and froze. The only way I could get out was by holding the power button down for about ten seconds to shut the computer down. I think I might be able to fix the problem if I can get on Ubuntu or even into recovery mode, but I can't do either. I have had Ubuntu for almost nine months and have never had this problem before.
The last time I was on the system it worked normally and I didn't do anything major. The only change I have made to any system that is even related to boot since I was last on was to change the default boot value in the Grub menu. I have a dual boot of Kali Linux (I am using the Kali Grub menu) and Windows 10 (which I am currently on) on the same system, but they have both been working fine.
Before the kernel error the output said something like:
[Firmware Bug]: TSC_DEADLINE disabled due to Errata; please update microcode to version: 0x22 (or later)
The system also kept talking about the VFS but I don't know why because in BIOS the VFS tab is blanked out and it has never had a problem before.
My problem is not a duplicate of this issue because I am stuck outside of my system, not just reading the logs through: [Firmware Bug]: TSC_DEADLINE disabled due to Errata - what should I do about this?
Image of my screen during kernel panic
boot kernel
asked Jan 8 at 13:17
HansHans
14
2
Possible duplicate of [Firmware Bug]: TSC_DEADLINE disabled due to Errata - what should I do about this?
– N0rbert
Jan 8 at 13:18
This is different because I am stuck outside of the system and can't get in. Not just reading through the logs.
– Hans
Jan 8 at 13:20
Then update your BIOS to the newest version (get it from the motherboard/laptop manufacturer site).
– N0rbert
Jan 8 at 13:23
I did this and when I got to the part about Flashing the system it said that my BIOS was on a higher system than the one in the update file, so I canceled the upgrade or 'downgrade'. My computer is refurbished. I wonder if that has anything to do with it.
– Hans
Jan 8 at 14:00
Okay, I believe I caused the issue when I changed the default boot option for GRUB and updated it. I am using the Kali GRUB menu, which complicates things, since my problem is with Ubuntu. I believe the problem is with the initramfs, but I can't figure out how to fix it. I can boot into Ubuntu on one of my older kernels, but still cannot with the current one. Suggestions would be appreciated for fixing the problem.
– Hans
Jan 8 at 21:09
add a comment |
I tried to boot into Ubuntu 18.04 today, but when it was starting up and all the output was running by it declared a kernel error and froze. The only way I could get out was by holding the power button down for about ten seconds to shut the computer down. I think I might be able to fix the problem if I can get on Ubuntu or even into recovery mode, but I can't do either. I have had Ubuntu for almost nine months and have never had this problem before.
The last time I was on the system it worked normally and I didn't do anything major. The only change I have made to any system that is even related to boot since I was last on was to change the default boot value in the Grub menu. I have a dual boot of Kali Linux (I am using the Kali Grub menu) and Windows 10 (which I am currently on) on the same system, but they have both been working fine.
Before the kernel error the output said something like:
[Firmware Bug]: TSC_DEADLINE disabled due to Errata; please update microcode to version: 0x22 (or later)
The system also kept talking about the VFS but I don't know why because in BIOS the VFS tab is blanked out and it has never had a problem before.
My problem is not a duplicate of this issue because I am stuck outside of my system, not just reading the logs through: [Firmware Bug]: TSC_DEADLINE disabled due to Errata - what should I do about this?
Image of my screen during kernel panic
boot kernel
asked Jan 8 at 13:17
HansHans
14
I tried to boot into Ubuntu 18.04 today, but when it was starting up and all the output was running by it declared a kernel error and froze. The only way I could get out was by holding the power button down for about ten seconds to shut the computer down. I think I might be able to fix the problem if I can get on Ubuntu or even into recovery mode, but I can't do either. I have had Ubuntu for almost nine months and have never had this problem before.
The last time I was on the system it worked normally and I didn't do anything major. The only change I have made to any system that is even related to boot since I was last on was to change the default boot value in the Grub menu. I have a dual boot of Kali Linux (I am using the Kali Grub menu) and Windows 10 (which I am currently on) on the same system, but they have both been working fine.
Before the kernel error the output said something like:
[Firmware Bug]: TSC_DEADLINE disabled due to Errata; please update microcode to version: 0x22 (or later)
The system also kept talking about the VFS but I don't know why because in BIOS the VFS tab is blanked out and it has never had a problem before.
My problem is not a duplicate of this issue because I am stuck outside of my system, not just reading the logs through: [Firmware Bug]: TSC_DEADLINE disabled due to Errata - what should I do about this?
Image of my screen during kernel panic
boot kernel
boot kernel
asked Jan 8 at 13:17
HansHans
14
asked Jan 8 at 13:17
HansHans
14
edited Jan 8 at 14:37
Hans
asked Jan 8 at 13:17
HansHans
14
asked Jan 8 at 13:17
HansHans
14
asked Jan 8 at 13:17
HansHans
14
14
2
Possible duplicate of [Firmware Bug]: TSC_DEADLINE disabled due to Errata - what should I do about this?
– N0rbert
Jan 8 at 13:18
This is different because I am stuck outside of the system and can't get in. Not just reading through the logs.
– Hans
Jan 8 at 13:20
Then update your BIOS to the newest version (get it from the motherboard/laptop manufacturer site).
– N0rbert
Jan 8 at 13:23
I did this and when I got to the part about Flashing the system it said that my BIOS was on a higher system than the one in the update file, so I canceled the upgrade or 'downgrade'. My computer is refurbished. I wonder if that has anything to do with it.
– Hans
Jan 8 at 14:00
Okay, I believe I caused the issue when I changed the default boot option for GRUB and updated it. I am using the Kali GRUB menu, which complicates things, since my problem is with Ubuntu. I believe the problem is with the initramfs, but I can't figure out how to fix it. I can boot into Ubuntu on one of my older kernels, but still cannot with the current one. Suggestions would be appreciated for fixing the problem.
– Hans
Jan 8 at 21:09
add a comment |
2
Possible duplicate of [Firmware Bug]: TSC_DEADLINE disabled due to Errata - what should I do about this?
– N0rbert
Jan 8 at 13:18
This is different because I am stuck outside of the system and can't get in. Not just reading through the logs.
– Hans
Jan 8 at 13:20
Then update your BIOS to the newest version (get it from the motherboard/laptop manufacturer site).
– N0rbert
Jan 8 at 13:23
I did this and when I got to the part about Flashing the system it said that my BIOS was on a higher system than the one in the update file, so I canceled the upgrade or 'downgrade'. My computer is refurbished. I wonder if that has anything to do with it.
– Hans
Jan 8 at 14:00
Okay, I believe I caused the issue when I changed the default boot option for GRUB and updated it. I am using the Kali GRUB menu, which complicates things, since my problem is with Ubuntu. I believe the problem is with the initramfs, but I can't figure out how to fix it. I can boot into Ubuntu on one of my older kernels, but still cannot with the current one. Suggestions would be appreciated for fixing the problem.
– Hans
Jan 8 at 21:09
2
2
Possible duplicate of [Firmware Bug]: TSC_DEADLINE disabled due to Errata - what should I do about this?
– N0rbert
Jan 8 at 13:18
Possible duplicate of [Firmware Bug]: TSC_DEADLINE disabled due to Errata - what should I do about this?
– N0rbert
Jan 8 at 13:18
This is different because I am stuck outside of the system and can't get in. Not just reading through the logs.
– Hans
Jan 8 at 13:20
This is different because I am stuck outside of the system and can't get in. Not just reading through the logs.
– Hans
Jan 8 at 13:20
Then update your BIOS to the newest version (get it from the motherboard/laptop manufacturer site).
– N0rbert
Jan 8 at 13:23
Then update your BIOS to the newest version (get it from the motherboard/laptop manufacturer site).
– N0rbert
Jan 8 at 13:23
I did this and when I got to the part about Flashing the system it said that my BIOS was on a higher system than the one in the update file, so I canceled the upgrade or 'downgrade'. My computer is refurbished. I wonder if that has anything to do with it.
– Hans
Jan 8 at 14:00
I did this and when I got to the part about Flashing the system it said that my BIOS was on a higher system than the one in the update file, so I canceled the upgrade or 'downgrade'. My computer is refurbished. I wonder if that has anything to do with it.
– Hans
Jan 8 at 14:00
Okay, I believe I caused the issue when I changed the default boot option for GRUB and updated it. I am using the Kali GRUB menu, which complicates things, since my problem is with Ubuntu. I believe the problem is with the initramfs, but I can't figure out how to fix it. I can boot into Ubuntu on one of my older kernels, but still cannot with the current one. Suggestions would be appreciated for fixing the problem.
– Hans
Jan 8 at 21:09
Okay, I believe I caused the issue when I changed the default boot option for GRUB and updated it. I am using the Kali GRUB menu, which complicates things, since my problem is with Ubuntu. I believe the problem is with the initramfs, but I can't figure out how to fix it. I can boot into Ubuntu on one of my older kernels, but still cannot with the current one. Suggestions would be appreciated for fixing the problem.
– Hans
Jan 8 at 21:09
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%2f1107983%2fubuntu-18-04-having-kernel-panic-on-boot%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%2f1107983%2fubuntu-18-04-having-kernel-panic-on-boot%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
2
Possible duplicate of [Firmware Bug]: TSC_DEADLINE disabled due to Errata - what should I do about this?
– N0rbert
Jan 8 at 13:18
This is different because I am stuck outside of the system and can't get in. Not just reading through the logs.
– Hans
Jan 8 at 13:20
Then update your BIOS to the newest version (get it from the motherboard/laptop manufacturer site).
– N0rbert
Jan 8 at 13:23
I did this and when I got to the part about Flashing the system it said that my BIOS was on a higher system than the one in the update file, so I canceled the upgrade or 'downgrade'. My computer is refurbished. I wonder if that has anything to do with it.
– Hans
Jan 8 at 14:00
Okay, I believe I caused the issue when I changed the default boot option for GRUB and updated it. I am using the Kali GRUB menu, which complicates things, since my problem is with Ubuntu. I believe the problem is with the initramfs, but I can't figure out how to fix it. I can boot into Ubuntu on one of my older kernels, but still cannot with the current one. Suggestions would be appreciated for fixing the problem.
– Hans
Jan 8 at 21:09