You can make a difference in the Apple Support Community!
When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.
When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.
Running out of time. Will a late 2012 Mac Mini work for FCP 10.6.5 if I update the OS as far as it can go? 10.15.7 Catalina I think? I can't find a compatibility matrix for Mac, macOS and FCP version.
I'll have an M4 Pro Mac Mini by Nov 12 and will run tests.
However, from the already-published numbers, compared to a 2017 i7 iMac 27 with the top 8GB Radeon Pro 580 GPU, even the *base* M4 Mac Mini is about 2.5x faster at single-core, 3x faster at multi-core and about 15% faster at GPU. That doesn't consider the video acceleration, which is much faster than 2017-era Quick Sync.
Terry, sorry about the delayed response; I just saw this.
MacOS kernel panic logs should be in:
/Library/Logs/DiagnosticReports,
/Library/Logs/DiagnosticReports/Archive or:
/var/db/PanicReporter
The filenames should contain "panic", however I think for Apple Silicon Macs (not your case) there may also be a file with a similar date/time with the ".ips" file extension.
Note those locations are not indexed by Spotlight, so a Finder search will not locate them. You can go to the above folders using Finder's SHIFT+CMD+G command.
You can also use terminal to perform a recursive wildcard search from a given directory downward. E.g:
find /Library/Logs -name "*panic*" -ls
If you post these somewhere I can access them, I'll examine them.
joema wrote:
Terry, sorry about the delayed response; I just saw this.
MacOS kernel panic logs should be in:
/Library/Logs/DiagnosticReports,
/Library/Logs/DiagnosticReports/Archive or:
/var/db/PanicReporter
The filenames should contain "panic", however I think for Apple Silicon Macs (not your case) there may also be a file with a similar date/time with the ".ips" file extension.
Note those locations are not indexed by Spotlight, so a Finder search will not locate them. You can go to the above folders using Finder's SHIFT+CMD+G command.
You can also use terminal to perform a recursive wildcard search from a given directory downward. E.g:
find /Library/Logs -name "*panic*" -ls
If you post these somewhere I can access them, I'll examine them.
Caution - in the above command, you need to use single quotes instead of double quotes, like this:
find /Library/Logs -name '*panic*' -ls
The reason is that double quotes let the shell expand the asterisks, and you want to pass them unchanged to the find command.
I'm sure that you know this, but I think it is worth point it out for the benefit of others trying the command.
Yes, no 3rd party kexts. That was just making sure. If I had to guess, I'd say it's an incipient hardware problem, maybe involving the GPU.
You've probably done the usual stuff such as vacuuming out the air intakes on the bottom edge of the screen and verifying disk space is OK.
When my 2015 iMac started failing I ran Apple Diagnostics numerous times and it never found anything. I think I ran Prime95 and GPUTest (similar to Furmark) concurrently. Reproducing the problem was impossible until the Genius Bar ran their ASD/AST stress tests overnight. I don't know if they still use those or if they now have something else.
Thanks joema. My searching last night on the M4 Pro mini found good numbers too. I will be interested to see your testing results. I'm sure everyone at next week's FCP Creative Summit would be interested too. Are you attending?
If you have any time, I'd love to get your take on my panicking issue. This 2018 5K iMac kernel panicked once on Wednesday and once on Thursday while running FCP 10.6.5 in Ventura 13.7.1. Yesterday I ran GPU tests using two instances of an in-browser GPU stress test (mprep dot info slash gpu) along with playing a couple YouTube videos for about an hour. While the GPU tests were running the YT videos were only able to do about 2-3 FPS. At the same time I also ran 12 'yes' processes that got the CPU close to 100%. Fans were cranking but no problems over the hour. I then ran AJA and BM disk speed tests on SMB mounted QNAP volumes via the Sonnet Thunderbolt to 10GbE adaptor. Also no problems. I rebooted into Diagnostics mode and it reported no problems.
I swapped the keyboard and mouse, disconnected an inexpensive TimeMachine SSD and ran FCP 10.6.5 with a relatively simple library on a QNAP 10GbE NAS -- three 5 minute projects of 4K FX6 multicam footage with only a couple built-in effects. After about 15 minutes, it kernel panicked and rebooted itself. I can't find mention of any of the panics in the logs.
This iMac is of the Fusion Drive era and the spinning drive failed a few years ago. I took the iMac apart and replaced it with an OWC SSD and left the smaller original SSD. Yesterday I attempted Recovery mode twice to re-install Ventura on an external Crucial SSD, but I'd check on its progress periodically and see it back at the login screen as if it had rebooted back to the internal SSD. The external SSD didn't have a complete System on it.
I realize I didn't run disk tests on the internal SSDs, so I'll try that next. I also haven't run any RAM tests. I won't be in front of the machine again until tomorrow, but I'm curious if you have any thoughts at what you'd look at. Also, why no panic logs? Thanks for any advice.
Thank you joema. www dot filemail dot com slash d slash zezovzowjupnmim
One of the troubleshooting steps I did was to update Ventura from 13.7 to 13.7.1 so the panic logs were moved into a /Library/Logs/DiagnosticsReports/Retired/ directory so I didn't notice them.
Thank you Luis - I probably would've forgotten about the single quotes when doing the find.
Terry, I looked through your panic log files. It looks related to GPU calls. I had a 2015 i7 iMac27 with a 4GB AMD Radeon R9 M395X. At age of one year, it gradually started experiencing intermittent kernel panics and spontaneous reboots. At first, it was once every two weeks, then once a week then once a day. It passed built-in Apple Diagnostics.
At the Apple Store Genius Bar, it initially passed their more extensive diagnostics but when they ran overnight bench diagostics (Apple Service Diagnostics, Apple Service Tests), it eventually failed a GPU test. The main board was replaced under AppleCare. It ran OK for eight more years, and my wife still uses it.
My first guess is something like that is happening to your 2018 iMac. However, if you could run this terminal command, it would let us examine any third-party kernel extensions:
kextstat | grep -v com.apple
In general, I'd suggest getting an M4 Mac Mini.
Hi joema,
Thank you for having a look. Here's the output:
user@mac ~ % kextstat | grep -v com.apple
Executing: /usr/bin/kmutil showloaded
No variant specified, falling back to release
Index Refs Address Size Wired Name (Version) UUID <Linked Against>
user@mac ~ %
Here's the GPU info:
Radeon Pro 580:
Chipset Model: Radeon Pro 580
Type: GPU
Bus: PCIe
PCIe Lane Width: x16
VRAM (Total): 8 GB
Vendor: AMD (0x1002)
Device ID: 0x67df
Revision ID: 0x00c0
ROM Revision: 113-D000AA-931
VBIOS Version: 113-D0001A1X-025
EFI Driver Version: 01.00.931
Metal Support: Metal 2
Same empty result, so no 3rd party kexts installed.
user@mac ~ % sudo kmutil showloaded | grep -v com.apple
Password:
No variant specified, falling back to release
Index Refs Address Size Wired Name (Version) UUID <Linked Against>
user@mac ~ %
FCP 10.6 required Big Sur 11.5.1 and Monterey for Cinematic mode. 10.6.2 for Voice Isolation required Monterey 12.2.
Thanks Tom. Well, might be an excuse to try an M4 Mac Mini. I've seen some reviews and it seems to work with FCP okay. Anyone here tried it?
I think today is the first deliveries of the base M4 mini, Nov 22 for M4 Pro machines.
Quite a few test reviews of the M4 on YT.
The base model has a Geekbench multi score of well over 15000 together with the 16 GB RAM and faster 2 NAND SSD.
Terry, I accidentally gave you the old kextstat command which does not work after Big Sur. Please try this instead:
sudo kmutil showloaded | grep -v com.apple
Yes, the usual stuff has been done. Thank you very much for your help. Much appreciated!
iMac kernel panicking, will old Mac Mini work in a pinch?
