MacBook Pro 2017 15" kernel panic after going to sleep

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

Seems like a problem with that Security update. I installed that same security update (Security update 2019-004 - not the beta) on July 22nd, and I immediately started having the same problem.

Are you still having this problem after upgrading to Mojave (10.14.6, you solve the problem only installing the last upgrade)?

Re applied latest 2019-004 on Macbook Pro 15" with TB 2016...the issue has been fixed 👏

A new security update is released and that has solved the problem for me (at least until now)

I just got the same kernel panic after my Mac went to sleep and after installing the mentioned Security update.

Just wondering: Do you have Virtual Box installed? It's the only app that installed third-party kernel extension for me, so I'm wondering if other people did the same. I filed this as Feedback issue #6797116.

So today I restored my machine from time machine prior to the 2019-004 update. Kernel Panic on wake did NOT go away. So, either coincidence with applying 2019-004...or the update (somehow) broke hardware...or the update updated some firmware somewhere that has a defect that triggers the panic...

Interesting as well, the download page for 2019-004 High Sierra is gone today...

https://support.apple.com/kb/DL2012?locale=en_US

Apple must be on to something. Hope it didn't break my hardware (rather it be a firmware 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.

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.

I have the exact same problem after doing the exact same thing with that security update on my MacBook Pro. Every time it goes to sleep. I've been through the link provided below and nothing helps. This is not a hardware problem but most certainly related to Security Update 2019-004 Version 10.12.6. Apple needs to address this issue.

This is not a Mac OS "software" problem, it's a firmware issue, caused by the update. As long as Apple does not publish a firmware update for this bug, all affected systems simply need to be replaced to a prior firmware version that works. And a working firmware can be found on replacement boards. So I am happy that they've replaced it.

Yeah it's definitely a software issue, too many are having the exact same kernel panic - I'm trying to reinstall right now changing from HFS+ to APFS and see if that helps.

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-...)

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...

I fully agree that this is really embarrassing for Apple. People do not pay twice as much for a MacBook than for comparable Dell notebook not in order to receive security updates that severely mess up their system.

Apple, with their armada of highly paid software engineers, should do a better job at testing products before releasing them.

I invite everyone to let Apple know about this problem on their feedback site, maybe this will encourage them to find a fix soon:

https://www.apple.com/feedback/