Kernel panic not syncing : System is deadlocked on memory
0
I updated my Ubuntu 14.04 kernel to 4.19, however,when I reboot there's a error: Kernel panic - not syncing: System is deadlocked on memory.
It remains there, and I don't know what to do.
- I have made my kernel several times and installed the modules,there's no error show in the old terminal.
- I used GParted to enlarge my dev/sda1,and I have set the Swap area, all done.
- Everything is pretty well about the old kernel. I can login and use smoothly.
14.04 boot kernel compiling
edited Jan 5 at 12:19
Zanna
50.4k13133241
asked Jan 5 at 3:25
wjrforcyberwjrforcyber
11
|
show 3 more comments
0
I updated my Ubuntu 14.04 kernel to 4.19, however,when I reboot there's a error: Kernel panic - not syncing: System is deadlocked on memory.
It remains there, and I don't know what to do.
- I have made my kernel several times and installed the modules,there's no error show in the old terminal.
- I used GParted to enlarge my dev/sda1,and I have set the Swap area, all done.
- Everything is pretty well about the old kernel. I can login and use smoothly.
14.04 boot kernel compiling
edited Jan 5 at 12:19
Zanna
50.4k13133241
asked Jan 5 at 3:25
wjrforcyberwjrforcyber
11
How did you upgrade the kernel? Also, why did you want to use the newer kernel? Any problem with just using the stock one? There might be an easier way to get the feature(s) you need from the newer kernel.
– Zanna
Jan 5 at 10:09
I installed a new one linux-4.19,I reboot and want to use the new one because I added a syscall in linux-4.19...actually,this is my homework and I have to make it right...
– wjrforcyber
Jan 5 at 10:23
yeah but how did you install it? what process did you follow? It seems like you did something wrong in the configuration, but we can't see what it was since you haven't given any info... A deadlock means processes are waiting for each other so that none of them can start...
– Zanna
Jan 5 at 10:30
Command I have used:#cp /boot/config-**** .config; # make menuconfig;#make -j4;#make modules_install ;#make install;#reboot;As for the syscall,I just add a very simple helloword in the sys.c and I have added it in the syscalls.h and syscall_64.tbl. Everything works well in the old one...I really don't know.
– wjrforcyber
Jan 5 at 10:38
well what do you do inmake menuconfig:) ? Really you are not giving enough information for anyone to help you! I would expect to see in your question (not in the comments) every command you have run and any warnings frommake(teeout to a file if you don't want to sit and watch it). Does this kernel build and boot without you adding your patch and whatever you do inmake menuconfig? The vanilla kernel (if that's what you're building - you haven't said!) will be very light on drivers compared to the Ubuntu kernel, might not have everything for your device. Also why compile as root?
– Zanna
Jan 5 at 12:17
|
show 3 more comments
0
0
0
I updated my Ubuntu 14.04 kernel to 4.19, however,when I reboot there's a error: Kernel panic - not syncing: System is deadlocked on memory.
It remains there, and I don't know what to do.
- I have made my kernel several times and installed the modules,there's no error show in the old terminal.
- I used GParted to enlarge my dev/sda1,and I have set the Swap area, all done.
- Everything is pretty well about the old kernel. I can login and use smoothly.
14.04 boot kernel compiling
edited Jan 5 at 12:19
Zanna
50.4k13133241
asked Jan 5 at 3:25
wjrforcyberwjrforcyber
11
I updated my Ubuntu 14.04 kernel to 4.19, however,when I reboot there's a error: Kernel panic - not syncing: System is deadlocked on memory.
It remains there, and I don't know what to do.
- I have made my kernel several times and installed the modules,there's no error show in the old terminal.
- I used GParted to enlarge my dev/sda1,and I have set the Swap area, all done.
- Everything is pretty well about the old kernel. I can login and use smoothly.
14.04 boot kernel compiling
14.04 boot kernel compiling
edited Jan 5 at 12:19
Zanna
50.4k13133241
asked Jan 5 at 3:25
wjrforcyberwjrforcyber
11
edited Jan 5 at 12:19
Zanna
50.4k13133241
asked Jan 5 at 3:25
wjrforcyberwjrforcyber
11
edited Jan 5 at 12:19
Zanna
50.4k13133241
edited Jan 5 at 12:19
Zanna
50.4k13133241
edited Jan 5 at 12:19
Zanna
50.4k13133241
50.4k13133241
asked Jan 5 at 3:25
wjrforcyberwjrforcyber
11
asked Jan 5 at 3:25
wjrforcyberwjrforcyber
11
asked Jan 5 at 3:25
wjrforcyberwjrforcyber
11
11
How did you upgrade the kernel? Also, why did you want to use the newer kernel? Any problem with just using the stock one? There might be an easier way to get the feature(s) you need from the newer kernel.
– Zanna
Jan 5 at 10:09
I installed a new one linux-4.19,I reboot and want to use the new one because I added a syscall in linux-4.19...actually,this is my homework and I have to make it right...
– wjrforcyber
Jan 5 at 10:23
yeah but how did you install it? what process did you follow? It seems like you did something wrong in the configuration, but we can't see what it was since you haven't given any info... A deadlock means processes are waiting for each other so that none of them can start...
– Zanna
Jan 5 at 10:30
Command I have used:#cp /boot/config-**** .config; # make menuconfig;#make -j4;#make modules_install ;#make install;#reboot;As for the syscall,I just add a very simple helloword in the sys.c and I have added it in the syscalls.h and syscall_64.tbl. Everything works well in the old one...I really don't know.
– wjrforcyber
Jan 5 at 10:38
well what do you do inmake menuconfig:) ? Really you are not giving enough information for anyone to help you! I would expect to see in your question (not in the comments) every command you have run and any warnings frommake(teeout to a file if you don't want to sit and watch it). Does this kernel build and boot without you adding your patch and whatever you do inmake menuconfig? The vanilla kernel (if that's what you're building - you haven't said!) will be very light on drivers compared to the Ubuntu kernel, might not have everything for your device. Also why compile as root?
– Zanna
Jan 5 at 12:17
|
show 3 more comments
How did you upgrade the kernel? Also, why did you want to use the newer kernel? Any problem with just using the stock one? There might be an easier way to get the feature(s) you need from the newer kernel.
– Zanna
Jan 5 at 10:09
I installed a new one linux-4.19,I reboot and want to use the new one because I added a syscall in linux-4.19...actually,this is my homework and I have to make it right...
– wjrforcyber
Jan 5 at 10:23
yeah but how did you install it? what process did you follow? It seems like you did something wrong in the configuration, but we can't see what it was since you haven't given any info... A deadlock means processes are waiting for each other so that none of them can start...
– Zanna
Jan 5 at 10:30
Command I have used:#cp /boot/config-**** .config; # make menuconfig;#make -j4;#make modules_install ;#make install;#reboot;As for the syscall,I just add a very simple helloword in the sys.c and I have added it in the syscalls.h and syscall_64.tbl. Everything works well in the old one...I really don't know.
– wjrforcyber
Jan 5 at 10:38
well what do you do inmake menuconfig:) ? Really you are not giving enough information for anyone to help you! I would expect to see in your question (not in the comments) every command you have run and any warnings frommake(teeout to a file if you don't want to sit and watch it). Does this kernel build and boot without you adding your patch and whatever you do inmake menuconfig? The vanilla kernel (if that's what you're building - you haven't said!) will be very light on drivers compared to the Ubuntu kernel, might not have everything for your device. Also why compile as root?
– Zanna
Jan 5 at 12:17
How did you upgrade the kernel? Also, why did you want to use the newer kernel? Any problem with just using the stock one? There might be an easier way to get the feature(s) you need from the newer kernel.
– Zanna
Jan 5 at 10:09
How did you upgrade the kernel? Also, why did you want to use the newer kernel? Any problem with just using the stock one? There might be an easier way to get the feature(s) you need from the newer kernel.
– Zanna
Jan 5 at 10:09
I installed a new one linux-4.19,I reboot and want to use the new one because I added a syscall in linux-4.19...actually,this is my homework and I have to make it right...
– wjrforcyber
Jan 5 at 10:23
I installed a new one linux-4.19,I reboot and want to use the new one because I added a syscall in linux-4.19...actually,this is my homework and I have to make it right...
– wjrforcyber
Jan 5 at 10:23
yeah but how did you install it? what process did you follow? It seems like you did something wrong in the configuration, but we can't see what it was since you haven't given any info... A deadlock means processes are waiting for each other so that none of them can start...
– Zanna
Jan 5 at 10:30
yeah but how did you install it? what process did you follow? It seems like you did something wrong in the configuration, but we can't see what it was since you haven't given any info... A deadlock means processes are waiting for each other so that none of them can start...
– Zanna
Jan 5 at 10:30
Command I have used:
#cp /boot/config-**** .config; # make menuconfig;#make -j4;#make modules_install ;#make install;#reboot;As for the syscall,I just add a very simple helloword in the sys.c and I have added it in the syscalls.h and syscall_64.tbl. Everything works well in the old one...I really don't know.– wjrforcyber
Jan 5 at 10:38
Command I have used:
#cp /boot/config-**** .config; # make menuconfig;#make -j4;#make modules_install ;#make install;#reboot;As for the syscall,I just add a very simple helloword in the sys.c and I have added it in the syscalls.h and syscall_64.tbl. Everything works well in the old one...I really don't know.– wjrforcyber
Jan 5 at 10:38
well what do you do in
make menuconfig :) ? Really you are not giving enough information for anyone to help you! I would expect to see in your question (not in the comments) every command you have run and any warnings from make (tee out to a file if you don't want to sit and watch it). Does this kernel build and boot without you adding your patch and whatever you do in make menuconfig? The vanilla kernel (if that's what you're building - you haven't said!) will be very light on drivers compared to the Ubuntu kernel, might not have everything for your device. Also why compile as root?– Zanna
Jan 5 at 12:17
well what do you do in
make menuconfig :) ? Really you are not giving enough information for anyone to help you! I would expect to see in your question (not in the comments) every command you have run and any warnings from make (tee out to a file if you don't want to sit and watch it). Does this kernel build and boot without you adding your patch and whatever you do in make menuconfig? The vanilla kernel (if that's what you're building - you haven't said!) will be very light on drivers compared to the Ubuntu kernel, might not have everything for your device. Also why compile as root?– Zanna
Jan 5 at 12:17
|
show 3 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
});
}
});
draft saved
draft discarded
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%2f1107077%2fkernel-panic-not-syncing-system-is-deadlocked-on-memory%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
draft saved
draft discarded
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.
draft saved
draft discarded
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%2f1107077%2fkernel-panic-not-syncing-system-is-deadlocked-on-memory%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
How did you upgrade the kernel? Also, why did you want to use the newer kernel? Any problem with just using the stock one? There might be an easier way to get the feature(s) you need from the newer kernel.
– Zanna
Jan 5 at 10:09
I installed a new one linux-4.19,I reboot and want to use the new one because I added a syscall in linux-4.19...actually,this is my homework and I have to make it right...
– wjrforcyber
Jan 5 at 10:23
yeah but how did you install it? what process did you follow? It seems like you did something wrong in the configuration, but we can't see what it was since you haven't given any info... A deadlock means processes are waiting for each other so that none of them can start...
– Zanna
Jan 5 at 10:30
Command I have used:
#cp /boot/config-**** .config; # make menuconfig;#make -j4;#make modules_install ;#make install;#reboot;As for the syscall,I just add a very simple helloword in the sys.c and I have added it in the syscalls.h and syscall_64.tbl. Everything works well in the old one...I really don't know.– wjrforcyber
Jan 5 at 10:38
well what do you do in
make menuconfig:) ? Really you are not giving enough information for anyone to help you! I would expect to see in your question (not in the comments) every command you have run and any warnings frommake(teeout to a file if you don't want to sit and watch it). Does this kernel build and boot without you adding your patch and whatever you do inmake menuconfig? The vanilla kernel (if that's what you're building - you haven't said!) will be very light on drivers compared to the Ubuntu kernel, might not have everything for your device. Also why compile as root?– Zanna
Jan 5 at 12:17