2018 Mac Mini 6 Core i7

[Darryl Ramm]

Originally Posted by Siegfried Meier

Ya, UAD Apollo Twin in this case...but I've had the weird shutdown stuff on a separate MacBook Pro 2012 with only a Duet2 installed...

Never had this kinda stuff in older OS's, it's new...always just assumed it was the older computers not jiving with Mojave or High Sierra, but now I'm seeing it again on this mini and it's making me question it...

It’s not macOS, it’s something you are doing/installing. Just keep looking and you will find.

[Siegfried Meier]

Ya I dunno...I just used Activity Monitor to quit every single app I’ve installed to see, and it still won’t shut down. My 2012 has identical software and hardware installed and it “almost always” shuts down...but a much leaner identical 2012 Macbook Pro has issues like this too.

I’ll have to keep trying stuff, I can’t imagine what else would cause it?

[Darryl Ramm]

Originally Posted by Siegfried Meier

Ya I dunno...I just used Activity Monitor to quit every single app I’ve installed to see, and it still won’t shut down. My 2012 has identical software and hardware installed and it “almost always” shuts down...but a much leaner identical 2012 Macbook Pro has issues like this too.

I’ll have to keep trying stuff, I can’t imagine what else would cause it?

Might Be SMC needing a reset. but with new computers... should not be needed. Should also not happen across different computers. But you can try a reset as well.

What did you install on them that was the same?

You unplugged the interface? That should unload the kernel drivers. (but you can check with kexstat). Actually look for any non-apple drivers.

e.g.

$ kextstat | grep -v com.apple

Besides drivers potentially loaded into the kernel that can stop shutdown, there are lots of background processes that are not "apps" (...which will mostly show up n Activity Monitor without an icon, you can also see them with ps -el for example).

And I would uninstall Avid Link and Avid Cloud junk just as a matter of principle.

/var/log/kernel-shutdown.log is one place to look (directly at the file or via Console.app).

[Siegfried Meier]

Well, my 2012 MacBook Pro has hung twice now shutting it down tonight, and there's absolutely nothing at all plugged into it...the Mini has done it once to me tonight too, and probably will again when I try to shut down after session now.

I gotta figure out what's causing this, because it never happened on any other OS before we moved to Mojave...and I can't keep forcing a shutdown as I'm going to start corrupting files or worse. I even did an SMC reset and PRAM reset just before.

If the system is freshly restarted, they tend to shut down with ease...but, if they've been sitting for awhile, or some apps have been opened and closed down, they don't wanna shut down anymore. In the case of the laptop, all I opened was my email...

Very frustrating and hard to pin down. I've been reading many other cases of people having issues with APFS drives, and something being wrong with an upgraded install...that would seem to make sense on this laptop - but we have an identical 2012 MacBook Pro with a fresh install of Mojave and very limited software installed, it too does it. And of course, the new Mini was a total fresh install of Moj as well...I need to learn more about APFS and what it's doing, as this never happened before we started using APFS formatted drives.

[Siegfried Meier]

I took a look at the kernel extensions on both the new Mini and my MacBook Pro. The mini shows this:

Index Refs Address Size Wired Name (Version) UUID <Linked Against>
142 0 0xffffff7f84383000 0x4d000 0x4d000 com.uaudio.driver.UAD2System (9.10.1) no UUID <141 120 13 6 5 3 1>
164 0 0xffffff7f845d1000 0x23000 0x23000 com.uaudio.driver.UAFWAudio (4.3.1 47542) 7768A827-9D44-3C93-9B59-9224F4F8C9CE <141 120 6 5 3 1>
167 0 0xffffff7f846ba000 0x13000 0x13000 com.waves.driver.soundgrid (9.7.99) no UUID <120 23 6 5 3 1>




The MacBook Pro shows this:

Index Refs Address Size Wired Name (Version) UUID <Linked Against>
107 0 0xffffff7f8399a000 0x8000 0x8000 jp.plentycom.driver.SteerMouse (4.1.9) no UUID <106 102 56 45 6 5 3>
153 0 0xffffff7f83d09000 0x4d000 0x4d000 com.uaudio.driver.UAD2System (9.10.1) no UUID <98 69 13 6 5 3 1>
156 0 0xffffff7f83b22000 0x6000 0x6000 com.Cycling74.driver.Soundflower (1.6.7) 3579CD1C-ADE2-32EE-87C0-B8DD7E3A4CBB <98 6 5 3>
160 0 0xffffff7f830a2000 0x23000 0x23000 com.uaudio.driver.UAFWAudio (4.3.1 47542) 7768A827-9D44-3C93-9B59-9224F4F8C9CE <98 69 6 5 3 1>
164 0 0xffffff7f81166000 0x13000 0x13000 com.waves.driver.soundgrid (9.7.99) no UUID <98 17 6 5 3 1>

[Darryl Ramm]

Things to try there. Starting with soundgrid.

You can try to use kextunload to unload any driver. There are reasons that may not work, and you may want to just uninstall the whole software package to test. (it may be non-driver parts of that stuff preventing shutdown).

But as an example with the DigiDal driver on my Mac...

$ kextstat | grep DigiDal
173 0 0xffffff7f848f5000 0x8a000 0x8a000 com.digidesign.iokit.DigiDal (19.5.0f4) B99A2B8A-FEEA-390B-BE03-FA911738C8F8 <13 6 5 3 1>

$ sudo kextunload -b com.digidesign.iokit.DigiDal
Password:

$ kextstat | grep DigiDal
<It is an ex-loaded driver, it has ceased to be, ...>

[Siegfried Meier]

PS - the mini shut down twice in a row properly when I had the Apollo disconnected...doesn’t explain the laptop not shutting down as no hardware was connected, but I don’t recall anyone ever mentioning that they had to disconnect their Apollo’s before shutting down a Mac?

I’ve owned several Apollo’s since 2012, and I’ve never had to do that either...

[Darryl Ramm]

Originally Posted by Siegfried Meier

PS - the mini shut down twice in a row properly when I had the Apollo disconnected...doesn’t explain the laptop not shutting down as no hardware was connected, but I don’t recall anyone ever mentioning that they had to disconnect their Apollo’s before shutting down a Mac?

I’ve owned several Apollo’s since 2012, and I’ve never had to do that either...

Oh well you may be close. You can even try leaving it connected and see if you can force unload the driver like above and see if that works... and them maybe talk to UAD. There might be something subtle going on with driver and kernel versions etc.