XPost: comp.sys.mac.system, comp.sys.mac.systems, comp.sys.mac.hardware.misc XPost: comp.sys.mac.portables

In comp.sys.mac.portables Ant <ant@zimage.comant> wrote:

In comp.sys.mac.portables Ant <ant@zimage.comant> wrote:

In comp.sys.mac.portables Ant <ant@zimage.comant> wrote:

In comp.sys.mac.system Ant <ant@zimage.comant> wrote:
...

Since it's still a slow weekend, I decided to try resetting MBP's NVRAM first. So I told its macOS Big Sur v11.6.2 to shut down MBP, but it got stuck during its shutdown for like a minute with admin account's desktop
background (no icons and menu) for about a minute. Mouse cursor was still
movable. And then, it finally shut down. Weird lag. I booted it up, logged in, and then retried its shutdown. No long lags (only a second).

Anyways, I continued on to reset VRAM from https://www.macworld.com/article/224955/how-to-reset-a-macs-nvram-pram-and-smc.html's
instructions, I did:

"Intel Macs

To reset your NVRAM, you use exactly the same procedure you once used to reset PRAM.

1. Shut down your Mac.
2. Press the power button, and as soon as you power up the laptop, hold down Command-Option-P-R.
3. Keep holding down those keys for about 20 seconds. Then let go and allow your Mac to continue starting normally..."

Step #3 took a while to start up again after pressing all keys down for about 20 seconds. I thought I messed up since my four fingers hands, without thumbs, had a hard time pressing all. And then, about ten seconds later, MBP booted by itself. I hope that's normal.

Also, does "nvram ???-c" trick not work? It shows:
% nvram -c
nvram: Error clearing firmware variable fmm-computer-name: (iokit/common) not permitted
nvram: Error clearing firmware variable fmm-mobileme-token-FMM: (iokit/common) not permitted
nvram: Error clearing firmware variable fmm-mobileme-token-FMM-BridgeHasAccount: (iokit/common) not permitted
I even tried with sudo.

...

FYI. No new incidents so far. I hope it stays that way! :)

MBP was doing well until this morning, and then it wouldn't wake up this morning after sleeping since late last night. And then, it powered on by itself when I clicked on its trackpad. After logging in, it restored previous sessions from the crash. :(

Again, it wouldn't wake up correctly this evening like this morning. It powered on by itself with its Apple logo chime after I clicked on the
old external USB mouse's button. After logging in back into the standard level account, Chrome said to restore previous sessions from the crash. I tried to reproduce it manually, but no luck. Its console's logs are
confusing and so long. :( When I logged out and logged into the
admin-level account, then I saw its crash report that popped up for me
to to share to Apple and you guys: http://zimage.com/~ant/temp/MBP2020crashWhenWakingUp.txt.

Part of http://zimage.com/~ant/temp/MBP2020consoleSystemLogCrashWhenWakingUp.txt
from macOS Big Sur v11.6.3's console's system log.
--
:) CNY (h2o tiger) & Black History Mo. GG & go LA Rams! Dang tiredness, sickness, bodies, works, times, colony, nest, life, weather (winter again), etc. :(
Note: A fixed width font (Courier, Monospace, etc.) is required to see this signature correctly.
/\___/\ Ant(Dude) @ http://aqfl.net & http://antfarm.home.dhs.org.
/ /\ /\ \ Please nuke ANT if replying by e-mail.
| |o o| |
\ _ /
( )

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)