eGPU will not mount after power failure. "Error: synchronous call on workloop thread."
I had pulled all of my electronic equipment when going for a vacation in case of thunderstorms, came home and re-plugged it all, and there was a power outage as I flipped the switch on the power strip and the eGPU and Mac was booting. Possibly a short or me slipping on the switch to cause a short. I honestly don't know since it was hard to reach behind the shelf.
- Mac boots normally.
- eGPU internal fan responds to Thunderbolt cable being plugged in or out normally.
- Mac mini can read all other Thunderbolt devices. Can not seem to read eGPU however. Have tried different ports.
- Launching the Console and turning the eGPU on gives the following error message "IOThunderboltController::configReadDWord - ERROR: synchronous call on workloop thread." See image below.
- The system report is also affected by plugging in the eGPU. Before plugging it in both Thunderbolt ports show the salient information. After plugging the eGPU the relevant Bus looks radically different. You can compare below.
Below is a snippet from the Console, this text only turns up when the eGPU is running.
Did a component in either the eGPU or Mini fry as the power went out? Was a firmware or BIOS bricked? How can I tell?
Since the graphics card has two BIOS'es I've switched to the second to see if that was the issue. It's unresponsive still. I will have to take the eGPU to someone and check wether or not the either component is dead to the world.
At the behest of a Reddit user I have taken the following steps to get more data on the issue:
"Is the GPU card detected in System Report->Graphics Displays?" - No
"Do you get the console messages when plugging in the eGPU without the GPU in the enclosure?" - Yes
I do not know what to make of this information however. Other than the fact that the GPU certainly isn't seen by the OS.
For the sake of other users I am continuing to relate the progress on troubleshooting my Mac. If for no other reason than that others suffering from a similar issue might find solace in not being alone, and hopefully, get to find a possible solution through my experience.
The eGPU has now been tested with a friends 2016 MacBook Pro with a version of Mojave installed. The Razer Core X is recognised by name in the System Report field, and the graphics card is also identified. Sort of. I assume that particular Mojave edition doesn't have driver support for RDNA/NAVI as the only info available is that it's an AMD card, and some extra hardware codes. No error messages show up in the console either regarding thunderbolt. For all intents and purposes it's a working eGPU.
I therefore placed a call with Apple Support and have gone through the following steps on my Mac mini:
- SMC and NVRAM has been reset - no effect
- A clean install has been performed - no effect
- SSD tested - Cleared with flying colours
- No difference in behaviour aside from one:
- We did notice that the clock in the system would NOT get updated automatically. Reason unknown. It has since changed to the wrong date and time despite not being told to automatically update the clock after manually setting it to the correct time.
Further digging in the Console shows the following lines of code, referring to EEPROM and failed CRC checks, as well as a lack of communication with Apple services about the nature of the TB3 device connected to it. I have a text file of the console info if anyone is curious, but you can get a hint from the attached images.
After this was revealed I received a diagnostics tool that produced what I assume is some sort of kernel dump, and sent the information to Apple for evaluation.
I'm awaiting a call back during the week.
To continue from where I left off. Apple has not yet been able to ascertain why the fault is occurring. I left the machine turned off for a few days until they called back, did some keyboard command combos before startup to make another kind of kernel dump (I'm assuming) and hung up. The support guy I'm talking to has the patience of a saint and is a cheerful, interesting, dude. I don't mind being on the phone with him. But the reason is depressing.
After having up the phone I notice something in the corner of my eye. The eGPU icon is showing up. Everything is working again. To my knowledge I've done nothing but provide kernel dumps. The only difference, this time, was booting the computer with the gpu turned on and plugged in. If that did it I don't know why. I'm happy but confused.