JasonBee wrote:
Put me down as another Mac Pro user suffering from the "RAW" problem.
I've not heard it referred to as the "RAW" problem previously, and I can't figure out an acronym using those initials that indicates "reboot from sleep" or something similar.
Oops, you state it yourself, just below. However, I'd quibble a bit, because the reboot doesn't occur AFTER awakening, it reboots instead of awakening.
Has anyone noticed, you can force your MP to reboot after waking, simply by using VMware Fusion or Parallels, prior to setting the computer to sleep? Like clockwork, it will consistently reboot. I'm not saying it's a problem with Fusion/Parallels, but at least we have a way of demonstrating the issue in front of the Apple "geniuses".
Just for my own edification, can you clarify in what state one needs to leave Fusion or Parallels?
-app running, virtual machine active?
-app running, virtual machine suspended?
-app and virtual machine used during current power up session for the Mac Pro, but virtual machine now suspended and app no longer running?
-app and virtual machine used during current power up session for the Mac Pro, but virtual machine shut down and app no longer running?
This may be another clue that it's a USB problem. One of the issues that's challenged both Parallels and VMWare is sharing access to the USB ports between the Mac OS and virtualized OS. Running Fusion or Parallels may perhaps alter the state of the USB ports so that the Mac can't complete waking up from sleep under some circumstances. Of course, that would need to be a symptom of a larger USB issue, but it is a clue perhaps, as is the suggestion that USB PCI cards may be a way to avoid the problem.
I continue to monitor this thread, but I'll wait for Apple to solve the problem rather than pretending I can do their work for them. I simply don't put my machine to sleep (I allow the displays to sleep automatically and the hard drives to spin down automatically, and sometimes I leave Fusion running - sometimes with the virtual machine active), and I've not had an unintended reboot now since I discovered the problem two days after I bought the machine at MWSF in January but gave up trying to solve it myself a few days later.
It's my sense that one or another of the new observations offered here may provide Apple engineers with the clue they need to tie all the occurrences together, but it's unlikely any of us will solve it. We don't even know if the motherboards are all the same, and they won't tell us. Their resources in their own labs are vastly superior to ours. Of course, the "missing link" for us users is the absence of an acknowledgement from the company in an official tech note that there even IS a problem, and that in my view is unconscionable.
