Q: Dual Quad-core Mac Pro reboots from sleep

Yep. Reboot on wake. Have the HD2600, 4 drives, 4G of OWC ram in addition to stock. No graphics issues, before or after the HD2600 firmware update.

My guess is that DIAG means Diagnostic and is linked to the row of LEDs, for most of which the meaning is fairly plain.

I may try to get a good picture later today. Not much room in there...

Photos:

DIAG Button: This one is behind the memory risers; top riser removed.

Reset Button: This is below Drive Bay 4, next to the filler plate for the top card slot.

That second button (or, rather, the pad area next to it) is labeled "RESET" not "RST". See picture links above.

Bill et al,

I've got my Mac Pro opened up and I found the buttons. I pressed the SMC Reset button for a few seconds, but did not see any LED light up confirming the reset. Is that supposed to happen?

Well I'll be stuffed, you are correct sir. I in fact posted a photo of the DIAG, didn't notice until I saw the photo up close due to the lighting. Will be pulling the other photo so other's don't get confused. Just to confirm, I checked and also have the Reset behind bay 4.

So, unless I am missing something, even if (as it is) the physical button is still there - it's not supposed to do anything else that the 'soft' reset (off power etc) should be doing?
I want to believe very badly that this has been a fix at least for some; but with new systems still shipping with the affliction, and lots of users having tried reset with relapse after a week or so, I remain skeptical. And of the opinion, the fix needs to come from Apple (not to say I don't really want 'us' to solve it!)

After finding a different layout than I expected, I didn't push any buttons. Just took pictures. (Although I doubt, with power removed especially, pushing buttons would do any harm). There are, as far as I could tell, no LEDs near the button in the top right near the 4th drive bay.

Just an update. I have now had the reset after sleep come back again. I have had a archive and install done at the Apple store (for the freezing problem that they never duplicated), done the Reset SMC/PRAM, run with no Hub/ DId not Run Parallels/ Did not use wireless mouse or keyboard and now after a few days, the reset after sleep came back. At this point I think I will just set it to never sleep, but to sleep the display and spin down the hard drives like someone else mentions. I am tired of fighting this. I hope Apple will fix this at some point. Now I just have to hope that the firmware update at least fixed the freezing problem.

I just reset the SMC with the button, so we'll see what happens.

In the meantime, I've been using the "Deep Sleep" widget and liking it a lot. Google it and check it out. Some people actually prefer using it even when their computers don't have this "reboot from sleep" issue.

I agree that Apple needs to address this. Said it many times myself! Everyone please take a moment and fill out the Mac Pro feedback form if you haven't already.

Likewise. Yesterday's ATI update did not fix my restart from sleep issues either. I tested the MP three times, in this order: a short, 1-hour sleep (woke ok), then an 8-hour overnight sleep (woke ok), and finally today an 8-hour sleep while at work (failed - startup chime). Sidenote: 32 pages and no fix?!!

Well, after my fifth call to Apple care, I'm down to stock configuration (without 8 gigs of owc memory and my windows drive) waiting to see if the "wake with reboot" from sleep problem returns. I've tried resetting smc and pram (many ways, many times) and archive/install. Have to admit apple care people have been friendly (in a kafka-ish fashion), but I can understand why people who are losing work hours over this would be angry about having to sit around for a week waiting to see if the problem returns.

Last specialist said that bad ram has been linked to sleep problems but he didn't know anything about macpro having specific problems, so I'll go along for the ride. Will check to see what OWC says, although I've never had a problem with their products. Frankly, I very rarely used sleep in the past but since realizing there might be a problem, I've been losing sleep trying to solve it. I've been using computers for works since early 80s so I've grown to expect little oddities and work around them. Like others, I'm tempted to just avoid sleep because I like this machine (quiet, looks good, thief would have a hard time hauling it away, and it almost works to perfection). I'll give it a week and try not to think about it.
LZ
Lou

Good luck; but while memory (from any vendor) can always be problematic, we already know that stock systems with no memory added at all (other than apple's) has the issue; so I don't see how adding OWC or any other high-end memory could be a problem unless by pure coincidence of that memory being bad. Apple uses stock machines with stock memory only in the Apple Stores; and those systems exhibit the reboot issue.
I doubt OWC will be of much help (no fault of theirs)....
cheers

I called with apple care something more than a week ago, did the 4x reset pram thing, and it worked.. UNTIL TODAY!!!

I TRIED TO GET IT OUT OF SLEEP MODUS AND IT REBOOTED IT AGAIN!!! Darned!!!

I really tought it was finished!! BUT NOOOOooooo... i gonna call apple helpdesk again...

Yeah.. I hate to say it, but at this point I don't think the pram/smc resets are doing anything in the long-term, for anyone. Sure enough, they seem to 'reset', that is, fix this temporarily for most, but it always seems to come back - so really can't be considered any fix....

About memory thing - I thought RAM might be a culprit first. However, after seeing reports from people having this issue with any brand of RAM including Apple's own I just can't agree with the statement. The only common thing all RAM variations have is 800 MHz frequency, but it can't be accounted for any issues.

Next thing - power. My Mac Pro is connected to UPS and that along should isolate it from any circuit problems, however looking at Mac's monster of a PSU I can't imaging that it may fail to provide stabilised current in meagre amounts needed to power the RAM during the sleep.

It seems the problem lies deeper. SMC looks like the number one suspect.