Macbook Air M1 - Kernel Error code 86

@lerklerk You sure it started on 11.2? I haven't seen a single reported case yet of an M1 user that doesn't have it - on any version of Big Sur.

@harrisonjr98 I can't say it for sure as I don't know on which versions I used the Console before but the huge mass of those messages only catched my attention on 11.2.

Same. Apple Support was no help at all. I got the same instructions for my M1 Mac mini.

Same issue here in my Mac mini M1 using macOS Big Sur Version 11.0.1 with unstable bluetooth connection! (Actually I came to here searching "to SMC with errors code 86"). I am also having several errors from "bluetootl" such as "Apple80221Get(APPLE80211_IOC_BTCOEX_MODE) returned error-3903".

In my case the bluetooth issue has gone after disconnecting current Wi-Fi connection and using tethering via my iPhone but the "SMC" errors persist. Not sure if both symptoms are related.

Quick update from me:

I have a AppleCare call booked today. I did briefly speak with them over chat but they basically just got me to do a reinstall I’d already done.

I have two friends receiving their MacBook Pro 13’s this week, one of which has already contacted me to say his doesn’t show this issue. This has made me even more curious!

Note: I did plug in a Belkin USB-C adapter at one point but had thought the issue existed beforehand.

Since then I’ve tried:

1. Removed any reference to the Belkin peripheral (network profile)
2. Reinstalled Big Sur in-place (WiFI).
3. Erase Mac + Reinstall with setup (WiFi)
4. Erase Mac + Reinstall with setup (Ethernet via old USB-A apple adapter + converter, WiFi off)
5. Erase Mac + Reinstall with no setup (WiFI).

Interestingly things took a turn for the worse at this point as because I had to wipe the partition manually and now it won’t reinstall giving “personalisation error” during install.

So, I’m likely going to need to pull out Configurator 2 and bootstrap it from my MacMini. Interesting this does also have a revive option that will rewrite firmware, and I do wonder if this might do the trick and explain why it doesn’t affect all units (and thus not hardware fault)!

Link: https://support.apple.com/en-gb/guide/apple-configurator-2/apdd5f3c75ad/mac

Cheers.

I have a new M1 (so that makes two M1 machines that I own). They both have this error in the logs.

The new M1 is about 40 minutes old (outside of its box), and has no software installed yet.

This IS a macOS issue.

Updating to 11.1 beta did not fix this issue.

I have the same run away error code 86, M1 Mac Mini 16G/256 G.