MacBook Pro 2017 15" kernel panic after going to sleep

Same issue after security update 2019-004, very annoying.

panic log:

Tue Jul 23 11:29:12 2019

*** Panic Report ***

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

Backtrace (CPU 0), Frame : Return Address

0xffffff91fdf4bbb0 : 0xffffff80056e837c

0xffffff91fdf4bc30 : 0xffffff7f88668303

0xffffff91fdf4bc90 : 0xffffff7f88667ee6

0xffffff91fdf4bce0 : 0xffffff7f8866b95f

0xffffff91fdf4bd00 : 0xffffff8005cdb86e

0xffffff91fdf4bd60 : 0xffffff8005d0626e

0xffffff91fdf4bde0 : 0xffffff8005ca5c6c

0xffffff91fdf4be50 : 0xffffff8005ca2df4

0xffffff91fdf4beb0 : 0xffffff8005c9fb22

0xffffff91fdf4bef0 : 0xffffff8005c9f9a2

0xffffff91fdf4bf30 : 0xffffff8005cbb5e1

0xffffff91fdf4bf80 : 0xffffff8005cbad3c

0xffffff91fdf4bfb0 : 0xffffff8005698957

Kernel Extensions in backtrace:

com.apple.driver.AppleACPIPlatform(5.0)[65E05472-6AE7-3308-8CC8-FA6CB0DB2AEE]@0xffffff7f8865d000->0xffffff7f886bcfff

dependency: com.apple.iokit.IOACPIFamily(1.4)[4F7FB6AD-2498-3F71-827C-ED7AA4BF2511]@0xffffff7f85e8a000

dependency: com.apple.iokit.IOPCIFamily(2.9)[D5DA7B81-DCD5-39AC-8DC9-796A4D1D6A20]@0xffffff7f85e4f000

BSD process name corresponding to current thread: kernel_task

Mac OS version:

16G2127

Kernel version:

Darwin Kernel Version 16.7.0: Sun Jun 2 20:26:31 PDT 2019; root:xnu-3789.73.50~1/RELEASE_X86_64

Kernel UUID: 9778BC83-2647-3AE4-A7F2-8A2F41FA8791

Kernel slide: 0x0000000005400000

Kernel text base: 0xffffff8005600000

__HIB text base: 0xffffff8005500000

System model name: MacBookPro13,3 (Mac-...)

Same here (15 MBP 2018, 10.13.6). I doubt it can be hardware problem... I restart computer daily multiple times, so I don`t believe one update with two restarts would start it. It is something with the software.

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

Exactly the same problem -> Kernel Panic after waking from sleep !

Running macOS 10.13.6 on a MacBook Pro TB 15"

This can't be a hardware issue, too many other people are experiencing the exact same issue which can only mean the update brakes something somewhere...

If anyone has a solution please post it asap, I've already tried boot from external drive, and currently trying a clean install...

Encountered this exact issue after installing security update 2019-004 on macOS High Sierra on my 15" MBP 2017. Consistent kernel panic every time after waking up from sleep mode.

Upgrading to Mojave resolved this issue for me.

I just upgraded the OS to Mojave (10.14.6) and the issue no longer occurs.

Initially I tried SMC reset, disk first aid from recovery OS, clearing the system cache, removing VirtualBox, but none of those attempts fixed the issue.

I checked once more and the EFI Firmware indeed received an update. But it's strange in my eyes that Apple apparently either shipped different code inside a security update that handles the same Firmware differently or that the 2019-004 update has different firmware than the Mojave 10.4.6 firmware. It's annoying you can't restore the firmware yourself these days.

What let me think in the first place that it was a Hardware issue was that the problem occurred with earlier macOS updates on 2017 and 2016 models. I also saw a report with the same kernel panic after a palmrest replacement: https://boards.rossmanngroup.com/forum/board-repair-troubleshooting/44882-2016-17-mbp-w-tb-kernel-panic-after-palmrest-replacement

Are there people that installed Mojave? I will attempt it this weekend if more people say it's successful.

I can confirm that an update to macOS Mojave from High Sierra with the Security Update 004, does indeed fix the kernel panic upon waking from sleep...

Sad that Apple couldn't do this PROPERLY with the 10.13.6 Security Update 004... oddly enough, that 004 update works just fine on my 2008 MacPro running High Sierra using the "macOS High Sierra Patcher Tool for Unsupported Macs".

Same issue for me after installing 2019-004 on my 2017 MBP 15" running High Sierra. Rock solid before that update, now it panics on wake from sleep. SMC reset didn't help. Sure hope Apple pushes a fix for this since upgrading to Mojave isn't particularly convenient right now.

As I mentioned in my earlier post, I did a time machine restore to a day prior to my 2019-004 install, and the kernel panics are still occurring:

sw_vers:

ProductName: Mac OS X

ProductVersion: 10.13.6

BuildVersion: 17G7024

so, guessing some firmware? changes bundled with 2019-004 that were applied are not reverted during the restore. If it helps, some more version info:

Hardware Overview:

Model Name: MacBook Pro

Model Identifier: MacBookPro13,3

Processor Name: Intel Core i7

Processor Speed: 2.7 GHz

Number of Processors: 1

Total Number of Cores: 4

L2 Cache (per Core): 256 KB

L3 Cache: 8 MB

Memory: 16 GB

Boot ROM Version: 259.0.0.0.0

SMC Version (system): 2.38f7

Yes, a Time Machine restore *DOES NOT* fix this issue. Why? Apple seems to have applied a firmware update to an internal component (T1/T2?) that lets your Mac crash on sleep, no matter what kind/version/lfavor of system (High Sierra, Mojave/..) you are booting of at any later time.

I guess only a firmware update or a mainboard swap can fix this issue. My MacBook Pro is currently at the Apple Store for a mainboard swap.

Dang, ya you will have to wait as the problem looks to be in the BridgeOS T2 Security Chip update and not the 2019-004 update code. This would be why Macs not running a T1 or T2 chip are fine and don't crash.

You can either wait for the fix from Apple or update to Mojave.

Successfully updated to Mojave without any sleep panics yesterday after trying countless fixes; SMC, PRAM, booting from a previous clone, re-installing a previous clone, clean install, etc, etc... the only thing that worked for me was upgrading to Mojave - after I re-installed a cloned backup that didn't have any Security or Safari Update applied to it, I upgraded my 2016 15" MBP to Mojave from the latest 10.14.6 full installer. I typically shut the lid ( sleep ) overnight and can verify that it works fine for me. Yesterday I had only performed shorter sleep tests and found it worked.

I also tested a cloned re-install by just 'sleeping' from the menu and found that short ( less then a minute or so ) sleeping worked but anything longer then that minute would immediately set off a panic.

Apple really does need to be held publicly responsible for this fiasco. I've never experienced as many problems with Apple software / hardware ever.

related blog post:

https://mrmacintosh.com/apple-pulls-2019-004-high-sierra-and-sierra-security-updates-after-kernel-panics/

very useful lesson from this: with Apple software updates always wait some time before installing...

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