Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
Dont have Applecare; machine is 6 years old. I just got on the phone to Apple Support and its now with engineering :)
Great to hear they might take care of the issue. Those of us who upgraded parts like the CPU are probably out of luck. Unless things have changed at Apple, if you do a major change to the original configuration they have on paper, they will consider any issues not theirs but yours (caused the issue yourself). I think us who upgrade parts without Apple doing it are stuck unless things have changed.
 
Great to hear they might take care of the issue. Those of us who upgraded parts like the CPU are probably out of luck. Unless things have changed at Apple, if you do a major change to the original configuration they have on paper, they will consider any issues not theirs but yours (caused the issue yourself). I think us who upgrade parts without Apple doing it are stuck unless things have changed.
Who is feeding you these lies lol. I’ve upg the CPU and SSD in mine; the apple store didn’t even bat an eyelid.
 
Who is feeding you these lies lol. I’ve upg the CPU and SSD in mine; the apple store didn’t even bat an eyelid.
Not lies, it depends if they check the serial number or not to see if there had been non-apple modifications after purchase (like going from a 6-Core to a 12-Core) and/or they did not do the upgrade on record. They can say the damage happen because you did the upgrade yourself or did it at a non authorized Apple service and therefore not take responsibility. I was told that some time back from Apple. They can fix it regardless, but they will charge a grip to do it if they see any non-Apple changes.

It also depends who you talk too. Some don't check, others do. It depends on who helps.

Not sure if you said they charged you or not. Also, Did you upgrade the CPU before etc. and then take it to Apple?

That infö. would help a lot of us..
 
So my local apple store know I've upgraded the CPU and SSD. They mentioned it to me as part of our discussions to narrow-down the cause of the issue. Both upgrades were done post-purchase. The CPU they didnt care about; the SSD they said we would need to temporarily swap out for one of our own SSDs to run tests and I said ofcourse.

I was charged for the price of one daughterboard and the labour fee (out-of-warranty) to fit it :)
 
So my local apple store know I've upgraded the CPU and SSD. They mentioned it to me as part of our discussions to narrow-down the cause of the issue. Both upgrades were done post-purchase. The CPU they didnt care about; the SSD they said we would need to temporarily swap out for one of our own SSDs to run tests and I said ofcourse.

I was charged for the price of one daughterboard and the labour fee (out-of-warranty) to fit it :)
Appreciate you taking the time to go through the hurdles of support for this, hopefully results in a fix being pushed for everyone.
 
  • Like
Reactions: loby
On my MacPro 6,1 with 12.2 and all "Energy Saver" checkboxes unchecked it goes to sleep with pulsing power led - but when it wakes up its like a restart without the warning dialog that the machine had a abnormal shutdown?!?
All apps will be loaded as like e fresh power on.
 
There was a firmware update in 12.3. See this post #141 which shows firmware 447.80.3.0.0. That thread appears to indicate the new firmware has broken sleep for a lot more people.
 
There was a firmware update in 12.3. See this post #141 which shows firmware 447.80.3.0.0. That thread appears to indicate the new firmware has broken sleep for a lot more people.
I guess Apple’s thinking was that if they can’t fix it, we should all suffer together.
 
There was a firmware update in 12.3. See this post #141 which shows firmware 447.80.3.0.0. That thread appears to indicate the new firmware has broken sleep for a lot more people.
yeah, i read something that some macbook owners encounter a bluetooth problem which consumes all batterie life over night in sleep. don't know if this is also something handled by the firmware but indicates that apple's software quality reaches now windows level ;)
 
It seems everybody with this problem is running a MacBook. I just want too make sure you know this has been happening on my iMac (Retina 5K, 27-inch, 2019) also, currently running Monterey 12.2.
 
Most of the folk here are running Mac Pro 6,1.
It seems everybody with this problem is running a MacBook. I just want too make sure you know this has been happening on my iMac (Retina 5K, 27-inch, 2019) also, currently running Monterey 12.2.
Most of the folk here are actually running Mac Pro 6,1s. The problem can occur with 11.6.1 or .2 or 12.1. We're trying to establish whether it also occurs with 11.6.3 or 12.2, and also if the firmware has been updated with those new releases, or with 12.3 beta.
 
For what it’s worth, I haven’t had a crash since updating to 12.2. I didnt use the beta or RC and has the issue on 12.0 and 12.1. Anecdotal, I know, but I’ll update if that changes. (Also on a Mac Pro 6,1 for clarification.)
 
  • Like
Reactions: loby
There was a firmware update in 12.3. See this post #141 which shows firmware 447.80.3.0.0. That thread appears to indicate the new firmware has broken sleep for a lot more people.
Nope. Wrong Mac. The 6,1 firmware with 12.3 beta is still 429.60.3.0.0. The sleep crash issue still happened in 12.2 for me (D700 6,1). It hasn't happened in 12.3 beta yet for me, but that doesn't mean it won't.
 
Nope. Wrong Mac. The 6,1 firmware with 12.3 beta is still 429.60.3.0.0. The sleep crash issue still happened in 12.2 for me (D700 6,1). It hasn't happened in 12.3 beta yet for me, but that doesn't mean it won't.
It sure to be a firmware issue and not an OS. I booted up into boot camp with Windows 10 and it did not hesitate to reboot/crash when entering sleep. Did not do this before.
 
Hello. I am experiencing the same issue like you with my Mac Pro 6,1 (12-Core, D500). For me, as a temporary work around, worked the following terminal command: sudo pmset -a standby 0.

After a reboot you need to enter it again.

Maybe it also helps you until Apple releases a new firmware fixing the general issue.
 
Getting same problem, Kernal Panic when I try to wake it.
on Catalina 10.15.7 My Macs have never crashed so much before.
I've gone years without seeing the Panic! till recently ... Sigh.
 
looks like 12.2.1 solves the problem. my macpro 6,1 wakes up like it should. but i will test it overnight with a longer period of sleep before i can give green light :D
 
looks like 12.2.1 solves the problem. my macpro 6,1 wakes up like it should. but i will test it overnight with a longer period of sleep before i can give green light :D
The last time I had the problem .. it took two weeks for it to occur. After that I stopped it from sleeping. I noticed that it needed a long period of sleep, like a day. Short periods were no problem.
 
For what it’s worth, I haven’t had a crash since updating to 12.2. I didnt use the beta or RC and has the issue on 12.0 and 12.1. Anecdotal, I know, but I’ll update if that changes. (Also on a Mac Pro 6,1 for clarification.)
It’s begun crashing on 12.2 :(
 
looks like 12.2.1 solves the problem. my macpro 6,1 wakes up like it should. but i will test it overnight with a longer period of sleep before i can give green light :D
Was your problem SO frequent and consistent that you can ALREADY tell that "it's solved"? — I understand you're saying you'll give it overnight, but as other users are stating, some of us won't see a crash for 4-10 DAYS, and then it'll crash during sleep.

Also: What's your "System Firmware Version" after the update? Is it still: 429.60.3.0.0?
 
And FWIW, my measurement (via a crontab, using the "uptime" being output to a text file every 1hr) seems to prevent the crashing from ever taking place. I've only had 1 crash-during-sleep since my post on Jan 24th.
 
Was your problem SO frequent and consistent that you can ALREADY tell that "it's solved"? — I understand you're saying you'll give it overnight, but as other users are stating, some of us won't see a crash for 4-10 DAYS, and then it'll crash during sleep.

Also: What's your "System Firmware Version" after the update? Is it still: 429.60.3.0.0?
Yes, firmware is still 429.60.3.0.0 in 12.2.1. I have yet to test the sleep function...
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.