[gdm-list] Keyboard becoming unresponsive?

[Simon Bowden <simonb cse unsw EDU AU>]

Hi There,

I'm currently testing GDM on a lab of 19 computers, and am finding that 
about 5-6 per day have their keyboards lock up in the GDM login screen. If 
I kill/restart gdm remotely, then the keyboard comes back to life and 
works in the subsequent GDM session.

We're running 2.6.0.8 from Debian sarge (Xfree86 X server), is anyone 
aware of a problem like this being fixed in the interim? Or perhaps of 
things that might cause it?

I fiddled around with options etc, and couldn't easily reproduce it.
I have a suspicion that it is likely to happen on boot, but not 
subsequently.

The keybaord is very dead - the capslock/numlock etc lights are off and do 
not toggle when pressing keys. Replugging it in (PS/2) does not help - 
only restarting gdm (or rebooting) helps.

Maybe worth noting is that I have:
FirstVT=7
VTAllocation=false

in the config file. I want it to use vt7, but sometimes it seems to use 
VT8, no idea why.

Cheers,

 - Simon