Hello, I have noticed with gentoo-sources-2.6.12-rc6 that *sometimes* my keyboard hangs when I start to type something. I do have a KVM installed, but it does not seem to be responsible for this. Once this happens, nothing on the keyboard responds per se (e.g., caps lock and numlock); however, some low-level keyboard buttons for macros do work. I may be wrong, but I think that CTRL+ALT+DEL may have actually worked on once or twice. My KVM is a TK-210K and uses two ScrollLock depresses to activate its commands. My machine is roughly as follows: Asus A8N-SLI Premium AMD64 4200 X2 Hauppauge WinTV 150 I am curious is this likely to be a fault of the kernel, the KVM or some odd quirk of AMD64 systems? I would not like to fault the KVM, for I believe that I have noticed this behavior before without it. Moreover, once the odd keyboard shenanigans happen, I have disconnected my keyboard from the KVM and directly plugged it into the machine, only to find it keeps misbehaving. Reproducible: Sometimes Steps to Reproduce: 1. Use the keyboard as normal. Actual Results: 1. Works most of the time and then suddenly freezes, never to recover. Expected Results: Keyboard should work as before. emerge info Portage 2.0.51.22-r2 (default-linux/amd64/2005.0, gcc-3.4.3, glibc-2.3.5-r0, 2.6 .12-gentoo-r6 x86_64) ================================================================= System uname: 2.6.12-gentoo-r6 x86_64 AMD Athlon(tm) 64 X2 Dual Core Processor 4 200+ Gentoo Base System version 1.6.13 dev-lang/python: 2.3.5 sys-apps/sandbox: 1.2.11 sys-devel/autoconf: 2.13, 2.59-r6 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.5 sys-devel/binutils: 2.15.92.0.2-r10 sys-devel/libtool: 1.5.18-r1 virtual/os-headers: 2.6.11-r2 ACCEPT_KEYWORDS="amd64" AUTOCLEAN="yes" CBUILD="x86_64-pc-linux-gnu" CFLAGS="-march=athlon64 -O2 -pipe" CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/lib/X1 1/xkb /usr/share/config /usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/ config/ /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/ /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-march=athlon64 -O2 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig distlocks sandbox sfperms strict" GENTOO_MIRRORS="http://distfiles.gentoo.org http://distro.ibiblio.org/pub/Linux/ distributions/gentoo" MAKEOPTS="-j3" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="X Xaw3d a52 aac acl acpi aim alsa amd64 apm arts audiofile avi bash-complet ion berkdb bitmap-fonts bluetooth bmp bonobo bzip2 calendar cdparanoia cdr crypt cups curl dbus dga directfb doc dvd dvdr dvdread eds emacs encode esd evo exif expat fam fbcon ffmpeg foomaticdb foomaticfb fortran ftp gcj gdbm ggi gif glut g nome gnustep gnutls gphoto2 gpm gstreamer gtk gtk2 hal howl icq ieee1394 imagema gick imap imlib inifile ipv6 jabber jack javascript jpeg kde kerberos ldap lesst if libwww lirc lzw lzw-tiff mad maildir mailwrapper mbox mcal mikmod mime mmap m ng motif mozilla mozsvg mp3 mpeg mpi msession msn mysql nas ncurses nls nptl off ensive ogg oggvorbis openal opengl osc oscar oss pam pcre pda pdflib perl php pn g portaudio posix ppds python qt quicktime readline ruby samba sdl session share dmem shorten sndfile sox speex spell ssl svg szip tcpd tetex theora threads tidy tiff truetype truetype-fonts type1-fonts unicode usb userlocales v4l v4l2 vcd v orbis wifi wmf wxwindows xine xinerama xml xml2 xmms xosd xpm xprint xsl xv xvid yahoo zeroconf zlib userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS, PORTDIR_OVERLAY
I hope this may be helpful; but I have found that when I leave the machine for a while or switch back to it from the KVM, sometimes some compiling operation may hang at a point where it shouldn't, so I hit CTRL+C cancel the job, at which point the keyboard suddenly freezes as described above. The mouse does work during this time, I should note.
I apologize for spamming, but I am trying to provide as much information as I can to get this fixed. I managed to have kept a few xterm open and used its copy-and-paste mechanism to type simple commands. When I looked at dmesg, I saw something similar to what was reported here: http://www.x86-64.org/lists/discuss/msg06735.html > Call Trace:<ffffffff8011dea1>{powernowk8_get+145} > <ffffffff802e2b90>{cpufreq_get+96} > <ffffffff8011266a>{handle_cpufreq_delayed_get+58} > <ffffffff80148eec>{worker_thread+476} > <ffffffff801326d0>{default_wake_function+0} > <ffffffff80130733>{__wake_up_common+67} > <ffffffff80148d10>{worker_thread+0} > <ffffffff8014d7a9>{kthread+217} > <ffffffff80133be0>{schedule_tail+64} > <ffffffff8010f5b7>{child_rip+8} > <ffffffff8011d4f0>{flat_send_IPI_mask+0} > <ffffffff8014d6d0>{kthread+0} > <ffffffff8010f5af>{child_rip+0}
This mailing list thread seems to encompass the whole problem very well: http://www.uwsg.iu.edu/hypermail/linux/kernel/0507.0/1378.html
Have you tested the patch posted in the thread?
Daniel, Yes, I patched gentoo-sources-2.6.12-rc6, and I have been running for the past ten hours without a glitch--something I would not have been able to have done before. Everything appears to be working well; I hope that the kernel maintainers are able to incorporate this fix into the sources soon.
Fixed in gentoo-sources-2.6.12-r7 Fixed in genpatches-2.6.12-11
