I have the same problem. However the lockup most often occurs after
switching with Ctrl+Alt+Fx from plain text console to X. PS/2 mouse +
keyboard, gpm running.
> 440BX UP celeron mobo here (Abit - BH6?), '94 AT keyboard, '2000 A4tech
> 2-wheel mouse, various Linux 2.4 versions (usually -ac, currently 2.4.10ac3).
> I'm using NVidia Xserver module, but it doesn't seem related (the lookup
> occured with no X while starting gpm once or twice).
I had this problem for quite some time with 2.2.x and 2.4.x kernels,
XFree86 3.3.x -- 4.1.0 and S3 Trio3D / NVidia TNT2 M64 / NVidia
GeForce2. Lockups with S3 convice me that NVidia module is probably
irrelevant here.
> If I kill Xserver (haven't tried with gpm), the keyboard (and mouse) start
> working again (the next Xserver spawn works fine).
I've found out that ssh'ing to the host and running chvt 1 (as root)
helps. Switching back to X usually works fine.
I haven't tried monitoring /proc/interrupts, but even the magic SysRq
doesn't work during the lock-up.
P.S. I'm not subscribed to linux-kernel.
Marius Gedminas
-- "I'll be Bach." -- Johann Sebastian Schwarzenegger - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/