Comment 5 for bug 458469

OK, so finally was able to google enough to find what was needed to restart the mouse this issue, but still don't understand why there was a regression in ubuntu on this, and don't know what the longterm fix is.

On Fedora 11 Naresh Kumar posted the following issue with a workaround at the below link. Basically, the bcm5974 driver is getting loaded after X.org is restarted after resume. Because the driver is loaded so late, the touchpad is not configured by X.

if your mouse freezes, you can manually remove the kernel driver and then renable it to start up the mouse again:

sudo /sbin/rmmod bcm5974
sudo /sbin/modprobe bcm5974

He provides a script that you can place in /usr/lib/pm-utils/sleep.d in section 14. in the below post:
http://nareshv.blogspot.com/2009/06/fedora-11-64-bit-final-on-macbook-pro.html

Here's the deal... is this the ultimate fix, or a workaround? If this is the best fix, can we get it into an ubuntu package so that people on this machine don't have this issue?

Here is a redhat bug that was filed, and seems to have been abandoned when fedora 10 was end-of-lifed:
https://bugzilla.redhat.com/show_bug.cgi?id=465677#c3