Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

There is a topic by essentially the same name, but my answer leads to another question which I would like answered so... My case is as follows:

I connect through SSH to my server... no problems for many months on Ubuntu Server 9.04. Eventually I decided to updgrade and straight away I get the 10 minutes freeze problem. I went through all the possible fixes (many can be found here but my quick fix, the only that worked, leaves me with no real answer as to why and how to properly correct it...

As ridiculous as it sounds... while I leave a keyboard plugged in... it runs without flaw.

Can anyone make sense of this?

For the sake of completeness, (although none of the following made any difference upon subsequent completion), some of the permanent changes I have made while trying to correct the issue are: replacing samba config file with 9.04 backup, booting with noapic and modifying sysctl.conf, just uncommenting additional settings for enhanced security.

share|improve this question
The first thing you should do is to look through your /var/log/syslog, and share it with us ;) – kolypto Nov 26 '09 at 2:37
I've had this happen to me, especially with a flaky KVM. The solution was to plug a keyboard in to it. ;) – Kyle Hodgson Nov 26 '09 at 4:53

Hard to help without additional info.

To narrow down the issue: Please provide the end of /var/log/syslog, there may be something in there.

Also, in case the system crashes so hard that even /var/log/syslog can not be written, try switching to a virtual console if in X, and leave it running until it hangs. Any kernel trouble should also be printed to a virtual console.

share|improve this answer
Ok, before I post more... this strikes me as possibly relevant to the keyboard... I managed to recreate the freeze by unplugging the keyboard again and rebooting... but upon checking the last entries of the syslog... well, the last entry to be exact... Do you think the following could point to the cause? – L33tCh Nov 27 '09 at 0:03
Nov 26 23:56:09 server console-kit-daemon[616]: WARNING: Couldn't read /proc/599/environ: Failed to open file '/proc/599/environ': No such file or directory – L33tCh Nov 27 '09 at 0:04
A few other points, X is not installed and I have never, (until this issue,) used a peripheral or monitor on this box since it's initial install. – L33tCh Nov 27 '09 at 0:05
Ok, it now froze with the keyboard... looking back I'm wondering why I didn't let sleeping dogs lie... Here was the last entry in the log this time.. nearly 10 minutes after the previous entries: Nov 27 00:17:01 server CRON[1986]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) – L33tCh Nov 27 '09 at 0:25
Sorry, these log entries all look perfectly normal. No clue really... – sleske Nov 30 '09 at 9:31

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.