Bug 638085

Confirmed!
I also can add that my ps/2 keyboard is not affected. So it must be a USB-Problem. To reactivate my USB-Mouse I have to push a button - moving is not awaking the mouse. This Bug is definitely critical.
(system 11.3 64bit)
I also have to add that the entries in grub were not updated with the kernel so that I had to edit it via command-line to boot!
Alltogether thats the worst security-update since years!

A Japanese user reported the problem which looks like this.
His analysis is that it was caused by USB auto-suspend function.

He said that the workaround of this is to disable the auto-suspend:

"echo -1 > /sys/bus/usb/devices/?-?/power/autosuspend" (from root user)
where "?-?" is the USB device number (can be found by comparing 'lsusb' output with idVendor/idProduct file under "/sys/bus/usb/devices/?-?" directory).

He reported that this problem occurs at Lenovo USB Trackpoint keyboard.
Logitech G700 mouse does not occur (no freeze).

Confirmed too! Its not affecting every mouse. My old wireless logitech mx1000 has no problem while my new "A4 X7 XL-750BK" has the problem described above.
I also want to add my update method was "zypper patch". I´ve now used yast to reinstall the kernel package (this loads not only the delta but the full rpm, so it should be same as "zypper up or dup").
This different update method is not affecting the usb-problem but it solved the grub-problem and updated the entries correctly so that i can boot without command-line editing grubs entries...

(In reply to comment #2)
> A Japanese user reported the problem which looks like this.
> His analysis is that it was caused by USB auto-suspend function.
> 
> He said that the workaround of this is to disable the auto-suspend:
> 
> "echo -1 > /sys/bus/usb/devices/?-?/power/autosuspend" (from root user)
> where "?-?" is the USB device number (can be found by comparing 'lsusb' output
> with idVendor/idProduct file under "/sys/bus/usb/devices/?-?" directory).
> 

Have the same problem, and can confirm that this workaround works!

In my case at least, it looks like the problem was caused by the nvidia driver rpms from nvidia repository. Not surprising actually since it was built for the old kernel.

After uninstalling nvidia rpms and installing nvidia driver from
http://www.nvidia.com/Download/index.aspx
the problem seems to be gone.

I cannot confirm that this is a problem caused by the nvidia driver from the nvidia repository. I am using the driver from the nvidia website and compiled the module for the recent kernel update and encountering the described problem, too.

I have this problem too - but ...

a) it's not only a mouse freeze: the whole screen freezes (I'm running xosview and gkrellm, and for some seconds their display is frozen)

b) I use an USB mouse, but with a PS/2 adaptor. lsusb does not show any connected items:

# lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

I have the problem since I installed (about an hour after installing the OS) the nvidia driver from the repos on my openSUSE 11.3 x86_64. Since I have 8 GiB RAM and an AMD Athlon II X4 605e plus different nVidia cards (but same driver) both at home and at the office, I can't tell the cause.

See also Bug #638250

(In reply to comment #7)
> a) it's not only a mouse freeze: the whole screen freezes (I'm running xosview
> and gkrellm, and for some seconds their display is frozen)
> 
> b) I use an USB mouse, but with a PS/2 adaptor.

Then you probably have a similar problem to the guys in bug 625339. Do you have nvidia graphics?



The other reports here are the same as bug 638200.

*** This bug has been marked as a duplicate of bug 638200 ***

Jiri, I wrote that I installed the nvidia driver ;-) Yes, this is because I have nvidia graphics :-)

Yes, it is the problem described in bug 625339, as you mentioned. Thanks for the hint!

Regards, Werner

the workaround in #c2 doesn't work for me... or i'm too stupid to put it in.

lsusb output:
lapislazuli:~ # lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 004: ID 04b3:4485 IBM Corp. Serial Converter
Bus 001 Device 005: ID 17ef:1004 Lenovo 
Bus 001 Device 006: ID 046d:c517 Logitech, Inc. LX710 Cordless Desktop Laser
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 002: ID 08ff:2810 AuthenTec, Inc. 
Bus 004 Device 003: ID 0a5c:2145 Broadcom Corp. 
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub


so i do "echo -1 > /sys/bus/usb/devices/1-6/power/autosuspend" in a startup script, but my keyboard still switches off after a few seconds...

Mathias, 

First number is the bus, second the device number -1. (bus 001 device 001 = 1-0, bus 001 device 002 = 1-1, etc)

Try "echo -1 > /sys/bus/usb/devices/1-5/power/autosuspend"

I can confirm the autosuspend workaround works for me. I hope they fix this soon!