Q: Dual Quad-core Mac Pro reboots from sleep

Perhaps you can try the experiment overnight to see if anything changes in the morning...?

If it's a software issue, how would reïnstalling the SAME software help ?
If it's a hardware issue, how would reïnstalling the SAME software on the SAME hardware help ?
I don't believe in fairy-tales anymore.
Tom.

From what feedback there is on AYM by Mike Breedon, the build on the DVD and on the original drive are not the same. And because there are more than one issue at work with these systems.

I have posted earlier in this thread some of my experiences on the issue of the Mac Pro rebooting from sleep. I completely erased and zeroed my internal HD. I reinstalled OS 10.5.1 and all updates directly from the installation disk shipped with the PC. Even before installing any software other than the OS, my Mac Pro Early 2008 machine underwent a reboot when awakened form sleep mode. I do not have Bluetooth turned on. I feel these observations rule out the value of reinstalling the OS and software and that Bluetooth has nothing to do with the problem.

I have also had my Mac Pro fail to either awaken or reboot from sleep (twice over a three week period) requiring a forced reboot using the power button.

I do not know whether this is a firmware or a Leopard OS problem on the Early 2008 Mac Pros. If I had to guess, I would guess that the driver for the video card (ATI HD 2600) are involved, but that is nothing but a guess on my part.

This problem is irritating in the top end Mac and I have sent Apple some strong feedback to the effect that the problem needs to be solved soon. I have not heard from a single Early 2008 Mac Pro owner who has NOT experienced this problem at least once. I would urge others to send feedback to Apple.

Tom

Good points but when calling apple techs they pretty much thought it was hardware related but were not 100% sure (as usual). Not to mention the computer will lock up (but still run) often! and the frickin video noise issue happens ever so often also. Hey Tommy, here is your "useful" information 1) My Dual G5 never did this 2) When you drop over 5k (8-core +30") on a new system you expect it to work better then before and to not lock-up or restart -ever. Thats the point of a "pro" system. If apple would just admit it's a software issue (pretty obvious Leopard is not stable) and not make my do the return thing (there suggestion!) I would not have to worry and just deal with it till they fix it with an update. In the mean time, I have a computer that restarts at will and I loose all my work thats open not to mention the random lockups. The fact you had to install Vista to trouble shot a Mac OS X Leopard problem should tell you something... by the way why the **** are we trouble shooting their products anyway!

Seems it is time to select Sosumi from the Sound Effects prefs panel.

UPDATE: my new (2nd 8 core Mac Pro) still has not rebooted when I wake it up from sleep. I have had it for 10 days.

TAKE YOUR MACHINES BACK TO WHERE YOU PURCHASED THEM. They are defective.

To give you an idea how erratic this issue is, I haven't had a single reboot for the last week. Sleeping several times a day as well as every night.
No changes to my rig whatsoever.

i've had this mac pro for a week. the wake from sleep crashing pretty much started as soon as i got it somewhat set up. no airport. no networking. i don't need hard crashes a couple of times a day. i respect my data. lol

if it's not fixed in a week with a software update, it's going back to the apple store to find a new owner.

leopard is by far the worst operating system apple's ever come out with, although i'll admit i skipped 10.1 and10.2. crashes, defects ... which the software companies somehow got us to call bugs. bugs my ***... this stuff is defective. folders not remembering views. programs crashing constantly. apps run slower. and i cant even get a pci express firewire card for this thing yet.

windows 3.11 was better than leopard. maybe not as purty... but i have actual work to do on this POS.

#####################################

cpe-555:CrashReporter dave$ ls
ConfigureMimeTypes2008-02-07-162808daves-mac-pro.crash
qmasterd2008-02-07-162741daves-mac-pro.crash
qmasterd2008-02-07-165250daves-mac-pro.crash
qmasterd2008-02-07-221823daves-mac-pro.crash
qmasterd2008-02-08-021657daves-mac-pro.crash
qmasterd2008-02-08-091602daves-mac-pro.crash
qmasterd2008-02-08-104441daves-mac-pro.crash
qmasterd2008-02-08-144951daves-mac-pro.crash
qmasterd2008-02-09-012632daves-mac-pro.crash
qmasterd2008-02-09-121559daves-mac-pro.crash
qmasterd2008-02-09-184420daves-mac-pro.crash
qmasterd2008-02-09-222544daves-mac-pro.crash
qmasterd2008-02-09-225723daves-mac-pro.crash
qmasterd2008-02-09-231337daves-mac-pro.crash
qmasterd2008-02-10-020343daves-mac-pro.crash

#########################################

apple puts PPC code in leopard?

Version: ??? (???)
Code Type: PPC (Translated)
Parent Process: qmasterd [75]

Date/Time: 2008-02-10 02:03:43.236 -0500
OS Version: Mac OS X 10.5.1 (9B2117)
Report Version: 6

Exception Type: EXC_CRASH (SIGTRAP)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Crashed Thread: 0

Thread 0 Crashed:
0 ??? 0x801a194a 0 + 2149194058
1 translate 0xb80b6670 0xb8000000 + 747120
2 translate 0xb80b6b77 0xb8000000 + 748407
3 translate 0xb80d4530 0xb8000000 + 869680
4 translate 0xb813c9e9 spinlockwrapper + 1981

Thread 1:
0 translate 0xb8152b85 spinlockwrapper + 92505
1 translate 0xb8162c89 CallPPCFunctionAtAddressInt + 36409
2 translate 0xb80bd6fb 0xb8000000 + 775931
3 translate 0xb80b6b77 0xb8000000 + 748407
4 translate 0xb80d4530 0xb8000000 + 869680
5 translate 0xb813d2cf spinlockwrapper + 4259

Thread 0 crashed with X86 Thread State (32-bit):
eax: 0x00000000 ebx: 0xb80b67e8 ecx: 0xb7fff9ac edx: 0x801a194a
edi: 0xb8208980 esi: 0x00000005 ebp: 0xb7fff9d8 esp: 0xb7fff9ac
ss: 0x0000001f efl: 0x00000246 eip: 0x801a194a cs: 0x00000007
ds: 0x0000001f es: 0x0000001f fs: 0x00000000 gs: 0x00000037
cr2: 0x8028e76b

TomWheeler wrote:
I have posted earlier in this thread some of my experiences on the issue of the Mac Pro rebooting from sleep. I completely erased and zeroed my internal HD. I reinstalled OS 10.5.1 and all updates directly from the installation disk shipped with the PC. Even before installing any software other than the OS, my Mac Pro Early 2008 machine underwent a reboot when awakened form sleep mode. I do not have Bluetooth turned on. I feel these observations rule out the value of reinstalling the OS and software and that Bluetooth has nothing to do with the problem.

I have also had my Mac Pro fail to either awaken or reboot from sleep (twice over a three week period) requiring a forced reboot using the power button.

I do not know whether this is a firmware or a Leopard OS problem on the Early 2008 Mac Pros. If I had to guess, I would guess that the driver for the video card (ATI HD 2600) are involved, but that is nothing but a guess on my part.

This problem is irritating in the top end Mac and I have sent Apple some strong feedback to the effect that the problem needs to be solved soon. I have not heard from a single Early 2008 Mac Pro owner who has NOT experienced this problem at least once. I would urge others to send feedback to Apple.

Tom

Tom, although I sympathize with your problems. I have had my Mac Pro for five days and I have put it through its paces and tested it thoroughly and have not experienced a single issue (knocking on my wood desk..) But seriously, no sleep/reboot issues, no freezing screen or graphics card issues.. None.. It runs like a dream. Coming from a G4 MDD, I couldn't be happier..

Perhaps the affected machines come from a bad production run? I'm not sure, but I do know that not all of the new Mac Pro's have issues.

Does 10.5.2 help?

Nope, nor does the Leopard graphics update...!

According to my quick Google search "qmasterd" is part of Final Cut Pro or DVD Studio:

http://forums.macosxhints.com/archive/index.php/t-36424.html

Since most of your crash files indicate "qmasterd", maybe you can temporarely kill it from the terminal and see if your problem persists.

You can get a lot of information out of crash files.
I would not blame the whole OS just because someone messed up a small part of it ...

I'm 0 for 3 so far, but this issue is so arbitrary I'm not breaking out the party hats just yet.

My first overnight sleep after installing the latest updates ended with a reboot rather than re-awakening, so it appears the issue isn't resolved yet.