MP 6,1 Mac Pro 6.1 Monterey - Crashes in Sleep

[adingley]

And a quick (unfortunate, but expectable) update: I woke the machine this morning to check something for a second / but didn't log-in — then I walked away for an hour or two. Just came back to the machine 10min ago, and it was just coming back to the log-in screen after a crash&reboot. So I'll go report back to Apple that neither the SMC reset, nor an NVRAM reset, nor updating to 12.1 has resolved this behavior.

 

[vddobrev]

And a quick (unfortunate, but expectable) update: I woke the machine this morning to check something for a second / but didn't log-in — then I walked away for an hour or two. Just came back to the machine 10min ago, and it was just coming back to the log-in screen after a crash&reboot. So I'll go report back to Apple that neither the SMC reset, nor an NVRAM reset, nor updating to 12.1 has resolved this behavior.

Same experience here.

 

[haroldkman2000]

And a quick (unfortunate, but expectable) update: I woke the machine this morning to check something for a second / but didn't log-in — then I walked away for an hour or two. Just came back to the machine 10min ago, and it was just coming back to the log-in screen after a crash&reboot. So I'll go report back to Apple that neither the SMC reset, nor an NVRAM reset, nor updating to 12.1 has resolved this behavior.

And same for me. I tried SMC reset and NVRAM reset yesterday and it earlier crashed after being asleep for a few hours. This time it crashed in com.apple.iokit.IOUSBHostFamily but it's crashed in different places over the weeks.

 

[SimonHodgkiss]

I have a MacPro Late 2013 and have had the crash on sleep issues on and off since upgrading to Monterey. No issues before that. 12.1 has not helped at all. I have a MacBookPro 2016 model and a MacMini 2018 model on Monterey with no issues. When I spoke with Apple support a month ago they had me boot into safe mode, and no issues were reported. They said if it kept happening they would want me to re-install the OS. Since it never has issues while running, I have just lived with the issue in hopes they will get around to fixing it.

Please test my fix after you have put the Mac Pro 2013 to sleep disconnect all power to ALL connected displays either at the outlet or by using a smart plug.

 

[SimonHodgkiss]

Just a quick note — You maybe have been one of the folks who already did submit reports to apple, but I'm also certain that a lot of people don't (they might just dismiss the prompt). Moreover, I know that a lot of folks don't spend their time calling into AppleCare, but I encourage anyone else who's dealing with this to call in about it too.

I spent 20+ min on the phone with a tier 2 support specialist at Apple (about 10days ago) and at the time, he shared that there were no similar/related issues reported to Apple Support... so my thoughts would be: If you're ONLY posting here on this thread, make sure to a) submit your error reports/crash-reports when you get the 'restarted because of a problem' pop-up and/or b) call this in to AppleCare and give them a thorough run-down of your MP6,1 setup & what you're experiencing.

My AppleCare case is still open, and I've been experimenting with 12.1 for 3+ days now — not a single crash so far. I have restarted the machine myself for other reasons, but it's never restarted itself since the update. If I get a week+ out of 12.1, I'm gonna go ahead and update my other partition to 11.6.2 (11.4 is rock solid, but 11.6 crashes in the same way on this machine) — as for 12.1: I'm still hesitant to imagine that it's truly solved (especially reading that others have not seen improvements) but seriously — make noise with Apple Support directly (if you haven't already).

That's an absolute load of rubbish that you've been told because I've spent about 3 hours on the phone with Apple since October about this issue.

They told me there was 1 other user reporting this.

I believe they are not providing you with the correct information.

As I've previously on this post there is a simple work around that I've found.



Completely remove power to all connected displays once the Mac Pro is in sleep mode.

Either by killing power at the outlet or by smart plugs works a dream not crashed since.

 

[Savorn]

I just finished a conversation with support. The employee had no clue about this issue and referred me to a local service provider.

Rebooting seems to get worse over time. Last night 24 hours it rebooted 4 times.

I do seem to have a different shutdown cause than others in this thread. My log reads -63.

Will try removing power from the connected displays next as suggested by @SimonHodgkiss

 

[adingley]

I've spent about 3 hours on the phone with Apple since October about this issue.

Well, That's a bummer — and I'm sorry you've also sunk so much time into this. I think I'm pushing 2-3hrs now as well. I just wrapped a call with support after the problem has recurred on ALL partitions of my SSD boot drive. (even the 11.4 Big Sur partition that I previous thought was immune to the problem)

So I'm going to spend the next 48hrs with none of my USB / TB2 peripherals plugged into the Mac Pro. Once I've gone a couple of days with nothing more than power / ethernet / HDMI connected, I'll report it back to them either way. They've detailed that the next step (if it recurs with no peripherals) is to do a detailed call with them to capture a ton of data that gets put directly in front of some engineers / who'll then report back on what they believe the problem is.

Painful process so far — certainly not conducive to being super productive. And due to my cable-management & the lacking ergonomics of my studio, I'm not really able to try the "just unplug the monitor whenever you're not using the Mac" method.

 

[SimonHodgkiss]

Well, That's a bummer — and I'm sorry you've also sunk so much time into this. I think I'm pushing 2-3hrs now as well. I just wrapped a call with support after the problem has recurred on ALL partitions of my SSD boot drive. (even the 11.4 Big Sur partition that I previous thought was immune to the problem)

So I'm going to spend the next 48hrs with none of my USB / TB2 peripherals plugged into the Mac Pro. Once I've gone a couple of days with nothing more than power / ethernet / HDMI connected, I'll report it back to them either way. They've detailed that the next step (if it recurs with no peripherals) is to do a detailed call with them to capture a ton of data that gets put directly in front of some engineers / who'll then report back on what they believe the problem is.

Painful process so far — certainly not conducive to being super productive. And due to my cable-management & the lacking ergonomics of my studio, I'm not really able to try the "just unplug the monitor whenever you're not using the Mac" method.

Yeah I guess that’s how things go.

I went through the exact same steps with my senior Apple Tech too. They downloaded the logs for the days when it crashed to check what was going on.

Honestly I’ve given up on speaking to Apple since I learned that if you just disconnect power to ALL connected displays while in sleep the Mac no longer crashes. I understand this may not be convenient for you to do so. But I can confirm that it also works with a smart plug as long as you kill the power to all displays.

Good luck with the rat hole you’ve gone down unfortunately their doesn’t seem to be an end anytime soon.

 

[adingley]

Has anyone (specifically with a Mac Pro 6,1 — I know there are/were some Mac mini / MacBook Pro folks in this thread too) tried running their tower with no peripherals plugged in? (or just the bare minimum?). I've been running since 36hr ago with no crash/restarts (but I have no USB / no TB2 peripherals plugged-in). I'm only running my HDMI monitor (LG 34" Ultrawide) & Power & gigabit ethernet & headphones out, at the moment. Waiting to see how long it goes before it crashes during sleep. If I get to 3 days — I'll bring one additional peripheral back every 48 hrs and see if/when the crash/reboots finally recur.

 

[pTz]

What I’ve noticed is if you run transmission and have an active torrent, my MacBook Pro won’t crash/reboot. I too am sick of returning to it only to find myself looking at the login screen. I think it’s something to do with power-states triggering something. Hoping for a fix sooner than later.

Possible fix/workaround:

This is usually caused by peripherals that are not sleep-compliant. Security & Privacy > General, do not tick "Require password [immediately] after sleep or screen saver begins. If there's a closed padlock icon in the lower left corner of the preference pane, click it and enter your login password when prompted.

Cancel that - another reboot to login screen - arghhh

Having transmission running with an active torrent seems to solve the issue though.

And yes - turning off my 2 external monitors allows my Mac to power down or sleep without any issues. It never shuts down 100%, it hangs at the black screen but the power light stays on.

 

[Savorn]

Disconnecting my display after sleep didn't prevent my Mac from crashing. Got two last 24h:

2021-12-24 18:13:23.775901+0100 0xd1       Default     0x0                  0      0    kernel: (AppleSMC) Previous shutdown cause: -63
2021-12-25 08:32:40.824200+0100 0xd0       Default     0x0                  0      0    kernel: (AppleSMC) Previous shutdown cause: -2

I now have a -2 also ?‍♂️..

Only peripherals I have connected are my wireless Apple Keyboard, a Logitech MX mouse with its own dongle, my display through HDMI, an external audio controller through USB and ethernet.

 

[TheJae]

Having problem with my MacBook going to sleep and crashing

MacBook Pro (13-inch, 2019, Four Thunderbolt 3 ports)

 

[chkwong]

Disconnecting my display after sleep didn't prevent my Mac from crashing. Got two last 24h:

2021-12-24 18:13:23.775901+0100 0xd1       Default     0x0                  0      0    kernel: (AppleSMC) Previous shutdown cause: -63
2021-12-25 08:32:40.824200+0100 0xd0       Default     0x0                  0      0    kernel: (AppleSMC) Previous shutdown cause: -2

I now have a -2 also ?‍♂️..

Only peripherals I have connected are my wireless Apple Keyboard, a Logitech MX mouse with its own dongle, my display through HDMI, an external audio controller through USB and ethernet.

Bluetooth wireless apple keyboard is the cause
The Bluetooth connected device cause the problem.

 

[TheValleyOfDefilement]

Clean your systems out, and replace the BR2032 battery.
I run loads of accessories, 4K ultra wide screen, and keep it on 24/7. No issues. No KPs.
E5-2667 V2, D-700 A card, D-500 B card.

 

[SimonHodgkiss]

Has anyone (specifically with a Mac Pro 6,1 — I know there are/were some Mac mini / MacBook Pro folks in this thread too) tried running their tower with no peripherals plugged in? (or just the bare minimum?). I've been running since 36hr ago with no crash/restarts (but I have no USB / no TB2 peripherals plugged-in). I'm only running my HDMI monitor (LG 34" Ultrawide) & Power & gigabit ethernet & headphones out, at the moment. Waiting to see how long it goes before it crashes during sleep. If I get to 3 days — I'll bring one additional peripheral back every 48 hrs and see if/when the crash/reboots finally recur.

Yeah Apple Support told me to try running it without anything plugged in but my Mac Pro still crashed.

My workaround of removing power to all displays works like a dream. I'm close to 4 weeks without any crashes since removing the power to the displays. I have 12 USB devices and Apple Bluetooth Keyboard and Trackpad still connected and it doesn't crash.

 

[Corkers]

My 12.1 update seemed to work for a day or so, but then went back to its regular "crash and restart on wake" behaviour. Thought I'd try @SimonHodgkiss suggestion - put a smart plug on the monitor. When I leave my Mac I ask Siri to turn off the monitor, the Mac goes to sleep, and when I come back to it, just wake the Mac, then ask Siri to wake the monitor. Been working perfectly for a few days now, so thanks Simon ? It's still a fudge rather than a fix, but hopefully it'll be sorted in the next update. Hey, I can dream... ?

 

[adingley]

Yeah Apple Support told me to try running it without anything plugged in but my Mac Pro still crashed.

My workaround of removing power to all displays works like a dream. I'm close to 4 weeks without any crashes since removing the power to the displays. I have 12 USB devices and Apple Bluetooth Keyboard and Trackpad still connected and it doesn't crash.

So during my disappointing call with Apple (following up after engineering looked at my captured data) They told me that engineering had seen two errors in my system. I think they were “-2” and “-35”, and she suggested that they believe the problem is a failing power supply and a failing Logic board. I pushed back politely, stating that it seemed really odd that the timing of this failure would be “nearly immediately after the Monterey update” and that my symptoms would be identical to those of several other users with this same machine after the Monterey update.

I don’t know the AppleSupport repair cost for a Tier2 (or maybe it’s tier 3) repair in 6,1 tower, but it can’t be cheap.

Before I decide whether to humor them with a drop off for a proper quote, I decided to try something simple. I stopped using hdmi on the Mac Pro. I had an old “DisplayPort -> hdmi” cable and I popped that into a thunderbolt port on the tower. I did that the afternoon of Tuesday the 28th. So far, not a single crash since. It’s only been ~4 days, but I’m starting to wonder if this might solve it for me. Not sure that I saw anyone posting specifics about how their respective displays are connected.

 

[adingley]

I run loads of accessories, 4K ultra wide screen, and keep it on 24/7. No issues. No KPs.
E5-2667 V2, D-700 A card, D-500 B card.

so, did you ever experience this issue after upgrading to Monterey? (And is your suggestion “how” you solved it?) Or has your 6,1 tower been crash-free the whole time?

 

[haroldkman2000]

So during my disappointing call with Apple (following up after engineering looked at my captured data) They told me that engineering had seen two errors in my system. I think they were “-2” and “-35”, and she suggested that they believe the problem is a failing power supply and a failing Logic board. I pushed back politely, stating that it seemed really odd that the timing of this failure would be “nearly immediately after the Monterey update” and that my symptoms would be identical to those of several other users with this same machine after the Monterey update.

I don’t know the AppleSupport repair cost for a Tier2 (or maybe it’s tier 3) repair in 6,1 tower, but it can’t be cheap.

Before I decide whether to humor them with a drop off for a proper quote, I decided to try something simple. I stopped using hdmi on the Mac Pro. I had an old “DisplayPort -> hdmi” cable and I popped that into a thunderbolt port on the tower. I did that the afternoon of Tuesday the 28th. So far, not a single crash since. It’s only been ~4 days, but I’m starting to wonder if this might solve it for me. Not sure that I saw anyone posting specifics about how their respective displays are connected.

IMHO, Apple Support and Engineering is completely clueless about this. Failing power supply and or logic board? No way. As you mention, there are many experiencing this right after upgrading to Monterey and in the same manner. That certainly sounds like software and not hardware.

I'm still crashing just about every day still on the Mac Mini 2018 I upgraded to Monterey about a month ago. I have HDMI going out to my TV but haven't tried not using HDMI or using a smart outlet to block power to the TV, but will probably give the smart outlet a go soon.

 

[edanuff]

I guess just keep sending in the crash reports. There’s little chance that any software engineers were looking at the backlog the last two weeks of the year so I’d not put much stock in feedback from support at this point.

 

[adingley]

IMHO, Apple Support and Engineering is completely clueless about this. Failing power supply and or logic board? No way. As you mention, there are many experiencing this right after upgrading to Monterey and in the same manner. That certainly sounds like software and not hardware.

I'm still crashing just about every day still on the Mac Mini 2018 I upgraded to Monterey about a month ago. I have HDMI going out to my TV but haven't tried not using HDMI or using a smart outlet to block power to the TV, but will probably give the smart outlet a go soon.

And just an update. Another day / no crashes (since I switched to using Mini DisplayPort-to-hdmi to feed my 34” ultra wide monitor) if I get a full week without crashes, I’m gonna see if the support rep will do a second “capture data” session with me and have engineers look again. So I’ll report back again on Tuesday night

 

[Mr.Chefkoch]

I'm still running my 6,1 without any peripherals connected at all, only power plug and two LAN cables connected to it and just using remote access to connect to it and seeing crashes all the time. I'm quite sure it's not related to displays or bluetooth keyboards.

And I have a new BR2032 battery and everything is nice and clean, as suggested by @TheValleyOfDefilement.

 

[adingley]

Monday morning — still no crashes on my 6,1 Tower since I switched over to using TB→HDMI for my display instead of the HDMI port. Tomorrow afternoon it'll have been 7 days with no crash. Fingers-crossed.

 

[wagonfixin]

I'm still running my 6,1 without any peripherals connected at all, only power plug and two LAN cables connected to it and just using remote access to connect to it and seeing crashes all the time. I'm quite sure it's not related to displays or bluetooth keyboards.

And I have a new BR2032 battery and everything is nice and clean, as suggested by @TheValleyOfDefilement.

Interesting configuration/way to better isolate. I’m assuming your crash log files consistently show the same reason/cause for the crashes?

Will try this configuration in the coming week - or so (currently using macOS’s caffeinate with launchd as a workaround to prevent any sleep states).

Sounds much quicker than the already multiple hours on the phone with Apple tiers just to run remote diagnostics (nothing found for both the boot diag or their remote Apple tool), then an ask for me to run some other long-winded local diagnostic utility with upload of collected data, then told to bring it in for further testing (where they couldn’t replicate the crash over a 5 day period) - followed by a less-than-reassuring offer to replace the main logic board (at my cost) to ”be sure it wasn’t a defective component causing an intermittent issue”.

I remain fairly confident that this is a firmware based issue as it occurred on both Catalina and Monterey immediately following the nMP’s upgrade to firmware 429.40.7.0.1, and has remained under subsequent firmware 429.60.3.0.0.

To be clear, I’ve had no crashes whatsoever on Catalina (and now Monterey) when running many multi-day heavy loads. All crashes occur after the loads have completed and the nMP has gone into a prolonged sleep state. When woke, the crash has already occurred (eg: it died earlier as it came in/out of Power-Nap or changed to/from one of Intel’s power-saving states), and it’s back at the macOS login prompt followed by the crash submission dialog.

 

[adingley]

Sounds much quicker than the already multiple hours on the phone with Apple tiers just to run remote diagnostics (nothing found for both the boot diag or their remote Apple tool), then an ask for me to run some other long-winded local diagnostic utility with upload of collected data, then told to bring it in for further testing (where they couldn’t replicate the crash over a 5 day period) - followed by a less-than-reassuring offer to replace the main logic board (at my cost) to ”be sure it wasn’t a defective component causing an intermittent issue”.

I remain fairly confident that this is a firmware based issue as it occurred on both Catalina and Monterey immediately following the nMP’s upgrade to firmware 429.40.7.0.1, and has remained under subsequent firmware 429.60.3.0.0.

Are you suggesting that you were also spending all those hours with Apple Support and that you were also provided the option to replace YOUR MLB, or were you simply suggesting that it sounds better to do the aforementioned test than to do what us other folks have had to do?

Just trying to get a sense of how many folks have gone all the way down the same path that I went down.