flooded console: Failed to write key to SMC with error code 86

[fluxtransistor]

Exactly 4 errors per second on the Pro as well. 16G, 256GB.

 

[w0lf]

Kind of annoying but most likely less than 0.01 CPU cycles to log something like that so not really an issue. If you need to watch console for something just filter for what you're looking for or filter out the smc error.

 

[BeeRich33]

March arrives. Still happening, and I've had this box for two weeks. Mini M1. Chrome hangs, Firefox sits idle for over a minute before going somewhere, as well as Safari, all with this error in the console. 11.2.3 which is brand new.

 

[CMMChris]

It will be fixed in 11.3. Issue is gone in the latest beta.

 

[BeeRich33]

It will be fixed in 11.3. Issue is gone in the latest beta.

Any estimate when it will be out? I literally just installed 11.2.3.

 

[CMMChris]

End of March to early April I guess.

 

[BeeRich33]

So a brand new Mini M1 is absolutely useless for three weeks, maybe. That's fantastic. Yay Apple.

Thanks for the notes.

 

[w0lf]

So a brand new Mini M1 is absolutely useless for three weeks, maybe. That's fantastic. Yay Apple.

Thanks for the notes.

How does text output in the Console app make your computer complete useless?

 

[BeeRich33]

How does text output in the Console app make your computer complete useless?

A Mac Mini M1 that has hugely dysfunctional browsers, is useless. You think I was talking about the console output? Uh, no. At no point did I ever refer to the console's ability to output text. That's what it's for. Now, let's look at what I actually said:

So a brand new Mini M1 is absolutely useless for three weeks, maybe.

The context comes from the sentence which I posted. No mention of console. Try to keep up.

 

[w0lf]

A Mac Mini M1 that has hugely dysfunctional browsers, is useless. You think I was talking about the console output? Uh, no. At no point did I ever refer to the console's ability to output text. That's what it's for. Now, let's look at what I actually said:



The context comes from the sentence which I posted. No mention of console. Try to keep up.

But that has nothing to do with this thread?

As for the issue with your browsers that sounds like a personal problem specific to your setup and likely has nothing to with it being an M1 mac. Maybe try doing a reinstall or create a new user account and see if the issues persist because no update is going to fix the issues you posted about.

 

[BeeRich33]

But that has nothing to do with this thread?

As for the issue with your browsers that sounds like a personal problem specific to your setup and likely has nothing to with it being an M1 mac. Maybe try doing a reinstall or create a new user account and see if the issues persist because no update is going to fix the issues you posted about.

Many people have reported the same issue. It's been addressed here on MR. Reinstalling on a brand new machine? Or reinstall three browsers? The beta of Big Sur has shown to fix this.

 

[harrisonjr98]

Anyone able to install the public release of 11.3 and verify that it’s fixed? (Bonus points if you observe it on 11.2 before upgrading, and then it’s gone )

 

[CMMChris]

It will be fixed in 11.3. Issue is gone in the latest beta.

It already has been fixed in the early beta cycle. Of course it is fixed in the final release as well.

 

[harrisonjr98]

It already has been fixed in the early beta cycle. Of course it is fixed in the final release as well.

Ah, missed that- sorry! Thanks!

 

[BeeRich33]

Fixed. All my issues are fixed, including SoftRaid, 3 external monitors (Mini M1) and errors.