Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
MP 6,1 Mac Pro 6.1 Monterey - Crashes in Sleep
- Thread starter vddobrev
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
Having the same issue. Thing is, I just purchased this refurbished 6,1 12 core, and it had an older version of Mac OS on it. So i upgraded right away. Subsequently, I have nothing to compare it against, as in, previous OS versions. Im jumping n this thread to see if anyone has further info, if not I'm returning it and getting an M1.
As I previously mentioned
I recommend you try this!
Sleep your Mac Pro 6,1 as normal and then completely unplug all connected displays from the power outlet.
Alternatively use a smart plug and disable the power to all connected displays completely.
When you are ready to use your Mac again.
Reconnect power displays and wake the Mac with keyboard / mouse as you normally would do so.
I’d try it without power to display first because I fixed the issue for myself by doing that.
My 6,1 d500 with apple cinema started doing this a long time ago --3 years. Macs go into extended sleep about 30 min after first level of sleep. I think it was the logitec mx master bluetooth mouse. I just plug in a wired usb mouse as well; I think that may keep it from the really deep sleep so no crashes.
I’m seeing the same crashes on Monterey (on 12.1 beta, as well). I’m running the Mac as a server, no peripherals connected at all. I tested using the original SSD and my M.2 upgrade, same issue. Replaced my CPU, same issue.
So I guess it’s either a hardware issue on the logic board or an issue in macOS.
Maybe I’ll get another logic board to find out if that’s the cause.
(Registered just to share my test results)
So I guess it’s either a hardware issue on the logic board or an issue in macOS.
Maybe I’ll get another logic board to find out if that’s the cause.
(Registered just to share my test results)
I'm currently having the same issue on a different cMP with Catalina, so I wonder if it's just an underlying macOS thing?
The macbook came back from sleep this morning without a crash, after I disconnected the display last night (left the USB-C hub connected with WD hard drive and USB connection to the display). So it could be the display indeed, but how to fix? Disconnecting the display every night isn't really workable..
I tried unchecking everything in the Energy Saver and Mac went into deep sleep.
Checked to see that I have Bluetooth as a network interface and also am using a Logitech bluetooth mouse. Could Wake for network access and bluetooth networking keep it from a deep sleep? I removed the bluetooth interface from the network panel, then checked Wake for network access, and it seems to go to sleep without crashing.
So maybe wake for network access and the bluetooth network interface cause issues?
I will try to add more of the Energy Saver checkboxes and see what happens.
Checked to see that I have Bluetooth as a network interface and also am using a Logitech bluetooth mouse. Could Wake for network access and bluetooth networking keep it from a deep sleep? I removed the bluetooth interface from the network panel, then checked Wake for network access, and it seems to go to sleep without crashing.
So maybe wake for network access and the bluetooth network interface cause issues?
I will try to add more of the Energy Saver checkboxes and see what happens.
For folks jumping in, what we're talking about is not a hardware issue and it's not a problem that existing with previous versions. There are a set of longstanding hardware issues with the 6,1 and a few software issues that can look a lot like this, and it's possible that a few people on the thread are seeing those. However, this is a new problem that is specific to Monterey 12.0.1. For a number of us, our systems were in rock solid state up until the date of the upgrade and then the crashes started.
It turns out that my EFI partition had some errors, the -69766 error, so I ran this command:
Code:
sudo fsck_msdos diskXsXand it's been smooth since then. Sleep seems to have gone back to normal.
This will be my last post in this thread since:
1) this thread is for 6,1 nMP's
2) my machine is "officially unsupported" as MarkC426 is indicating
3) this issue seems to be specific to Monterey
Cheers
*poof*
Last edited:
You could just use a smart plug from Amazon or something I found you only need to kill the power to the display and leave it connected.
It seems like it's something to do with 'Display's Renegotiation' which causes the system to wake up and go back to sleep multiple times per night so if there is no power to the displays they can't do it.
Not sleep related, but today I experience multiple crashes when changing the output rate from Audio MIDI Setup. I had connected both my TV and receiver, and tried to change the audio bit rate from 48KHz to 192KHz. Crashed every time I tried.
I read that 12.1 fixes some bugs, of which: External displays may not charge some MacBook Pro and MacBook Air computers when connected using Thunderbolt or USB-C
Now this is not exactly the bug that we're experiencing nut as this has to do with exernal monitors and usb-c hubs this will hopefully fix the issue?
I've learned my lesson though, I upgraded to mojave and big sur (skipped catalina) when they got on their .5 release and upgraded to monterey because I was eager but this is really annoying.
Experienced a crash again (with display connected). Will continue to unplug my external display to see if that isolates the issue.
Now this is not exactly the bug that we're experiencing nut as this has to do with exernal monitors and usb-c hubs this will hopefully fix the issue?
I've learned my lesson though, I upgraded to mojave and big sur (skipped catalina) when they got on their .5 release and upgraded to monterey because I was eager but this is really annoying.
Experienced a crash again (with display connected). Will continue to unplug my external display to see if that isolates the issue.
Yes. Similar issue. I can no longer wake my computer if the lid is shut for more than 60 seconds (I timed it). This triggers a kernel panic. A restart is now always required if I shut my lid. Frustrating!!!
Changing arious PMSET codes (standby, hibernate, sleep, etc.) did not resolve the problem for me.
Apple IT support completed a full erase, OS Monterey installation and file reinstallation from icloud. The issue persisted.
Bottom line: There is no resolution at this time. I will need to wait for the next OS update. In the meantime I can't shut my computer lid without a full restart.
Model Identifier: MacBookPro16,1
Processor Name: 8-Core Intel Core i9
Processor Speed: 2.4 GHz
My last crash from sleep resulted in a restart, as usual... what was not usual was that the fan was stuck at 0, and guess what pretty soon the Mac Pro overheated... and kernel_task could not spin up the fan... and it shut down because of overheating...
I'm now using the following workaround: in the morning activate 'amphetamine' and set it to not sleep for 12 hours. Before sleep I disconnect the external display and reconnect it in the morning. Hopefully 12.1 fixes this which will probably be released to the public next week.
Interesting workaround and thanks. I've thought about using 'amphetamine'. If 12.1 doesn't solve the problem I think I'll explore that route. Appreciate your comment.
It is not good practice to remove your gpu cable while the Mac is on, you could damage your gpu.
Last edited:
Sitting hopeful for a fix in 12.1 too… Apple's firmware has struggled with Sleep/USB bugs/issues for years. Some versions have been better than others (only to see regressions in future updates).
This condition on the nMP 2013 "6,1" started following the latest Security Update 2021-007 for Catalina 10.15.7 (19H1519) with firmware 429.40.7.0.1. This issue remains after laboriously moving to fresh install of Monterey 12.0.1 (21A559), which keeps the same firmware 429.40.7.0.1 (as expected per hoakley's informative Eclectic Light Co).
A similar workaround to Amphetamine, has been running /usr/bin/caffeinate as a boot process via launchd and then manually poking at the monitors' off button when not in use. Nothing like finessing another sleep/power-management bug on a 12 core Xeon with a brutish Burn-All-The-Watts™ hammer.
Edit: Looks like expectations for a fix should be kept low if Monterey 12.1 (or Catalina Security Update 2021-008) arrive next week with firmware 429.60.3.0.0 …
Last edited:
I'm using a macbook air, so I don't think that's really an issue as it switch to the retina screen when I disconnect my external screen.
That's really annoying.