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

[Torq]

Quick update ... 9 straight days with no issues. Best I'd managed previously, after installing Monterey, was 3, and usually only half of that. Frustrating that it took so long to get the issue fixed, but definitely glad that it is.

 

[wagonfixin]

did the latest firmware work for you?

Yeppers! Catalina's Security-Update 2022-004 included updated firmware v430.120.6.0.0, which to-date, appears to have addressed my sleep/wake related panics/crashes on the nMP 6,1!

 

[loby]

This time it seemed to pay off contacting Apple or submitting a problem ticket about this issue. It caught someone’s attention and they gave us a fix.

Thanks to those who (at times painfully) talked with support to get through the denials or “it’s just an old part problem” etc. or “We did not do anything” response.

Shows it does pay off to submit a trouble ticket or contact Apple support when needed.

Back when Logic Pro X first came out, I had a project that needed to be completed and an update literally wrecked the program. I called support and support actually connected me with the one who created the program “eLogic” and he was still working at Apple at the time (I knew it was the guy through the German accent . I explained the problem and he told me that upper management was given him heat about this problem…BUT no one was giving him any technical information on the issue, “Just it was broke, fix it”. And was a little pissed off about it (had a laugh talking with him).

I gave him some technical info what I saw happening and what I thought was the problem (and solution), he actually thanked me for taking the time to explain the issue to my surprise. My solution probably was not the solution…but what I talked with him probably gave him enough to figure it out and come up with a patch that was sent out a week later.

This does not always happen of course, but unless Apple gets feedback or info., they might not know if there is a problem or may not have enough info. From real world users to fix the issue. Beta programs are good of course, but until it is actually “live” you won’t get all of the info. That is needed for a fix if needed.

Us users “scored” on this one, so “thanks” to all who contacted Support. We probably got our fix!

 

[ikir]

I am still having the same problem with my base-model 14" MBP 2021 on the latest MacOS Monterey 12.4. The kernel panic is the following:

panic(cpu 1 caller 0xfffffe001c4208d4): Wake transition timed out after 35 seconds while calling rootDomain's clients about completed rootDomain's state changes.

Normally I use an external monitor, a type C converter for the ethernet cable, and the Magsafe 2. That is all. I can not get rid of the issue. This is what I so far tested and not helped me:

- plugging off the HDMI cable before I put the device to sleep
- plugging off both the HDMI and the ethernet type C converter before the sleep
- plugging off all cables including Magsafe before the sleep
- turning off the wifi before the sleep
- turning off the bluetooth before the sleep
- turning off both wifi and bluetooth before the sleep

So you see, I find no solution to this issue and this makes me really angry and upset.
I can not understand why Apple has released these M1 chips with this major bug.
We are lots of people experiencing the same annoying problem.

Never heard of this issue in real life, like an hardware defect on you unit. I have a lot of costumers with new MacBook Pro and I own use one daily myself

I appreciate the positivity, but truly, this one squarely rests with Apple's software/firmware teams and their regression testing processes. Their customer-facing response (as well stated above by @haroldkman2000), only compounded the mistake of pushing out broken firmware v429.40.7.0.1 across all versions of macOS:

• In October 21, firmware v429.40.7.0.1 was quietly installed during a routine Security Update "2021-007" for Catalina v10.15.7 (19H1519), of note, this same defective firmware was also wholesale pushed to Big Sur and Monterey
• Shortly after installing 2021-007, our six Mac Pro 2013's began intermittently kernel panicking
• Multiple man hours on were wasted trying to figure out what/why was causing these mysterious kernel panics
• Several on our team assumed it was Apple pushing us to move to Big Sur/Monterey, and so, spent additional time upgrading to the newer macOS versions (and buying replacement Apple SSDs) - along with the time sunk into configuring their new OS, as it continued to kernel-panic on the new OS which shared the same defective firmware
• Support calls to Apple were disappointingly slow, across multiple days/levels - recursively painful, consisting of the expected scripted requests to reboot, PRAM/SMC reset, boot to Safe mode, diagnostics, and "perhaps try the new OS"
• As these attempts continued to "not work", escalated Support requested us to "install this tool and collect some data and send it in so we can analyze it" (this was the first response that appeared to recognize an issue, and didn't involve a canned Support response of "Hmmm, very strange, perhaps it's just you and something weird with your machine/config")
• When nothing came back from Apple Support after the collected data was submitted, the lacking response was escalated, leading to "it's likely a unique issue isolated to the macOS configuration" (which actually, was fairly different at that point!) as "Apple was unaware of anyone else experiencing these nMP kernel panics"
• When pushed for an Apple resolution for the two nMPs that still had AppleCare, I was told to take mine into the Apple store for additional troubleshooting and advanced diagnostics
• I'm not familiar with the nMP diagnostics tools at the Apple store, but they were unable to identify any specific problem that could cause the kernel panics, and stated that no kernel panic had occurred while they were testing it over several days. Perhaps it was my monitor? Would I be willing to try it with a different monitor? Why sure, I'd get a different model monitor and try that
• Trying a single LG monitor instead of the two Dell P2715Qs produced the same kernel panics, so it was lugged back to the Apple store for more analysis
• Finally, one young tech said he'd seen two panics over a 5 day period. It was assumed that it was a defective Logic, Interconnect, or I/O board. They'd order in the three boards in an attempt to isolate which one
• At this point all Apple Care was expired on all but one of the six nMPs. Our team had been moved onto Dell Xeon workstations (painfully screaming and kicking about their workflows - we loved our little trashcans!).
• Several of us had been advised it was likely an issue with the I/O board, but mine had kernel panicked several times with AppleCare's new I/O board
• I kept mine, setting it up with a startup daemon that launched caffeinate to prevent sleep mode
• Several of the unused nMPs were sold as "having macOS issues after sleeping"
• The rest were shelved, including mine after it's AppleCare expired in March

This thread and several others are littered with ideas to fix it by buying timered-outlets for the monitors, GUI power tweak ideas, voodoo involving pm/nvram Terminal commands attempting to whack Mac/macOS into not panicking, grasping at betas with more untested/unreleased firmware. Countless man-hours and aging synapses wasted - including this post.

I write this from my old nMP, still on my original install of Catalina, the only difference being: 7 lost months and May's Security Update 2022-004 (19H1922) which kindly included an updated firmware: v430.120.6.0.0. I've had this thing up and running with varying sleep/wake cycles since applying the 2022-004 update with no panics/crashes.

Apple has not contacted any of us to communicate this resolution.

I truly enjoy my Apple products. The hardware design, execution, and quality is unparalleled. The OS(s) and integration across the multiple device families are delightfully magical.

Apple needs to hear and understand their opportunities to improve - they need to be clearly informed of these stumbles so that they can adjust internally and externally.

Yes I get it, I agree, what I wanted to say is it still updated even if it was 2013-2014 machine and yes many PCs are left with not working components, bugs, we have at work HP with problematic USB-C ports whic will probably never fixed but they are recent only few years model.

And about all the other resolutions, those are old machines and some users had it runnning for years, full of dust and with cooked thermal paste. Some had both problems do not always is easy to identity the main issue this is the reason why you are so many different suggestion for a fix which was impossible since it was a firmware issue.

 

[Kaida]

Apple finally fixed the sleep problem and decided to remove it from Ventura... GG...

 

[arw]

Apple finally fixed the sleep problem and decided to remove it from Ventura... GG...

Or you could phrase it: "Despite Apple seeing no future for the MP6,1, they spent the resources to fix the (botched) firmware."
I honestly was not 100% convinced they would...
Don't demand too much from them 😅
edit: I understood "remove it (the MP6,1) from Ventura". If you meant the bug, then my response makes no sense.

 

[loby]

Apple finally fixed the sleep problem and decided to remove it from Ventura... GG...

Probably different teams working on Monterey and Ventura.

What has always amazed me is that when the next OS comes out, they don't use the old last version (like Monterey) and start from there. So Ventura probably started sometime last year or January and is why we have bugs that we don't have in the resent version of Monterey, but in Ventura.

This is probably why "once" it seems a stable OS...we start all over and takes another year to get to a stable version...then...back to the beginning...each year.

 

[fiatlux]

Glad to see Apple finally fixing the MP6,1 but almost suspicious that they waited for the Mac Studio release before releasing the fix.

I see the Studio as fairly close in philosophy to the MP6,1 and an upgrade option for many.

The recurring issues with my MP6,1 were a large part of my motives to moving on to a Studio. I don't regret the move as the newer machine is definitely much faster, with up-to-date interfaces and the capability to driver higher-res monitors, but I might have waited a bit more had that fix arrived before the release of the Mac Studio...

 

[arw]

For completeness' sake: No new firmware in yesterday's Big Sur Update (2022-06-09).
So the problem seems to have been fixed for good.

11.6.7 MP61 EFI Version: 430.120.6.0.0 (2022-05-16)

 

[FilthyMcNasty]

Not sure if this thread has taken over from https://forums.macrumors.com/threads/mac-pro-late-2013-gpu-driver-issues.1860297/page-82

I used to get the GPU freezes until I updated to Mojave.. since which it's not crashed ONCE.

I'm keen to upgrade, but nervous about it..

Is it categorically the case that, as far as we know, both GPU freezes and sleep issues have been resolved with Big Sur? Can I safely upgrade?

I have the base 6,1 mode with D400 GPUs.

 

[arw]

Is it categorically the case that, as far as we know, both GPU freezes and sleep issues have been resolved with Big Sur? Can I safely upgrade?

I have the base 6,1 mode with D400 GPUs.

You probably mean D300.
I can confirm 100% stable with D300 and Big Sur 11.6.7, which includes the latest official firmware 430.120.6.0.0. The latter is important regarding the sleep issue.

Although with this firmware, my D500 crashes when unplugging my EIZO CS2730 (even in boot picker). Hopefully it will get resolved with the even newer firmware (430.140.2.0.0) of the latest Monterey beta (RC). Or my display is faulty.
edit reason: actual cause currently unclear; unlikely firmware related

Update 2022-07-20: Big Sur 11.6.8 also includes the new firmware: 430.140.2.0.0 (Build Date 2022-04-18)

 

[Funk-O-Meter]

Hey all, I just wanted to say thanks for the help with my 6,1 that was having sleeping and freezing issues. I did the firmware update to 430.120.6.0.0 and crossed my fingers while I updated to Big Sur 11.6.7 and I've been crash-free since! I'm only going on 5 days of uptime so far, but I'm calling it a win! 🏆

My problems were the typical crashing while waking up from sleep, and 2-3 times a week I'd get the beachball-screen-freeze-reboot that was so common. It was almost always while using Safari, but occasionally when using something like Avid Pro Tools. Doing the tricks like putting the machine to sleep quickly using Shift+Cntrl+Eject or pulling the monitor cable out of the Mac didn't stop the machine rebooting itself like it has for some people. Since updating firmware and OS, I've not had a single crash, even with Power Nap turned back on. I have noticed that things are perhaps a bit more sluggish using Big Sur than with Catalina although I haven't played around to see if that's a screen resolution thing, and once or twice a day I have whatever video I'm watching flicker once, then behave normally. Not sure if this is a Big Sur thing, or if it's the video driver handling its issues differently. Anyway, for me, it's finally fixed! Thanks all!

Specs:

Model Identifier: MacPro6,1
Processor Name: 12-Core Intel Xeon E5 (upgraded from 6 core recently)
Processor Speed: 2.7 GHz
GPU: Dual D300's
Drive: Intel 2TB MVNE on an adapter
Memory: 32 GB
System Firmware Version: 430.120.6.0.0
SMC Version (system): 2.20f18
Panel Illumination Version: 1.4a6
Displays: Two Samsung 4k 27" 4k displays on TB2 ports (2560x1440 using EZ RES app to switch)
Audio: 2 UA Apollo audio interfaces on TB2 ports
USB Peripherals: 5 devices including 3 drives
Mac OS history: Mojave -> High Sierra -> Catalina -> Big Sur

 

[netkas]

Hello, what's up with 430.140.2.0.0 ? is it still stable with D300 ?

 

[FilthyMcNasty]

You probably mean D300.
I can confirm 100% stable with D300 and Big Sur 11.6.7, which includes the latest official firmware 430.120.6.0.0. The latter is important regarding the sleep issue.

Although with this firmware, my D500 crashes when unplugging my EIZO CS2730 (even in boot picker). Hopefully it will get resolved with the even newer firmware (430.140.2.0.0) of the latest Monterey beta (RC). Or my display is faulty.

Update 2022-06-20: Big Sur 11.6.8 also includes the new firmware: 430.140.2.0.0 (Build Date 2022-04-18)

Hi, thanks and yes I did mean the D300.

I see you reworded your reply but I'm wondering if I'll have problems with my monitors I use three concurrently :

1. HDMI to a 1080p monitor
2. Thunderbolt 2 to HDMI adaptor going to a plasma 1080p
3. Thunderbolt 2<3 convertor connecting to a WD50 Dock, from there a Mini DisplayPort to HDMI adapter runs to a projector.

On a reboot, I usually have to physically unplug 3 (the DP adaptor) then it's fine. No biggie.

Another question if I may : If the Big Sur firmware is working fine, does that mean it's possible to revert back to older versions of macOS, or is one committing to going in a forward direction? I'd prefer to install Big Sur to an external SSD and try it before committing, ideally!

Also curious why many posters have a preference for Big Sur over Monterey.

 

[tsialex]

Another question if I may : If the Big Sur firmware is working fine, does that mean it's possible to revert back to older versions of macOS,

Yes, you can boot Mavericks if you want to, like I did some days ago.

or is one committing to going in a forward direction?

Nope.

I'd prefer to install Big Sur to an external SSD and try it before committing, ideally!

No problem, if your main disk (the internal Apple blade) is formatted to APFS and you run 10.13.6->.

Also curious why many posters have a preference for Big Sur over Monterey.

Big Sur is stable, while Monterey is a moving target and different things break in different ways each new release.

12.5 betas and the RC1 didn't even opened the trash reliably.

 

[arw]

(...) I'm wondering if I'll have problems with my monitors (...)

Well, nobody knows what Apple changed in the firmware. But at this (evolved) point of Big Sur and MP6,1 I think it should be pretty unlikely.

3. Thunderbolt 2<3 convertor connecting to a WD50 Dock, from there a Mini DisplayPort to HDMI adapter runs to a projector.

I guess it would be less prone to problems if you'd just go the same route as in "2. Thunderbolt 2 to HDMI adaptor going to a plasma 1080p". Which is actually Mini Displayport to HDMI. TB2 and Mini DP just share the same geometry.

I can only say that the problem with my D500 and Displayport introduced in 430.120.6.0.0 persists in 430.140.2.0.0.
I narrowed it down: When booting from an external (USB) SSD and then rebooting from the internal SSD, I often have no signal on my Displayport monitors and the Mac just halts; luckily it doesn't even start booting so I can just force a power off. After disconnecting power (SMC reset) everything works again. So not a big problem.

edit reason: actual cause currently unclear; unlikely firmware related

 

[tsialex]

I can only say that the problem with my D500 and Displayport introduced in 430.120.6.0.0 persists in 430.140.2.0.0.

This afternoon @Borowski asked me the VBIOS + EFI module for the D700 and while extracting the EFI modules from the whole capsule I took some minutes to compare both the modules extracted from MP61.0124.B00 and 430.140.2.0.0 - both are exactly the same. Maybe the problem is not really with the GPU/VBIOS/EFI and your issue is just a consequence of problem somewhere else.

VBIOS was from 20160826, EFI was from 20170110.

 

[arw]

This afternoon @Borowski asked me the VBIOS + EFI module for the D700 and while extracting the EFI modules from the whole capsule I took some minutes to compare both the modules extracted from MP61.0124.B00 and 430.140.2.0.0 - both are exactly the same. Maybe the problem is not really with the GPU/VBIOS/EFI and your issue is just a consequence of problem somewhere else.

VBIOS was from 20160826, EFI was from 20170110.

Thanks for the info! Although I can't think of anything else, it obviously must be.
edit: In my case it has something to do with the last boot disk not being present on reboot. I thought handling the blessed volumes is firmware related.

 

[tsialex]

Thanks for the info! Although I can't think of anything else, it obviously must be.

MacPro6,1 firmware is very different from the MacPro5,1 one, that I know inside out, so I can't really suggest how to track/debug your issue, but if I have any ideas I'll ping you.

 

[tsialex]

In my case it has something to do with the last boot disk not being present on reboot. I thought handling the blessed volumes is firmware related.

Interesting, this could a NVRAM volume issue instead. You already know how to dump the BootROM, disable SIP, do a dump, compress it and send me by PM - I'll take a look.

Before I forget, ROMTool will gonna ask for the correct MXIC model with 3 possibilities, this don't really matter for now and you can select any of the three.

 

[steve123]

After a couple months without a sleep crash I have experienced a crash during sleep last night. I am running Monterey 12.5.1 with firmware 430.140.2.0.0 on a MP 6,1 w. D500. Noteably, when I rebooted I did not see the tell tale crash report. Not sure if that is a Monterey thing or not as my prior crashes occurred when I was running Big Sur. I started using Monterey about three weeks ago.

 

[SimonHodgkiss]

After a couple months without a sleep crash I have experienced a crash during sleep last night. I am running Monterey 12.5.1 with firmware 430.140.2.0.0 on a MP 6,1 w. D500. Noteably, when I rebooted I did not see the tell tale crash report. Not sure if that is a Monterey thing or not as my prior crashes occurred when I was running Big Sur. I started using Monterey about three weeks ago.

I've yet to test any recent updates to MacOS I gave up hope.

I have continued to just use a smart plug to power off all ALL connected displays to my Mac Pro and this works fine for me.

Little hassle for big rewards allowing me to keep the Mac Pro powered on and all apps open for when I return in my eyes just click the power on the smart plug and then wake the Mac Pro with Keyboard / Trackpad and everything runs as expected.

 

[harriska2]

My intel 2018 mini had sleep off but I couldn’t get the screen to wake. No problems for 4 years and upgraded to Monterey late last year. Not even unplugging the monitor fixed it. I had to do a complete reboot. I put the mini on its side and no problems since. I seriously wonder if it had heat problems.

 

[vddobrev]

After a couple months without a sleep crash I have experienced a crash during sleep last night. I am running Monterey 12.5.1 with firmware 430.140.2.0.0 on a MP 6,1 w. D500. Noteably, when I rebooted I did not see the tell tale crash report. Not sure if that is a Monterey thing or not as my prior crashes occurred when I was running Big Sur. I started using Monterey about three weeks ago.

My MP 6,1 is with D700 and I have not had any sleep crashes.
However, I still remember the Catalina security update that kind killed it. It had to be serviced, thankfully under UK consumer law and free of charge. The CPU riser card was replaced some two months ago. Ever since then, Monterey is rock solid on this machine.

 

[GoztepeEge]

My MBP 2021 14" M1 Pro is with the Monterey 12.5.1, with the latest update, and I have never encountered with a crash since I updated it a few weeks ago. I tried almost all scenarios: e.g. with and without HDMI, with and without charger cable plugged, with and without any USB C accessory plugged. In each scenario, everything went well and I had no issue so far.