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

Yes! "CLEARLY... there is a problem with Sequoia 15.4 in Apple's software

update... for M1 processors... that needs to be fixed... submitted logs

and link to this thread as FYI."

Am having the same issue on an M1 Macbook Air. Upgrade from 14.7.5 to either 15.4 via the systems settings or to 15.3 via the Appstore failed with the same message.

Apple support confirmed that the are currently running an internal investigation.

I was able to fix this!! 16" M1 Max from Sonoma to Sequoia 15.4. Apple wanted me to bring it into the repair shop but I insisted its a software issue.

Many M1 Mac users experienced a kernel panic when upgrading to macOS Sequoia (15.x) caused by an error in the AppleT6000DART driver, with the message "Can't ignore lock validation" at t6000dart.c:437. This issue occurs on clean, stock installations with no third-party drivers or devices attached, which points to a software bug rather than a hardware fault. Despite some support channels attributing the problem to hardware, community testing shows that reverting to an earlier version of macOS Sequoia resolves the issue.

A proven solution is to install macOS Sequoia 15.2, which does not include the problematic driver code. To do this, open Terminal and run:

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

This command downloads the full installer for macOS 15.2, allowing you to upgrade without encountering the kernel panic. It is advisable to back up your data before proceeding and to stay on version 15.2 or an earlier stable release until Apple releases an official patch addressing the bug.

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

I would suggest a DFU Firmware Revive or better yet a DFU Firmware Restore. Both of these will reset the secure enclave chip & system firmware. The latter will also reset the internal SSD & push a clean copy of macOS onto the internal SSD. Unfortunately this process requires access to another Mac currently running macOS 15.x Sequoia.

How to revive or restore Mac firmware - Apple Support

FYI, "dart" I believe is Device Address Resolution Table used to delineate hardware and memory on an M-series Mac (internal & external). I'm not certain on the exact name since I'm unable to locate the information with a quick search, but this is what I recall from investigating a year or so ago to assist another user.

If you are seeing this crash with a clean install with no external devices connected and without any third party apps & restore from backup, then you have a hardware issue most likely with the Logic Board.

Edit: Please keep us updated with the results and whatever happens with Apple.

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

have the same problem, and it appeared the same way. (I updated from 15.3.2 to 15.4, then decided to do a clean install. So I reseted the Mac to 14.7.5, and now it panics when I try to update to 15.4). I managed to get back to 15.3.2, but I'm unable to update from that version to 15.4 again due to this error.

Customers don't purchase Macs to do firmware updates and run shell scripts.

This is the manufacture's job, which has not been done.

This feels like a Linux install project, not a professionally maintained commercial product.

I am having the same problem, I already contacted Apple's support and did not solve.

I've tried in every way: Safe mode, recovery mode, Reinstall.

Nothing works. It is certainly an Apple bug.

We need to strengthen the community here to see if they investigate and solve soon.

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.

It is unacceptable for technicians to give a solution where you need to reinstall completely and still do a wipe

I attended Apple Office Hours today and asked the Apple Engineers about M1's failing to update to 15.4

They confirmed that the 15.4.1 update that was just released today addresses this issue