Kernel Panics after swapping from 2014 MBA to 2017 MBA

[plentyoftimeto69]

Hello everybody. Recently I have swapped my SSD (512GB stock Samsung) from my 2014 MacBook Air into a 2017 MacBook Air. System booted fine, Catalina 10.15.3, and is working, but it's been kernel panicking daily. The panics appear to happen when the lid is closed and the system is woken up from a sleep state by opening the lid. The first panics were related to an application called Across, so I smoked it and removed the daemon. Those panics stopped. Then I was getting the following panic:

panic(cpu 0 caller 0xffffff80198288b7): "PRT0::setPowerState(0xffffff802c57a800 : 0xffffff7f9c9e7626, 0 -> 2) timed out after 30337 ms"@/BuildRoot/Library/Caches/com.apple.xbs/Sources/xnu/xnu-6153.81.5/iokit/Kernel/IOServicePM.cpp:5302

I reset the SMC and PRAM and thought that I nailed it. Opened the lid on my system this morning, went to log in, the system hung, and then I received the following panic:

panic(cpu 0 caller 0xffffff801a4288b7): "AppleAHCIDiskQueueManager::setPowerState(0xffffff802ceb4d80 : 0xffffff7f9cc14958, 0 -> 3) timed out after 101083 ms"@/BuildRoot/Library/Caches/com.apple.xbs/Sources/xnu/xnu-6153.81.5/iokit/Kernel/IOServicePM.cpp:5302

I've tried disabling HDD sleep in the power settings, removing almost all 3rd party kernel modules (I left the 2 modules for my NAS application), and removing a bunch of unsigned software from loading at boot. Not really sure where to go next to shake this problem down, so now I'm here. Attached are the logs from the gen_debug utility. I've also attached an EtreCheck log. Any help would be appreciated.

 

[chrfr]

Did you run the 10.15.3 installer on your 2017 Air or did the computer end up on 10.15.3 just by moving the disk. If you didn't use the installer, download it and run it; the firmware on the computer may be out of date, and running the 10.15.3 installer will update the firmware.

 

[plentyoftimeto69]

Did you run the 10.15.3 installer on your 2017 Air or did the computer end up on 10.15.3 just by moving the disk. If you didn't use the installer, download it and run it; the firmware on the computer may be out of date, and running the 10.15.3 installer will update the firmware.

That's absolutely something I didn't think about and probably it. I did not run the installer, I just swapped the disc and booted thinking "Eh, it's Darwin, it'll boot right up," and it did. The 2014 MBA was upgraded cleanly to Catalina, but the 2017 was only running High Sierra when I did the swap. The firmware on the 2017 is probably out of date.

So just kick off the Catalina installer and that's it? Will it do a reinstall over what I have now preserving my profile or what? Does it just update the firmware if I'm already on 10.15.3?

 

[chrfr]

That's absolutely something I didn't think about and probably it. I did not run the installer, I just swapped the disc and booted thinking "Eh, it's Darwin, it'll boot right up," and it did. The 2014 MBA was upgraded cleanly to Catalina, but the 2017 was only running High Sierra when I did the swap. The firmware on the 2017 is probably out of date.

So just kick off the Catalina installer and that's it? Will it do a reinstall over what I have now preserving my profile or what? Does it just update the firmware if I'm already on 10.15.3?

It'll just reinstall without deleting anything, and will update the firmware as well.

 

[plentyoftimeto69]

It'll just reinstall without deleting anything, and will update the firmware as well.

So far so good. I installed Catalina over the top and I've been able to wake this MacBook up a few times now with no issue. I'll find out for sure tomorrow if it wakes up from a sleep overnight. Thanks for the suggestion!

 

[plentyoftimeto69]

Well, it panics different now. I just dumped out with:

2020-03-13 15:03:13 PerfPowerServices - Crash

Executable: /usr/libexec/PerfPowerServices

Details:

dyld3 mode

abort() called

PerfPowerServices(278,0x70000fe87000) malloc: *** error for object 0x7

f9686f04b00: pointer being freed was not allocated

 

[chrfr]

Well, it panics different now. I just dumped out with:

2020-03-13 15:03:13 PerfPowerServices - Crash

Executable: /usr/libexec/PerfPowerServices

Details:

dyld3 mode

abort() called

PerfPowerServices(278,0x70000fe87000) malloc: *** error for object 0x7

f9686f04b00: pointer being freed was not allocated

Have you tried resetting NVRAM and SMC?

 

[plentyoftimeto69]

Have you tried resetting NVRAM and SMC?

I did right after the Catalina over-the-top install, but I'll do it again.

 

[plentyoftimeto69]

SMC/PRAM reset until today. I just got:

2020-03-19 11:02:57 Kernel Panic (2 times)

Details:

panic(cpu 1 caller 0xffffff80202288b7): "PRT0::setPowerState(0xffffff8

033061000 : 0xffffff7fa3395626, 0 -> 2) timed out after 30362 ms"@/Bui

ldRoot/Library/Caches/com.apple.xbs/Sources/xnu/xnu-6153.81.5/iokit/Ke

rnel/IOServicePM.cpp:5302



3rd party kernel extensions:

foo.tap

foo.tun

 

[plentyoftimeto69]

So I think the kernel panics happen when I enable the option to unlock the MBA with my Apple Watch. Has anybody seen that before?

 

[plentyoftimeto69]

I'll assume this thread is dead, but it's not like I'm doing anything else. So I wiped this MacBook, installed Catalina fresh, and restored from my Time Capsule backup. Issue still persists. Could it be something in my user profile causing it?