I bumped an old thread related to this issue earlier today, but figured it prudent to make another to bring more attention to this problem while everyone is still within their holiday return periods.
As you may or may not be aware, there's currently an issue that appears to affect all M1 Macs on all versions of Big Sur that Apple hasn't acknowledged yet. It's been reported here on MR as well as Apple's own forums.
The issue can be recreated as follows - open Console on your M1-based Mac. Select "start streaming" and then the tab "errors and faults" to weed out the normal activity. You should see an error populating in rapid succession:
The key numbers, represented by "xxx" above, vary. SMC resets don't appear to solve this, new installs don't solve it, machine replacements and recreating before doing *anything else* after setup - still there!
The very-very-woefully-unqualified techie in me wants to postulate that it could be an Intel-based operation in macOS trying and failing to write to a now nonexistant Intel SMC.
That being said, I don't want to throw gas on the fire as specific error codes pertaining to kernel-level activity are well outside of my knowledge. If you know more about why this might be happening, please chime in! If not, see if it's happening on your machine as well! Across multiple forum threads, I have not once yet witnessed someone who *doesn't* have a Console flooded with this same error, and its been happening since before 11.1 as well so its not something new.
The title of this thread is not intending to be dramatic or start a "-gate," I'm just an M1 owner puzzled by this issue and hopeful to see it resolved via software before the return period is up.
As you may or may not be aware, there's currently an issue that appears to affect all M1 Macs on all versions of Big Sur that Apple hasn't acknowledged yet. It's been reported here on MR as well as Apple's own forums.
The issue can be recreated as follows - open Console on your M1-based Mac. Select "start streaming" and then the tab "errors and faults" to weed out the normal activity. You should see an error populating in rapid succession:
The key numbers, represented by "xxx" above, vary. SMC resets don't appear to solve this, new installs don't solve it, machine replacements and recreating before doing *anything else* after setup - still there!
The very-very-woefully-unqualified techie in me wants to postulate that it could be an Intel-based operation in macOS trying and failing to write to a now nonexistant Intel SMC.
That being said, I don't want to throw gas on the fire as specific error codes pertaining to kernel-level activity are well outside of my knowledge. If you know more about why this might be happening, please chime in! If not, see if it's happening on your machine as well! Across multiple forum threads, I have not once yet witnessed someone who *doesn't* have a Console flooded with this same error, and its been happening since before 11.1 as well so its not something new.
The title of this thread is not intending to be dramatic or start a "-gate," I'm just an M1 owner puzzled by this issue and hopeful to see it resolved via software before the return period is up.
