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.
--
GG & go LA Rams! Dang tiredness, winds, 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| |
\ _ /
( )

On 2022-02-01, 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.

I particularly like how you are doing everything you can to avoid
contacting Apple while the computer is in this problem state, so as to
avoid actually allowing anyone to diagnose and resolve the issue.
Instead, you fumble around until it's up and running again, so that
nobody on the planet can tell what was actually wrong. Good work, and
may you continue to "struggle" so that you can endlessly complain
without actually allowing anyone to help.

Mission accomplished! ; )

--
E-mail sent to this address may be devoured by my ravenous SPAM filter.
I often ignore posts from Google. Use a real news client instead.

JR

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| |
\ _ /
( )

In comp.sys.mac.portables Jolly Roger <jollyroger@pobox.com> wrote:
....
> I particularly like how you are doing everything you can to avoid
> contacting Apple while the computer is in this problem state, so as to
> avoid actually allowing anyone to diagnose and resolve the issue.
> Instead, you fumble around until it's up and running again, so that
> nobody on the planet can tell what was actually wrong. Good work, and
> may you continue to "struggle" so that you can endlessly complain
> without actually allowing anyone to help.

> Mission accomplished! ; )

Apple's guy told me to try disabling macOS' power nap. I don't see how
that will fix it, but we'll see. Also, I wasn't able to reproduce the
symptoms after last night and before this idea.
--
:) (L/C)NY (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| |
\ _ /
( )

In comp.sys.mac.portables Ant <ant@zimage.comant> wrote:
> In comp.sys.mac.portables Jolly Roger <jollyroger@pobox.com> wrote:
> ...
> > I particularly like how you are doing everything you can to avoid
> > contacting Apple while the computer is in this problem state, so as to
> > avoid actually allowing anyone to diagnose and resolve the issue.
> > Instead, you fumble around until it's up and running again, so that
> > nobody on the planet can tell what was actually wrong. Good work, and
> > may you continue to "struggle" so that you can endlessly complain
> > without actually allowing anyone to help.

> > Mission accomplished! ; )

> Apple's guy told me to try disabling macOS' power nap. I don't see how
> that will fix it, but we'll see. Also, I wasn't able to reproduce the
> symptoms after last night and before this idea.

Nope, it happened again with disabled power nap. :(
--
:) (L/C)NY (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| |
\ _ /
( )

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.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.

I updated the linked logs again with new datas due to another crash this
evening (a pattern now it happens at evening PST?). Before that, I
noticed lack of Messages screen saver before going to sleep. Or maybe I
missed it. When I noticed MBP wasn't waking up, I disconnected external
AUSKEY hub and then MBP powered up with its Apple logo and audio chime.
I guess it's not the hub?

I also retried NVRAM and SMC hotkeys (hope I did them right since I have
small hands with four fingers and no thumbs) to see if that helps again like last month.
--
:) (L/C)NY (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| |
\ _ /
( )

Hello.

Since 12/29/2021 afternoon PST, MacBook Pro (MBP) froze hard twice minutes after waking up.

First one was when MBP was asleep (lid closed) and moved (cables were still connected) from the desk due to cleaning the room. Opened its lid up, relogged in the current standard(not admin)-level account, and used it for a few minutes. It was fine and then it froze hard.

Second one was about 30 minutes ago after MBP was asleep for hours from its idle time. Logged in just fine and then log out of this same standard account back to the login screen with multiple accounts. And then, it froze hard right away.

When MBP was frozen, its cursor (both external USB mouse and internal trackpad) and keyboard navigations (including LED lights) didn't respond. Closing and reopening lid, and disconnecting and reconnecting external powered USB devices didn't help at all. I even tried to reproduce this hard lock ups from what I remember. I doubt it is temperature related since it had been in the 60-70 degrees(F) indoor from the outdoor cold weather and rain. Right now, I'm running Disk Utility app's first aid to see if its internal 2 TB SSD is OK.

I'm wondering if there is a hardware issue in this year old (12/29/2020) 13" 2020 A2251 model (MWP62LL/A) MBP. It has Intel Core i7 (2.3 GHz; quad-core 10th gen. i7 CPU; 8 MB; L3 cache (Turbo Boost up to 4.1 GHz)), 32 GB of 3733MHz LPDDR4X RAM, 2 TB PCIe-based SSD, Intel Iris Plus graphic, macOS Big Sur v11.6.2, etc. Using AUKEY USB C Hub 12-in-1 Type C Adapter for ASUS VA27DQSB 27??? 1080P monitor's HDMI and a very old MS USB mouse.

Is there anything else to try before going to an Apple store to diagnose and fix? I assume warranty extended since it was from 12/29/2020. :( Thank you for reading and hopefully answering soon. :)
--
Go away 2021. 2022, please be better! :) NY (Eve)! 2.5-<3" rain fell over the last 2 days. Dang new issues! RIP, Betty White! 99?! :( More like rad 80 2 me.
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| |
\ _ /
( )

Disk Utility app found no issues in all of SSD's APFS default three
partitions. Also, I found out it is 90 days warranty and not a year.
Oops. :(

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

> Since 12/29/2021 afternoon PST, MacBook Pro (MBP) froze hard twice minutes after waking up.

> First one was when MBP was asleep (lid closed) and moved (cables were still connected) from the desk due to cleaning the room. Opened its lid up, relogged in the current standard(not admin)-level account, and used it for a few minutes. It was fine and then it froze hard.

> Second one was about 30 minutes ago after MBP was asleep for hours from its idle time. Logged in just fine and then log out of this same standard account back to the login screen with multiple accounts. And then, it froze hard right away.

> When MBP was frozen, its cursor (both external USB mouse and internal trackpad) and keyboard navigations (including LED lights) didn't respond. Closing and reopening lid, and disconnecting and reconnecting external powered USB devices didn't help at all. I even tried to reproduce this hard lock ups from what I remember. I doubt it is temperature related since it had been in the 60-70 degrees(F) indoor from the outdoor cold weather and rain. Right now, I'm running Disk Utility app's first aid to see if its internal 2 TB SSD is OK.

> I'm wondering if there is a hardware issue in this year old (12/29/2020) 13" 2020 A2251 model (MWP62LL/A) MBP. It has Intel Core i7 (2.3 GHz; quad-core 10th gen. i7 CPU; 8 MB; L3 cache (Turbo Boost up to 4.1 GHz)), 32 GB of 3733MHz LPDDR4X RAM, 2 TB PCIe-based SSD, Intel Iris Plus graphic, macOS Big Sur v11.6.2, etc. Using AUKEY USB C Hub 12-in-1 Type C Adapter for ASUS VA27DQSB 27??? 1080P monitor's HDMI and a very old MS USB mouse.

> Is there anything else to try before going to an Apple store to diagnose and fix? I assume warranty extended since it was from 12/29/2020. :( Thank you for reading and hopefully answering soon. :)
--
Go away 2021. 2022, please be better! :) NY (Eve)! 2.5-<3" rain fell over the last 2 days. Dang new issues! RIP, Betty White! 99?! :( More like rad 80 2 me.
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| |
\ _ /
( )