Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

New MacBook kernel panics

crouch

crouch

macrumors regular
Original poster
Jan 4, 2012
144
264
I just received my MBP 16" yesterday, and it's crashed four times in less than 24 hours, all after I've left the computer alone for some time. I even upgraded to 10.15.4 as soon as I received the thing (knowing how buggy Catalina was) yet it's still crashing. And it's not like I'm putting the computer through anything crazy right now (Spotlight indexing, etc.) I even set it up as brand new.

I know a large number of you love the thing, but this is the worst experience I've had with Apple. Anyhow, if anyone could help clue me in to what's wrong, I'd appreciate it. The latest crash log (first few lines):


panic(cpu 0 caller 0xffffff8018e16487): "AppleIntelFramebuffer::setPowerState(0xffffff81c7f7c000 : 0xffffff7f9c3b9d88, 1 -> 0) timed out after 45932 ms"@/AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Sources/xnu/xnu-6153.101.6/iokit/Kernel/IOServicePM.cpp:5296
Backtrace (CPU 0), Frame : Return Address
0xffffff8218063b40 : 0xffffff80187215cd
0xffffff8218063b90 : 0xffffff801885a3c5
0xffffff8218063bd0 : 0xffffff801884bf7e
0xffffff8218063c20 : 0xffffff80186c7a40
0xffffff8218063c40 : 0xffffff8018720c97
0xffffff8218063d40 : 0xffffff8018721087
0xffffff8218063d90 : 0xffffff8018ec2c7c
0xffffff8218063e00 : 0xffffff8018e16487
0xffffff8218063e50 : 0xffffff8018e15d69
0xffffff8218063e60 : 0xffffff8018e2d2fe
0xffffff8218063ea0 : 0xffffff8018e14b18
0xffffff8218063ec0 : 0xffffff8018763545
0xffffff8218063f40 : 0xffffff8018763071
0xffffff8218063fa0 : 0xffffff80186c713e

BSD process name corresponding to current thread: kernel_task
Boot args: chunklist-security-epoch=0 -chunklist-no-rev2-dev

Mac OS version:
19E266
 
  • Like
Reactions: simonmet and nitschi
Yeah I'm also getting the exact same error on my 16" but unlike Jammy I've had mine for quite some time and only started seeing this issue recently, the specs on my laptop are the completely maxed out except storage.

Edit: I just remembered I did have one happen when I first got it while running Unreal Engine, but other than that it's only occurred while sleeping.

Edit 2: I just looked up the code for the class where the kernel panic is reporting the issue (IOServicePM.cpp on line 5296) and what I've found with my limited C++ knowledge is that this error lies in the function where the driver makes changes to the power state of the hardware. And I've looked at the functions inside that do this and I've compared them to Mojave as most users with older models that are capable of running Mojave have stated that downgrading solves it. And this code in Mojave is much different and simpler, So as was evident this issue is being provoked from the Mojave rework of the way this works.

Edit 3: Here you can find the links if you want to take a look for yourselves (Catalina is 1, and Mojave is 2)
  1. https://opensource.apple.com/source/xnu/xnu-6153.11.26/iokit/Kernel/IOServicePM.cpp
  2. https://opensource.apple.com/source/xnu/xnu-4903.241.1/iokit/Kernel/IOServicePM.cpp
 
Last edited:
  • Like
Reactions: simonmet, obargy, planteater and 3 others
Same thing for me. Happens when i'm connected to power and it goes to sleep. Doesn't happen every time, but happens a lot. Also a new purchase for me, less than a week old. 16" macbook pro
 
  • Like
Reactions: simonmet, obargy and crouch
Also experiencing this issue, my work 15" doesn't have this issue but my new 16" I received on Friday is doing this. Connected to a 4K monitor with power delivery USB-C. Will have a play with the energy settings over the next few days and see if anything improves, also just keep sending the crash logs to Apple.
 
  • Like
Reactions: obargy, 4sallypat and crouch
Is there a solution to this? Or is this a known issue? I was just about to decide between the Macbook Pro 16 or the new Macbook Air. I would really rather not have to deal with this issue with a $2k+ laptop...
 
  • Like
Reactions: Falcon80 and crouch
Seems like it's related to sleep while connected to a monitor that is powering the device for me. I spoke with Apple support and they had me reset NVRAM/SMC as well as clear the /Library/Caches. It hasn't happened since then but I've also not been leaving it connected to my thunderbolt dock overnight.
 
  • Like
Reactions: obargy, Tnanman and crouch
Question to those experiencing this do you all have external monitors or no?

I see a few threads come up on Google from Apple Community going back to around release of 16".
 
  • Like
Reactions: crouch
It's happened to me twice without an external monitor and once with, the 2 times it happened without an external monitor I did have a USB capture card connected, And the 1 time when I had the the monitor connected I had USB devices connected so I think USB might have something to do with it.
 
  • Like
Reactions: crouch, aajeevlin and Chevysales
Bought the 16in base model last Wednesday. Running into the same issue as aikenberry where every time it goes into sleep mode while plugged into power it shuts off. Read on another thread that it has to do with 10.15.4 so I reinstalled the version of MacOS (I think 10.15.3) that came with it. Will update you guys if it this works - I didn’t have this problem the day before I originally updated it
[automerge]1585539536[/automerge]
Let me know if anyone finds a solve for this though outside of what I stated above
 
Last edited:
  • Like
Reactions: obargy and crouch
I think it has something to do with the power adapter and the Mac going to sleep. Right now I have it set to “Prevent computer from sleeping automatically when the display is off”, which is pausing the scenario in which the kernelpanic occurs. This is obviously not a real fix, but a band-aid until we here something from Apple. I assume this is a software issue.
 
  • Like
Reactions: simonmet, obargy and crouch
I let it go to sleep several times connected to the thunderbolt dock yesterday and overnight and didn't experience the panic. So maybe the SMC/NVRAM/clearing caches dir did something. Will report back if it happens again and in what circumstances.
 
  • Like
Reactions: obargy, crouch and aajeevlin
I just got my first panic on my MacBook Pro 16", in WindowServer, I was working on the laptop, walked away from my desk for about 2 minutes, came back and it was all frozen. I just let it sit there, it eventually shut down. I powered it up, and it reported this (I have more of it if anyone is curious):

panic(cpu 2 caller 0xffffff7f94da0ad5): userspace watchdog timeout: no successful checkins from com.apple.WindowServer in 120 seconds
service: com.apple.logd, total successful checkins since wake (2260 seconds ago): 227, last successful checkin: 0 seconds ago
service: com.apple.WindowServer, total successful checkins since wake (2260 seconds ago): 215, last successful checkin: 120 seconds ago

No external monitors, I was only gone about 2 minutes tops it would have only powered off the display but at 15 minutes - no hibernate or other actions.
 
  • Like
Reactions: aajeevlin and crouch
aeikenberry said:
I let it go to sleep several times connected to the thunderbolt dock yesterday and overnight and didn't experience the panic. So maybe the SMC/NVRAM/clearing caches dir did something. Will report back if it happens again and in what circumstances.
Click to expand...
I tried a number of things, and finally found a fix that's worked for at least 48 hours now: the SMC reset.

When I first read about the NVRAM/SMC reset, and did some googling, I thought they were the same thing -- that it was just one thing getting reset. Turns out I was wrong. The NVRAM reset did not fix things, but the SMC reset finally did. No sleep crashes (or crashes of any type) ever since.

The exact steps I took: https://support.apple.com/en-us/HT201295, under the section "Reset SMC on computers that have the T2 chip"
 
  • Like
Reactions: rtr1985 and donawalt
I disabled power nap in the settings and I haven't experienced since then either so I'm not too sure these "attempts" are actually affecting more so just showings its inconsistency.
 
  • Like
Reactions: rtr1985
Seeing all these reports across other forums.

Apple, send us a supplemental fix soon! It’s not significant during casual use. But it’s not workable to have a complete restart when you’re expecting (and need) to pick up where you left off. If this was iOS, they would be sh*#?ing razor blades to get a fix out.
 
  • Love
Reactions: simonmet
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back