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 7,1 Cursed Mac Pro 2019.... help?
- Thread starter Dt990
- Start date
- Sort by reaction score
I stated this before, I yanked every, replaced the RAM, and booted off the basically untouched SSD, still had issues. This is so not being fixed by reinstalling the OS.
Also I noticed that in the console log, the KPs are as follows:
macOS Version: Mac OS X 13.4.1 (22F82)
Bridge OS Version: Bridge OS 7.5 (20P5060)
Panic String: SEP Panic: :SEPD/intr: 0x0000f732 0x000240d7 0x0000be61 0x000078f5 0x00000000 0x00000000 0x00000000 0x00000000 [vnji]
Panic Flags: 0x802
Seems like the T2 is ******** the bed, taking a day off Friday so I can go to the apple store mid day.
Basically, it's happened with 3 different boot drives, at stock hardware. The fact it keeps unknown thread crashing makes me think this isn't software.
Last edited:
Then, in that case, have you tried doing a DFU restore of bridgeOS on the T2 chip? That generally resolves most issues pertaining to the T2 chip.
Be warned, it's a finnicky process. They made booting to DFU mode much...easier with the Apple Silicon Macs. Though, once you get to that point, it'll be the same steps (and quicker since DFU restoring on a T2 Mac just restores the T2 Mac's firmware, whereas a DFU restore on an Apple Silicon Mac restores the whole Mac and therefore requires the size of a full macOS installer). It will also completely wipe the stock SSD (since the storage controller for that drive is integrated into the T2).
You'll also need another Mac, preferably one equipped with some form of USB-C (can be Intel or Apple Silicon) running the most recent version of Apple Configurator 2.
Toward this end, while I've found that the documentation to "Revive or Restore a Mac with Apple Silicon" from Apple is pretty decent, the "Revive and Restore an Intel Mac with the T2 Security Chip" counterpart article, on the other hand, has some...misleading information and will probably have you pulling out your hair a few times. www.mrmacintosh.com has a much better guide to follow for T2 Intel Macs that works more consistently.
Actually was just trying this tonight, I've set an Apple Silicon Mac in DFU but holy christ I cannot get this **** to work, the Apple guide as mentioned just says to plug in the Mac Pro 2019 on the right hand top port and then hold the power button for 4 seconds. Hold it down much longer it and it aborts the boot and shuts down.
There there's 10 seconds of latency between hitting power and the chime.
I've tried just randomly hitting the power button for a second or two and then holding the keys before the chime like option booting, diagnostics, clearing NVRAM, safe booting etc. It just inits booting off the internal SSD.
As mentioned my internal SSD is basically unused, so any data on it is fine to wipe, yanked out my six SSDs to be safe but I cannot get this sumbitch into DFU.
The two things I checked out was:
/edit: see next post
Last edited:
Okay, never mind, gotta read closer.
Here's the step incase some poor soul google's it, I'll make this a better guide on my personal blog as well.
IGNORE ANY INFORMATION ABOUT KEY COMBOS OR ANY INFO ABOUT OTHER MACS.
Here's the step incase some poor soul google's it, I'll make this a better guide on my personal blog as well.
How to restore a Mac Pro 2019 desktop into DFU.
IGNORE ANY INFORMATION ABOUT KEY COMBOS OR ANY INFO ABOUT OTHER MACS.
- Have a second Mac, Apple Silicon works fine. I used a M1 Max. Get the Apple Configuration utility.
- Connect your Macs together, use the right most top port (away from the power button). I used a Thunderbolt cable because it was the first thing on my desk
- Unplug the Mac Pro. The trick is when you yank the power cord, you'll hear a "ding". At least mine does, that means waiting all of about 2 seconds.
- Hold down the power button and plug in the power cable. Count off to about 5.
- You will not hear any fans spin, the light will not change or receive iany confirmation that the Mac Pro has booted, check your other Mac in Apple Configuration utility, it should display the dfu screen.
- Proceed as planned. Right click in the configurator, and go to advanced -> Revive Device.
Last edited:
Yeah, it's confusing that it's different between Intel Macs with the T2 chip and Apple Silicon Macs. Again, Apple's documentation and steps for the Apple Silicon Macs seems sound. I've almost never been able to get their steps for Intel Macs with the T2 to work (and I've had to do it on 2019 Mac Pros, 2019 MacBook Airs, and some 2018 and 2019 MacBook Pros as part of my last job), whereas Mr. Macintosh's steps for it seems to work pretty much every time.
And yeah, your average bridgeOS install file is around ~650MB; the average Apple Silicon Mac restore file is around 14GB, but that's because it contains macOS rather than bridgeOS. So, downloading that file will be quick on all but the absolute worst of Internet connection speeds. Fun fact: you also don't have to re-download it again so long as the version you previously downloaded is current (though, that's more handy for the much larger Apple Silicon Mac restore files).
WAY more importantly, did it resolve your issues?
Haven't had time to test yet, just did the DFU last night. My gut says no but who ok.
I'd be curious. It tends to resolve a surprising amount of random issues. While I am somewhat sad that the Intel era is over, I'm not even remotely sad to see the T2 chip on its path to extinction. I hate that thing with a passion.
You and me both, I had a MacBook Pro 2017 (work provided) and the touchbar decided to take a vacation, nothing worked. Then 3 weeks later, it came back to life. Absolute madness.
Anyhow, I did experience a long beach ball quasi-crash where the whole system is mostly unresponsive. Logd and Bluetoothd
The logs always wantonly unhelpful:
Bash:
-------------------------------------
Translated Report (Full Report Below)
-------------------------------------
Process: logd [-1]
Path: ???
Identifier: logd
Version: ???
Code Type: 00000000 (Native)
Parent Process: ??? [Unknown]
User ID:
Date/Time: 2023-07-25 13:33:47.8864 -0700
OS Version: macOS 13.5 (22G74)
Report Version: 12
Anonymous UUID: 3E07AEA0-3737-2A3D-6127-D2CDC7759A43And of course
Code:
-------------------------------------
Translated Report (Full Report Below)
-------------------------------------
Process: bluetoothd [172]
Path: /usr/sbin/bluetoothd
Identifier: bluetoothd
Version: ???
Code Type: X86-64 (Native)
Parent Process: launchd [1]
User ID: 0
Date/Time: 2023-07-25 13:34:34.5378 -0700
OS Version: macOS 13.5 (22G74)
Report Version: 12
Bridge OS Version: 7.6 (20P6072)
Anonymous UUID: 3E07AEA0-3737-2A3D-6127-D2CDC7759A43
Sleep/Wake UUID: C857BF35-500F-443D-897F-88330C286CDB
Time Awake Since Boot: 7500 seconds
Time Since Wake: 3991 seconds
System Integrity Protection: enabled
Crashed Thread: 8 Dispatch queue: com.apple.root.utility-qos
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Termination Reason: Namespace SIGNAL, Code 6 Abort trap: 6
Terminating Process: bluetoothd [172]
Application Specific Information:
abort() calledAnd some of the general lagginess from random beach balling. It's baffling.
Fascinating looking through my logs as I keep seeing the following error:
Doubt this is what's really the root but trying to execute ARM64 on my Mac? WTF.
Also went on a permissions checking spree, following electric light co's advise, can't run `diskutil resetUserPermissions` these days so used the PermScan and rm-d prefs that weren't writable and chmodded recursively pretty much everything sans containers in ~/Library.
Code:
2023-07-25 13:45:13.971047 (pid/1128/com.apple.speech.MacinTalkFramework.WardaSynthesizer.arm64) <Notice>: service state: not running
2023-07-25 13:45:13.971060 (pid/1128/com.apple.speech.MacinTalkFramework.WardaSynthesizer.arm64) <Notice>: canceling penalty-box spawn
2023-07-25 13:45:13.971063 (pid/1128/com.apple.speech.MacinTalkFramework.WardaSynthesizer.arm64) <Notice>: internal event: SPAWNED, code = 89
2023-07-25 13:45:13.971068 (pid/1128/com.apple.speech.MacinTalkFramework.WardaSynthesizer.arm64) <Notice>: internal event: WILL_SPAWN, code = 0
2023-07-25 13:45:13.971071 (pid/1128/com.apple.speech.MacinTalkFramework.WardaSynthesizer.arm64) <Notice>: service state: spawn scheduled
2023-07-25 13:45:13.971073 (pid/1128/com.apple.speech.MacinTalkFramework.WardaSynthesizer.arm64) <Notice>: service state: spawning
2023-07-25 13:45:13.971171 (pid/1128/com.apple.speech.MacinTalkFramework.WardaSynthesizer.arm64) <Notice>: launching: launch job demand
2023-07-25 13:45:13.971633 (pid/1128/com.apple.speech.MacinTalkFramework.WardaSynthesizer.arm64 [5492]) <Notice>: xpcproxy spawned with pid 5492
2023-07-25 13:45:13.971649 (pid/1128/com.apple.speech.MacinTalkFramework.WardaSynthesizer.arm64 [5492]) <Notice>: internal event: SPAWNED, code = 0
2023-07-25 13:45:13.971652 (pid/1128/com.apple.speech.MacinTalkFramework.WardaSynthesizer.arm64 [5492]) <Notice>: service state: xpcproxy
2023-07-25 13:45:13.971669 (pid/1128/com.apple.speech.MacinTalkFramework.WardaSynthesizer.arm64 [5492]) <Notice>: internal event: SOURCE_ATTACH, code = 0
2023-07-25 13:45:13.976790 (pid/1128/com.apple.speech.MacinTalkFramework.WardaSynthesizer.arm64 [5492]) <Warning>: Could not find and/or execute program specified by service: 86: Bad CPU type in executable: /System/Library/PrivateFrameworks/MacinTalk.framework/Versions/A/PlugIns/WardaSynthesizer_arm64.appex/Contents/MacOS/WardaSynthesizer_arm64
2023-07-25 13:45:13.976800 (pid/1128/com.apple.speech.MacinTalkFramework.WardaSynthesizer.arm64 [5492]) <Error>: Service could not initialize: posix_spawn(/System/Library/PrivateFrameworks/MacinTalk.framework/Versions/A/PlugIns/WardaSynthesizer_arm64.appex/Contents/MacOS/WardaSynthesizer_arm64) EBADARCH, error 0x6f - Invalid or missing Program/ProgramArguments
2023-07-25 13:45:13.976803 (pid/1128/com.apple.speech.MacinTalkFramework.WardaSynthesizer.arm64 [5492]) <Error>: initialization failure: 22G74: xpcproxy + 22576 [1063][E5C56CFD-9EFD-3187-8D09-B350D1F17D04]: 0x6f
2023-07-25 13:45:13.976805 (pid/1128/com.apple.speech.MacinTalkFramework.WardaSynthesizer.arm64 [5492]) <Notice>: Service setup event to handle failure and will not launch until it fires.
2023-07-25 13:45:13.976808 (pid/1128/com.apple.speech.MacinTalkFramework.WardaSynthesizer.arm64 [5492]) <Notice>: draining messages from com.apple.speech.MacinTalkFramework.WardaSynthesizer.arm64
2023-07-25 13:45:13.976812 (pid/1128/com.apple.speech.MacinTalkFramework.WardaSynthesizer.arm64 [5492]) <Notice>: draining messages from com.apple.speech.MacinTalkFramework.WardaSynthesizer.arm64.apple-extension-service
2023-07-25 13:45:13.976816 (pid/1128/com.apple.speech.MacinTalkFramework.WardaSynthesizer.arm64 [5492]) <Error>: Missing executable detected. Job: 'com.apple.speech.MacinTalkFramework.WardaSynthesizer.arm64' Executable: '/System/Library/PrivateFrameworks/MacinTalk.framework/Versions/A/PlugIns/WardaSynthesizer_arm64.appex/Contents/MacOS/WardaSynthesizer_arm64'
2023-07-25 13:45:13.976818 (pid/1128/com.apple.speech.MacinTalkFramework.WardaSynthesizer.arm64 [5492]) <Notice>: internal event: INIT, code = 111
2023-07-25 13:45:13.976820 (pid/1128/com.apple.speech.MacinTalkFramework.WardaSynthesizer.arm64 [5492]) <Notice>: job state = spawn failed
2023-07-25 13:45:13.976979 (pid/1128/com.apple.speech.MacinTalkFramework.WardaSynthesizer.arm64 [5492]) <Error>: Could not remove job: error = 144: Requestor lacks required entitlement
2023-07-25 13:45:13.977400 (pid/1128/com.apple.speech.MacinTalkFramework.WardaSynthesizer.arm64 [5492]) <Notice>: xpcproxy exited due to exit(78)
2023-07-25 13:45:13.977413 (pid/1128/com.apple.speech.MacinTalkFramework.WardaSynthesizer.arm64 [5492]) <Notice>: exited due to exit(78)
2023-07-25 13:45:13.977430 (pid/1128/com.apple.speech.MacinTalkFramework.WardaSynthesizer.arm64 [5492]) <Notice>: already handled failed init, ignoring
2023-07-25 13:45:13.977433 (pid/1128/com.apple.speech.MacinTalkFramework.WardaSynthesizer.arm64 [5492]) <Notice>: service state: exited
2023-07-25 13:45:13.977438 (pid/1128/com.apple.speech.MacinTalkFramework.WardaSynthesizer.arm64 [5492]) <Notice>: internal event: EXITED, code = 0
2023-07-25 13:45:13.977441 (pid/1128 [axassetsd]) <Notice>: service inactive: com.apple.speech.MacinTalkFramework.WardaSynthesizer.arm64
2023-07-25 13:45:13.977443 (pid/1128/com.apple.speech.MacinTalkFramework.WardaSynthesizer.arm64 [5492]) <Notice>: draining messages from com.apple.speech.MacinTalkFramework.WardaSynthesizer.arm64
2023-07-25 13:45:13.977448 (pid/1128/com.apple.speech.MacinTalkFramework.WardaSynthesizer.arm64 [5492]) <Notice>: draining messages from com.apple.speech.MacinTalkFramework.WardaSynthesizer.arm64.apple-extension-service
2023-07-25 13:45:13.977452 (pid/1128/com.apple.speech.MacinTalkFramework.WardaSynthesizer.arm64 [5492]) <Notice>: service state: not running
2023-07-25 13:45:13.977454 (pid/1128/com.apple.speech.MacinTalkFramework.WardaSynthesizer.arm64) <Notice>: internal event: WILL_SPAWN, code = 0
2023-07-25 13:45:13.977457 (pid/1128/com.apple.speech.MacinTalkFramework.WardaSynthesizer.arm64) <Notice>: service state: spawn scheduled
2023-07-25 13:45:13.977872 (pid/1128/com.apple.speech.MacinTalkFramework.WardaSynthesizer.arm64) <Notice>: signal service: caller = axassetsd[1128], value = 0x9
2023-07-25 13:45:14.816536 <Notice>: Last log repeated 2 timesDoubt this is what's really the root but trying to execute ARM64 on my Mac? WTF.
Also went on a permissions checking spree, following electric light co's advise, can't run `diskutil resetUserPermissions` these days so used the PermScan and rm-d prefs that weren't writable and chmodded recursively pretty much everything sans containers in ~/Library.
Last edited:
The 2016 and 2017 Touch Bar MacBook Pros had the T1 chip and ran an entirely different OS to govern both it and Touch ID that lived in the EFI partition on the drive. It was called embeddedOS and it was installed and updated as part of macOS on those machines (rather than its own separate system with bridgeOS and the T2 chip). I'm not saying I preferred the T1's approach to the T2's approach; both are two entirely different flavors of kludgy. The former makes for some interesting challenges when trying to set up Windows 10 as the sole OS (rather than do Apple's guided dual-boot setup via the Boot Camp Assistant).
I'm inclined to believe you have a bad logic board, at this point. I do not believe the Bluetooth module is removable and whether or not it is ultimately the actual issue, you've definitely narrowed out software (by trying other OSes on both the T2-governed drive as well as other internal storage).
The T2 is effectively an Apple A10 Fusion, but specifically for bridgeOS on the T2 (rather iOS on an iPhone 7/7 Plus or 7th Generation iPod touch). It's an ARM64 processor, even if only an extremely specialized one.
Incidentally, most of the "Hey, Siri" flavor of voice processing is handled by the T2 and not by the Intel Processors or any other system component. Seeing as you have just done a DFU restore of the Mac Pro and are still having issues, my guess goes right back to a failing logic board (seeing as the T2 is absolutely an unremovable logic board component.
Hopefully, you are under AppleCare+ still. If not, see what the cost to fix the logic board is. I don't know that it's quite the cost of a new 2023 model, but it's possible that it might be similar to the cost of a refurbished 2019 model that is similar in specs to what you have. My guess is that switching to an Apple Silicon Mac Pro would probably be a massive pain and more trouble than it's worth for you with your current setup.
Hoping for the best for you, friend. Let us know how it all goes!
Right, forgot the 2017 was T1. It didn’t have the Secure Enclave running sepOS etc.
Didn’t buy Apple Care as I’ve never had a Mac go bad, at least within 3 years. I’m not really sure what I’d do if apple tossed out some sort of insane pricing to fix it. Kinda ****ed as the Mac Pro 2019 was a wacky purchase made by the happenstance of having a few GPUs during the gpu crisis and selling off my two Mac Pro 5,1s. I have my M1 Max but I cannot justify purchasing a 7,1 nor do I particularly want one.
Used Mac Pros are as low as $3k but not sure if there’s any street value in my Mac Pro. I suppose I could go M1 Max only and just have a pile of NVMe enclosures and a Thunderbolt dock, and an intel mac to open up legacy audio projects.
Friday will be interesting.
T1 did have the Secure Enclave; just not sure about the sepOS detail. I often forget that sepOS is even a thing.
I'd still take it to your local Genius Bar and see what they tell you. They'll have more tools and will be able to give you way more of a conclusive picture of what's going on than either of us can. Their diagnostics services are free and they'll, for sure, call you with a quote before having you go any further.
There is if it is in working order. Not as much if the logic board is toast. There are a lot of people not happy with the 2023 Mac Pro and will probably cling to the 2019 Mac Pro for several years to come.
If you don't have a need for PCIe nor a Mac with AMD PCIe graphics cards, then yeah, I might not look at replacing this Mac Pro with another if it is, indeed totaled. If performance is important, an Ultra variant Mac Studio might be the more practical choice. You might be able to find a multi-drive NVMe enclosure so as to not have a pile of them.
Best of luck! (I still wouldn't give up hope.) I'd also still take the Mac Pro to your local Apple Store and see what they say.
Dropped off the Mac Pro at Apple, It'll be about 3 days before I hear back. Should be interesting.
Well, there's something weird with possibly the fan sensor. I have the fan assembly on order to see if that fixes. The most annoying part is Apple charges $259 but a $99 service fee. I cannot ****ing install it myself which is absolutely absurd and wave the fee. It'll come out $359.
There is an off chance the fan sensor on an a totally off chance causes the system to flip out waiting for information to relay or strange voltage regulation issues according to the tech but it's unknown. I guess there's a deep diagnostic that can be run that I've requested.
I may just need to start fresh and reinstall everything from scratch, from NI Komplete, to Logic, to Ableton, to Cubase, to Final Cut Pro/Motion/Comrpessor, Pixelmator, Docker, Xcode, the various homebrew packages, Parallels, restore my VScode config and I'm just getting tired thinking about it.
The big ???? is why I'd still get the logd issues on my internal SSD, so hence why I'm buying the fan module.
There is an off chance the fan sensor on an a totally off chance causes the system to flip out waiting for information to relay or strange voltage regulation issues according to the tech but it's unknown. I guess there's a deep diagnostic that can be run that I've requested.
I may just need to start fresh and reinstall everything from scratch, from NI Komplete, to Logic, to Ableton, to Cubase, to Final Cut Pro/Motion/Comrpessor, Pixelmator, Docker, Xcode, the various homebrew packages, Parallels, restore my VScode config and I'm just getting tired thinking about it.
The big ???? is why I'd still get the logd issues on my internal SSD, so hence why I'm buying the fan module.
Hey, $359 to fix it is WAY less than I was expecting. Though, if the aftermarket part is easy to install and works, that's all the better!
Only fan array I could find on ebay was like $300 and in Israel. Apple it is... I'll ask to keep the array though, perhaps I can sell
In some places you are legally entitled to keep old replaced parts, but Apple ignores that and says that parts that have been replaced by newer parts return to Apple's ownership - they likely will not hand that over because Apple's policies forbid it.In any case, I wouldn't trust that this will actually resolve the problem.
I would almost* want to give Apple the money because they only return fully working devices and if they quote you that number for the repair and the Mac doesn't make it through testing afterwards, according to their own policies they cannot charge you since you didn't agree to the extra charges beforehand.
Meaning, either they fix your Mac and charge you the $359, or they return the Mac free of charge (and likely without a fix).
*almost because there have been reports of Apple Stores that do not really follow Apple's policies and return the Mac to you in a worse condition if you don't pay for the full repair. And then it's a hassle to get that rectified or even impossible. For example, people have handed in a working, but not fully working Mac asking for a repair quote, then asked for the device back when the absurdly high quote came in and found the device was completely dead.
I'll just ****ing remove the fan in front of them when I go to drop it off once the part is in so I can keep it and sell it for someone else, as they might be able to pull the working fans from it even if the sensor is bad. At least someone else can avoid the shake down and I can get some of my money back.
The fan array is so easily removed that it's insulting that I can't replace it myself. They make a god damn computer that's user serviceable and yet demand I pay their techs to do the thing its designed for me to do.
10000% this!
I'll add that Apple Authorized Service Providers generally have the flexibility to sell you a replacement part as a "stocking" part, which is to say that they do not require your defective part back. Though the parts cost is higher and almost always not worth it unless you just want the extra part to keep in stock (hence, "stocking").
Why do you need to keep the fan assembly? Isn't the entire point of this exercise to return your machine to working order? I get wanting to be in control over your own repair and over the defective part, but I'd just pay the cost to return your computer to working condition, especially if a $359 repair bill is all it is. That's honestly the best news when it comes to fixing a Mac Pro that, at the absolute minimum, was $6000 before taxes.