kernel panic three times since upgrading to 10.14.6

Yet another user here with the same problem. 10.14.6 / MacBook Pro 2019 (15,1)

FaceTime, hangs, fans go super fast, shuts down.

Have reset SMC and NVRA, also repaired disk.

Issue carries on....

Only ever crashes in FaceTime, and only since 10.14.6

Crashed using Firefox (last version) during Hangouts Meet session.

Tell the Apple’s “senior adviser” that the problem is massive and it can not wait until next OS release otherwise Apple will lose customers and revenue

Yes. My machine has crashed 4 times as a result of ANY application using the camera. First I thought it was a FaceTime bug, but then it also crashed when I used Skype.

I talked with an Apple Senior Advisor. Here is the solution. https://www.youtube.com/watch?v=-Icp8ljJ_No

Yes, it seems they have fixed the issue in Catalina.

Same problem during a Skype video call - happened a bit after 1h into the call.

{"caused_by":"unknown","macos_version":"Mac OS X 10.14.6 (18G87)","os_version":"Bridge OS 3.6 (16P6568)","macos_system_state":"running","incident_id":"DDE85C08-EF84-4AB5-BA78-553A8A8EEC54","timestamp":"2019-08-11 15:15:05.35 +0000","bug_type":"210"}

{

"build" : "Bridge OS 3.6 (16P6568)",

"product" : "iBridge2,3",

"kernel" : "Darwin Kernel Version 18.7.0: Tue Jun 25 21:35:19 PDT 2019; root:xnu-4903.270.47~9\/RELEASE_ARM64_T8010",

"incident" : "DDE85C08-EF84-4AB5-BA78-553A8A8EEC54",

"crashReporterKey" : "c0dec0dec0dec0dec0dec0dec0dec0dec0de0001",

"date" : "2019-08-11 15:15:05.29 +0000",

"panicString" : "panic(cpu 0 caller 0xfffffff017965bec): \"void AppleEmbeddedPCIeUpLinkMgmt::_linkInterruptAction(IOInterruptEventSource *, int): \" \"A link timeout has been seen after 100000 microseconds and 49999 iterations.\"@\/BuildRoot\/Library\/Caches\/com.apple.xbs\/Sources\/AppleEmbeddedPCIeUpLinkMgmt\/AppleEmbeddedPCIeUpLinkMgmt-76.260.2\/AppleEmbeddedPCIeUpLinkMgmt.cpp:3982\nDebugger message: panic\nMemory ID: 0x6\nOS version: 16P6568\nmacOS version: 18G87\nKernel version: Darwin Kernel Version 18.7.0: Tue Jun 25 21:35:19 PDT 2019; root:xnu-4903.270.47~9\/RELEASE_ARM64_T8010\nKernelCache UUID: DB4E28E6354462E8ADC412A804EB32E1\nKernel UUID: 9FC93C85-B7C5-3723-92B7-293273AB9C4F\niBoot version: iBoot-4513.270.14\nsecure boot?: YES\nx86 EFI Boot State: 0x16\nx86 System State: 0x0\nx86 Power State: 0x0\nx86 Shutdown Cause: 0x5\nx86 Previous Power Transitions: 0x20002000200\nPCIeUp link state: 0x94721611\nPaniclog version: 13\nKernel slide: 0x000000001125c000\nKernel text base: 0xfffffff018260000\nmach_absolute_time: 0xc9433452e6\nEpoch Time: sec usec\n Boot : 0x5d48acf8 0x00058207\n Sleep : 0x5d50176a 0x0005f01b\n Wake : 0x5d50204d 0x000d1a3a\n Calendar: 0x5d5030db 0x000418c5\n\nPanicked task 0xffffffe00010e1c0: 8382 pages, 207 threads: pid 0: kernel_task\nPanicked thread: 0xffffffe0004d73e0, backtrace: 0xffffffe010ef3590, tid: 280\n\t\t lr: 0xfffffff01836e2a4 fp: 0xffffffe010ef3620\n\t\t lr: 0xfffffff01845b5a4 fp: 0xffffffe010ef3760\n\t\t lr: 0xfffffff018339610 fp: 0xffffffe010ef3770\n\t\t lr: 0xfffffff01836d848 fp: 0xffffffe010ef3ae0\n\t\t lr: 0xfffffff01836dbc0 fp: 0xffffffe010ef3b20\n\t\t lr: 0xfffffff01836da14 fp: 0xffffffe010ef3b40\n\t\t lr: 0xfffffff017965bec fp: 0xffffffe010ef3bd0\n\t\t lr:

Thanks for sharing! I have a 2019 model and it only happened once so I'll wait to see if it happens again. I'm quite confident that if it's a hardware issue they'll address it. Thank you for sharing your experience!

Same problem here. 2019 MBP 15'' base model restarts at random during FaceTime calls, since the 10.14.6 update. The system worked flawlessly before the update. Until a solution is found, is there a way to revert to 10.14.5? Preferably without having to do a clean install.

Same problem over here, during a Hangouts Meet calling.

{"caused_by":"unknown","macos_version":"Mac OS X 10.14.6 (18G87)","os_version":"Bridge OS 3.6 (16P6568)","macos_system_state":"running","incident_id":"FA4FD925-D179-4AD7-979E-82F94B9C10F6","timestamp":"2019-08-14 18:06:48.06 +0000","bug_type":"210"}
{
  "build" : "Bridge OS 3.6 (16P6568)",
  "product" : "iBridge2,3",
  "kernel" : "Darwin Kernel Version 18.7.0: Tue Jun 25 21:35:19 PDT 2019; root:xnu-4903.270.47~9\/RELEASE_ARM64_T8010",
  "incident" : "FA4FD925-D179-4AD7-979E-82F94B9C10F6",
  "crashReporterKey" : "c0dec0dec0dec0dec0dec0dec0dec0dec0de0001",
  "date" : "2019-08-14 18:06:47.82 +0000",
  "panicString" : "panic(cpu 0 caller 0xfffffff021d75bec): \"void AppleEmbeddedPCIeUpLinkMgmt::_linkInterruptAction(IOInterruptEventSource *, int): \" \"A link timeout has been seen after 100000 microseconds and 49999 iterations.\"@\/BuildRoot\/Library\/Caches\/com.apple.xbs\/Sources\/AppleEmbeddedPCIeUpLinkMgmt\/AppleEmbeddedPCIeUpLinkMgmt-76.260.2\/AppleEmbeddedPCIeUpLinkMgmt.cpp:3982\nDebugger message: panic\nMemory ID: 0xff\nOS version: 16P6568\nmacOS version: 18G87\nKernel version: Darwin Kernel Version 18.7.0: Tue Jun 25 21:35:19 PDT 2019; root:xnu-4903.270.47~9\/RELEASE_ARM64_T8010\nKernelCache UUID: DB4E28E6354462E8ADC412A804EB32E1\nKernel UUID: 9FC93C85-B7C5-3723-92B7-293273AB9C4F\niBoot version: iBoot-4513.270.14\nsecure boot?: YES\nx86 EFI Boot State: 0x16\nx86 System State: 0x0\nx86 Power State: 0x0\nx86 Shutdown Cause: 0xec\nx86 Previous Power Transitions: 0x70707060400\nPCIeUp link state: 0x1611\nPaniclog version: 13\nKernel slide:     0x000000001b66c000\nKernel text base: 0xfffffff022670000\nmach_absolute_time: 0x15ee76189\nEpoch Time:        sec       usec\n  Boot    : 0x5d544ca9 0x000726d0\n  Sleep   : 0x00000000 0x00000000\n  Wake    : 0x00000000 0x00000000\n  Calendar: 0x5d544d99 0x000c73f9\n\nPanicked task 0xffffffe000736d00: 8112 pages, 207 threads: pid 0: kernel_task\nPanicked thread: 0xffffffe000b033e0, backtrace: 0xffffffe0161b3590, tid: 280\n\t\t  lr: 0xfffffff02277e2a4  fp: 0xffffffe0161b3620\n\t\t  lr: 0xfffffff02286b5a4  fp: 0xffffffe0161b3760\n\t\t  lr: 0xfffffff022749610  fp: 0xffffffe0161b3770\n\t\t  lr: 0xfffffff02277d848  fp: 0xffffffe0161b3ae0\n\t\t  lr: 0xfffffff02277dbc0  fp: 0xffffffe0161b3b20\n\t\t  lr: 0xfffffff02277da14  fp: 0xffffffe0161b3b40\n\t\t  lr: 0xfffffff021d75bec  fp: 0xffffffe0161b3bd0\n\t\t  lr: 0xfffffff022c05fc4  fp: 0xffffffe0161b3c10\n\t\t  lr: 0xfffffff022c04ad8  fp: 0xffffffe0161b3c50\n\t\t  lr: 0xfffffff022c0434c  fp: 0xffffffe0161b3c90\n\t\t  lr: 0xfffffff022754614  fp: 0x0000000000000000\n\n",
  "panicFlags" : "0x2",
  "otherString" : "\n** Stackshot Succeeded ** Bytes Traced 104496 **\n",
  "macOSPanicFlags" : "0x0",
  "macOSPanicString" : "BAD MAGIC! (flag set in iBoot panic header), no macOS panic log available",
  "memoryStatus" : {"compressorSize":0,"compressions":0,"decompressions":0,"busyBufferCount":0,"pageSize":16384,"memoryPressure":false,"memoryPages":{"active":5567,"throttled":0,"fileBacked":9141,"wired":11008,"purgeable":46,"inactive":3056,"free":7243,"speculative":3532}},

Well, my Mac with replaced internals just did it again this morning. Was flawless for about a week, this morning it crashed after 5 min. but then after a reboot I was able to Skype without any issue for 30+ minutes. It shows the same error message in the logs as the ones posted here.

Contacted Apple Support again, and we'll see what happens from there.

Yes, the same thing has happened to me repeatedly. I am someone who uses live streaming professionally to see clients and attend group sessions on Zoom. I've been forced to use my phone which simply not as effective. Please apple techs, fix this problem!

I've been hitting this kernel panic for the last week or two. It seems to happen randomly during video conferences over Hangouts and, after reading the other reports here, seems to be a common symptom. Perhaps related to video encoding/decoding?

This is brand new 2019 machine so I'd be surprised if it turns out to be hardware.

Exactly! This is not some minor inconvenience! Live streaming has been integrated into business communications & training. I actually had to reschedule a business conference call because of this problem. Let's not wait until the next OS. We need a fix NOW. I'm about ready to drop Mac products altogether.

+1. It's pretty embarrassing and unprofessional to have everything freeze up in the middle of a call with clients.

On the plus side, I'm able to show the crash report immediately after the reboot as evidence :)