How to debug a completely stuck kernel?
Clash 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?
fedora linux-kernel debugging
add a comment |Â
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?
fedora linux-kernel debugging
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
add a comment |Â
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?
fedora linux-kernel debugging
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?
fedora linux-kernel debugging
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
add a comment |Â
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
add a comment |Â
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
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
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
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
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
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
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