You are not logged in.

#1 2008-12-16 16:46:46

esh
Member
Registered: 2008-11-05
Posts: 28

Keyboard lock-ups, "blocked for more than 120 seconds"

Have been having a lot of problems today. This is a fairly new system (past couple of weeks) so I cannot speak too much from experience. When my system is maxed out (ie. all processors working) input gradually becomes intermittent until one cannot use the keyboard at all. Not even pressing the numlock causes any change. The mouse works fine. I tried changing the keyboard, and even putting in a USB keyboard but this made no difference despite showing as connected in dmesg via ssh. Also in dmesg I am getting a lot of

INFO: task ssh:11581 blocked for more than 120 seconds.
INFO: task bash:14204 blocked for more than 120 seconds.
INFO: task bash:14207 blocked for more than 120 seconds.
INFO: task xconsole:17030 blocked for more than 120 seconds.

Two processors just became free as jobs finished and now I can use the keyboard again. This is really very troublesome. I believe I am on kernel 2.6.27.4. Has anyone seen this before and has any suggestions?

Offline

#2 2008-12-17 10:37:25

esh
Member
Registered: 2008-11-05
Posts: 28

Re: Keyboard lock-ups, "blocked for more than 120 seconds"

I currently suspect the CFQ scheduler and have employed the anticipatory scheduler on all drives to see if this sorts the issue out.

Offline

#3 2009-11-17 15:22:02

esh
Member
Registered: 2008-11-05
Posts: 28

Re: Keyboard lock-ups, "blocked for more than 120 seconds"

Hate to bump my own threads but I still periodically get this issue over a year later. I don't always get the INFO messages in dmesg however. For example, it just happened with 7 processors working with NICE'd tasks and 1 free, and the keyboard was 'stuck' on pressing the space key. Any window I clicked on it would just act like the spacebar was held down. However, as soon as a process swapped to another CPU, the keyboard freed up again.

Offline

Board footer

Powered by FluxBB