How to troubleshoot a (near total) freeze?
Clash Royale CLAN TAG#URR8PPP
up vote
0
down vote
favorite
I'm running Gnome on Ubuntu 17.04. I had gnome-terminal in fullscreen, neovim in a tmux session, a background process compiling code, and Chromium running as well, when my system froze up on me. I could move the mouse cursor, barely, with extreme lag, but that's all I could do. I waited several minutes, then tried Ctrl-C, Ctrl-Alt-Delete, Alt-F2, but nothing responded.
Finally, I gave up and held down the power button until the machine shut down.
What I'm wondering is, how can I troubleshoot this? Is there something else I could have tried before forcing a shutdown? Are there logs I can inspect to see what happened? I tried journalctrl after rebooting, but it only shows logs from the current boot. I also see some log files in ~/.local/share/xorg/, but I'm not sure if they're relevant, or what to search for.
logs freeze troubleshooting
asked Nov 11 '17 at 3:51
ivan
650718
add a comment |Â
up vote
0
down vote
favorite
I'm running Gnome on Ubuntu 17.04. I had gnome-terminal in fullscreen, neovim in a tmux session, a background process compiling code, and Chromium running as well, when my system froze up on me. I could move the mouse cursor, barely, with extreme lag, but that's all I could do. I waited several minutes, then tried Ctrl-C, Ctrl-Alt-Delete, Alt-F2, but nothing responded.
Finally, I gave up and held down the power button until the machine shut down.
What I'm wondering is, how can I troubleshoot this? Is there something else I could have tried before forcing a shutdown? Are there logs I can inspect to see what happened? I tried journalctrl after rebooting, but it only shows logs from the current boot. I also see some log files in ~/.local/share/xorg/, but I'm not sure if they're relevant, or what to search for.
logs freeze troubleshooting
asked Nov 11 '17 at 3:51
ivan
650718
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I'm running Gnome on Ubuntu 17.04. I had gnome-terminal in fullscreen, neovim in a tmux session, a background process compiling code, and Chromium running as well, when my system froze up on me. I could move the mouse cursor, barely, with extreme lag, but that's all I could do. I waited several minutes, then tried Ctrl-C, Ctrl-Alt-Delete, Alt-F2, but nothing responded.
Finally, I gave up and held down the power button until the machine shut down.
What I'm wondering is, how can I troubleshoot this? Is there something else I could have tried before forcing a shutdown? Are there logs I can inspect to see what happened? I tried journalctrl after rebooting, but it only shows logs from the current boot. I also see some log files in ~/.local/share/xorg/, but I'm not sure if they're relevant, or what to search for.
logs freeze troubleshooting
asked Nov 11 '17 at 3:51
ivan
650718
I'm running Gnome on Ubuntu 17.04. I had gnome-terminal in fullscreen, neovim in a tmux session, a background process compiling code, and Chromium running as well, when my system froze up on me. I could move the mouse cursor, barely, with extreme lag, but that's all I could do. I waited several minutes, then tried Ctrl-C, Ctrl-Alt-Delete, Alt-F2, but nothing responded.
Finally, I gave up and held down the power button until the machine shut down.
What I'm wondering is, how can I troubleshoot this? Is there something else I could have tried before forcing a shutdown? Are there logs I can inspect to see what happened? I tried journalctrl after rebooting, but it only shows logs from the current boot. I also see some log files in ~/.local/share/xorg/, but I'm not sure if they're relevant, or what to search for.
logs freeze troubleshooting
asked Nov 11 '17 at 3:51
ivan
650718
asked Nov 11 '17 at 3:51
ivan
650718
asked Nov 11 '17 at 3:51
ivan
650718
asked Nov 11 '17 at 3:51
ivan
650718
650718
add a comment |Â
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
0
down vote
accepted
The following logs can help you debug your system from the last boot:
journalctl --boot=-1 | less
tail /var/log/syslog.1
tail /var/log/kern.log.1
tail /var/log/debug.1
tail /var/log/Xorg.0.log.old
answered Nov 11 '17 at 4:26
jdwolf
2,392116
Unfortunately, I didn't have logs persisting across boots. I've updated my journald configuration so if it happens again I'll have a better chance of getting insight into the issue.
– ivan
Nov 11 '17 at 12:33
Debian keeps logs by default. I assumed Ubuntu did as well. I think you should add your configuration change to the answer.
– jdwolf
Nov 11 '17 at 12:47
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
accepted
The following logs can help you debug your system from the last boot:
journalctl --boot=-1 | less
tail /var/log/syslog.1
tail /var/log/kern.log.1
tail /var/log/debug.1
tail /var/log/Xorg.0.log.old
answered Nov 11 '17 at 4:26
jdwolf
2,392116
Unfortunately, I didn't have logs persisting across boots. I've updated my journald configuration so if it happens again I'll have a better chance of getting insight into the issue.
– ivan
Nov 11 '17 at 12:33
Debian keeps logs by default. I assumed Ubuntu did as well. I think you should add your configuration change to the answer.
– jdwolf
Nov 11 '17 at 12:47
add a comment |Â
up vote
0
down vote
accepted
The following logs can help you debug your system from the last boot:
journalctl --boot=-1 | less
tail /var/log/syslog.1
tail /var/log/kern.log.1
tail /var/log/debug.1
tail /var/log/Xorg.0.log.old
answered Nov 11 '17 at 4:26
jdwolf
2,392116
Unfortunately, I didn't have logs persisting across boots. I've updated my journald configuration so if it happens again I'll have a better chance of getting insight into the issue.
– ivan
Nov 11 '17 at 12:33
Debian keeps logs by default. I assumed Ubuntu did as well. I think you should add your configuration change to the answer.
– jdwolf
Nov 11 '17 at 12:47
add a comment |Â
up vote
0
down vote
accepted
up vote
0
down vote
accepted
The following logs can help you debug your system from the last boot:
journalctl --boot=-1 | less
tail /var/log/syslog.1
tail /var/log/kern.log.1
tail /var/log/debug.1
tail /var/log/Xorg.0.log.old
answered Nov 11 '17 at 4:26
jdwolf
2,392116
The following logs can help you debug your system from the last boot:
journalctl --boot=-1 | less
tail /var/log/syslog.1
tail /var/log/kern.log.1
tail /var/log/debug.1
tail /var/log/Xorg.0.log.old
answered Nov 11 '17 at 4:26
jdwolf
2,392116
answered Nov 11 '17 at 4:26
jdwolf
2,392116
answered Nov 11 '17 at 4:26
jdwolf
2,392116
answered Nov 11 '17 at 4:26
jdwolf
2,392116
2,392116
Unfortunately, I didn't have logs persisting across boots. I've updated my journald configuration so if it happens again I'll have a better chance of getting insight into the issue.
– ivan
Nov 11 '17 at 12:33
Debian keeps logs by default. I assumed Ubuntu did as well. I think you should add your configuration change to the answer.
– jdwolf
Nov 11 '17 at 12:47
add a comment |Â
Unfortunately, I didn't have logs persisting across boots. I've updated my journald configuration so if it happens again I'll have a better chance of getting insight into the issue.
– ivan
Nov 11 '17 at 12:33
Debian keeps logs by default. I assumed Ubuntu did as well. I think you should add your configuration change to the answer.
– jdwolf
Nov 11 '17 at 12:47
Unfortunately, I didn't have logs persisting across boots. I've updated my journald configuration so if it happens again I'll have a better chance of getting insight into the issue.
– ivan
Nov 11 '17 at 12:33
Unfortunately, I didn't have logs persisting across boots. I've updated my journald configuration so if it happens again I'll have a better chance of getting insight into the issue.
– ivan
Nov 11 '17 at 12:33
Debian keeps logs by default. I assumed Ubuntu did as well. I think you should add your configuration change to the answer.
– jdwolf
Nov 11 '17 at 12:47
Debian keeps logs by default. I assumed Ubuntu did as well. I think you should add your configuration change to the answer.
– jdwolf
Nov 11 '17 at 12:47
add a comment |Â
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%2f403860%2fhow-to-troubleshoot-a-near-total-freeze%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