Kernel panic during Sequoia 15.4 installation on Apple M1 2021 MacBook Pro with Sonoma 14.7.5

Question

Grant L Author

Level 1

92 points

Kernel panic during Sequoia 15.4 installation on Apple M1 2021 MacBook Pro with Sonoma 14.7.5

Have tried upgrading w 400GB disk space, no apps running.

Make it through Sequoia download, preparing and installation, but always KERNEL PANIC on restart.

/Library/Logs/DiagnosticReports shows 5x panic-full... reports for 5x times I have tried to upgrade to Sequoia.

1st time all apps on Sonoma 14.7.5 up to date.

2nd time restarted 3x times to clear any updates/locked files and safe mode on last boot, then normal boot and install... failed

3rd time ... tried Recovery Mode, installed Sonoma on top of existing,

Weird, noticed updated for Safari update available from 17.6 to 18.4, so installed it... then tried Sequoia upgrade... failed.

4th time... entered Diagnostics Mode, submitted report to Apple Support... no hardware issues....upgraded Parallels v19 to v20.2.2 because their web site now shows "*" by v19 support and forums show restart issues and kernel panic ... better to be on v20 for tested/supported use... maybe ARM drivers causing issue... then installed Sequoia update... failed.

Not sure where the 5th was... used a new TEST user... all the same failures.... reported to Apple... and Support...

PANIC - latest

"panicString" : "panic(cpu 0 caller 0x0): t6000dart 0xfffffdf03b568d70 (dart-dispext0): Can't ignore lock validation @t6000dart.c:437\nDebugger message: panic\nMemory ID: 0x6\nOS release type: Not set yet\nOS version: Not set yet ...

Kernel Extensions in backtrace:

com.apple.driver.AppleT6000DART(1.0)

com.apple.driver.AppleARMPlatform(1.0.2)

com.apple.driver.IODARTFamily(1)

SEE ATTACHED TEXTLOG FILE.

Just noticed SHUTDOWN_STALL(s) and RESET COUNTER with these Panic Reports. SPINDUMP?

Looking at web/apple forums... this appears to be kernel issue w M1 processor and in past, seems to be resolved by coding fix by Apple.... som refer to FIRMWARE updates for?

Thoughts?/Fixes? I'm scheduled to see Apple tech at Apple Store... Thursday.

PS. I thought maybe install Sequoia v15.0/1 and see if install based and then upgrade... avoid major "leap" of if M1 problems brought into play w later Sequoia release (regression). But I was told Apple hasn't made Sequoia individual downloads available?! I just spent $100 for Parallels update to work with Sequoia...

Grant

[Re-Titled by Moderator]

MacBook Pro 16″

Posted on Apr 1, 2025 5:15 PM

Reply

Answer 1

Apr 4, 2025 8:26 AM in response to Grant L

I got that exact same error message when trying to upgrade to 15.4 from 15.3, on an m1 pro. After the installation failed, I also had a bunch of apps start crashing with segfault errors. This completely ruined my work day, but I did eventually figure out that the problem only occurred on x86 architecture apps. I ran a terminal command to force-install rosetta, and now I am at least able to work on 15.3 again. In case anyone is experiencing the same issue, I ran this command to install rosetta again:

softwareupdate --install-rosetta --agree-to-license

Reply

Answer 2

Grant L Author

Level 1

92 points

Apr 4, 2025 9:58 AM in response to guitaristtuck

Interesting.

I did notice a fatal error around rosetta in the Sequoia 15.4 install logs. That may be a fix.

Also, some have not had any problems, so maybe something specific to my/some others environments and/or Apple changed something on 15.4 update.

I am going to try updating again and see if it resolves... after rosetta update...

Hmmm... interesting error...

grantl@MBP-G ~ % softwareupdate --install-rosetta --agree-to-license

By using the agreetolicense option, you are agreeing that you have run this tool with the license only option and have read and agreed to the terms.

If you do not agree, press CTRL-C and cancel this process immediately.

2025-04-04 12:49:53.191 softwareupdate[5312:237067] Package Authoring Error: 072-44352: Package reference com.apple.pkg.RosettaUpdateAuto is missing installKBytes attribute

Install of Rosetta 2 finished successfully

Reply

Answer 3

Apr 5, 2025 2:41 AM in response to Grant L

Morning all, I now have 5 M1s all reporting this same error from our fleet companyt of macs. There was some suggestion that this might be a conflict between 15.4 and Docker (https://forums.docker.com/t/docker-desktop-causing-kernel-panic-on-macos-15-4-developer-beta-1-apple-silicone/146811) but I've tested disabling/removing Docker on a mac where I was able to recreate the issue and the problem still persists.

It's a strange issue as we have a number of M1 macs that have successfully updated to 15.4 with no issue so trying to find the commonality on the affected ones is proving difficult.

I spoke with Apple Support, who were about as useful as a chocolate teapot. Their solution, just reinstall MacOS on the affected devices! *sigh* They didn't even seem to be aware that this was proving to be an issue for lots of people. So hopefully the more it gets reported to them the better, as it might make them acknowledge it is something they need to look at!

In the meantime I'll be attempting to find a fix.

Removing Docker hasn't worked
Reinstalling Rosetta hasn't worked
Installing via the Terminal hasn't worked

Reply

Answer 4

Goxlet

Level 2

259 points

Apr 5, 2025 1:18 PM in response to Goxlet

Apple has solved it for my MacBook Pro 16-inch (2021). My Apple Store techs performed a wipe and install (I couldn't wipe, reinstall 15.3.2, then update to 15.4 without the kernel panic, at which point I took it in) and I've migrated my Carbon Copy Cloner backup data. I did have two reports of damaged apps, but they aren't among my frequently used apps anymore. I will probably try to install them, mainly out of curiosity. I use a lot of old software, much of which requires Rosetta and can't be updated.

Reply

Answer 5

Grant L Author

Level 1

92 points

Apr 18, 2025 6:12 AM in response to Grant L

Well... my problem has finally been resolved.

Update from 15.2 to 15.4.1 was successful this morning and the issue has been resolved from my standpoint.

Unfortunately, it appears a few others with later Mx apple silicon may still have some issues.

Please feel free to continue to update this discussion thread to track the issues.

It's unfortunate that this issue happened. Due to widespread impact to Apple Silicon customers, often with expensive MBPs, it would have been better if (a) Apple Support & Development acknowledged that there was an issue (perhaps with an explanation) AND (b) that they were investigating and/or working on developing a fix.. with expected resolution date.

Otherwise customers are left hanging and unsure what is happening, unable to upgrade to latest MacOS, exposed in terms of missing critical security updates, and may be forced to take corrective actions on their own (return MBP purchase as some have as not working, pay for and install software that is not needed too try to solve MacOS problem, spend HOURS of time trying different things, performing backups/restores, etc). All of these things have a cost, not just in money and resources but time. Customers buy an Apple product because they expect it to work properly, especially with the latest software. When this doesn't happen, it hurts the Apple brand, not just customers.

It really comes down to trust and respect. I'm not pointing fingers or aggressive about this point, just expressing there is a tremendous opportunity for Apple and Customers to partner and work together... it is in each of our best interests.

In my case, I had to spend over $100 to upgrade Parallels software when not needed (yet). v19 was compatible with Sequoia, but I assumed some Mx driver may be causing the issue.

I really hope for others than still have this problem that Apple will provide a(n) (update and) fix for you ASAP.

I also hope this problem does not regress and come up again in a later update/release.

Thanks, Grant

Reply

Answer 6

onworks

Level 1

4 points

Jun 15, 2025 3:38 AM in response to Grant L

I have this same issue. It's doing my head in and regularly causing loss of work in progress. I've been discussing the issue and sharing crash reports with GPT-o3 reasoning model. Here's the key insights and conclusions that others may find useful:

macOS 15.5 shipped with a more aggressive memory-compression engine. Combine that with 8 GB unified memory, lots of Electron/JetBrains apps (also heavy crash reports with decompressor faults stackoverflow.com youtrack.jetbrains.com), and Chrome’s thread pool → perfect storm.

This lines up with the wave of M-series kernel panics on macOS 15.4/15.5 reported by other users — always Kernel data abort, often after wake-from-sleep or light workloads, and never involving third-party drivers.

The crash signature points to macOS’s compressed-swap subsystem. Give the system breathing room (RAM + disk), run Apple Diagnostics, and keep an eye out for a 15.5.1 update.

Apple will likely slip a 15.5.1 kernel fix soon, but meanwhile free disk space and lighter RAM load are your best friends.

["COME ON APPLE!!!! This has been a known problem for 2 to 3 months and is clearly your issue to fix. When will we see 15.5.1? Why was I not warned of the M1 issue before the install? Seems the least you could do. Meantime there's a growing community of users out here being significantly impacted. WE EXPECT MORE FROM YOU! ]

Reply

Answer 7

Grant L Author

Level 1

92 points

Apr 1, 2025 5:44 PM in response to Grant L

UPDATES...

5th attempt was disconnecting all peripherals except power and USB-c 2.5G ethernet.
Trying the following:

Open Terminal -> softwareupdate --fetch-full-installer --full-installer-version 15.2 and will then run /Applications/Install macOS Sequoia over the top of your existing installation.... (15.1 and earlier not available)

( YES... I have a couple of TimeMachine Backups )

Reply

Answer 8

Apr 4, 2025 1:21 PM in response to whataboutmac

They don't care man!! I was on the phone with them and they wanted me to bring my laptop (without coverage) to a certified reseller for diagnosis, which of course cost extra money. They ignored my claims of it being a software in quality control issue. As a long-term customer, this is very disappointing. Upgrading to 15.2 instead of 15.4 solved the problem

Reply

Answer 9

Goxlet

Level 2

259 points

Apr 4, 2025 7:39 PM in response to Grant L

I’m also having the issue of updating my M1 MacBook Pro 16-inch (2021) from 15.3.2 to 15.4. I have another issue to report. I launched Disk Utility and erased the Mac at the request of Apple Support after I reported the issue and requested its escalation.

When the computer presented the main screen in Recovery mode afterwards, I chose the 2nd option - Reinstall macOS Sequoia, I thought installation was proceeding as normal although what was actually installed was Sonoma 14.7.5. Anyone else had that experience? Anyway, partly because I’ve experienced that before when installing to external drives, I decided to go month by month with AppleCare after the original term expired. I’m wondering if the Sonoma installation may provide additional evidence that the logic board will require replacing. A caveat to the assumption that my Mac needs hardware repair is that I didn’t know Recovery mode had installed Sonoma, so I had already performed the restoration of my backed up boot drive before I realized I would have to upgrade to Sequoia before applying the 15.4 update. So my drive was restored in Sonoma, updated to 15.3.2, then I again experienced the kernel panic when trying to update to 15.4. My local Apple Store has my Mac now, and the request is simply to apply the 15.4 update. We erased the computer again while I was at the Genius Bar, so I’m waiting to hear what happens.

Reply

Answer 10

Grant L Author

Level 1

92 points

Apr 6, 2025 9:41 AM in response to probablyjoshh

Thank you. This was already identified as partial solution for 14.7.5 migration to 15.4... upgrade to 15.2.

Once at 15.2, upgrading to 15.4 receive same kernel panic error.

I've tried this several times now, although some suggested it worked for them, without success.

I also tried the rosetta upgrade but still the same errors after doing this.

I also indicated that Apple Support ran remote diagnostics and confirmed hardware did not have any issues.

They also tried to convince me to visit Apple Store/Third Party but I refused as software issue and found Sequoia upgrade workaround.... I cancelled as they wouldn't be able to the me.

Problem now, keep getting daily notifications from MacOS to upgrade to 15.4.

This is clearly a software issue w 15.4.... why push customers to this level when issues?

Someone suggested DFU firmware revive/restore to try to resolve. Managed to test this process on another MBP but haven't had time to test on problem MBP with another MBP at

Another person has suggested upgrading to 15.3.2 and then to 15.4 as it worked for them, but others have also reported that 15.3 to 15.4 failed for them with panic errors.

Finally, someone else did go to Apple Store, format and new install Sequoia and was able to get things working.

Clearly, there are some nuances depending on individual's M1 set up, apps used, etc. as to whether problem occurs or not.

I don't have time right now to backup (3rd time) and re-build MBP and then restore primary working environment (1-2 days)... work deadline. This is a time consuming and costly workaround due to MacOS software issues.

I would hope Apple development is aware of and working on this problem and will soon release an updated 15.4.1(?) to resolve the M1 processor issues... for everyone.

Some of you can try the above options/steps if you want to try to continue working on the problem.

If you have any additional observations, findings or a solution, post back here and let us know.

I will try to perform DFU update as interim step, when I have some more time.

Thank you.... Grant

Reply

Answer 11

Grant L Author

Level 1

92 points

Apr 6, 2025 9:56 AM in response to TheTemplar1307

Share your pain.

You could try to use command line version of MacOS software upgrade to 15.2 or 15.3.2 that are also available, instead of 15.4.... if you need to get to Sequoia for some reason... until Apple fix released.

softwareupdate --fetch-full-installer --full-installer-version 15.2

( ...or... 15.3.2 )

Reply

Answer 12

Grant L Author

Level 1

92 points

Apr 6, 2025 10:22 AM in response to spambilly23

Interesting, thanks for sharing ... for me, very good to know!

Knowing this, a clean install may not be a true workaround, and may set the user back to 15.2/15.3.2... after a lot of work to backup/restore... I don't think I will try to do this, but rather, wait for Apple to fix. Please ensure you make a TimeMachine Backup (before) if you decide to try to upgrade to 15.4.. simpler recovery process.

I did think of another solution... use Recovery Mode and re-install the current MacOS version (in my case 15.2, others at 15.3.2) on top of existing setup. It does not erase existing apps, etc... just a fresh install if MacOS (upgrade) issues (ghosts). It was actually one of the steps Apple Support suggested that I do on Sonoma 14.7.5 to see if it would upgrade to Sequoia or just refresh current Sonoma (it did latter). Maybe that's the difference between some M1 Macs and whether they upgrade to 15.4 or not, see kernel panic problems, or wait until clean install?!

Reply

Answer 13

Ranch001

Level 1

12 points

Apr 7, 2025 11:03 PM in response to Grant L

Any solution to this?

So far only softwareupdate --fetch-full-installer --full-installer-version 15.2 worked, and now I'm stuck on that version which is progress but 15.4 patched some serious security vulnerabilities.

Thanks!

Reply

Answer 14

Apr 17, 2025 3:31 AM in response to c01nd01r

yes i do not have the exact same issue as M1 macs users, but check Macrumors or reddit , a lot of M2 or M3 or M4 users also had the same kernel panic for no reason just after the installation of 15.4 .. i've installed 15.4.1 i was on safe mode for a fex days no issue...

Reply

Answer 15

Grant L Author

Level 1

92 points

Apr 1, 2025 7:08 PM in response to Grant L

I was able to successfully upgrade to Sequoia v15.2 using the identified commands in my last post.

There were several restarts during the installation process (apple logo with status bar, until N mins shown and completed).

I am now attempting to use the Software Update function to upgrade to Sequoia v15.4.

Weirdly, when I first requested this update, I got a message available software updates have changed and were not available?! See screenshot. I tried again and it then appeared to work, started download and installation process.

Is there something wrong with the Apple Update Service currently, and maybe why I have been having issues all day? Or perhaps some issues w upgrade from Sonoma directly to Sequoia 15.4 due (to M1)?

Reply