It happened again only two hours later. None of the files in /var/log had been modified in the minutes preceding the problem, but here's Xorg.0.log anyway. (Both it and kern.log had mtimes shortly after the most recent boot, two hours before the problem.)
The keyboard appears to be driven by serio, which is built into the kernel, so I can't rmmod/modprobe it. I looked it up in sysfs and don't see anything particularly pokable. # cd /sys/devices/platform/i8042/serio0/input/input1 # head -1 **/*(.) ==> capabilities/abs <== 0 ==> capabilities/ev <== 120013 ==> capabilities/ff <== 0 ==> capabilities/key <== 4 2000000 3803078 f800d001 feffffdf ffefffff ffffffff fffffffe ==> capabilities/led <== 7 ==> capabilities/msc <== 10 ==> capabilities/rel <== 0 ==> capabilities/snd <== 0 ==> capabilities/sw <== 0 ==> event1/dev <== 13:65 ==> event1/power/wakeup <== ==> event1/uevent <== MAJOR=13 ==> id/bustype <== 0011 ==> id/product <== 0001 ==> id/vendor <== 0001 ==> id/version <== ab41 ==> modalias <== input:b0011v0001p0001eAB41-e0,1,4,11,14,k71,72,73,74,75,76,77,79,7A,7B,7C,7D,7E,7F,80,8C,8E,8F,9B,9C,9D,9E,9F,A3,A4,A5,A6,AC,AD,B7,B8,B9,D9,E2,ram4,l0,1,2,sfw ==> name <== AT Translated Set 2 keyboard ==> phys <== isa0060/serio0/input0 ==> power/wakeup <== ==> uevent <== PRODUCT=11/1/1/ab41 ==> uniq <== I killed X (using kill, not kill -9). After that chvt worked again, no hang. The kernel didn't log anything meanwhile, and the sysfs files didn't change. Is there something I should try to do with sysfs or elsewhere next time? I think I'll try to strace X a little more, to see what it does with its tty fd during shutdown. ** Attachment added: "Xorg.0.log" http://launchpadlibrarian.net/14558966/Xorg.0.log -- x randomly stops responding to keyboard, chvt then freezes kernel https://bugs.launchpad.net/bugs/231031 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
