How to debug a completely stuck kernel?

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
1
down vote

favorite












Running kernel 4.15 here from F27. Since I moved a week ago from 4.13 to 4.15, a highly threaded app I have been developing started to hang the kernel. Not always, but most of the times. I have an i7 cpu with 8 cores, 16 threads. When running my app with several threads, usually > 20, sooner or later I get my machine to hang and only a hard reboot will shutdown the PC.



Unfortunately there's no info in journalctl to analyze once I reboot the PC.



How can I understand what's going on to be able to report a bug or fix my app?







share|improve this question






















  • 2 things to get you started: en.wikipedia.org/wiki/Magic_SysRq_key (see the crashdump & backtrace keys) & google for "linux crashdump"
    – Patrick
    Mar 22 at 23:16











  • Related: unix.stackexchange.com/questions/287890/how-to-debug-linux-hang
    – Matheus Santana
    Mar 23 at 10:58










  • It'd be great presenting some logs (perhaps from the app itself or diagnosis tools) or even a minimal set of lines of code representing the app's core behavior.
    – Matheus Santana
    Mar 23 at 11:04














up vote
1
down vote

favorite












Running kernel 4.15 here from F27. Since I moved a week ago from 4.13 to 4.15, a highly threaded app I have been developing started to hang the kernel. Not always, but most of the times. I have an i7 cpu with 8 cores, 16 threads. When running my app with several threads, usually > 20, sooner or later I get my machine to hang and only a hard reboot will shutdown the PC.



Unfortunately there's no info in journalctl to analyze once I reboot the PC.



How can I understand what's going on to be able to report a bug or fix my app?







share|improve this question






















  • 2 things to get you started: en.wikipedia.org/wiki/Magic_SysRq_key (see the crashdump & backtrace keys) & google for "linux crashdump"
    – Patrick
    Mar 22 at 23:16











  • Related: unix.stackexchange.com/questions/287890/how-to-debug-linux-hang
    – Matheus Santana
    Mar 23 at 10:58










  • It'd be great presenting some logs (perhaps from the app itself or diagnosis tools) or even a minimal set of lines of code representing the app's core behavior.
    – Matheus Santana
    Mar 23 at 11:04












up vote
1
down vote

favorite









up vote
1
down vote

favorite











Running kernel 4.15 here from F27. Since I moved a week ago from 4.13 to 4.15, a highly threaded app I have been developing started to hang the kernel. Not always, but most of the times. I have an i7 cpu with 8 cores, 16 threads. When running my app with several threads, usually > 20, sooner or later I get my machine to hang and only a hard reboot will shutdown the PC.



Unfortunately there's no info in journalctl to analyze once I reboot the PC.



How can I understand what's going on to be able to report a bug or fix my app?







share|improve this question














Running kernel 4.15 here from F27. Since I moved a week ago from 4.13 to 4.15, a highly threaded app I have been developing started to hang the kernel. Not always, but most of the times. I have an i7 cpu with 8 cores, 16 threads. When running my app with several threads, usually > 20, sooner or later I get my machine to hang and only a hard reboot will shutdown the PC.



Unfortunately there's no info in journalctl to analyze once I reboot the PC.



How can I understand what's going on to be able to report a bug or fix my app?









share|improve this question













share|improve this question




share|improve this question








edited Mar 23 at 12:07









Matheus Santana

16911




16911










asked Mar 22 at 22:24









Paulo Matos

105129




105129











  • 2 things to get you started: en.wikipedia.org/wiki/Magic_SysRq_key (see the crashdump & backtrace keys) & google for "linux crashdump"
    – Patrick
    Mar 22 at 23:16











  • Related: unix.stackexchange.com/questions/287890/how-to-debug-linux-hang
    – Matheus Santana
    Mar 23 at 10:58










  • It'd be great presenting some logs (perhaps from the app itself or diagnosis tools) or even a minimal set of lines of code representing the app's core behavior.
    – Matheus Santana
    Mar 23 at 11:04
















  • 2 things to get you started: en.wikipedia.org/wiki/Magic_SysRq_key (see the crashdump & backtrace keys) & google for "linux crashdump"
    – Patrick
    Mar 22 at 23:16











  • Related: unix.stackexchange.com/questions/287890/how-to-debug-linux-hang
    – Matheus Santana
    Mar 23 at 10:58










  • It'd be great presenting some logs (perhaps from the app itself or diagnosis tools) or even a minimal set of lines of code representing the app's core behavior.
    – Matheus Santana
    Mar 23 at 11:04















2 things to get you started: en.wikipedia.org/wiki/Magic_SysRq_key (see the crashdump & backtrace keys) & google for "linux crashdump"
– Patrick
Mar 22 at 23:16





2 things to get you started: en.wikipedia.org/wiki/Magic_SysRq_key (see the crashdump & backtrace keys) & google for "linux crashdump"
– Patrick
Mar 22 at 23:16













Related: unix.stackexchange.com/questions/287890/how-to-debug-linux-hang
– Matheus Santana
Mar 23 at 10:58




Related: unix.stackexchange.com/questions/287890/how-to-debug-linux-hang
– Matheus Santana
Mar 23 at 10:58












It'd be great presenting some logs (perhaps from the app itself or diagnosis tools) or even a minimal set of lines of code representing the app's core behavior.
– Matheus Santana
Mar 23 at 11:04




It'd be great presenting some logs (perhaps from the app itself or diagnosis tools) or even a minimal set of lines of code representing the app's core behavior.
– Matheus Santana
Mar 23 at 11:04















active

oldest

votes











Your Answer







StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
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',
convertImagesToLinks: false,
noModals: false,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);








 

draft saved


draft discarded


















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f432953%2fhow-to-debug-a-completely-stuck-kernel%23new-answer', 'question_page');

);

Post as a guest



































active

oldest

votes













active

oldest

votes









active

oldest

votes






active

oldest

votes










 

draft saved


draft discarded


























 


draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f432953%2fhow-to-debug-a-completely-stuck-kernel%23new-answer', 'question_page');

);

Post as a guest













































































Popular posts from this blog

How to check contact read email or not when send email to Individual?

Christian Cage

How to properly install USB display driver for Fresco Logic FL2000DX on Ubuntu?