kernel panic three times since upgrading to 10.14.6

I have been having the same problem, kernel panic on a brand-new Mac Mini 2019 after upgrading to Mojave 10.14.6 (18G87).

But for me the trigger is different -- it happens whenever Time Machine starts a backup. After a few seconds of "preparing", the machine freezes, then spontaneously shuts down. It appears to be reproducible on demand -- I just manually start a Time Machine backup, and the kernel panics.

I agree with others in this thread, waiting till Catalina to fix this issue is unacceptable. It may be a pain and inconvenient and embarrassing to have to spin up a macOS 10.14.7 or macOS 10.14.6 Supplement 2, but it needs to be done. I cannot back up my machine (e.g. to prepare for an upgrade to Catalina) without a fix to this issue in Mojave.

Attached is the crash report I see when I've restarted.

It is impossible to say for sure but as far as I can tell, it doesn’t seem like your KP are related. There is a commonality that is use of built-in camera in videoconferencing, which is not your case.

Same here. This machine is not reliable anymore. Any video application will crash my 2019 Macbook Pro. Did they say they will fix it? It must be a hardware issue, as I have all my software updated, including the OS. I'm a software developer by the way.

Installed the update yesterday, restarted once in between, Mac was sleeping overnight. This morning had a 1hr Skype conversation using the integrated webcam, no issues at all. Let's see if it stays this way.

They have my Laptop in the shop now. It's VERY displeasing. And another user above stated that they had their logic board replaced and it STILL happened. NEVER will I accept it's a software issue. Get it together Tim Cook and Apple.

Same problem.

When I'm on and video call, it's freeze and turning off after random period of time (up to 60 mins).

How to fix it?

I have MacBookPro15,1 2018, bought it 3 weeks ago (new)

 {
  "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": "87BC0CD3-4B0F-4DE7-99ED-E5FF5BDAED81",
  "timestamp": "2019-09-02 17:47:16.50 +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" : "87BC0CD3-4B0F-4DE7-99ED-E5FF5BDAED81",
  "crashReporterKey" : "c0dec0dec0dec0dec0dec0dec0dec0dec0de0001",
  "date" : "2019-09-02 17:47:16.46 +0000",
  "panicString" : "panic(cpu 1 caller 0xfffffff00dc85bec): \"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: 0xc1\nx86 Previous Power Transitions: 0x70707060400\nPCIeUp link state: 0x1611\nPaniclog version: 13\nKernel slide:     0x000000000757c000\nKernel text base: 0xfffffff00e580000\nmach_absolute_time: 0x78c41a5af\nEpoch Time:        sec       usec\n  Boot    : 0x5d6d5044 0x000d68b0\n  Sleep   : 0x00000000 0x00000000\n  Wake    : 0x00000000 0x00000000\n  Calendar: 0x5d6d5586 0x00051b16\n\nPanicked task 0xffffffe0006d0b40: 8089 pages, 207 threads: pid 0: kernel_task\nPanicked thread: 0xffffffe000a9b910, backtrace: 0xffffffe016813590, tid: 280\n\t\t  lr: 0xfffffff00e68e2a4  fp: 0xffffffe016813620\n\t\t  lr: 0xfffffff00e77b5a4  fp: 0xffffffe016813760\n\t\t  lr: 0xfffffff00e659610  fp: 0xffffffe016813770\n\t\t  lr: 0xfffffff00e68d848  fp: 0xffffffe016813ae0\n\t\t  lr: 0xfffffff00e68dbc0  fp: 0xffffffe016813b20\n\t\t  lr: 0xfffffff00e68da14  fp: 0xffffffe016813b40\n\t\t  lr: 0xfffffff00dc85bec  fp: 0xffffffe016813bd0\n\t\t  lr: 0xfffffff00eb15fc4  fp: 0xffffffe016813c10\n\t\t  lr: 0xfffffff00eb14ad8  fp: 0xffffffe016813c50\n\t\t  lr: 0xfffffff00eb1434c  fp: 0xffffffe016813c90\n\t\t  lr: 0xfffffff00e664614  fp: 0x0000000000000000\n\n",
  "panicFlags" : "0x2",
  "otherString" : "\n** Stackshot Succeeded ** Bytes Traced 108000 **\n",
  "macOSPanicFlags" : "0x0",
  "macOSPanicString" : "BAD MAGIC! (flag set in iBoot panic header), no macOS panic log available",

Ah crap, it worked fine for almost two weeks. Now this morning it just crashed again two times after a couple minutes of Skypeing. Called Apple and let them know their stuff is still not working, and they told me that the engineers are still working on this particular issue. Back to using a USB webcam.

Does Apple have a fix for this yet? I reinstalled the MacOS and then it crashed again during a video teaching session on Thursday again. The computer gets hot and it only crashes when the camera is in use. The crashes aren't easily repeated. Sometimes it's one after another and other times I can go a couple of days between. I bought an external camera and am using that because my job depends on my not dropping clients. Has anyone actually had this fixed at the store? I don't want to bring my laptop in and not have it fixed. It is extremely difficult to go without my mac when I work from video at home. I am under warranty, but don't want to go in until they have a fix.

same thing. macOS 10.14.6。

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: 16P6571\nmacOS version: 18G95\nKernel version: Darwin Kernel Version 18.7.0: Tue Aug 20 15:27:14 PDT 2019; root:xnu-4903.271.2~1\/RELEASE_ARM64_T8010\nKernelCache UUID: 885977DF2F52326CF4784472A3CF2590\nKernel UUID: DE3F494A-B901-34B4-9504-6454BC772145\niBoot version: iBoot-4513.270.14\nsecure boot?: YES\nx86 EFI Boot State: 0xe\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: 0x00000000129fc000\nKernel text base: 0xfffffff019a00000\nmach_absolute_time: 0x2334a6c7c36\nEpoch Time: sec usec\n Boot : 0x5d805926 0x000c0b30\n Sleep : 0x5d82bb68 0x00022da3\n Wake : 0x5d82c49a 0x00007cba\n Calendar: 0x5d82d8a9 0x0000933e\n\nPanicked task 0xffffffe000401c20: 8246 pages, 207 threads: pid 0: kernel_task\nPanicked thread: 0xffffffe0007bf3e0, backtrace: 0xffffffe03766b590, tid: 280\n\t\t lr: 0xfffffff019b0e2a4 fp: 0xffffffe03766b620\n\t\t lr: 0xfffffff019bfb5a4 fp: 0xffffffe03766b760\n\t\t lr: 0xfffffff019ad9610 fp: 0xffffffe03766b770\n\t\t lr: 0xfffffff019b0d848 fp: 0xffffffe03766bae0\n\t\t lr: 0xfffffff019b0dbc0 fp: 0xffffffe03766bb20\n\t\t lr: 0xfffffff019b0da14 fp: 0xffffffe03766bb40\n\t\t lr: 0xfffffff019105bec fp: 0xffffffe03766bbd0\n\t\t lr: 0xfffffff019f95fac fp: 0xffffffe03766bc10\n\t\t lr: 0xfffffff019f94ac0 fp: 0xffffffe03766bc50\n\t\t lr: 0xfffffff019f94334 fp

I forgot to mention:

1. I also only started seeing this after the recent upgrade to 10.14.6
2. The mac has: Radeon Pro 560X 4 GB . Intel UHD Graphics 630 1536 MB
3. UVC Camera VendorID_1452 ProductID_34068

I have exactly the same issue as well :(

i have the same issue too,

it happened serval times when using camera since upgrading to 10.14.6

it seems to be a system bug.

hope it will be solved soon.

Get it three times during one video session (1.5h) using internal website in Chrome. Didn't get it during another 1.5h session earlier today. Never seen any crashes on this MacBook Pro at all.

Yes I did.

Let us know what they said!