vmware-player 3.1.4-385536.i386 blocks machine suspend

[Andreas Hasenack]

After installing VMware-Player-3.1.4-385536.i386.bundle on my Lucid thinkpad t61 running "2.6.32-33-generic-pae #70-Ubuntu SMP Thu Jul 7 22:51:12 UTC 2011 i686 GNU/Linux" I noticed two things:

- suspend stopped working: it wouldn't suspend. The "moon" light would flash, fans would spin up and it would stay stuck there, unresponsive to anything (see bug #814323 for a very similar, if not identical, behavior). I needed to power it off to get out of this state.

- modprobe -r parport_pc, or rmmod parport_pc would hang the process in a D state. The machine would still be usable after that, just the rmmod process would be stuck in D.

I noticed the rmmod problem because it's what the vmware initscript does at some point. So to use vmware I basically commented that line in the initscript. I also tried to blacklist the parport modules, but something was still loading them at boot, maybe the initrd. I don't even have the parallel port enabled in the BIOS of this machine.

Even though it's very similar to bug #814323, I was asked to open this bug report. I don't have vmware installed anymore and the machine suspends and resumes just fine again. Inserting and removing parport_pc also works again.

$ cat /proc/version_signature
Ubuntu 2.6.32-33.70-generic-pae 2.6.32.41+drm33.18

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 816963

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

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

[Seth Forshee (sforshee)]

Along with the logs, please provide the output of running 'cat /proc/$(pgrep rmmod)/wchan' while rmmod is stuck in the D state.

You'll probably have to take this up with vmware, since it's likely their modules are what are causing the problems. But when you provide the requested information I'll take a look to see if I find any kernel problems.

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]