Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

Mojave crash on sleep

T

tommiy

macrumors 6502
Original poster
Dec 11, 2015
420
128
First night running Mojave and woke up this morning to find the machine had crashed overnight. First time every on my 2017 Mac. PCIe error....sent report to Apple but a rollback may be in order if it keeps this performance up.
 
tommiy said:
First night running Mojave and woke up this morning to find the machine had crashed overnight. First time every on my 2017 Mac. PCIe error....sent report to Apple but a rollback may be in order if it keeps this performance up.
Click to expand...


It happened 2 times, MacBook Pro 2015 15 i7 16GB can't wake up from the sleep option, then I had to force a restart.
 
tommiy said:
First night running Mojave and woke up this morning to find the machine had crashed overnight. First time every on my 2017 Mac. PCIe error....sent report to Apple but a rollback may be in order if it keeps this performance up.
Click to expand...

Same here. Late 2015 iMac. Crashes every time it goes to sleep.
 
  • Like
Reactions: TokMok3
Suttree said:
Same here. 2017 MacBook.
Click to expand...


It crashed again. I've done a SMC reset. Its lasted 2 days now. I cross my fingers. I'm keeping my last full backup before upgrading in case I need to go back.
 
Same problem here on my MBP (15-inch, 2016). Does anyone know if this is being addressed in a beta?
 
tommiy said:
First night running Mojave and woke up this morning to find the machine had crashed overnight. First time every on my 2017 Mac. PCIe error....sent report to Apple but a rollback may be in order if it keeps this performance up.
Click to expand...

Check your usb devices that are connected to your MacBook, disconnect all of them and let the MacBook goes to sleep for 2 hours, maybe some usb device is causing Mojave to malfunction.

In my case, I think I solve my problem, it seems that my usb wireless keyboard was the culprit. I change the keyboard and it seems that the problem was fixed. I will report tomorrow to see if that fixed the problem.

Update: After a reinstalling Mojave it work without problems for 3 days, then this bug returns. MacBook can't wake from sleep.
 
Last edited:
I took off all my usb devices and the crashing stopped. I’ve been adding them back one by one and so far so good. It’s looking like my Wacom tablet may be the problem.
 
Mac mini 2012 (upgraded to 16GB), installed official Mojave when it was released (no betas). After computer goes to sleep, I need to press the power button to wake it up (USB wired keyboard or USB wireless mouse don't wake it up). It then wakes from sleep and I get the login page (after a minute or so), but the keyboard/mouse are not reacting. Then after a minute or so goes to display sleep again. Disconnecting and reconnecting the mouse/keyboard sometimes helps, sometimes doesn't. Need to press the power button again, sometimes only after 3-4 attempts I get it to work.
In short, Mojave has turned the computer sleep feature into useless. I have set it up now to go to computer sleep after 3 hours, I have no interest in wasting 5-10 minutes every time I need to wake it up.
 
  • Like
Reactions: TokMok3
Just got a new mid-2017 27" 3.5ghz iMac 3 weeks ago and updated to Mojave last week.

Since the update, I've been having the same issue. I checked and there are no kernel panic reports. I'm considering stepping back in my time machine to High Sierra. Anyone else have any ideas or should I just be patient and wait for drivers? The only peripherals I have plugged in is my satechi hub, my RAID drive, a Seagate drive for time machine, and a Logitech mouse. The only culprit I can think of is the mouse if it is hardware related, but Logitech is pretty good lately about pushing updates.

Avast found nothing on a full scan, and I'm really not in the mood to start uninstalling individual programs to see if it is a software issue.
 
crg5698 said:
Same problem here on my MBP (15-inch, 2016). Does anyone know if this is being addressed in a beta?
Click to expand...
I have Mojave running on MBPr15(2016), iMac27, 2 MacMini servers ( one of the old 8 core and one of the 2016? newer ones ). Have not had a single system crash ( or crash from wake ), although I do get the occasional mail app crash when connecting to exchange server.
 
Mine doesnt crash but it is extremely slow to wake up...2015 Macbook Pro Retina with Dell monitor....need to open lid to awaken.
 
After reseting my SMC I've not had a crash during sleep again. Mojave has actually done a full blown kernel panic while I was actively working. First time I've seen that in a number of years. Sent the dump off to apple.
 
spoke too early. Beach balled 3 times today and would not respond to even a forced quit. Had to hold down the power button in the end ;(
 
Got another one during sleep. I was shredding papers and I could hear the external speakers attached to the iMac making the popping sound when the shredder went on. Suddenly I see the iMac Crash image and needs to reboot. I'll detach the external speakers from the headphone jack and see if that's what caused the crash.

What is this:
Oct 9 13:29:22 iMac2015 com.apple.xpc.launchd[1] (com.apple.xpc.launchd.user.domain.501.100007.Aqua): com.apple.ReportCrash (lint): Unrecognized MachService property: DrainMessagesOnCrash
Oct 9 13:29:22 iMac2015 com.apple.xpc.launchd[1] (com.apple.xpc.launchd.user.domain.501.100007.Aqua): com.apple.ReportCrash.Self (lint): Unrecognized MachService property: DrainMessagesOnCrash






Anonymous UUID: 60A7DC44-6C7A-309A-72C1-82D796CC69F3

Tue Oct 9 13:29:04 2018

*** Panic Report ***
panic(cpu 1 caller 0xffffff80178b867f): initproc exited -- exit reason namespace 2 subcode 0xa description: none

Thread 1 crashed

RAX: 0x0000000000000000, RBX: 0x0000000105449060, RCX: 0x0000000105446000, RDX: 0x0000000105449080
RSP: 0x0000700001d9c300, RBP: 0x0000700001d9c3a0, RSI: 0x0000000105449070, RDI: 0x00000001053fb000
R8: 0x00000001053fbae8, R9: 0x0000000000000f0e, R10: 0x00007fff69e59aa3, R11: 0x0000000000000206
R12: 0x0000000100010c22, R13: 0x0000000000001ea8, R14: 0x000000010544b728, R15: 0x00000001053fb000
RFL: 0x0000000000010246, RIP: 0x00007fff69c6b7f7, CS: 0x000000000000002b, SS: 0x0000000000000023

Thread 0: 0xffffff803973f7b0
0x00007fff69da9a5e
0x00007fff69c2e894
0x0000000000000000

Thread 1: 0xffffff8041fa31d0
0x00007fff69c6b7f7
0x00007fff69c6b67d
0x00007fff69c6b549
0x00007fff69ccae74
0x000000010540bc22
0x000000010540b25d
0x00007fff69c1edcb
0x00007fff69c215d8
0x00007fff69c308e1
0x00007fff69c24fc5
0x00007fff69c25bd8
0x00007fff69c2e084
0x00007fff69e5e61c
0x00007fff69e5e415
0x0000000000070507

Thread 2: 0xffffff804252d1d0
0x00007fff69dc42a6
0x00007fff69c215d8
0x00007fff69c308e1
0x00007fff69c24fc5
0x00007fff69c25bd8
0x00007fff69c2e084
0x00007fff69e5e61c
0x00007fff69e5e415
0x0000000000000000

Thread 3: 0xffffff8042cbbe60
0x00007fff69e5e408


Mac OS version:
18A391

Kernel version:
Darwin Kernel Version 18.0.0: Wed Aug 22 20:13:40 PDT 2018; root:xnu-4903.201.2~1/RELEASE_X86_64
Kernel UUID: DF83AD37-501E-3B4F-B1F0-04F3AC90FE35
System model name: iMac14,1 (Mac-031B6874CF7F642A)

EOF
 
Last 2 days it got worse - The power button (short press) doesn't even wake up the mini. I need to force shutdown by a long press. Well done Apple, I have now disabled sleep AT ALL. QA level of a few of the latest OS releases (iOS 11.4 and now Mac OS 10.14) is abysmal. Apple has become Microsoft of the 90's.
tsipo said:
Mac mini 2012 (upgraded to 16GB), installed official Mojave when it was released (no betas). After computer goes to sleep, I need to press the power button to wake it up (USB wired keyboard or USB wireless mouse don't wake it up). It then wakes from sleep and I get the login page (after a minute or so), but the keyboard/mouse are not reacting. Then after a minute or so goes to display sleep again. Disconnecting and reconnecting the mouse/keyboard sometimes helps, sometimes doesn't. Need to press the power button again, sometimes only after 3-4 attempts I get it to work.
In short, Mojave has turned the computer sleep feature into useless. I have set it up now to go to computer sleep after 3 hours, I have no interest in wasting 5-10 minutes every time I need to wake it up.
Click to expand...
 
tommiy said:
spoke too early. Beach balled 3 times today and would not respond to even a forced quit. Had to hold down the power button in the end ;(
Click to expand...

This machine is getting lazy, I have to do this every morning to wake up this MacBook pro 2015 15.
 
I have the same issue with my MacBook Pro, but I don't have anything connected to it, and I let it sleep on battery overnight, and right when I try to wake it up, the battery is drained (below 80%) and it becomes unresponsive until I force restart it. I don't have any crash reports.
 
KatPR said:
I have the same issue with my MacBook Pro, but I don't have anything connected to it, and I let it sleep on battery overnight, and right when I try to wake it up, the battery is drained (below 80%) and it becomes unresponsive until I force restart it. I don't have any crash reports.
Click to expand...


My MacBook Pro 15 mid 2015 is connected all the time and keep having this problem, tonight I'm going to disconnect the power adapter to check the battery drain issue, I will report tomorrow.
 
TokMok3 said:
Check your usb devices that are connected to your MacBook, disconnect all of them and let the MacBook goes to sleep for 2 hours, maybe some usb device is causing Mojave to malfunction.

In my case, I think I solve my problem, it seems that my usb wireless keyboard was the culprit. I change the keyboard and it seems that the problem was fixed. I will report tomorrow to see if that fixed the problem.

Update: After a reinstalling Mojave it work without problems for 3 days, then this bug returns. MacBook can't wake from sleep.
Click to expand...

What is a "USB wireless" keyboard..If it is wireless why USB?
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back