Crash-on-sleep: Mojave 10.14.6, Mini 8,1

[allpar]

This has been discussed in Apple Communities with no resolution so far. I've tried Apple but they are insisting now that I update to Catalina before they help. I am hoping someone here can help... I have crash reports!

I have tried starting from an external drive newly formatted with Mojave - instant crash on sleep. New test account - crash on sleep. What MIGHT be working so far - unplug iKey keyboard. However... I've had this problem go away for a couple of days only to return. Other tries: reset PRAM, SMC, safe boot.

Any thoughts?

 

[H2SO4]

This has been discussed in Apple Communities with no resolution so far. I've tried Apple but they are insisting now that I update to Catalina before they help. I am hoping someone here can help... I have crash reports!

I have tried starting from an external drive newly formatted with Mojave - instant crash on sleep. New test account - crash on sleep. What MIGHT be working so far - unplug iKey keyboard. However... I've had this problem go away for a couple of days only to return. Other tries: reset PRAM, SMC, safe boot.

Any thoughts?

Not right at the moment but I can tell you I’ve recently started experiencing the same.
milk post some logs later.
I think it’s connected to the T2.

 

[H2SO4]

Ok, so it's not just crash on sleep for me. I shut the Mini down and when I restarted I had the same crash notification. I have the same issue as you, don't want to update to Catalina so I know that Apple will not help.
As this problem was around way before Catalina they should provide a fix without requiring you to upgrade.

 

[Hessel89]

I have the same issue. Because of this I've turned off sleep completely using the command: sudo pmset -a hibernatemode 0 on my Mac Mini, but now also happens when only the screen was turned off (by pressing Shift+Control+Eject)

Updating to Catalina is not an option for me. The software I use to make a living with is not compatible with Catalina and there is no alternative.

 

[madrich]

Well, I am not sure, but there have been system crashes tied to the security update 2020-002. If you have installed it I would try reinstalling the iOS without this security update.

 

[Hessel89]

Well, I am not sure, but there have been system crashes tied to the security update 2020-002. If you have installed it I would try reinstalling the iOS without this security update.

tried and doesn’t work. once the T2 chip has been updated, there’s no going back. we’ll have to wait and see if SU 2020-003 fixes it.

 

[madrich]

tried and doesn’t work. once the T2 chip has been updated, there’s no going back. we’ll have to wait and see if SU 2020-003 fixes it.

I have MBA early 2015 that I reinstalled Mojave without the security update 2002-002. How is it that the T2 chip would prevent a reinstallation for you and not me?

 

[Hessel89]

I have MBA early 2015 that I reinstalled Mojave without the security update 2002-002. How is it that the T2 chip would prevent a reinstallation for you and not me?

The 2015 MBA doesn't have a T2 or T1 chip.

 

[madrich]

The 2015 MBA doesn't have a T2 or T1 chip.

So do those chips retain some type of memory of an operating system? I just do not understand how it prevents you from superseding it.

Also what would happen with a Time Machine restore where you did not backup the security update previously?

 

[Hessel89]

So do those chips retain some type of memory of an operating system? I just do not understand how it prevents you from superseding it.

Also what would happen with a Time Machine restore where you did not backup the security update previously?

Yeah they're on BridgeOS. a seperate OS. My T2 chip is on BridgeOS 4.5 now, and there is no way of downgrading..

Also tried restoring from a TM backup but this only ''restores'' the MacOS side. It's better to reinstall MacOS completely though, which is what I also tried.

 

[madrich]

Yeah they're on BridgeOS. a seperate OS. My T2 chip is on BridgeOS 4.5 now, and there is no way of downgrading..

Also tried restoring from a TM backup but this only ''restores'' the MacOS side. It's better to reinstall MacOS completely though, which is what I also tried.

Thank you for explaining this situation.

 

[H2SO4]

Last night, I installed security update 2020-003. No change.
In fact on reboot, black screen, so hard shutdown.
On re(re)boot, it came up with the password reset utility.

 

[allpar]

Yes, the latest update made it worse.

 

[galactic orange]

Have you tried Security Update 2020-004? I’m on 003 and I have the same crash on sleep (or after restart/shutdown) problem. I’m not optimistic that it was fixed. Very frustrating that such a critical issue has gone unsolved after several updates.

 

[allpar]

No crash on sleep overnight after 2020-004.

 

[H2SO4]

No crash on sleep overnight after 2020-004.

Will give it a try this weekend.

 

[galactic orange]

Will give it a try this weekend.

Same here. Will report back.

 

[H2SO4]

Same here. Will report back.

No change. Still crashing for me.

 

[galactic orange]

No change. Still crashing for me.

I updated and so far I haven’t had a crash on sleep, restart, or shut down and reboot. Somehow it feels like it could crash at any time based on previous update experiences. I feel bad for everyone still having the issue.

 

[H2SO4]

I updated and so far I haven’t had a crash on sleep, restart, or shut down and reboot. Somehow it feels like it could crash at any time based on previous update experiences. I feel bad for everyone still having the issue.

It's sooooooo annoying.

 

[galactic orange]

It's sooooooo annoying.

I spoke too soon. Came home from work. The Mini had been shut down so I fired it up. No problems. Put it to sleep then came back a few minutes later and it’s off. “Did I shut it down?” I thought. But no. After starting back up I got the error message. This is more than just annoying. It’s downright embarrassing.

"build" : "Bridge OS 4.6 (17P6065)",
"product" : "iBridge2,5"

 

[H2SO4]

I spoke too soon. Came home from work. The Mini had been shut down so I fired it up. No problems. Put it to sleep then came back a few minutes later and it’s off. “Did I shut it down?” I thought. But no. After starting back up I got the error message. This is more than just annoying. It’s downright embarrassing.

"build" : "Bridge OS 4.6 (17P6065)",
"product" : "iBridge2,5"

Problem is we’re out in the cold. Need to wait till it happens to someone clever because Apple WILL insist that you install Catalina before they do anything.
[automerge]1595325395[/automerge]

I spoke too soon. Came home from work. The Mini had been shut down so I fired it up. No problems. Put it to sleep then came back a few minutes later and it’s off. “Did I shut it down?” I thought. But no. After starting back up I got the error message. This is more than just annoying. It’s downright embarrassing.

"build" : "Bridge OS 4.6 (17P6065)",
"product" : "iBridge2,5"

Problem is we’re out in the cold. Need to wait till it happens to someone clever because Apple WILL insist that you install Catalina before they do anything.

 

[weezin]

Just found this thread via google search and am having the same problem with my 2018 Mac Mini.

{"caused_by":"bridgeos","macos_system_state":"shutdown","bug_type":"210","os_version":"Bridge OS 4.6 (17P6065)","timestamp":"2020-07-25 22:39:13.00 +0000","incident_id":"013D4CCA-C41E-47BA-858C-A475C0770745"}
{
"build" : "Bridge OS 4.6 (17P6065)",
"product" : "iBridge2,5",
"kernel" : "Darwin Kernel Version 19.6.0: Thu Jul 9 01:45:19 PDT 2020; root:xnu-6153.145.1~7\/RELEASE_ARM64_T8010",
"incident" : "013D4CCA-C41E-47BA-858C-A475C0770745",
"crashReporterKey" : "c0dec0dec0dec0dec0dec0dec0dec0dec0de0001",
"date" : "2020-07-25 22:39:13.19 +0000",

I now just don't let my Mac Mini go to sleep anymore, but that is annoying. I'm on Mojave and would prefer not to upgrade to Catalina at this point.

 

[H2SO4]

Anybody tried this at all?

Download Security Update 2020-005 (Mojave) – Apple Support (UK)

Security Update 2020-005 is recommended for all users and improves the security of macOS.

support.apple.com

 

[allpar]

Yes, it does not help, and some are saying now that it's a bad update.