Ask Ubuntu is a question and answer site for Ubuntu users and developers. It's 100% free.

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

I have problems when I leave computer on during the night, when I resume it in the morning, it becomes very slow, I often wait for few minutes until login form renders, when I login, apps freeze randomly and I must restart it in order to work normally.

What can be the problem?

share|improve this question
Did you check for a) high disk activity and b) memory usage? I had a similar problem a few weeks ago (which looks like solved itself with some updates coming in from the repos) -- you might check this question for details and possible steps.. – Izzy Jul 12 '12 at 11:03
I checked, no memory or CPU overloads. Didn't check HDD activity, how to check that? Thanks. – umpirsky Jul 12 '12 at 13:17
Easiest way: check the LED attached and listen to the noise (grin). Without physical approximity, and to figure out who is doing all the business: Take a look at iostat (see also: iostat short description and screenshots. If it's not installed, it ships with the sysstat package (so sudo apt-get install sysstat to get it). – Izzy Jul 12 '12 at 13:37
It got hanging untill it render login form for 2 minutes, then it worked fine after login. Here is output of iostat – umpirsky Jul 13 '12 at 6:21
And it got frozen after few minutes, so I must restart. I disabled sleep and screen locking to prevent this. BTW, after waking from sleep, hard drive LED was glowing all the time, non stop! – umpirsky Jul 13 '12 at 6:35
up vote 1 down vote accepted

Solution as extracted from the comments:

Steps to find the cause involve checking...

  • memory/cpu usage (e.g. using top to look at the processes using most of it)
  • disk activity (first check the disk LED, then iotop from the iotop package proves helpful)

In most cases, one of these two steps identify the process lagging the system. Depending on what it is, further actions can be evaluated (stopping/killing that process or, as in this case, re-organize cron jobs causing heavvy activity to not have them all run at the same time in parallel).

share|improve this answer
I will accept it next week, if problem is solved, thanks ;) – umpirsky Jul 13 '12 at 9:32
You're welcome -- glad I could help! – Izzy Jul 13 '12 at 9:55

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.