iMac sleep wake failure

Question

Leon Roy Author

Level 1

15 points

iMac sleep wake failure

I have an iMac 2017. After sleep it never wakes up, instead it needs to be powered back on.

On wake I see a sleep wake failure popup. A sample of the report it generates is attached.

iMac Sleep Wake Failure

Any ideas?

Posted on May 27, 2019 10:01 AM

Reply

Answer 1

Best reply

Tesserax

Level 10

148,583 points

May 27, 2019 10:04 AM in response to Leon Roy

Based on the report, the Thunderbolt port failed to initialize and caused the kernel panic.

At this point, I would suggest that you run Apple Diagnostics to see if it uncovers any hardware issues with your iMac.

If it does not, then I would recommend resetting your Mac's SMC.

Reply

Answer 2

macjack

Level 10

111,168 points

May 27, 2019 10:19 AM in response to Leon Roy

After taking Tesserax's good advice, if your Sleep issue still isn't sorted know that I gave up on the Sleep function years ago. Ever since the inception of OS X there have been Sleep related issues. And even more lately.

I just use Display Sleep and keep it set for 15 minutes so I'm not burning the screen. That way your Mac uses very little power over Sleep and is ready to use at the touch of a key without any grogginess. UNIX based systems were made to be always on and they’ve been running busy servers 24/7 for decades.

Reply

Answer 3

Leon Roy Author

Level 1

15 points

May 31, 2019 4:12 AM in response to Tesserax

Just an update. I opened the SamsungPortableSSD software and checked for updates. There was a firmware for the T5 portable SSD (no changelog I can find though) which seems to have resolved the issue completely.

Unfortunately no way to update the firmware AFAIK without install Samsung's utility.

Reply

Answer 4

Leon Roy Author

Level 1

15 points

Jun 9, 2019 1:31 AM in response to SeaPapp

Thanks, after a week the app corrupted itself and won't even open to uninstall itself. I found the following script in the SamsungPortableSSD.app's Contents/Resources folder CleanupAll.scpt which goes through and removes all traces of Samsung's software.

Here's what I ran to stop/remove the kext:

sudo kextunload /System/Library/Extensions/SamsungPortableSSDDriver.kext

sudo rm -rf /System/Library/Extensions/SamsungPortableSSDDriver.kext

sudo kextunload /System/Library/Extensions/SamsungPortableSSDDriverX.kext

sudo rm -rf /System/Library/Extensions/SamsungPortableSSDDriverX.kext

Reply

Answer 5

Leon Roy Author

Level 1

15 points

May 27, 2019 10:12 AM in response to Tesserax

that's helpful @Tesserax - could a USB-C portable SSD plugged into the Thunderbolt port be the cause (Samsung T5)?

Reply

Answer 6

Tesserax

Level 10

148,583 points

May 27, 2019 10:24 AM in response to Leon Roy

Yes, that would be a very good possibility. Please remove it and see if the issue still persists. If not, you certainly found the culprit. Please post back your results.

Reply