Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
MBP Kernel Panics Overnight Every Night
- Thread starter bertie343
- Start date
- Sort by reaction score
Hi Bertie,
You are not alone - I suspect Apple is simply killing Intel Machines by lack of testing and care. Plenty of models having T1 chip are affected by this bug.
I have the same issue at MacBook Pro 15-inch, 2017, after update into Big Sur 11.3: panic(cpu 0 caller 0xffffff800af6e4f9): "hibernate_lookup_paddr [...]".
You are not alone - I suspect Apple is simply killing Intel Machines by lack of testing and care. Plenty of models having T1 chip are affected by this bug.
I have the same issue at MacBook Pro 15-inch, 2017, after update into Big Sur 11.3: panic(cpu 0 caller 0xffffff800af6e4f9): "hibernate_lookup_paddr [...]".
It depends. When my battery did swell this year after just 50 charging cycles on my 2017 MacBook Pro (15", i7, 16G RAM), Apple support did answer that "It is not dangerous and it is expected." So you can pretty much anticipate fireworks going out of 3-years old Macs. It is expected behavior.My 10 machines date from 2009-2014. Sometimes Apple can help even with old machines
I don't think that's the case. As an app developer I'm fully aware of how difficult it is to maintain a massive code base. It's most likely human error.
11.3.1 update didn't fix it for me.. can always count on Apple to fix 1 bug and create another 20 lol
Updated to 11.3.1 yesterday in the evening. After reboot I didn't start any application, just closed the MB. When I opened it this morning, everything was fine, no reboot. No application or program was running though, so there was nothing to reopen, that's why I'm not sure yet ... hard to tell if it's fixed.
I'm so glad I found this thread. Wow. It isn't just me.
PRAM and SMC resets made no difference. Nuking AnyConnect from Cisco ditto.
Turned power nap off and, this morning, was delighted to lift the lid and *not* see either the grey screen of death or the login-post-restart prompt.
11.3.1 wants to deploy tonight. Let's see what happens then...
PRAM and SMC resets made no difference. Nuking AnyConnect from Cisco ditto.
Turned power nap off and, this morning, was delighted to lift the lid and *not* see either the grey screen of death or the login-post-restart prompt.
11.3.1 wants to deploy tonight. Let's see what happens then...
Same exact issue for me: MacBook Pro (15-inch, 2017).
Just submitted via the feedbackassistant per the suggestion above. Updating to 11.3.1 now, sounds like maybe that fixes it via this thread on reddit perhaps?
panic: hibernate lookup paddr
Just submitted via the feedbackassistant per the suggestion above. Updating to 11.3.1 now, sounds like maybe that fixes it via this thread on reddit perhaps?
panic: hibernate lookup paddr
Since the 11.3.1 update, have not had one single occurrence of this. This may have fixed it for me.
just updated to 11.4 RC and its still doing the kernel panic to think I FINALLY found a solution to the battery drain on my MBP and they had to ruin it in a few months...
to think I FINALLY found a solution to the battery drain on my MBP and they had to ruin it in a few months...FWIW:
One iMac at work (Guessing a late 2019 model) had daily freezes, and occasional KPs, mostly waking from overnight sleep after upgrading to OS 11. Sometimes would not wake at all, running but unresponsive, had to hold the power button down to shut down.
It had been upgraded to 11.3 (and then 11.3.1) from 10.15, and may have shipped with 10.14.
After a bunch of testing and an OS re-install was no help...I backed up the user account and wiped the SSD, and did a clean install of 11.3.1. Also did a PRAM and SMU reset...to check all boxes.
So far...no more KPs. Had one freeze in 20+ tests, but have not been able to duplicate it again. Most tests were sleep after less than an hour, but a couple were over night, and it always woke as expected in the morning.
Will post back if the issues return, but so far, seems like the clean install may have resolved it.
One iMac at work (Guessing a late 2019 model) had daily freezes, and occasional KPs, mostly waking from overnight sleep after upgrading to OS 11. Sometimes would not wake at all, running but unresponsive, had to hold the power button down to shut down.
It had been upgraded to 11.3 (and then 11.3.1) from 10.15, and may have shipped with 10.14.
After a bunch of testing and an OS re-install was no help...I backed up the user account and wiped the SSD, and did a clean install of 11.3.1. Also did a PRAM and SMU reset...to check all boxes.
So far...no more KPs. Had one freeze in 20+ tests, but have not been able to duplicate it again. Most tests were sleep after less than an hour, but a couple were over night, and it always woke as expected in the morning.
Will post back if the issues return, but so far, seems like the clean install may have resolved it.
Another one chiming in:
MacBook Pro (15-inch, 2017) running 11.3 (20E232) with same issue. It seems to also mess with my two external displays where only one will work until another complete shutdown and restart before the second one starts working.
MacBook Pro (15-inch, 2017) running 11.3 (20E232) with same issue. It seems to also mess with my two external displays where only one will work until another complete shutdown and restart before the second one starts working.
Code:
panic(cpu 0 caller 0xffffff801b76e4f9): "hibernate_lookup_paddr of 3913975 failed\n"@/System/Volumes/Data/SWE/macOS/BuildRoots/2288acc43c/Library/Caches/com.apple.xbs/Sources/xnu/xnu-7195.101.1/osfmk/vm/vm_resident.c:8099
Backtrace (CPU 0), Frame : Return Address
0xffffffb0e74ab8b0 : 0xffffff801b68e02d
0xffffffb0e74ab900 : 0xffffff801b7d48e3
0xffffffb0e74ab940 : 0xffffff801b7c4eda
0xffffffb0e74ab990 : 0xffffff801b632a2f
0xffffffb0e74ab9b0 : 0xffffff801b68d84d
0xffffffb0e74abad0 : 0xffffff801b68db43
0xffffffb0e74abb40 : 0xffffff801be9d68a
0xffffffb0e74abbb0 : 0xffffff801b76e4f9
0xffffffb0e74abbe0 : 0xffffff801b76e67c
0xffffffb0e74abc20 : 0xffffff801be1267f
0xffffffb0e74abc50 : 0xffffff801b7d279d
0xffffffb0e74abca0 : 0xffffff801c7367f8
0xffffffb0e74abcf0 : 0xffffff801c73ac4d
0xffffffb0e74abd10 : 0xffffff801be122e0
0xffffffb0e74abd60 : 0xffffff801be55d15
0xffffffb0e74abde0 : 0xffffff801bdd7383
0xffffffb0e74abe50 : 0xffffff801bdd40f1
0xffffffb0e74abea0 : 0xffffff801bdd1280
0xffffffb0e74abef0 : 0xffffff801bdd112a
0xffffffb0e74abf30 : 0xffffff801bdeeaae
0xffffffb0e74abf70 : 0xffffff801bdee096
0xffffffb0e74abfa0 : 0xffffff801b63213e
Kernel Extensions in backtrace:
com.apple.driver.AppleACPIPlatform(6.1)[7DACFA46-A157-3468-8779-21E8FFA3B799]@0xffffff801c72b000->0xffffff801c7a2fff
dependency: com.apple.driver.AppleSMC(3.1.9)[406AA67A-5111-3CA1-8C7A-A95B18AF6252]@0xffffff801cd4e000->0xffffff801cd66fff
dependency: com.apple.iokit.IOACPIFamily(1.4)[0D13DDA8-F6FE-3649-A850-DE1D9BFF8CEF]@0xffffff801dc3a000->0xffffff801dc3bfff
dependency: com.apple.iokit.IOPCIFamily(2.9)[29933CED-5D05-36A4-BFA1-6F4B4F349283]@0xffffff801e15f000->0xffffff801e187fff
I am having a similar problem, but I have different hardware and I am not receiving the kernel panic error. In fact, I receive no error.
My situation is this:
2019 MBP 15" running macOS 11.4
When I wake the computer in the morning, I am prompted by the login screen (after it takes way longer than normal to wake up) and it asks me to type in my password, as TouchID and Apple Watch unlocking are unavailable after a restart. Trouble is, I never restarted my MBP.
It only does this in the morning, and works as expected throughout the rest of the day.
Again, I am not receiving ANY error message, nothing telling me to restart the computer because of an error (the kernel panic screen), nothing like that. It just thinks it has restarted.
After I type my password, it jumps into my desktop just as it was the night before. I know it is not starting back up because there is only a slight delay after typing my password before I am into the desktop again. No progress bar showing it is starting up.
No idea what to do to fix this, but it has been going on for a few weeks now.
My situation is this:
2019 MBP 15" running macOS 11.4
When I wake the computer in the morning, I am prompted by the login screen (after it takes way longer than normal to wake up) and it asks me to type in my password, as TouchID and Apple Watch unlocking are unavailable after a restart. Trouble is, I never restarted my MBP.
It only does this in the morning, and works as expected throughout the rest of the day.
Again, I am not receiving ANY error message, nothing telling me to restart the computer because of an error (the kernel panic screen), nothing like that. It just thinks it has restarted.
After I type my password, it jumps into my desktop just as it was the night before. I know it is not starting back up because there is only a slight delay after typing my password before I am into the desktop again. No progress bar showing it is starting up.
No idea what to do to fix this, but it has been going on for a few weeks now.
Sounds like a similar issue I'm having here
forums.macrumors.com
Constant Panic/Restarts while asleep (iMac 2017 1tb/16GB)
My Dad's 2017 imac regularly fails to wake from sleep or spordically restarts when in sleep mode. When we have to force a restart, it doesn't always get back to the login screen first time round, it'll often hang on the loading bar to the point where we have to hold the power button down again...
forums.macrumors.com
Hi! I've had exactly the problems mentioned here.
After examining logs a bit, I've found out – it's crashing connected somehow with VirtualBox drivers.
After updating to the latest VirtualBox – problem seems gone. At least, no more reboots today.
TODO: please check & update VirtualBox, and 3rd party Drivers (like AMD?) – can help!
UPD: I still have kernel panics :/ Even full uninstall of Virtualbox didn’t help.
Looking further for a solution. Maybe 11.5 it is.
Cheers
After examining logs a bit, I've found out – it's crashing connected somehow with VirtualBox drivers.
After updating to the latest VirtualBox – problem seems gone. At least, no more reboots today.
TODO: please check & update VirtualBox, and 3rd party Drivers (like AMD?) – can help!
UPD: I still have kernel panics :/ Even full uninstall of Virtualbox didn’t help.
Looking further for a solution. Maybe 11.5 it is.
Cheers
Last edited:
I have a 2019 16" MacBook Pro with this same problem. I immediately started having this problem the first time I upgraded to Big Sur, then downgraded to Catalina, and then decided to give Big Sur another try. At first it was working ok, but then the most recent update from 11.3.1 to 11.4 has resurrected the issue. Such a pain in the butt.
I just wanted to let people know that it can come back, and it's not just 2017 machines affected.
I just wanted to let people know that it can come back, and it's not just 2017 machines affected.