Ubuntu Server 18.04 kernel panic on Linux 4.15.x kernel
I was using Ubuntu 14.04 Server then upgraded to Ubuntu 16.04 and then to the latest LTS version of Ubuntu 18.04 Server.
Updates changed the running kernel version too. Now my computer has two Linux kernels, 4.15.0-43 generic and 4.4.0-141-generic. The first option is 4.15.x and it's stuck at a kernel panic if it is selected.
Here are screenshots of the error:
And here is my installed kernels:
Kernel 4.4.0-141 boots successfully. but I'd like to use new version of Linux kernel.
Also there is another issue with Ubuntu 18.10. There was the same error, but after community updated Linux kernel version to 4.18.x the problems were gone.
18.04 kernel lts
|
show 4 more comments
I was using Ubuntu 14.04 Server then upgraded to Ubuntu 16.04 and then to the latest LTS version of Ubuntu 18.04 Server.
Updates changed the running kernel version too. Now my computer has two Linux kernels, 4.15.0-43 generic and 4.4.0-141-generic. The first option is 4.15.x and it's stuck at a kernel panic if it is selected.
Here are screenshots of the error:
And here is my installed kernels:
Kernel 4.4.0-141 boots successfully. but I'd like to use new version of Linux kernel.
Also there is another issue with Ubuntu 18.10. There was the same error, but after community updated Linux kernel version to 4.18.x the problems were gone.
18.04 kernel lts
The beginnig of the stack trace is missing. Try to scroll up (unix.stackexchange.com/questions/60382/…) and post the beginning of the trace
– Simon Sudler
Jan 10 at 11:35
None of key combinations worked. Maybe cause of It's not a VM?
– akikara
Jan 10 at 13:16
You need some why of capturing the beginning of that kernel panic... check if the VM has some means of logging the console output
– Simon Sudler
Jan 11 at 7:11
It is a real machine not VM. Can I check log files if exist from the working kernel 4.4?
– akikara
Jan 11 at 7:28
No. I assume the problem is the root file system. So there is no way for the kernel to write that logfile. Does the 4.15 recovery mode boot?
– Simon Sudler
Jan 11 at 7:30
|
show 4 more comments
I was using Ubuntu 14.04 Server then upgraded to Ubuntu 16.04 and then to the latest LTS version of Ubuntu 18.04 Server.
Updates changed the running kernel version too. Now my computer has two Linux kernels, 4.15.0-43 generic and 4.4.0-141-generic. The first option is 4.15.x and it's stuck at a kernel panic if it is selected.
Here are screenshots of the error:
And here is my installed kernels:
Kernel 4.4.0-141 boots successfully. but I'd like to use new version of Linux kernel.
Also there is another issue with Ubuntu 18.10. There was the same error, but after community updated Linux kernel version to 4.18.x the problems were gone.
18.04 kernel lts
I was using Ubuntu 14.04 Server then upgraded to Ubuntu 16.04 and then to the latest LTS version of Ubuntu 18.04 Server.
Updates changed the running kernel version too. Now my computer has two Linux kernels, 4.15.0-43 generic and 4.4.0-141-generic. The first option is 4.15.x and it's stuck at a kernel panic if it is selected.
Here are screenshots of the error:
And here is my installed kernels:
Kernel 4.4.0-141 boots successfully. but I'd like to use new version of Linux kernel.
Also there is another issue with Ubuntu 18.10. There was the same error, but after community updated Linux kernel version to 4.18.x the problems were gone.
18.04 kernel lts
18.04 kernel lts
edited Jan 24 at 22:39
karel
58.6k13128147
58.6k13128147
asked Jan 10 at 7:37
akikaraakikara
4281824
4281824
The beginnig of the stack trace is missing. Try to scroll up (unix.stackexchange.com/questions/60382/…) and post the beginning of the trace
– Simon Sudler
Jan 10 at 11:35
None of key combinations worked. Maybe cause of It's not a VM?
– akikara
Jan 10 at 13:16
You need some why of capturing the beginning of that kernel panic... check if the VM has some means of logging the console output
– Simon Sudler
Jan 11 at 7:11
It is a real machine not VM. Can I check log files if exist from the working kernel 4.4?
– akikara
Jan 11 at 7:28
No. I assume the problem is the root file system. So there is no way for the kernel to write that logfile. Does the 4.15 recovery mode boot?
– Simon Sudler
Jan 11 at 7:30
|
show 4 more comments
The beginnig of the stack trace is missing. Try to scroll up (unix.stackexchange.com/questions/60382/…) and post the beginning of the trace
– Simon Sudler
Jan 10 at 11:35
None of key combinations worked. Maybe cause of It's not a VM?
– akikara
Jan 10 at 13:16
You need some why of capturing the beginning of that kernel panic... check if the VM has some means of logging the console output
– Simon Sudler
Jan 11 at 7:11
It is a real machine not VM. Can I check log files if exist from the working kernel 4.4?
– akikara
Jan 11 at 7:28
No. I assume the problem is the root file system. So there is no way for the kernel to write that logfile. Does the 4.15 recovery mode boot?
– Simon Sudler
Jan 11 at 7:30
The beginnig of the stack trace is missing. Try to scroll up (unix.stackexchange.com/questions/60382/…) and post the beginning of the trace
– Simon Sudler
Jan 10 at 11:35
The beginnig of the stack trace is missing. Try to scroll up (unix.stackexchange.com/questions/60382/…) and post the beginning of the trace
– Simon Sudler
Jan 10 at 11:35
None of key combinations worked. Maybe cause of It's not a VM?
– akikara
Jan 10 at 13:16
None of key combinations worked. Maybe cause of It's not a VM?
– akikara
Jan 10 at 13:16
You need some why of capturing the beginning of that kernel panic... check if the VM has some means of logging the console output
– Simon Sudler
Jan 11 at 7:11
You need some why of capturing the beginning of that kernel panic... check if the VM has some means of logging the console output
– Simon Sudler
Jan 11 at 7:11
It is a real machine not VM. Can I check log files if exist from the working kernel 4.4?
– akikara
Jan 11 at 7:28
It is a real machine not VM. Can I check log files if exist from the working kernel 4.4?
– akikara
Jan 11 at 7:28
No. I assume the problem is the root file system. So there is no way for the kernel to write that logfile. Does the 4.15 recovery mode boot?
– Simon Sudler
Jan 11 at 7:30
No. I assume the problem is the root file system. So there is no way for the kernel to write that logfile. Does the 4.15 recovery mode boot?
– Simon Sudler
Jan 11 at 7:30
|
show 4 more comments
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%2f1108497%2fubuntu-server-18-04-kernel-panic-on-linux-4-15-x-kernel%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%2f1108497%2fubuntu-server-18-04-kernel-panic-on-linux-4-15-x-kernel%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
The beginnig of the stack trace is missing. Try to scroll up (unix.stackexchange.com/questions/60382/…) and post the beginning of the trace
– Simon Sudler
Jan 10 at 11:35
None of key combinations worked. Maybe cause of It's not a VM?
– akikara
Jan 10 at 13:16
You need some why of capturing the beginning of that kernel panic... check if the VM has some means of logging the console output
– Simon Sudler
Jan 11 at 7:11
It is a real machine not VM. Can I check log files if exist from the working kernel 4.4?
– akikara
Jan 11 at 7:28
No. I assume the problem is the root file system. So there is no way for the kernel to write that logfile. Does the 4.15 recovery mode boot?
– Simon Sudler
Jan 11 at 7:30