Karmic: Mouse pointer freezes on resume

[yareckon]

I have a Macbook Air 1,1 running the Karmic beta. When I resume from suspend, the mouse pointer does not reactivate, remaining stuck wherever it last was. The keyboard is fully functional. I don't know whether the file this against the x-server-intel or against the power management system.

Description: Ubuntu 9.10
Repeatability: Always
Observed behavior: the mouse is frozen on resume; the keyboard works
Expected behavior: the mouse should work too.

I have the karmic versions of gpomme and pommed from the mactel ppa installed in order to run the keyboard sensors and backlight.

[yareckon (yareckon)]

Two more data points:
* Removing gpomme and pommed and restarting the computer does not help resolve this suspend / resume issue.
* I am running the "Normal" Visual Effects on the GPU (Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 03))

The mouse is:
* Apple, Inc. Apple Internal Keyboard / Trackpad as /devices/pci0000:00/0000:00:1d.2/usb7/7-2/7-2:1.0/input/input6

[yareckon (yareckon)]

here is /var/log/messages during the suspend / resume process. (closing the lid until the lights go out and the sleep indicator goes on, then opening the lid and logging into the machine.)

* The mouse pointer is frozen even on the gnome screensaver login screen.
* I don't know why there is no break in the timestamps in the log between suspend and resume, maybe part of the suspend process is time suspension (?)

Anything else I can add to help you guys diagnose this?

[yareckon (yareckon)]

P.S. this is an upgrade (through upgrade manager) from Jaunty (where suspend resume has worked fine for 6 months), this is not a new conversion from MacOS.

[Tom Durrant (thdurrant)]

I can confirm this. I am in exactly the same position, i.e. macbook air, upgraded from jaunty, touchpad is unresponsive after suspend/resume

[yareckon (yareckon)]

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

[yareckon (yareckon)]

This bug still exists in Lucid beta as of today.

[Jeremy Foshee (jeremyfoshee)]

Hi yareckon,

This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 458469

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[Henri Bergius (bergie)]

Confirming that the issue still persists on MacBook Air 1,1 with a fresh Lucid installation.

[Tom Durrant (thdurrant)]

Confirming this issue on a MacBook Air 1.1 with a fresh Lucid install as well.

As a work around, using s2ram instead of the kernel suspend seems to be a good solution. Details are here:

http://www.mereo.ca/2010/05/18/howto-speed-up-hibernation-in-ubuntu-10-04/

Works very well for me!

[yareckon (yareckon)]

tdh. your solution works! Thank you for the tip about setting up userspace hibernation/suspend. However I don't know what to do about the core issue that stock ubuntu doesn't resume properly on macbook air 1,1. I've put a link back to this bug in the macbook 1,1 wiki page pointing out the regression, and our workarounds. Hope that helps folks who are getting stuck. https://help.ubuntu.com/community/MacBookAir1-1/Intrepid#preview

[Brad Figg (brad-figg)]

This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in a supported series, please file a new bug.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.