On Sun, 16 Jan 2011 11:35:50 -0800 Joe Riel <j...@san.rr.com> wrote: > A followup. Yesterday I installed the nvidia driver, > replacing the (default) nouveau driver. So far the > keyboard has not locked up, however, given its > random nature, there hasn't been enough time to > conclude that the problem is solved. If it runs > for a few days with no lockups (I've never gone more > than 2 days without one), I'll submit a bug report > against the nouveau driver.
So much for that...just had another lockup. Nothing in Xorg.0.log. The following tidbit is in syslog: Jan 17 10:50:42 gauss kernel: [48543.711837] atkbd.c: Unknown key pressed (translated set 2, code 0x0 on isa0060/serio0). Jan 17 10:50:42 gauss kernel: [48543.711842] atkbd.c: Use 'setkeycodes 00 <keycode>' to make it known. Jan 17 11:17:01 gauss /USR/SBIN/CRON[6167]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) The atkbd message occured at least 15 minutes before the lockup. The cron job occurred near the time of the lockout; I'll keep track of that in the future. Not sure how to file a useful Debian bug; what package would this apply? If I knew that ... -- Joe Riel -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110117120454.1387145d@gauss