Why is my terminal freezing up?
Sometimes when my terminal freezes up and it will not let me type. I can not identify any causes, nor how to diagnose. Any suggestions?
Thanks!
GNOME Terminal 2.30.2 on Ubuntu 10.04
10.04 command-line freeze
add a comment |
Sometimes when my terminal freezes up and it will not let me type. I can not identify any causes, nor how to diagnose. Any suggestions?
Thanks!
GNOME Terminal 2.30.2 on Ubuntu 10.04
10.04 command-line freeze
2
usually when the terminal freezes it is caused by another application in the background using too many resources, like the CPU or Disk I/O. If you runtop
in a terminal, you should be able to locate the problem easily.
– RolandiXor♦
Nov 30 '10 at 2:37
@roland - sounds like a catch-22, but good advice since sometimes when one terminal is frozen I can open another and it will work.
– David LeBauer
Nov 30 '10 at 2:38
I Know right? :) It is a bit of a catch-22, but it often works for me.
– RolandiXor♦
Nov 30 '10 at 2:46
add a comment |
Sometimes when my terminal freezes up and it will not let me type. I can not identify any causes, nor how to diagnose. Any suggestions?
Thanks!
GNOME Terminal 2.30.2 on Ubuntu 10.04
10.04 command-line freeze
Sometimes when my terminal freezes up and it will not let me type. I can not identify any causes, nor how to diagnose. Any suggestions?
Thanks!
GNOME Terminal 2.30.2 on Ubuntu 10.04
10.04 command-line freeze
10.04 command-line freeze
asked Nov 30 '10 at 2:24
David LeBauerDavid LeBauer
84741335
84741335
2
usually when the terminal freezes it is caused by another application in the background using too many resources, like the CPU or Disk I/O. If you runtop
in a terminal, you should be able to locate the problem easily.
– RolandiXor♦
Nov 30 '10 at 2:37
@roland - sounds like a catch-22, but good advice since sometimes when one terminal is frozen I can open another and it will work.
– David LeBauer
Nov 30 '10 at 2:38
I Know right? :) It is a bit of a catch-22, but it often works for me.
– RolandiXor♦
Nov 30 '10 at 2:46
add a comment |
2
usually when the terminal freezes it is caused by another application in the background using too many resources, like the CPU or Disk I/O. If you runtop
in a terminal, you should be able to locate the problem easily.
– RolandiXor♦
Nov 30 '10 at 2:37
@roland - sounds like a catch-22, but good advice since sometimes when one terminal is frozen I can open another and it will work.
– David LeBauer
Nov 30 '10 at 2:38
I Know right? :) It is a bit of a catch-22, but it often works for me.
– RolandiXor♦
Nov 30 '10 at 2:46
2
2
usually when the terminal freezes it is caused by another application in the background using too many resources, like the CPU or Disk I/O. If you run
top
in a terminal, you should be able to locate the problem easily.– RolandiXor♦
Nov 30 '10 at 2:37
usually when the terminal freezes it is caused by another application in the background using too many resources, like the CPU or Disk I/O. If you run
top
in a terminal, you should be able to locate the problem easily.– RolandiXor♦
Nov 30 '10 at 2:37
@roland - sounds like a catch-22, but good advice since sometimes when one terminal is frozen I can open another and it will work.
– David LeBauer
Nov 30 '10 at 2:38
@roland - sounds like a catch-22, but good advice since sometimes when one terminal is frozen I can open another and it will work.
– David LeBauer
Nov 30 '10 at 2:38
I Know right? :) It is a bit of a catch-22, but it often works for me.
– RolandiXor♦
Nov 30 '10 at 2:46
I Know right? :) It is a bit of a catch-22, but it often works for me.
– RolandiXor♦
Nov 30 '10 at 2:46
add a comment |
3 Answers
3
active
oldest
votes
A good general way to diagnose mysterious hangs:
- open a(nother) terminal, and use
ps axo pid,wchan:32,cmd
to find the other process id - note the
wchan
column, which should tell you whether it's stuck in the kernel - run
sudo strace -p PID
inserting the pid of that process; paste that into a bug report or question
If there's anything aside from just a dash in the wchan column, then the process is in the kernel doing something. Some typical values:
futex_wait_queue_me
- waiting on a futex for another thread in the same process
poll_schedule_timeout
- waiting for network or interprocess communication, or just sleeping for a while
pipe_wait
- reading/writing a pipe
There are thousands of possibilities so I can't list them all. See What is the "Waiting Channel" of a process? for more.
Very useful for general purpose bug tracking. Can you please update your answer with some extensive description ? What message in wchan column indicates a program that is stuck in the kernel ?
– Salih Emin
Nov 30 '10 at 13:19
Thanks, Salih. Maybe we should have another question about how in general to diagnose hangs?
– poolie
Nov 30 '10 at 21:42
If people are curious about any other wchan values, please add a comment.
– poolie
Mar 14 '12 at 0:37
Anywchan
means the process is waiting in the kernel. If it stays there for a long time and for no good reason like listening for network io, then it's stuck. ;)
– poolie
Dec 11 '15 at 6:08
add a comment |
Did you press Ctrl+S by any chance? It's the terminal pause key that stops all output until you press Ctrl-Q to resume.
add a comment |
Mine is weird whenever I install something it fails and freezes and I have to restart ubuntu...
New contributor
add a comment |
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%2f15437%2fwhy-is-my-terminal-freezing-up%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
A good general way to diagnose mysterious hangs:
- open a(nother) terminal, and use
ps axo pid,wchan:32,cmd
to find the other process id - note the
wchan
column, which should tell you whether it's stuck in the kernel - run
sudo strace -p PID
inserting the pid of that process; paste that into a bug report or question
If there's anything aside from just a dash in the wchan column, then the process is in the kernel doing something. Some typical values:
futex_wait_queue_me
- waiting on a futex for another thread in the same process
poll_schedule_timeout
- waiting for network or interprocess communication, or just sleeping for a while
pipe_wait
- reading/writing a pipe
There are thousands of possibilities so I can't list them all. See What is the "Waiting Channel" of a process? for more.
Very useful for general purpose bug tracking. Can you please update your answer with some extensive description ? What message in wchan column indicates a program that is stuck in the kernel ?
– Salih Emin
Nov 30 '10 at 13:19
Thanks, Salih. Maybe we should have another question about how in general to diagnose hangs?
– poolie
Nov 30 '10 at 21:42
If people are curious about any other wchan values, please add a comment.
– poolie
Mar 14 '12 at 0:37
Anywchan
means the process is waiting in the kernel. If it stays there for a long time and for no good reason like listening for network io, then it's stuck. ;)
– poolie
Dec 11 '15 at 6:08
add a comment |
A good general way to diagnose mysterious hangs:
- open a(nother) terminal, and use
ps axo pid,wchan:32,cmd
to find the other process id - note the
wchan
column, which should tell you whether it's stuck in the kernel - run
sudo strace -p PID
inserting the pid of that process; paste that into a bug report or question
If there's anything aside from just a dash in the wchan column, then the process is in the kernel doing something. Some typical values:
futex_wait_queue_me
- waiting on a futex for another thread in the same process
poll_schedule_timeout
- waiting for network or interprocess communication, or just sleeping for a while
pipe_wait
- reading/writing a pipe
There are thousands of possibilities so I can't list them all. See What is the "Waiting Channel" of a process? for more.
Very useful for general purpose bug tracking. Can you please update your answer with some extensive description ? What message in wchan column indicates a program that is stuck in the kernel ?
– Salih Emin
Nov 30 '10 at 13:19
Thanks, Salih. Maybe we should have another question about how in general to diagnose hangs?
– poolie
Nov 30 '10 at 21:42
If people are curious about any other wchan values, please add a comment.
– poolie
Mar 14 '12 at 0:37
Anywchan
means the process is waiting in the kernel. If it stays there for a long time and for no good reason like listening for network io, then it's stuck. ;)
– poolie
Dec 11 '15 at 6:08
add a comment |
A good general way to diagnose mysterious hangs:
- open a(nother) terminal, and use
ps axo pid,wchan:32,cmd
to find the other process id - note the
wchan
column, which should tell you whether it's stuck in the kernel - run
sudo strace -p PID
inserting the pid of that process; paste that into a bug report or question
If there's anything aside from just a dash in the wchan column, then the process is in the kernel doing something. Some typical values:
futex_wait_queue_me
- waiting on a futex for another thread in the same process
poll_schedule_timeout
- waiting for network or interprocess communication, or just sleeping for a while
pipe_wait
- reading/writing a pipe
There are thousands of possibilities so I can't list them all. See What is the "Waiting Channel" of a process? for more.
A good general way to diagnose mysterious hangs:
- open a(nother) terminal, and use
ps axo pid,wchan:32,cmd
to find the other process id - note the
wchan
column, which should tell you whether it's stuck in the kernel - run
sudo strace -p PID
inserting the pid of that process; paste that into a bug report or question
If there's anything aside from just a dash in the wchan column, then the process is in the kernel doing something. Some typical values:
futex_wait_queue_me
- waiting on a futex for another thread in the same process
poll_schedule_timeout
- waiting for network or interprocess communication, or just sleeping for a while
pipe_wait
- reading/writing a pipe
There are thousands of possibilities so I can't list them all. See What is the "Waiting Channel" of a process? for more.
edited Apr 13 '17 at 12:24
Community♦
1
1
answered Nov 30 '10 at 3:12
pooliepoolie
7,30823158
7,30823158
Very useful for general purpose bug tracking. Can you please update your answer with some extensive description ? What message in wchan column indicates a program that is stuck in the kernel ?
– Salih Emin
Nov 30 '10 at 13:19
Thanks, Salih. Maybe we should have another question about how in general to diagnose hangs?
– poolie
Nov 30 '10 at 21:42
If people are curious about any other wchan values, please add a comment.
– poolie
Mar 14 '12 at 0:37
Anywchan
means the process is waiting in the kernel. If it stays there for a long time and for no good reason like listening for network io, then it's stuck. ;)
– poolie
Dec 11 '15 at 6:08
add a comment |
Very useful for general purpose bug tracking. Can you please update your answer with some extensive description ? What message in wchan column indicates a program that is stuck in the kernel ?
– Salih Emin
Nov 30 '10 at 13:19
Thanks, Salih. Maybe we should have another question about how in general to diagnose hangs?
– poolie
Nov 30 '10 at 21:42
If people are curious about any other wchan values, please add a comment.
– poolie
Mar 14 '12 at 0:37
Anywchan
means the process is waiting in the kernel. If it stays there for a long time and for no good reason like listening for network io, then it's stuck. ;)
– poolie
Dec 11 '15 at 6:08
Very useful for general purpose bug tracking. Can you please update your answer with some extensive description ? What message in wchan column indicates a program that is stuck in the kernel ?
– Salih Emin
Nov 30 '10 at 13:19
Very useful for general purpose bug tracking. Can you please update your answer with some extensive description ? What message in wchan column indicates a program that is stuck in the kernel ?
– Salih Emin
Nov 30 '10 at 13:19
Thanks, Salih. Maybe we should have another question about how in general to diagnose hangs?
– poolie
Nov 30 '10 at 21:42
Thanks, Salih. Maybe we should have another question about how in general to diagnose hangs?
– poolie
Nov 30 '10 at 21:42
If people are curious about any other wchan values, please add a comment.
– poolie
Mar 14 '12 at 0:37
If people are curious about any other wchan values, please add a comment.
– poolie
Mar 14 '12 at 0:37
Any
wchan
means the process is waiting in the kernel. If it stays there for a long time and for no good reason like listening for network io, then it's stuck. ;)– poolie
Dec 11 '15 at 6:08
Any
wchan
means the process is waiting in the kernel. If it stays there for a long time and for no good reason like listening for network io, then it's stuck. ;)– poolie
Dec 11 '15 at 6:08
add a comment |
Did you press Ctrl+S by any chance? It's the terminal pause key that stops all output until you press Ctrl-Q to resume.
add a comment |
Did you press Ctrl+S by any chance? It's the terminal pause key that stops all output until you press Ctrl-Q to resume.
add a comment |
Did you press Ctrl+S by any chance? It's the terminal pause key that stops all output until you press Ctrl-Q to resume.
Did you press Ctrl+S by any chance? It's the terminal pause key that stops all output until you press Ctrl-Q to resume.
answered Nov 30 '10 at 12:16
Marius GedminasMarius Gedminas
7,42573647
7,42573647
add a comment |
add a comment |
Mine is weird whenever I install something it fails and freezes and I have to restart ubuntu...
New contributor
add a comment |
Mine is weird whenever I install something it fails and freezes and I have to restart ubuntu...
New contributor
add a comment |
Mine is weird whenever I install something it fails and freezes and I have to restart ubuntu...
New contributor
Mine is weird whenever I install something it fails and freezes and I have to restart ubuntu...
New contributor
New contributor
answered 29 mins ago
CosmicskylightCosmicskylight
1
1
New contributor
New contributor
add a comment |
add a comment |
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%2f15437%2fwhy-is-my-terminal-freezing-up%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
2
usually when the terminal freezes it is caused by another application in the background using too many resources, like the CPU or Disk I/O. If you run
top
in a terminal, you should be able to locate the problem easily.– RolandiXor♦
Nov 30 '10 at 2:37
@roland - sounds like a catch-22, but good advice since sometimes when one terminal is frozen I can open another and it will work.
– David LeBauer
Nov 30 '10 at 2:38
I Know right? :) It is a bit of a catch-22, but it often works for me.
– RolandiXor♦
Nov 30 '10 at 2:46