MacBook Pro 2017 15" kernel panic after going to sleep

Same issue here, my MBP 2016 touch bar was running fine no issues, installed the latest security update and now it crashes and restarts after sleeping for about 2 minutes. This is just horrible, no QA teams to test this before releasing Apple ? If the fix is a new mother board it better be free and fast. same reports in crash log as others. AppleACPIPlatformPower.

I can only confirm this. I had just installed the 2019-004 security update on Thursday when the crashing started.

None of the options suggested by Apple support changed anything.

Upgrading to Mojave and then wiping the HD and installing a High Sierra backup were the last 2 things I tried.

The kernel panic report still reads the same.

Sun Jul 28 06:16:17 2019

*** Panic Report ***

panic(cpu 0 caller 0xffffff7f90bcafcd): "Failed to quiesce supporting devices\n"@/BuildRoot/Library/Caches/com.apple.xbs/Sources/AppleACPIPlatform/AppleACPIPlatform-281.70.3/AppleACPIPlatformPower.cpp:1970

...

...

I don't really want to believe that this software update ruined my main board, though.

Hello,

I have a Macbook Pro 15" 2018 and I have the same problem. I tried everything but nothing works, even the Os 10-14-6. I'm so annoying by this problem !

In a Genius Bar, they said we have to replace the mainboard and/or the upper box... What do you think ?

JeremyFr

Clearly 2019-004 security update messed up Macbook pro 2017 15inch considering there are so many people with the same problem here and also on Twitter(You can find them searching for 'mac 2019-004' on Twitter). I'll get so mad and disappointed in Apple if Apple doesn't do anything.

This is happening to 4-5 people on my team at work after installing the update released on July 22.(2019-004). Please fix!

Same problem on a MacBook Pro Late 2016 Touch bar with MacOs Sierra (10.12.6) after the Security Update.

I have received the same panic code on start up, when my laptop is asleep, but it awakes normally when attached to exterior power.

ATTENTION ALL = Apple has now released a new Security Update 004 patch, I'll let you know asap if it works for me...

WORD OF CAUTION : If your running a Nvidia Card the "new" security update will break the macOS 10.13.6 (17G8029) driver... Updates the system to macOS High Sierra 10.13.6 (17G8030) .

I have the daily kernel panics with a MacBook Pro (15-inch, 2017) and High Sierra 10.13.6 (regular, no developer previews installed)

It started the day after I've added a separate volume on my boot volume with "Apple File System Space Sharing" and installed the 10.15 beta on this new volume.

I reinstalled High Sierra, did First Aid, SMC and PRAM reset. Nothing helped so far. :-(

Applied 2019-004 yesterday, now kernel panic EVERY TIME the machine wakes after sleep. No hardware attached...

High Sierra 10.13.6

MBPro 15 inch, 2016

Logic board replaced a year ago b/c it completely quit working. Apple care said they have seen before.

*** Panic Report ***

panic(cpu 0 caller 0xffffff7f98c23fcd): "Failed to quiesce supporting devices\n"@/BuildRoot/Library/Caches/com.apple.xbs/Sources/AppleACPIPlatform/AppleACPIPlatform-281.70.3/AppleACPIPlatformPower.cpp:1970

Backtrace (CPU 0), Frame : Return Address

0xffffff92059039c0 : 0xffffff801746bf96

0xffffff9205903a10 : 0xffffff8017595354

0xffffff9205903a50 : 0xffffff80175875e4

0xffffff9205903ac0 : 0xffffff801741dfb0

0xffffff9205903ae0 : 0xffffff801746ba0c

0xffffff9205903c10 : 0xffffff801746b7cc

0xffffff9205903c70 : 0xffffff7f98c23fcd

0xffffff9205903cd0 : 0xffffff7f98c23b9e

0xffffff9205903d20 : 0xffffff7f98c280eb

0xffffff9205903d40 : 0xffffff8017ab9638

0xffffff9205903d90 : 0xffffff8017ae79e3

0xffffff9205903e00 : 0xffffff8017a8151b

0xffffff9205903e50 : 0xffffff8017a7e708

0xffffff9205903eb0 : 0xffffff8017a7b6e3

0xffffff9205903ef0 : 0xffffff8017a7b572

0xffffff9205903f30 : 0xffffff8017a97ed2

0xffffff9205903f70 : 0xffffff8017a974fc

0xffffff9205903fa0 : 0xffffff801741d557

Kernel Extensions in backtrace:

com.apple.driver.AppleACPIPlatform(6.1)[B0282791-F78C-3A3D-A829-629AD847C7EA]@0xffffff7f98c18000->0xffffff7f98cb3fff

dependency: com.apple.iokit.IOACPIFamily(1.4)[95DA39BB-7C39-3742-A2E5-86C555E21D67]@0xffffff7f98148000

dependency: com.apple.iokit.IOPCIFamily(2.9)[9C640A56-0FCC-39B4-B469-31F6ED15228E]@0xffffff7f97c94000

dependency: com.apple.driver.AppleSMC(3.1.9)[0249444C-80D4-3184-9060-F70DA3BEB17D]@0xffffff7f98151000

BSD process name corresponding to current thread: kernel_task

Mac OS version:

17G8029

I usually wait a week or more to apply updates, but I was catching up and didn't notice 2019-4 was just released before trying to apply it. The update at first brought me back to a login screen that had a different background and was missing users. After logging in things seemed to be normal, but the updater still indicating 2018-4 was available. Did it not take? With all the flakey things the OS has been doing over the pass few years, I though nothing of it, just another one of those details. So I did it again, after the second try things worked OK. I have no problem with sleeping, but about an hour later Time Machine said there was not enough disk space to backup. It appears for some reason the OS decided that it needed a fresh backup, blew away the previous backups but did not clean up (finder saying the 1.4TB older backups were still taking up disk space but not visible.. as if the trash wasn't emptied... but there were no files in the trash....)

Anyway I probably wouldn't have noticed it, if there were enough space on the drive for two full backups, until I wanted to recover something from months ago.

Perhaps a good reason for using a secondary backup plan. I use CCC so in the end I don't think I lost anything.

So what good is the beta process, if problems are ignored and updates are pushed anyway?

This is a 2017 iMac, High Sierra

...just tried your tip and it didn't work for me. I've alway had the 'Prevent Computer...' checked and unchecked the 'Wake for Wi-Fi...' to test your fix.

What really bothers me is that Apple hasn't said a word about this issue publicly, other then pulling the Security Update from their servers, which tells me that this is a very wide spread problem...

Anyways, not letting the MB sleep is not a solution, just as "not using the MP and going for a walk instead" is also not a solution if the MP is broken...

But seriously, how Apple handles this is a joke.