Hi Andrew, On 10/20/2010 11:41 PM, Andrew Clunis wrote:
> On my Thinkpad T61 with an Nvidia Quadro NVS140m (with proprietary > driver) with Ubuntu 10.10 x86_64, I have a very similar intermittent > behaviour after resuming from suspend. However, sometimes it varies: > sometimes only the Trackpoint won't work, but sometimes the trackpoint, > touchpad, and keyboard will not respond. I have the exact same hardware, and all the issues you describe in this paragraph above I also experience; exactly as you describe. Oh, the only difference is that I run x86_32. > Plugging in a USB mouse or keyboard works. Yes, I confirm. > Rebooting solves the > problem. Re-suspending or hibernating does not. The HAL process is > present and accounted for, and responding to D-Bus calls. Yes to all of these; I also confirm. > It occurs (very approximately, I haven't logged any real data about it) > about 20% of the time. More often than not it involves all three of the > input devices, but sometimes only the Trackpoint is affected. I haven't > (iirc) seen the trackpad and keyboard affected independently of one > another. Same here -- it does not happen all the time but it happens frequently enough to make it very annoying. > I've never had this problem before 10.10, and this machine has been > running Ubuntu since 7.04. This is the worst part -- I had solid suspend and resume with 10.04. With 9.10 or some previous releases I had issues, but 10.04 fixed all the issues and I was very happy to have 100% solid suspend and resume on this laptop. But now we have this regression. > If the keyboard is locked, attempting to switch between VTs > (ctrl+alt+fnX) does nothing. Catting /dev/input/mice produces no output > at all. Indeed. > I have not determined (I don't use it too often) if hibernating can > bring the problem on. > > I haven't noticed anything out of the ordinary in dmesg, syslog, or the > Xorg logs. > > I really have no idea where to begin debugging this one. At least, > since original reporter's machine has an Intel card with the Free > driver, we can (probably) rule out the graphics device here. Seems to > be a kernel-level issue. Here's something that I noticed and that I encourage you to check next time your keyboard is dead: sometimes there is a kernel oops in the kseriod thread. This kernel thread handles devices like keyboard and mouse so it makes sense for keyboard and mouse to stop working when there is an oops in this kernel thread. I found Ubuntu bug 630714 that seems very similar to the oops I sometimes see, so I subscribed to it. You should check for an oops in dmesg's output or in /var/log/syslog next time your keyboard and mouse stop working after resume, and if you find one in the kseriod thread then subscribe to the above bug and click on "this bug affects me". Hope the root cause of this issue gets found quickly since it is very annoying. It does seem to be a kernel problem. Cheers, Eloy Paris.- -- Mouse pointer doesn't work after resume from suspend on Thinkpad T60p (intermittent) https://bugs.launchpad.net/bugs/659219 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
