Big Sur crash restart loop after update

Question

Luismartinez OP

Created Aug ’20

Replies 50

Boosts 0

Views 23k

Participants

So after updating my MacBook Pro 16 inch , it starts up , then once I log on , it just completely turns off and reboots

Code Block panic(cpu 9 caller 0xffffff800189dc5a): "Inconsistent OOL/copyout size on 0xffffff86e59a7ba0: expected 44, got 0 @0xffffff86e604bf48"@/AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Sources/xnu/xnu-7195.40.44.151.1/osfmk/ipc/ipc_kmsg.c:5032Backtrace (CPU 9), Frame : Return Address0xffffffa0ee73b9b0 : 0xffffff80018be6ad 0xffffffa0ee73ba00 : 0xffffff80019fef13 0xffffffa0ee73ba40 : 0xffffff80019ef96a 0xffffffa0ee73ba90 : 0xffffff8001863a2f 0xffffffa0ee73bab0 : 0xffffff80018bdf4d 0xffffffa0ee73bbd0 : 0xffffff80018be238 0xffffffa0ee73bc40 : 0xffffff80020b9f1a 0xffffffa0ee73bcb0 : 0xffffff800189dc5a 0xffffffa0ee73bd10 : 0xffffff800189df92 0xffffffa0ee73bda0 : 0xffffff800189e4b1 0xffffffa0ee73bde0 : 0xffffff80018b126e 0xffffffa0ee73be60 : 0xffffff80018b1d2a 0xffffffa0ee73bef0 : 0xffffff80019d45e3 0xffffffa0ee73bfa0 : 0xffffff8001864216 Process name corresponding to current thread: endpointsecuritydBoot args: chunklist-security-epoch=0 -chunklist-no-rev2-dev chunklist-security-epoch=0 -chunklist-no-rev2-dev

Boost

Answer 1

kulvik OP

Aug ’20

Same problem when upgrading from beta 4 to beta 6. Have no one solved this yet? :(

0

Answer 2

7raveler OP

Sep ’20

Here’s what worked for me.
unplugged all TB and other accessories.
reset smc.

neither of those two had an effect on their own.

turned off Mac. Held right shift key when powering back on. Startup disk app loaded.

unlocked mac hard drive with password from that app. Clicked restart button from that app.

Mac rebooted and didn’t kernel panic and after two password prompts I was back in business.

hope this helps someone

1

Answer 3

rellect OP

Oct ’20

Had the same issue, I tried the usual things and it didn't work. Finally this is what solved it for me:

While mac is ON, long press on shutdown button until mac is turned off
Now press again to turn on (this will start recovery mode)
From the top bar choose Startup disk
Choose the disk and unlock it with the password
Click the restart button

After that I could log in as usual

7

Answer 4

Hk100 OP

Oct ’20

Thank you . Going to the recovery and then startup disk and unlocking it worked for me for beta 11 .

0

Answer 5

RomainDreidemy OP

Oct ’20

Hi all,

I have the same issue and when I go in the recovery mode, I just have a Grey page.

Please can you help me ?

Thanks

1

Answer 6

sumitarora OP

Nov ’20

Happening same with my Macbook Pro 16.
No trick worked for me, any solution?

0

Answer 7

archieinet OP

Nov ’20

Big Sur crash restart loop after update

it seems to happen every 32+ mins, I have reinstall BigSur, but it doesn't seem to work... HELP

Macbook 2019 16 GB 2667 MHz DDR4
'2.3 GHz 8-Core Intel Core i9

0

Answer 8

Armastus OP

Nov ’20

Same issue. Infinite crash loop. Apple, fix this! This is keeping me from making my living.

0

Answer 9

Bayounsa OP

Nov ’20

Same problem here on 11.0.1 (20B29) and it's not a beta version. This gonna be killing me. any solution?

0

Answer 10

Jason85 OP

Nov ’20

I had a similar problem on my MBP 16 after installing Big Sur (11.0.1) via Software Update. Endless kernel panics and reboots. Safe mode did not work. Weirdly, in Recovery mode I could not get the APFS disk mounted. The system volume reported "Sealed: Broken" and my user data was locked by FileVault and I could not unlockVolume. I also could not reinstall Big Sur, as the installer was unable to unlock the disk and reported an "unexpected error". (Same thing in Disk Utility when attempting First Aid)

I took a bunch of steps, and am unsure which were the essential ones so I'm posting everything I did. Maybe this will help someone else.

1. Reset SMC
2. Booted into recovery mode
3. [Unsure if useful] Attempted to use 3rd party APFS file recovery utility (iBoySoft), running: sh <(curl URL hidden
4. Played around a bit with 3rd party tool but it didn’t work - it asked for password to unlock disk, but none I tried worked.
5. In terminal, tried “resetpassword” - and selected forgot password. For the first time, it let me change the password for my user (admin) account. It had me authenticate via iCloud and sent a trusted device request/confirmation code, etc. It seemed to suggest I was changing the FileVault password.
6. [Unsure if useful] Startup Security Utility (from pulldown menu in Recovery mode) now worked for the first time. I reduced security level to medium to boot any previously authorized OS
7. Reinstalled Big Sur from recovery mode - it was now able to unlock the disk
8. Reinstallation successful

On first boot, Big Sur reported some 3rd party extensions were causing reboot and have been disabled. Based on others' experience, I'm guessing this was the cause of the previously encountered kernel panics (?)

My best guess is that the essential steps were 1,2,5, maybe 6, and 7. Good luck

1