Brian J Lopes <[EMAIL PROTECTED]> writes: > Haipeng Shen wrote: >> No. before I tried "top", I tried "ls", which generates response right >> away.
> I'm experiencing the same issue, although I would say that I'm also > having problems with ls. I tried restarting the ntp client to see if > the clock was slightly skewed (my previous inclination), but that didn't > seem to improve the situation. top is downright unresponsive for me. Something is interfering with scanning /proc and anything that touches it is being affected. I've seen this before and then it disappeared again and I don't remember what happened or changed to make it go away. If you run dmesg once the system is in this state, is there any interesting output at the end? -- Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
