On Tue, 21 Aug 2007, Florin Iucha wrote: > There is another interesting angle to this: in the past, every time I > had keyboard problems, it used to be caused by the VFS and/or NFS... > after much wrangling, a bunch of bugs were fixed (Hi Trond, Peter, > Alan!). Now, after the keyboard "locked up", I used the mouse to close > the gnome session, then I logged-in remotely to reboot. The reboot > process locked up and I need to use the reset button! The second time > the keyboard "locked up" I listed my processes, and I noticed that I had > a couple of bash processes and a ssh process in "D" state. Something is > fishy again in the VFS ;)
Yes, there were some NFS updates in between -rc2 and 28e8351ac22de25034e048c680014ad824323c65. I'd be now even more curious what are you going to find by bisect, please let us know. I added Trond to CC, full thread to be found at http://lkml.org/lkml/2007/8/21/151 for reference. Florin, it also might be useful to capture the states of stuck processess via alt-sysrq-T (or better by echo t > /proc/sysrq-trigger), so that we know better where are they stuck. -- Jiri Kosina - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
