Well, it's difficult to tell, really. The kernel that comes with Maverick contains Bug #588194 (solved by the same patch that solved Bug #380126), which makes it rare that I can even resume from suspend.
But when I do, I see a similar message in the messages logfile:
psmouse.c: resync failed, issuing reconnect request
psmouse.c: Mouse at isa0060/serio2/input0 lost synchronizaiton, throwing 2 bytes away.
After a couple occurrences of those messages, it went into suspend again. After waking after *that* suspend, I no longer get those messages, but the mouse no longer works, although the keyboard does (without dropping any inputs).
Well, it's difficult to tell, really. The kernel that comes with Maverick contains Bug #588194 (solved by the same patch that solved Bug #380126), which makes it rare that I can even resume from suspend.
But when I do, I see a similar message in the messages logfile:
psmouse.c: resync failed, issuing reconnect request serio2/ input0 lost synchronizaiton, throwing 2 bytes away.
psmouse.c: Mouse at isa0060/
After a couple occurrences of those messages, it went into suspend again. After waking after *that* suspend, I no longer get those messages, but the mouse no longer works, although the keyboard does (without dropping any inputs).
I'll try Lucid and get back to you.