https://bugzilla.novell.com/show_bug.cgi?id=399125 Summary: psmouse.c: Wheel Mouse at isa0060/serio1/input0 lost synchronization, throwing 3 bytes away. Product: openSUSE 10.3 Version: Final Platform: i586 OS/Version: openSUSE 10.3 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: robin.listas@telefonica.net QAContact: qa@suse.de Found By: --- I'm getting the above error. It is the second time I get this on a period of a month or two; last time I had to reboot to cure it. The machine has been up for 16 days, with hibernation cycles. I'm using gnome and I don't log off. cer@nimrodel:~> uptime 12:58am up 16 days 2:14, 35 users, load average: 4.75, 3.68, 1.81 This seems to happen after several s2disk cycles; the input numbers for the buttons are higher on every cycle (I opened a bugzilla for this time ago): Jun 10 21:35:22 nimrodel kernel: input: Power Button (FF) as /class/input/input138 Jun 10 21:35:22 nimrodel kernel: ACPI: Power Button (FF) [PWRF] Jun 10 21:35:22 nimrodel kernel: input: Power Button (CM) as /class/input/input139 Jun 10 21:35:22 nimrodel kernel: ACPI: Power Button (CM) [PWRB] Jun 10 21:35:22 nimrodel kernel: input: Sleep Button (CM) as /class/input/input140 Jun 10 21:35:22 nimrodel kernel: ACPI: Sleep Button (CM) [SLPB] The next kernel messages are these: Jun 10 23:32:41 nimrodel kernel: psmouse.c: Wheel Mouse at isa0060/serio1/input0 lost synchronization, throwing 3 bytes away. Jun 10 23:32:49 nimrodel kernel: psmouse.c: Wheel Mouse at isa0060/serio1/input0 lost synchronization, throwing 2 bytes away. Jun 10 23:32:51 nimrodel kernel: psmouse.c: Wheel Mouse at isa0060/serio1/input0 lost synchronization, throwing 1 bytes away. Jun 10 23:33:39 nimrodel kernel: psmouse.c: Wheel Mouse at isa0060/serio1/input0 lost synchronization, throwing 2 bytes away. Jun 11 00:35:31 nimrodel kernel: psmouse.c: Wheel Mouse at isa0060/serio1/input0 lost synchronization, throwing 1 bytes away. Jun 11 00:35:57 nimrodel kernel: psmouse.c: Wheel Mouse at isa0060/serio1/input0 lost synchronization, throwing 2 bytes away. Jun 11 00:35:59 nimrodel kernel: psmouse.c: Wheel Mouse at isa0060/serio1/input0 lost synchronization, throwing 3 bytes away. Jun 11 00:36:08 nimrodel kernel: psmouse.c: Wheel Mouse at isa0060/serio1/input0 lost synchronization, throwing 1 bytes away. Jun 11 00:38:01 nimrodel kernel: psmouse.c: Wheel Mouse at isa0060/serio1/input0 lost synchronization, throwing 1 bytes away. Jun 11 00:43:56 nimrodel kernel: psmouse.c: Wheel Mouse at isa0060/serio1/input0 lost synchronization, throwing 2 bytes away. Jun 11 00:46:13 nimrodel kernel: psmouse.c: Wheel Mouse at isa0060/serio1/input0 lost synchronization, throwing 1 bytes away. Jun 11 00:46:57 nimrodel kernel: psmouse.c: Wheel Mouse at isa0060/serio1/input0 lost synchronization, throwing 2 bytes away. Jun 11 00:47:36 nimrodel kernel: psmouse.c: Wheel Mouse at isa0060/serio1/input0 lost synchronization, throwing 1 bytes away. Jun 11 00:47:36 nimrodel kernel: psmouse.c: Wheel Mouse at isa0060/serio1/input0 lost synchronization, throwing 1 bytes away. Jun 11 00:48:34 nimrodel kernel: psmouse.c: Wheel Mouse at isa0060/serio1/input0 lost synchronization, throwing 2 bytes away. Jun 11 00:48:35 nimrodel kernel: psmouse.c: Wheel Mouse at isa0060/serio1/input0 lost synchronization, throwing 3 bytes away. Jun 11 00:48:35 nimrodel kernel: psmouse.c: Wheel Mouse at isa0060/serio1/input0 lost synchronization, throwing 3 bytes away. Jun 11 00:49:04 nimrodel kernel: psmouse.c: Wheel Mouse at isa0060/serio1/input0 lost synchronization, throwing 1 bytes away. They seem to be random, and the mouse sometimes halts while moving for a second or two. Mouse is type ps2, a logitech TrackMan Marble+ of some years that works fine, except when the above happens. Right now it is not happening; if I don't see loss of functionality I may keep the computer up for 2 days in case you want me to run some test. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.