Apple Says Latest macOS Supplemental Update Addresses Audio and Kernel Panic Issues on 2018 MacBook Pro

Apple on Tuesday released macOS High Sierra 10.13.6 Supplemental Update 2, exclusively for 2018 MacBook Pro with Touch Bar models, but the release notes only mention improved stability and reliability.

When contacted by MacRumors for clarification, Apple said the Supplemental Update improves system stability and reliability across a number of areas, and addresses several issues, including crackling audio and kernel panics. Apple said it recommends all users install the update on their MacBook Pros.

The 1.3GB update hasn't been available long enough yet for any conclusive evidence from affected users, with mixed reports across the Apple Support Communities, Reddit, and our own MacRumors discussion forums.

Apple Support Communities user takashiyoshida, for example, claimed his MacBook Pro "no longer outputs the crackling noise" after updating.

"This evening, I set the microphone and speaker's sampling format to 44100 Hz and began playing back music on iTunes," he explained. "Before the update, I would normally hear the noise in about an hour. I left my MacBook Pro to play music for about three hours and so far I am not hearing any noises."

Reddit user onceARMY, however, commented that he was "still getting audio crackling noise while playing YouTube content on Safari." He did note that there were "no issues with the Spotify app" after installing the update.

As far as kernel panics are concerned, a handful of users have reported experiencing at least one since installing the Supplemental Update.

"Installed today's update… and then it happened," wrote MacRumors forum member King724, referring to a kernel panic. He shared a log indicating a system crash related to bridgeOS, the device firmware on the logic board that controls many functions on the 2018 MacBook Pro, including the Apple T2 chip.

Last month, Apple said it was looking into a small number of indirect reports about the kernel panics, but wouldn't say if the T2 chip was to blame.

Similar reports of kernel panicking began last year with the iMac Pro, which is also equipped with the T2, so it did—or perhaps still does—seem to be a potential issue with the chip, or the bridgeOS firmware that manages it. There was some speculation that the T2 chip was also to blame for the crackling.

For context, the T2 chip integrates several previously separate components, including the system management controller, image signal processor, audio controller, and SSD controller. It also features a Secure Enclave coprocessor for secure boot, encrypted storage, and authenticating Touch ID.

Prior to yesterday's Supplemental Update, Apple support representatives provided customers with a wide variety of potential solutions to mitigate these issues, ranging from disabling FileVault to turning off Power Nap, but none of the workarounds appeared to permanently fix the problems.

Apple also asked some customers if they would be willing to send in their MacBook Pros so that its engineers can look into the issues. Some customers were apparently told that fixes were in the works, and at least based on what Apple told us, they are included in the Supplemental Update.

This is the second macOS High Sierra Supplemental Update for the 2018 MacBook Pro in as many months, with the first addressing a bug that contributed to excessive throttling of clock speeds under heavy thermal loads.

The Supplemental Update is not available to macOS Mojave users, but the issues could be resolved in future beta versions.

Related Roundup: MacBook Pro
Buyer's Guide: MacBook Pro (Caution)

Top Rated Comments

(View all)

19 months ago
Ever since Apple redesigned and updated the MacBook Pro in 2016, there's been nothing but bad news and problems with them. Even more infuriating is how expensive these laptops are. At this point, the redesigned MacBook Pros have a tainted image that I certainly don't want to be a part of.

Get your **** together Apple, making great laptops should be child's play for you. Lay off the iPhone green for a while and sober up.
Rating: 30 Votes
19 months ago


I hate this kind of response. I have spent tens of thousands of my own money on Apple products over the past decade (including $6,000 on the new MBP). Perhaps you're too young to remember, or just forgot, but things weren't 100% rosy when Steve was around. Remember Antenna Gate on the iPhone 4? We were all holding it wrong... Or how about how gawd awful Apple's cloud offerings used to be? Ever heard of Ping? Social for music...yeah, Myspace already happened.

Crap happens, and at least they are being proactive about trying to fix the issues.
Rating: 10 Votes
19 months ago

How’s about updating your software so it doesn’t pi$$ing stutter? I recently copped one of these and even Safari stutters when scrolling simple sites, I was shocked given the hardware and high price. Straight up embarrassing from Apple and goes to show it’s the software that really matters. Don’t care about pointless benchmarks. Will be returning mine as it doesn’t feel it’s worth £2,699 at all.

Edit: Running the latest Mojave beta which is supposed to be smoother but it isn’t? I guess you people had a different definition of ‘smooth’ to me. I can’t straight from a late 2013 MacBook Pro running Mavericks and it’s shocking the difference in smoothness (and design too which is hideous looking in comparison to Mavericks in my opinion).

God knows how Apple would manage developing an OS like Windows for BILLIONS of hardware combinations.

Apple can't even develop a stable OS for the 10 or so hardware configurations they haven't forced obsolescence on....
Rating: 10 Votes
19 months ago

Does this also address the kernel panics I've been getting on my 2016 MBP w/TB? Every time I zoom in and out on Google maps I get it.

No. The article clearly says 2018 MacBook Pro. If your model isn't mentioned, this update doesn't cover it. Pretty plain and simple.
Rating: 9 Votes
19 months ago
Gone are the days when all you had to worry about with the MacBook Pros was whether you got a Samsung or LG display.
Rating: 8 Votes
19 months ago
The 2108 Throttlebook Pro has gotten off to a terrible start. Worse when you consider it builds upon the controversial 2016/17 Mabook Pro to begin with.

Apple just needs to end the Mac because they seriously do not care about it.
Rating: 7 Votes
19 months ago
Well, since my 2018 MBP hasn't had any of these issues then there must be no issues! /s

It's always fascinating to me how when a small subset of uses experience issues and crashes, then those issues and crashes must equate a major failure across the board. But! when other users report no issues... Well they don't count
Rating: 7 Votes
19 months ago

False equivalence. One of the only things that makes the MacOS version different on my 2016 machine from a 2018 are the different kernel extensions that they run, hence kernel panics.

Code changes are not always model specific. A fix for a 2018 problem could have unknowingly fixed lesser known issues on the 2016 model.

The update clearly says "exclusively for 2018 MacBook Pro with Touch Bar models". It mentions no other models.

Exclusively: to the exclusion of others; only; solely.

Everything Apple has published along with this update says 2018 specifically and lists no other makes or models.

How much more clearly do they need to mark it for you? "This update IS NOT FOR THE 2016 MACBOOK PRO WITH TOUCH BAR. THAT MEANS YOU CerebralX. THIS DOESN'T APPLY TO YOUR MACHINE!"
Rating: 6 Votes
19 months ago

The 2108 Throttlebook Pro has gotten off to a terrible start. Worse when you consider it builds upon the controversial 2016/17 Mabook Pro to begin with.

Apple just needs to end the Mac because they seriously do not care about it.

/s (I hope)? I simply want them to start caring again. Hire more people. Or different ones. Or whatever is needed to right this ship.
Rating: 5 Votes
19 months ago

While I was reading this thread, responding to an iMessage in the quick reply feature, that reply hung and the computer shut off. I was finally able to get it to reboot and see the below log.

This is on a 2018 13 in MacBook Pro and is the second Bridge OS crash I've experienced in the last 8 hours. I posted details on that one in another thread, but seemed to be related to the sleep/wake. Both have occurred after installing yesterday's supplemental update. I don't recall a crash before that supplemental.

Today is 15 days since purchase, so I'm one day past my return window.

{"caused_by":"macos","macos_system_state":"running","bug_type":"210","os_version":"Bridge OS 2.4.1 (15P6805)","timestamp":"2018-08-29 18:33:34.50 +0000","incident_id":"7CE51A17-C3E0-4280-B609-9BDADABF7D6D"}
"build" : "Bridge OS 2.4.1 (15P6805)",
"product" : "iBridge2,4",
"kernel" : "Darwin Kernel Version 17.7.0: Fri Jul 6 19:25:51 PDT 2018; root:xnu-4570.71.3~1\/RELEASE_ARM64_T8010",
"incident" : "7CE51A17-C3E0-4280-B609-9BDADABF7D6D",
"crashReporterKey" : "c0dec0dec0dec0dec0dec0dec0dec0dec0de0001",
"date" : "2018-08-29 18:33:34.40 +0000",
"panicString" : "panic(cpu 0 caller 0xfffffff00b773984): macOS watchdog detected\nDebugger message: panic\nMemory ID: 0x6\nOS version: 15P6805\nKernel version: Darwin Kernel Version 17.7.0: Fri Jul 6 19:25:51 PDT 2018; root:xnu-4570.71.3~1\/RELEASE_ARM64_T8010\nKernelCache

SMH. Boggles the mind with all that cash pouring in and this is the user experience for Mac users.
Rating: 5 Votes

[ Read All Comments ]