Big Sur kernel panic

I see your update. I don't use Chrome either. Strictly Safari.

I do report the kernel panics upon reboot to Apple (a dialogue box comes up asking you to do so), so hopefully everyone else is doing the same.

I don't know what to tell you. Clicking that link takes me right to the bug. You probably have to sign in first. This is not the same as the feedback link. This opens a numbered bug which may be tracked. I guess it's possible that we can only see our own bugs.

I never had a kernel panic in Catalina, either on my old MacBook Pro or on this new one. I don't really have any new hardware except that I bought a new hub to go with the new Mac and its new ports. I doubt that is causing system panics. For a while, I was using two hubs, but they were drawing too much power so I switched everything to one hub, and there were no panics, just the system disabling the port that drew too much. You aren't the first to say that you had kernel panics in Catalina, but most of those who have commented had no kernel panics until Big Sur, and one reverted to Catalina and had the kernel panics cease. It's remarkable how many of us have new 16-inch MacBook Pros, which makes it very unlikely that this is caused by hardware unless these new machines share a common flaw.

Can anyone report Kernel panics on the latest release of Big Sur that was made available for download earlier this week?

Since updating to the latest version I have not experienced any further panics, but again, I don't want to claim "success" on this just yet.

Hey, a Sun alum!

Then you're also well aware that each new release of Solaris would bring reports of panics that ultimately were diagnosed to hardware issues because a memory location that had been used for something innocuous or not at all suddenly held something vital and boom, down the system went.

While it's entirely possible Big Sur is in some way at fault, at least some of the issues reported appear to be general strangeness as they were reported under Catalina as well, and some still have the problem despite them going away for others.

I'm quite sure Apple would be as thrilled to root cause the issue as you would be for them to fix it.

I have had Power Nap disabled for weeks now on my 16" MBP and it doesn't fix the issue.

I have read some people saying that Apple is blaming it on defective boards in the 16" MBPs, but I refuse to believe that as this only started occurring after I upgraded to Big Sur.

Of course, I have done that but it solved the issue only for a short period. After 3 or 5 days the MBP had another Kernel panic.

I must review my point about Apple Support: I have just contacted them over the phone, they escalated the issue further to the engineers and they asked me to provide them with the Kernel panic logs - let's see now.

Thanks for the advice William Kucharski.

I don't know what the cause of the panic is but it's the same exact situation as Alexandros80 is experiencing.

16" MBP. Big Sur.

Never happened prior to Big Sur. Been sending reports to Apple when the laptop reboots but I doubt they look at that stuff.

Indeed, the Kernel panic issue does not seem to be coming from a bug in the opereating system but a USB compatibility with one or some external devices - it is under investigation at the moment.

However, what looks strange to me is the fact that all the external devices (external display, external hard drives) that I have been using at the moment, are all new devices that I bought after the MacBook Pro purchase.

Let me get your opinion, folks...

I have been on the phone with Apple Tier 2 support for a few weeks now trying to resolve this issue.

They have been helpful and it has gotten to the point where they are willing to fix my 16" MBP a few months out of warranty.

However, I would lose my laptop for weeks while it gets repaired. I could push for a replacement instead. Not sure if Apple would agree.

Is it worth going down this road? Getting a replacement? Will I most likely have the same kernel panic issues with a fixed or replacement model? Have we determined if this is more a hardware or software issue?

Thanks for your advice in advance!

I get kernel panics on shutdown only (though I remember once getting a surprise shutdown/restart).

The bottom line for me is that the OS on the late 2015 iMac (which I have too, running Catalina) should not have been updated to Catalina or Big Sur, and Apple should have known it. I am not a software or hardware engineer, but it seems the hardware can't meet this performance standard demanded by the OS.

All, BTW, I ran Apple Disk First Aid on all the internal (partition and container) drives and the external 3TB Time Machine drive and DriveDX free version on the internal drive; nothing suspicious found.

Now testing (again) to satisfy myself that I can run all day an have a normal shutdown if I don't connect the external drive. However, at one time I was convinced that Web browsers apparently caused system degradation leading to kernel panics on shutdown. Maybe, even without Web browsers, over time the system will degrade to the point of preventing normal shutdown. So many possibilities, and I wonder how hard Apple is working to figure this out.

Thanks. No ADGUARD and no CalDigit dock, this is an iMac. The only peripheral device is my TimeMachine backup drive, LaCie. It was installed back in March, way in advance of all my issues. Just for curiosity I just turned off power nap - the issue rarely happens when I sitting here working on the iMac.

Here's my kernel panic log. Apple Tier-2 wouldn't even look at it. They were ready to have my bring in my laptop to fix.

It took a kind CalDigit support engineer to look at it and suggest AdGuard might be the issue (as well as the way I disconnect and connect my dock).

I would appreciate someone who knows how to read this giving me their impression...

I had kernel panic from November to today 6 times on MacBook Pro 13 inch 2019 and 1 on MacBook Pro 16 inch 2019. They started after the upgrade to Big Sur. All crash systems occurred when the system was shut down for a long time, followed by a restart with the error message in several languages. I sent the error results to Apple.

MBP 13 inch 2019

panic(cpu 0 caller 0xffffff80156bf643): "PowerOff timed out in phase 'Notifying power plane drivers'. Total 30000 ms:

IOHibernateSystemPostWake: 105 ms

vfs_unmountall: 495 ms

bufferclean: 116 ms

PowerOff/Restart message to priority client: 159 ms @ 0x<ptr>, com.apple.iokit.IOGraphicsFamily(585.0)[010A56CD-1229-3DA1-B6A8-666F37B48F21]@0x<ptr>->0x<ptr>

PowerOff/Restart still waiting on handler: 3003 ms @ 0x<ptr>, com.apple.iokit.IOUSBHostFamily(1.2)[A4EDF9D5-1A4C-35EA-A92E-88332B37F8D9]@0x<ptr>->0x<ptr>

"@/AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Sources/xnu/xnu-7195.60.75/iokit/Kernel/IOPMrootDomain.cpp:5791

Backtrace (CPU 0), Frame : Return Address

System model name: MacBookPro15,2 (Mac-827FB448E656EC26)

System shutdown begun: YES

Hibernation exit count: 0

MacBook Pro 16 inch

panic(cpu 0 caller 0xffffff800b4bf643): "PowerOff timed out in phase 'Notifying power plane drivers'. Total 30000 ms:

IOHibernateSystemPostWake: 107 ms

vfs_unmountall: 441 ms

bufferclean: 116 ms

PowerOff/Restart still waiting on handler: 3002 ms @ 0x<ptr>, com.apple.iokit.IOUSBHostFamily(1.2)[A4EDF9D5-1A4C-35EA-A92E-88332B37F8D9]@0x<ptr>->0x<ptr>

"@/AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Sources/xnu/xnu-7195.60.75/iokit/Kernel/IOPMrootDomain.cpp:5791

Backtrace (CPU 0), Frame : Return Address

System model name: MacBookPro16,1 (Mac-E1008331FDC96864)

System shutdown begun: YES

Hibernation exit count: 0

Has anyone had any support on this issue from Apple, happening here too? They just removed my post where I said I had tech support for 2 and half hours on a phone call and they have not helped me fix it but basically said I need to pay for support for a £4k machine I bought. :-(