Kernel Panic Mac Mini M1 8GB Ram in Final Cut Pro

Question

Level 1

11 points

Kernel Panic Mac Mini M1 8GB Ram in Final Cut Pro

Hey,

Anyone else had issues with Final Cut Pro on an M1 computer?

Have had 6 Kernel Panics in 24 hours with my New Mac Mini M1. All has happened in Final Cut Pro while editing XAVC files in 8-bit 4:2:0 from Sony a7siii.

Never been an issue on my Macbook Pro from 2018 running Mojave.

I don't know if this is related to hardware in my specific computer, if something is wrong, or if it's software. Have seen many others being able to edit flawlessly on their new M1 computers. I can edit for about a minute before the whole computer freezes for 1-2 minutes and then shutting down and restarting. I have a report log from one incident. If anyone can read it it would be very helpful.

I had two connected hard drives at the time that specific incident happened. One LaCie Rugged 2TB and one Samsung T7 1TB.

I later unplugged the LaCie drive while troubleshooting but it got Kernel Panic again with only the Samsung T7 was plugged in. I have all my footage and library on that drive, so I can't unplug it.

Really need to get this to work, since I need to send my Macbook Pro to service this week and I have work that has to be done in Final Cut Pro during the time it's away.

Posting a video of an incident and a report log down below.

Thanks in advance,

Kevin

Panic report

Mac mini, macOS 11.0

Posted on Nov 28, 2020 5:24 PM

Reply

Answer 1

Top-ranking reply

kevinmuturi Author

Level 1

11 points

Nov 30, 2020 1:55 PM in response to Tom Wolsky

Thank you Tom!

I feel very stupid right now, but I seem to have found where the issue is. I have since tried other troubleshooting steps, as it did not seem to be related to either my user, the OS and hardware.

I tried (which I should have from the beginning) to create a new project with different files, coming from different sources. I found other projects to be working without crashing. Looks like it's the library that does not work with the M1 Mac. I could not really switch library in the middle of the project I was working on, but I tried to import the same files into new library, and voilá. Seems to have been the library that was the issue (still don't know what part of the library since it does work on macOS Big Sur on my MacBook. However, that does not concern me anymore since I know that from now on, I have to start new, fresh libraries for upcoming projects that I will do on my new M1 Mac Mini.

Thanks for all your help guys, I really appreciate it!

Reply

Answer 2

kevinmuturi Author

Level 1

11 points

Nov 30, 2020 7:41 AM in response to Tom Wolsky

Returned the computer and purchased another one (same specs), and the same issue reoccurs. Now I start to think it's either the OS or FCP that is causing the problem. Stress tested Davinci Resolve 17 beta without any crashes even though I put it though more than the computer could handle with FCP. This is crazy.

Reply

Answer 3

Nov 30, 2020 8:22 AM in response to kevinmuturi

That's a panic report.

Etrecheck is a diagnostic utility you can get for free from the App Store.

Run it and it will produce a report describig your hardware and software, so we can have an idea of possible problems.

After running, click Share Report and choose Copy Report.

Then open a reply here, click "Additional Text" button and paste.

Reply

Answer 4

Tom Wolsky

Level 10

152,779 points

Nov 29, 2020 12:39 AM in response to kevinmuturi

What OS are you using? It should be 11.0.1. The computer probably came with 11.0.

Reply

Answer 5

kevinmuturi Author

Level 1

11 points

Nov 30, 2020 9:39 AM in response to Meg The Dog

XAVC files in 8-bit 4:2:0 from Sony a7siii. No optimized media or proxies. Never used them with my MBP.

Tried to set the playback to "better performance" without success, same issue there.

My next step is to make a completely clean reinstall of macOS and setting it up as new, then only install fcp to see if the issue occurs with other footage such as iPhone files or files downloaded from ex. youtube.

My theory is that FCP is bugged. Going to call Apple later today.

Reply

Answer 6

Nov 28, 2020 10:34 PM in response to kevinmuturi

At the very least as it is a new machine get it checked out by Apple.

Most of the recurring kernel panics I have had over the years have turned out to be hardware.

Reply

Answer 7

Meg The Dog

Level 6

13,796 points

Nov 30, 2020 9:45 AM in response to kevinmuturi

If you have time, you might try optimizing some of the media that you are having trouble with and see if the problem continues. That test will give you more info to report to Apple.

MtD

Reply

Answer 8

Tom Wolsky

Level 10

152,779 points

Jan 6, 2021 9:43 AM in response to ferencHun

Do a complete uninstall of Chrome and reboot the system.

Reply

Answer 9

BradSP

Level 1

75 points

Dec 3, 2020 1:12 PM in response to kevinmuturi

The watchdog timeout Kernel Panic has existed in macos for well over a year. Its interesting that its now made its way into the new hardware as well. You can search Mac rumours or these forums and find many long running threads with hundreds on responses from many hundreds of people trying to address and resolve this issue. Its the os and requires Apple to fix it. You can find the threads on mac rumors discussing the exact same KP on M1 under the 38 page thread.

Reply

Answer 10

Dec 29, 2020 6:51 AM in response to iNVisO

There have been some reports with issues with very large displays, so I'd expect this may be something to be fixed in a coming Big Sur update, or a firmware update.

You should report the situation using the feedback page:

http://www.apple.com/feedback

Reply

Answer 11

kevinmuturi Author

Level 1

11 points

Nov 29, 2020 11:42 AM in response to Tom Wolsky

It is 11.0.1.

Gonna return it. Such a hassle since it was supposed to serve as a replacement when my MBP is in for service. Now the store will probably want to examine it and in worst case it might take a few days. Really don't want to be without a workstation, but what to do.

Reply

Answer 12

kevinmuturi Author

Level 1

11 points

Nov 30, 2020 8:10 AM in response to Tom Wolsky

I have reported it and will now speak to Apple about the issue. Seems to be a very specific issue where it seems to only happen when grabbing the start or end of a clip and extending it or shorten it. About 50% of the times, the computer freezes and 2 minutes later the computer restarts.

This does not happen with the same project on another computer (MBP 15" 2018)

I don't have a smaller monitor unfortunately.

Reply

Answer 13

Tom Wolsky

Level 10

152,779 points

Nov 30, 2020 11:31 AM in response to kevinmuturi

I asked your question on the fcp.co forum. No one with a Mac mini running your setup, but the response from joema was, as always, very informative. The thread is here.

https://www.fcp.co/forum/4-final-cut-pro-x-fcpx/34543-m1-mac-mini-with-sony-xavc-media/111130

You might want to follow up directly.

Reply

Answer 14

Dec 5, 2020 1:26 PM in response to kevinmuturi

I am having the same issue but not as frequent. The other issues has been audio drop during editing. Here is a link to that discussion. Getty g no where with Apple. I have the 16gb version coming and will be returning the 8gb version. https://discussions.apple.com/thread/252083695?answerId=253994571022#253994571022

Reply

Answer 15

Dec 30, 2020 1:50 PM in response to seminolefans

Mine happens when it tries to put to sleep my thunderbolt-displayport connected 4k monitor or Promise R6 raid array. I use Final Cut Pro and no issues. Kernel panics occur when my M1 Mac mini (8 GB) tries to put thunderbolt connected devices to sleep. Here's one of the panic logs.

panic(cpu 0 caller 0xfffffe002c458d68): "virtual bool AppleT8103PCIeC::start(IOService *):116: REQUIRE failed: _tunnelClientManager != nullptr"

Debugger message: panic

Memory ID: 0x6

OS release type: User

OS version: 20C69

Kernel version: Darwin Kernel Version 20.2.0: Wed Dec 2 20:40:21 PST 2020; root:xnu-7195.60.75~1/RELEASE_ARM64_T8101

Fileset Kernelcache UUID: 3E6AA74DF723BCB886499A5AAB34FA34

Kernel UUID: 48F71DB3-6C91-3E62-9576-3A1DCEF2B536

iBoot version: iBoot-6723.61.3

secure boot?: YES

Paniclog version: 13

KernelCache slide: 0x0000000023244000

KernelCache base: 0xfffffe002a248000

Kernel slide: 0x0000000023d84000

Kernel text base: 0xfffffe002ad88000

Kernel text exec base: 0xfffffe002ae50000

mach_absolute_time: 0x698b53d1

Epoch Time: sec usec

Boot : 0x5fecf126 0x0002c6b5

Sleep : 0x00000000 0x00000000

Wake : 0x00000000 0x00000000

Calendar: 0x5fecf162 0x000005d4

CORE 0 recently retired instr at 0xfffffe002afb9798

CORE 1 recently retired instr at 0xfffffe002afbac5c

CORE 2 recently retired instr at 0xfffffe002afbac5c

CORE 3 recently retired instr at 0xfffffe002afbac5c

CORE 4 recently retired instr at 0xfffffe002afbac60

CORE 5 recently retired instr at 0xfffffe002afbac60

CORE 6 recently retired instr at 0xfffffe002afbac60

CORE 7 recently retired instr at 0xfffffe002afbac60

Panicked task 0xfffffe166d4618e0: 15707 pages, 420 threads: pid 0: kernel_task

Panicked thread: 0xfffffe166d65a610, backtrace: 0xfffffe3015c7b5f0, tid: 182

lr: 0xfffffe002ae9df8c fp: 0xfffffe3015c7b660

lr: 0xfffffe002ae9dd58 fp: 0xfffffe3015c7b6d0

lr: 0xfffffe002afbff5c fp: 0xfffffe3015c7b6f0

lr: 0xfffffe002afb1914 fp: 0xfffffe3015c7b7a0

lr: 0xfffffe002ae577e8 fp: 0xfffffe3015c7b7b0

lr: 0xfffffe002ae9d9e8 fp: 0xfffffe3015c7bb40

lr: 0xfffffe002ae9d9e8 fp: 0xfffffe3015c7bbb0

lr: 0xfffffe002b6383f8 fp: 0xfffffe3015c7bbd0

lr: 0xfffffe002c458d68 fp: 0xfffffe3015c7bc00

lr: 0xfffffe002c455c08 fp: 0xfffffe3015c7bc60

lr: 0xfffffe002b52f498 fp: 0xfffffe3015c7bd10

lr: 0xfffffe002b52ee84 fp: 0xfffffe3015c7be00

lr: 0xfffffe002b52cea0 fp: 0xfffffe3015c7be70

lr: 0xfffffe002b53286c fp: 0xfffffe3015c7bf00

lr: 0xfffffe002ae60c14 fp: 0x0000000000000000

Kernel Extensions in backtrace:

com.apple.driver.AppleT8103PCIeC(1.0)[35AEB73B-D51E-3339-AB5B-50AC78740FB8]@0xfffffe002c44c000->0xfffffe002c45bfff

dependency: com.apple.driver.AppleARMPlatform(1.0.2)[5CBA9CD0-E248-38E3-94E5-4CC5EAB96DE1]@0xfffffe002b790000->0xfffffe002b7dbfff

dependency: com.apple.driver.AppleEmbeddedPCIE(1)[4F37F34B-EE1B-3282-BD8B-00009B954483]@0xfffffe002bcfc000->0xfffffe002bd0ffff

dependency: com.apple.driver.ApplePIODMA(1)[A8EFA5BD-B11D-3A84-ACBD-6DB25DBCD817]@0xfffffe002c154000->0xfffffe002c15bfff

dependency: com.apple.iokit.IOPCIFamily(2.9)[5187699D-1DDC-3763-934C-1C4896310225]@0xfffffe002d290000->0xfffffe002d2abfff

dependency: com.apple.iokit.IOReportFamily(47)[93EC9828-1413-3458-A6B2-DBB3E24540AE]@0xfffffe002d2ac000->0xfffffe002d2affff

dependency: com.apple.iokit.IOThunderboltFamily(9.3.2)[11617399-2987-322D-85B6-EF2F1AD4A794]@0xfffffe002d3c8000->0xfffffe002d4dbfff

last started kext at 664790520: com.apple.driver.AppleActuatorDriver 4400.28 (addr 0xfffffe002a404000, size 16384)

loaded kexts:

com.apple.driver.AppleTopCaseHIDEventDriver 4020.6

com.apple.filesystems.autofs 3.0

com.apple.fileutil 20.036.15

com.apple.iokit.IOBluetoothSerialManager 8.0.2f9

com.apple.driver.BCMWLANFirmware4378.Hashstore 1

com.apple.driver.AppleAOPVoiceTrigger 11.5

com.apple.driver.AppleThunderboltIP 4.0.3

com.apple.iokit.AppleBCM5701Ethernet 11.0.0

com.apple.driver.CoreKDL 1

com.apple.driver.SEPHibernation 1

Reply

Kernel Panic Mac Mini M1 8GB Ram in Final Cut Pro

Similar questions