Q: Dual Quad-core Mac Pro reboots from sleep

Could it be some conflict we pulled over during Migration Assistant? It so happens that this is the 1st time I've used this feature...

I have the same problem with my week-old 2.8... I put 10.5.2 on it the day after I got it, so I can't say whether the problem existed on 10.5.1... but I didn't use migration assistant - it was a clean set-up.

I did a SMC/PRAM reset and the problem seems to have gone away (I did 5 sleep/wake cycles without a problem)... see how things go over the next few days.

I can't see how it could be a hardware fault as such - more likely (hopefully_ something apple can fix with a firmware revision - so I'm not planning to take my machine back just yet....

Nope;
my 3.2 was a brand-new install, NOTHING taken or migrated from my previous system (other than ical, safari, address etc data via .mac sync). Problem exists no matter if system is 'vanilla new' or 'migrated' it seems...
d

Reseting the PRAM worked for me for now. I will let you guys know if this comes back to haunt me.

Same Problem here again. With 10.5.1 it was okay, now sometimes not.

Sign me up, too. I had this problem under 10.5.1 with a stock configuration. Upgraded to 10.5.2 and added 2gb more RAM and it's still happening. Like others have said, it's intermittent and it's only happened a handful of times.

A week ago I took delivery of a refurb 2xquad 3.0ghz Mac Pro. I installed 2x2gb of Transcend Certified Mac ram on riser #1, moved the stock 2x512mb FB-Dimms to riser #2 and 2x512gb WD drives. It ran fine for about 30 minutes then started the sleep/reboot issue.

I followed this thread and reset the PRAM and SMC but no luck. The next day I started fiddling with the ram setup. I removed the Transcend ram and reinstalled the factory ram. The unit ran fine for most of the day. Then I swapped out the factory ram for the Transcend. Same deal, ran fine and no sleep or reboot issues. This is the way I have left it and so far for over a week it has been very stable. I am still in the setup mode so I leave it running extensive disk copies, etc overnight and each day it wakes from sleep with just a tap on the spacebar.

Anyway, if anyone is running the factory ram with additional 3rd party ram, you might want to try this. Lucky for me the 2x512mb rams that my machine came with are pretty insignificant and I will be adding 4gb more of the Transcend ASAP.

Well, sadly, even after trying all the suggestions here I've accepted defeat and Apple have agreed to take the unit back at their cost. I shall re-order once I read that this problem is finally sorted. I simply did not want such an expensive computer with what may be a motherboard problem. Apple should address this forum and let us know their findings and intended response as numerous returns will prove very costly.

If people here don't return their faulty units Apple will do nothing to correct the problem and you'll suffer this issue for the life of the computer. Notwithstanding the environmental issues I didn't want a computer I could never trust to sleep.

The hatter,

That would be me. Received my 3.0 MP on the 17th of Jan and has been having this issue since day one wether with the stock configuration or with added third party RAM and HDs. I have tried all of the suggestions, SMC reset, PRAM zap, etc. I don't have anything plugged into the USB/Firewire hub on the 23" Cinema Display. Have the ATI card and hooked up to Airport through ethernet. 4 WD 500GB drives (1 for boot, 1 for files and docs, 2 in mirrored RAID for Time Machine BU and PS scratch), 16GB from Transintl. Per the Apple Care product specialist I have the Energy Saver settings at Never, Never, and Only Restart from Power Failure Checked. I have removed all login items in Accounts per their recommendations the first time I called. Took three calls to get them to send a tech.

Did an Apple hardware test, passed - TechToolPro 4.6.1 hardware test, passed.

At this point I am waiting for my local repair service to receive the parts from Apple. Apple Care assured me that the new parts were indeed going to be new straight from the service department and not refurbs. They are going to come out and replace the logic board, power supply unit to hopefully correct the issue and install stock RAM for testing. Once the tech arrives they have been told to test the unit for at least 2 hours to see if the problem returns after the new hardware is installed as my system seams to on a somewhat regular basis only take a little over an hour for the restart from sleep to occur.

I'll update to let people know what the outcome is. As it looks won't be until next week and I got the process going with Apple Care this past Monday.

I just called apple and they said that I could have labels printed and I could ship my unit to their engineering department and then they would send me another unit. I said I can't go without my machine and they would have to send a replacement first. He said my other option was to go to an apple store which is 250 miles away. I complained and said that this was poor service and the guy wasnt too nice in response. I then hung up on him.

Apple is loosing my respect and my fanboy style for them over these kind of issues. Dell is so much better with dealing with issues. I will never go back to a dell though.

Fix this major screw up apple. I am disappointed with the original problem and with how you dealt with me in tech support.

They offer to give you a new unit so they can send it back to engineering and you call it "poor service"...? I can understand your need but I'd question your expectations... and you hang up on them and you're losing respect for them??
I'd bet with a better attitude you'd been able to talk to a supervisor and may be get a better deal... Now, you got squat!

New OEM octa 3.0 w/8 G OEM Apple RAM, 8800, and 750 G OEM HD. Same wake from sleep issue here.

Machine is 100 percent OEM Apple.

What next?

aehaas

Yes, it's poor service, probably The Riddle expected a computer that "just works" in exchange for a generous quantity of money. Not a computer with a serial tare that the manufacturer doesn't solve nor recognize.
Which attitude is the best when you feel cheated? Entering of knees and reverse gear the Apple store?

Clearly Apple don't know how to fix this issue , if they did they would tell everyone within seconds, no company can afford to alienate their client base as this problem has.
No doubt it will get rectified in time, it's costing "everyone" grief, I pity the dealers who sell Mac's they get very little for the sale of a box, and to get irate customer/s over production problems would be the pits. All we can hope for is that someone at apple can find a solution ASAP.
Cheers
Tom K

Tom K 7 wrote:
No doubt it will get rectified in time, it's costing "everyone" grief, I pity the dealers who sell Mac's they get very little for the sale of a box, and to get irate customer/s over production problems would be the pits. All we can hope for is that someone at apple can find a solution ASAP.

Well, it's not caused me a lot of grief. My machine is affected, but I know all I need to do to protect my data is not allow the computer to sleep. I allow the drives to spin down and the displays to sleep, and it doesn't seem to draw much power (box is very cool and extraordinarily quiet) when I'm not using it.

My major source of reassurance that it's not a hardware problem comes from a user on this thread who has reported that it simply doesn't happen when his machine is a REAL (not virtualized) Windows box.

It would be nice if Apple would make a public acknowledgement of the problem. There are users who've reported they'll be obtaining replacement machines. We can all hope that, absent candor on Apple's part, these customers will log back in and tell us if the problem really is solved by a machine or logic board swap. If that's uniformly the case and Apple hasn't acknowledged this, my disappointment meter goes WAY up. If, as I assume, it's a software problem (remember, it seems not to happen if the box is working as a Windows-only machine), I'm content to wait for them really to fix it.

Threads (besides this one) are easy to find on the support pages at Apple, so we MUST assume they're aware of it, but it sure would be nice for them to agree...