Kernel panic after macOS update

Question

Kernel panic after macOS update

Hi

I have had some problems with my macOS after updating to Sonoma.

Intel based MacBookPro 2018.

After update to Sonoma I had some Kernel panic. Log attached.

Also I had problems running my LaunchDaemon for starting macFUSE and connecting to SSHFS.

Kernel panic log

This used to work before.

Now, my plan forward is to restore a backup from the MacBook before update. I will restore the backup and remove any redundant/not in use .plist jobs ( especially ) LaunchDaemon jobs. When this is done I will try to update macOS again. I have many .plist jobs also Daemon.

Please supply information on how I can remove any redundant / not in use .plist jobs.

I belive the reason for the kernel panic was the

io.macfuse.filesystems.macfuse.23 4.7.2. ( attached log )

I want to keep the

io.macfuse.filesystems.macfuse.23 4.7.2

, but I want to remove other kexts not in use and other .plist not in use.

Please supply info in how to identify redundant kexts not in use and redundant .plist not in use.

How do I know if the induvidual kexts is needed or not ?

Best regards

MacBook Pro (2017 – 2020)

Posted on Nov 13, 2024 4:14 AM

Reply

Answer 1

Barney-15E

Level 10

116,680 points

Nov 15, 2024 6:45 PM in response to tormod_bjorøy

Please supply information on how I can remove any redundant / not in use .plist jobs.

I have no idea what property lists you have much less whether they are not in use or redundant.

I belive the reason for the kernel panic was the

io.macfuse.filesystems.macfuse.23 4.7.2. ( attached log )

You are most likely correct.

I want to keep the

io.macfuse.filesystems.macfuse.23 4.7.2

Then you should ask them if they have an update that doesn't cause kernel panics.

, but I want to remove other kexts not in use and other .plist not in use.

You use the uninstaller or instructions provided by the developer of the software.

If you can't find the uninstaller or instructions, the launchd plists are in /Library/LaunchAgents, /Library/LaunchDaemons, and ~/Library/LaunchAgents.

Apps can also embed them in the app package and load them from there, so the three locations are not all-inclusive.

Reply

Answer 2

Nov 18, 2024 2:08 PM in response to Barney-15E

Thank for the reply.

I have reinstalled the macOS by using an USB boot disk.

I deleted the mac disk before install.

Then I restored the user files by use of time machine.

I then reinstalled latest version on macFUSE.

The kernel panic is gone now. Probably the cause for the kernel panic was an unfavorable combination of kexts.

Regarding the plists. I did not reinstall any apps from the time machine, so just now I do not have any .plist

in /Library/LaunchAgents, /Library/LaunchDaemons. I will reinstall some of the apps / programs, but will be more selective when reinstalling programs.

There is an alternative to macFUSE, called fuse-t, but I have not tested fuse-t with sshfs. Most of the linux versions come with some sort of sshfs, but for mac this is not included.

Reply

Answer 3

Barney-15E

Level 10

116,680 points

Nov 18, 2024 7:04 PM in response to tormod_bjorøy

Regarding the plists. I did not reinstall any apps from the time machine, so just now I do not have any .plist

in /Library/LaunchAgents, /Library/LaunchDaemons. I will reinstall some of the apps / programs, but will be more selective when reinstalling programs.

Launch Agents and Daemons will not cause kernel panics, but they could cause other instability.

Reply