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

I had one of these crashes as well this morning, with the 10.5.4 Supplemental Update applied:

panic(cpu 4 caller 0xffffff8005416487): \"AppleIntelFramebuffer::setPowerState(0xffffff869b1aa000 : 0xffffff7f86100d88, 1 -> 0) timed out after 45986 ms

Happened on pressing spacebar on an external keyboard to wake the Mac from sleep; have an external keyboard, mouse & monitor all connected via USB-C.

I've disabled Powernap to see if that helps.
 
I haven't had this issue since I have disabled power nap and performed an SMC reset.

I think I also set the pmset standby to 0 from terminal

Its been more than a week now and have not seen the issue since
 
I just got my certified refurbished 16” Pro on Saturday and this has happened to me a few times over the last five days. However it ONLY happens when the Mac is plugged in to charge and goes to sleep. I have no other accessories attached to the computer and it’s basically “brand new” (other than the fact that it’s refurbished). It’s running 10.15.4 and the specific error message I am getting is “Sleep transition timed out after 180 seconds while notifying clients about upcoming system capability changes”

It seems like this is a software issue, but I’ve read that some people have seen this issue fixed with a new logic board? When I contacted Apple about this they had no idea what I was talking about. Their solution was to try and replicate the issue in safe mode. They said “If this issue still happens in safe mode then it’s a hardware issue and you’ll have to send it back for a replacement. If it doesn’t happen in safe mode then it’s a software issue and you’ll have to reinstall the OS”. Not sure what to believe at the moment..
 
frankjaeger said:
I just got my certified refurbished 16” Pro on Saturday and this has happened to me a few times over the last five days. However it ONLY happens when the Mac is plugged in to charge and goes to sleep. I have no other accessories attached to the computer and it’s basically “brand new” (other than the fact that it’s refurbished). It’s running 10.15.4 and the specific error message I am getting is “Sleep transition timed out after 180 seconds while notifying clients about upcoming system capability changes”

It seems like this is a software issue, but I’ve read that some people have seen this issue fixed with a new logic board? When I contacted Apple about this they had no idea what I was talking about. Their solution was to try and replicate the issue in safe mode. They said “If this issue still happens in safe mode then it’s a hardware issue and you’ll have to send it back for a replacement. If it doesn’t happen in safe mode then it’s a software issue and you’ll have to reinstall the OS”. Not sure what to believe at the moment..
Click to expand...
Some people have gotten defective gpu's. the panic log for this is different from the one we're experiencing. This is a software issue and engineering said they are aware of it. My advice is to turn off power sleep. Alternatively if you can revert back to 10.15.3 somehow the issue should go away but I don't know if that's possible.
 
Viamusic10000 said:
Some people have gotten defective gpu's. the panic log for this is different from the one we're experiencing. This is a software issue and engineering said they are aware of it. My advice is to turn off power sleep. Alternatively if you can revert back to 10.15.3 somehow the issue should go away but I don't know if that's possible.
Click to expand...

Do you know which panic log is for the defective GPUs? I don’t know if I’ve seen anyone post my exact “error message” yet. The “Sleep transition timed out after 180 seconds while notifying clients about upcoming system capability changes” one..
 
frankjaeger said:
Do you know which panic log is for the defective GPUs? I don’t know if I’ve seen anyone post my exact “error message” yet. The “Sleep transition timed out after 180 seconds while notifying clients about upcoming system capability changes” one..
Click to expand...
panic(cpu 4 caller 0xffffff8005416487): \"AppleIntelFramebuffer::setPowerState(0xffffff869b1aa000 : 0xffffff7f86100d88, 1 -> 0) timed out after 45986 ms

Is the one which is software related.
 
Viamusic10000 said:
panic(cpu 4 caller 0xffffff8005416487): \"AppleIntelFramebuffer::setPowerState(0xffffff869b1aa000 : 0xffffff7f86100d88, 1 -> 0) timed out after 45986 ms

Is the one which is software related.
Click to expand...

Hmm okay. Not sure if that helps me lol. This is my first new MacBook since my 2010 one, and I haven’t used that one in a couple years. So I’m still getting back into the swing of things. I was already hesitant about buying refurbished and then of course something happens lol. Though it’s only happening to me when the computer is charging and sleeping. It can sleep fine with no issue if it’s not plugged in. I can also use the computer fine if it’s charging. However the combo of being charged+going to sleep triggers this every single time.
 
frankjaeger said:
Hmm okay. Not sure if that helps me lol. This is my first new MacBook since my 2010 one, and I haven’t used that one in a couple years. So I’m still getting back into the swing of things. I was already hesitant about buying refurbished and then of course something happens lol. Though it’s only happening to me when the computer is charging and sleeping. It can sleep fine with no issue if it’s not plugged in. I can also use the computer fine if it’s charging. However the combo of being charged+going to sleep triggers this every single time.
Click to expand...
You can check the panic log in console. If it doesn't match what was posted above then unfortunately this is a different issue from the one introduced with 10.15.4. Did you try turning off power nap?
 
Viamusic10000 said:
You can check the panic log in console. If it doesn't match what was posted above then unfortunately this is a different issue from the one introduced with 10.15.4. Did you try turning off power nap?
Click to expand...

I haven’t tried the power nap thing, but i just checked my panic logs and they all say:

panic(cpu 4 caller 0xffffff8001091b2c): Sleep transition timed out after 180 seconds while notifying clients about upcoming system capability changes. Suspected bundle: com.apple.iokit.IOGraphicsFamily
 
frankjaeger said:
I haven’t tried the power nap thing, but i just checked my panic logs and they all say:

panic(cpu 4 caller 0xffffff8001091b2c): Sleep transition timed out after 180 seconds while notifying clients about upcoming system capability changes. Suspected bundle: com.apple.iokit.IOGraphicsFamily
Click to expand...
Hmm that does look different. I recommend trying turning off power nap and staying in contact with Apple support. Get in contact with engineering.
 
Viamusic10000 said:
Hmm that does look different. I recommend trying turning off power nap and staying in contact with Apple support. Get in contact with engineering.
Click to expand...

Checked the power nap settings and it turns out it has been off all along. Must have been by default as I never went in to turn it off until now and it was already off.
 
What should I do? As I said before I had kernel panic panic(cpu 0 caller 0xffffff8011291b2c): Sleep transition timed out after 180 seconds while notifying clients about upcoming system capability changes.
Had because after disable power nap and prevent monitor.... everything works fine. One disadvantage is that after hibernation I can turn on Mac only with power button. Anyway that’s fine for me. I can work with these settings. Anyway I have still opportunity to send it back. Time till Friday. What would you do? Return or not?
 
Update: Yesterday I turned back on power nap and no error at the morning. Before that I've changed few setting in Parallels. Parallels was mentioned in kernel panic so I thought that could be a problem.
 
My 16" just crashed while connected to the external display. I was using it, so it didn't go to sleep and crash like it happened last week.
PowerNap is disabled both on power and battery I just checked.
I hope the new macOS version solves the problem, it's been in beta for a while so maybe we can expect it in a couple of weeks.
 
kristof46 said:
What should I do? As I said before I had kernel panic panic(cpu 0 caller 0xffffff8011291b2c): Sleep transition timed out after 180 seconds while notifying clients about upcoming system capability changes.
Had because after disable power nap and prevent monitor.... everything works fine. One disadvantage is that after hibernation I can turn on Mac only with power button. Anyway that’s fine for me. I can work with these settings. Anyway I have still opportunity to send it back. Time till Friday. What would you do? Return or not?
Click to expand...

I sent mine back yesterday. It’s a refurb but once I get my refund I’m buying new.
 
Maybe it is not just about MBP 16 but have you ever experienced any problem with Touch ID? I couldn’t use it no response at all until smc reset. Then after 10-15 minutes or an hour once again. Is it another soft bug?
 
Hoooray! I just got one of these but I'm not on a 'new' 16" Macbook - I'm on a 15" 2018 macOS 10.15.4 with supp.

Hardware Overview:

Model Name: MacBook Pro
Model Identifier: MacBookPro15,1
Processor Name: 6-Core Intel Core i9
Processor Speed: 2.9 GHz
Number of Processors: 1
Total Number of Cores: 6
L2 Cache (per Core): 256 KB
L3 Cache: 12 MB
Hyper-Threading Technology: Enabled
Memory: 32 GB
Boot ROM Version: 1037.100.362.0.0 (iBridge: 17.16.14281.0.0,0)

And the panic details:

panic(cpu 1 caller 0xfffffff0163cb7b4): x86 CPU CATERR detected
Debugger message: panic
Memory ID: 0x6
OS version: 17P4281
macOS version: 19E287
Kernel version: Darwin Kernel Version 19.4.0: Mon Mar 2 20:38:56 PST 2020; root:xnu-6153.101.6~2/RELEASE_ARM64_T8010
Kernel UUID: 3695E9D9-323E-350E-9A6E-65819BE397D7
iBoot version: iBoot-5540.105.2
secure boot?: YES
x86 EFI Boot State: 0xe
x86 System State: 0x0
x86 Power State: 0x0
x86 Shutdown Cause: 0x0
x86 Previous Power Transitions: 0x20002000200
PCIeUp link state: 0x94721614
Paniclog version: 13
Kernel slide: 0x000000000e394000
Kernel text base: 0xfffffff015398000
mach_absolute_time: 0x1e6949c7685
Epoch Time: sec usec
Boot : 0x5eb27b72 0x000ee8ca
Sleep : 0x5eb3bf11 0x00031b76
Wake : 0x5eb3c709 0x00006f94
Calendar: 0x5eb4336c 0x0006733d

Panicked task 0xffffffe00086c200: 3160 pages, 217 threads: pid 0: kernel_task
Panicked thread: 0xffffffe000c40a90, backtrace: 0xffffffe01662b4b0, tid: 342
lr: 0xfffffff015c5c764 fp: 0xffffffe01662b4f0
lr: 0xfffffff015c5c5c0 fp: 0xffffffe01662b560
lr: 0xfffffff015d76e7c fp: 0xffffffe01662b610
lr: 0xfffffff01622562c fp: 0xffffffe01662b620
lr: 0xfffffff015c5bf28 fp: 0xffffffe01662b990
lr: 0xfffffff015c5c280 fp: 0xffffffe01662b9e0
lr: 0xfffffff016a92934 fp: 0xffffffe01662ba00
lr: 0xfffffff0163cb7b4 fp: 0xffffffe01662ba30
lr: 0xfffffff0163bcbe4 fp: 0xffffffe01662baa0
lr: 0xfffffff0163beb0c fp: 0xffffffe01662bb50
lr: 0xfffffff0163bc31c fp: 0xffffffe01662bbe0
lr: 0xfffffff016383780 fp: 0xffffffe01662bc10
lr: 0xfffffff016192abc fp: 0xffffffe01662bc50
lr: 0xfffffff016192340 fp: 0xffffffe01662bc90
lr: 0xfffffff016230514 fp: 0x0000000000000000
 
I had a senior tech advisor look into mine and tell me engineering knows of this issue and is investigating. (Yeah, we reset NVRAM/SMC/everything.) Mine gets hot with multiple external screens and it seems like the GPU is always in High Perf state. My 2017 MBP 13" attaches to the same TB3 dock and monitors and has no issues with running the same monitors. It's just Outlook and Safari really so as long as the CPU doesn't peg with dozens of Safari pages or something, the 13" handles everything without a peep from the fan. I'm RMA'ing mine and getting the new 13". I don't want to compete on Zoom meetings with fans at full blast even if the 16" has great microphones.

I hope they fix this with a driver update or something to get the GPU to settle down since that's what is hot. I don't need the eight cores but some folks do so the 13" may not be an option for them. For me, I'm off to get the 2020 13" MBP.
 
Yesterday I disabled PowerNap, left it like that for a couple of hours and then reenabled it. In the night, before going to sleep, I plugged my MBP to the a/c and then closed the lid. The MBP went to standby. Today morning my Macbook didn't crash. I hope it stays like that..
 
Hello,

I have just started getting a kernel panic this last month. The report is listed below. Is this the same problem everyone is having.?
panic(cpu 0 caller 0xffffff8014091b2c): Sleep transition timed out after 180 seconds while notifying clients about upcoming system capability changes. Suspected bundle: com.apple.iokit.IOGraphicsFamily. Thread 0x74.
Backtracing specified thread
Backtrace (CPU 0), Frame : Return Address
0xffffff820536b900 : 0xffffff8013a471e8
0xffffff82036eb920 : 0xffffff80139433f1
0xffffff82036eb990 : 0xffffff8013941c2f
0xffffff82036eb9e0 : 0xffffff8013a442e9
0xffffff82036eba20 : 0xffffff8013a43b4b
0xffffff82036eba50 : 0xffffff7f975beced
0xffffff82036eba80 : 0xffffff7f975d7f75
0xffffff82036eba90 : 0xffffff801402ff59
0xffffff82036ebaf0 : 0xffffff7f97bd8602
0xffffff82036ebb30 : 0xffffff7f975cc3a6
0xffffff82036ebbb0 : 0xffffff7f975c78eb
0xffffff82036ebc50 : 0xffffff80140020cf
0xffffff82036ebcc0 : 0xffffff801401a770
0xffffff82036ebd60 : 0xffffff80140028b9
0xffffff82036ebdb0 : 0xffffff8014017e1b
0xffffff82036ebe50 : 0xffffff8014014294
0xffffff82036ebea0 : 0xffffff8014011d40
0xffffff82036ebef0 : 0xffffff8014011bd9
0xffffff82036ebf30 : 0xffffff801402d43e
0xffffff82036ebf70 : 0xffffff801402ca36
0xffffff82036ebfa0 : 0xffffff80138c713e
Kernel Extensions in backtrace:
com.apple.iokit.IOGraphicsFamily(575.1)[D47CA481-C5E5-3F03-9B04-6634DF5F3121]@0xffffff7f975b6000->0xffffff7f97606fff
dependency: com.apple.iokit.IOPCIFamily(2.9)[1B1F3BBB-9212-3CF9-94F8-8FEF0D3ACEC4]@0xffffff7f94311000
com.apple.driver.AppleMuxControl2(5.1.16)[35A245F9-3261-359F-925C-59CDBE8FF584]@0xffffff7f97bcd000->0xffffff7f97be1fff
dependency: com.apple.driver.AppleGraphicsControl(5.1.16)[B2381909-ADF2-3459-AA30-4D8D2DC2AF73]@0xffffff7f97bca000
dependency: com.apple.iokit.IOACPIFamily(1.4)[9D1FF279-C4A2-3344-902F-E0B22B508689]@0xffffff7f94308000
dependency: com.apple.iokit.IOPCIFamily(2.9)[1B1F3BBB-9212-3CF9-94F8-8FEF0D3ACEC4]@0xffffff7f94311000
dependency: com.apple.iokit.IOGraphicsFamily(575.1)[D47CA481-C5E5-3F03-9B04-6634DF5F3121]@0xffffff7f975b6000
dependency: com.apple.AppleGraphicsDeviceControl(5.1.16)[56FDE242-D4A6-3E8F-A81C-CE9BA61E3828]@0xffffff7f976cb000

BSD process name corresponding to current thread: kernel_task
 
I'm getting a kernel panic when I Boot up the Mac. - I have the log saved from the start up and the fault that it is stating relates to - IOAcceleratorFamily2 , any know more about that and how to prevent it happening again ?
 
teerexx52 said:
Hello,

I have just started getting a kernel panic this last month. The report is listed below. Is this the same problem everyone is having.?
panic(cpu 0 caller 0xffffff8014091b2c): Sleep transition timed out after 180 seconds while notifying clients about upcoming system capability changes. Suspected bundle: com.apple.iokit.IOGraphicsFamily. Thread 0x74.
Backtracing specified thread
Backtrace (CPU 0), Frame : Return Address
0xffffff820536b900 : 0xffffff8013a471e8
0xffffff82036eb920 : 0xffffff80139433f1
0xffffff82036eb990 : 0xffffff8013941c2f
0xffffff82036eb9e0 : 0xffffff8013a442e9
0xffffff82036eba20 : 0xffffff8013a43b4b
0xffffff82036eba50 : 0xffffff7f975beced
0xffffff82036eba80 : 0xffffff7f975d7f75
0xffffff82036eba90 : 0xffffff801402ff59
0xffffff82036ebaf0 : 0xffffff7f97bd8602
0xffffff82036ebb30 : 0xffffff7f975cc3a6
0xffffff82036ebbb0 : 0xffffff7f975c78eb
0xffffff82036ebc50 : 0xffffff80140020cf
0xffffff82036ebcc0 : 0xffffff801401a770
0xffffff82036ebd60 : 0xffffff80140028b9
0xffffff82036ebdb0 : 0xffffff8014017e1b
0xffffff82036ebe50 : 0xffffff8014014294
0xffffff82036ebea0 : 0xffffff8014011d40
0xffffff82036ebef0 : 0xffffff8014011bd9
0xffffff82036ebf30 : 0xffffff801402d43e
0xffffff82036ebf70 : 0xffffff801402ca36
0xffffff82036ebfa0 : 0xffffff80138c713e
Kernel Extensions in backtrace:
com.apple.iokit.IOGraphicsFamily(575.1)[D47CA481-C5E5-3F03-9B04-6634DF5F3121]@0xffffff7f975b6000->0xffffff7f97606fff
dependency: com.apple.iokit.IOPCIFamily(2.9)[1B1F3BBB-9212-3CF9-94F8-8FEF0D3ACEC4]@0xffffff7f94311000
com.apple.driver.AppleMuxControl2(5.1.16)[35A245F9-3261-359F-925C-59CDBE8FF584]@0xffffff7f97bcd000->0xffffff7f97be1fff
dependency: com.apple.driver.AppleGraphicsControl(5.1.16)[B2381909-ADF2-3459-AA30-4D8D2DC2AF73]@0xffffff7f97bca000
dependency: com.apple.iokit.IOACPIFamily(1.4)[9D1FF279-C4A2-3344-902F-E0B22B508689]@0xffffff7f94308000
dependency: com.apple.iokit.IOPCIFamily(2.9)[1B1F3BBB-9212-3CF9-94F8-8FEF0D3ACEC4]@0xffffff7f94311000
dependency: com.apple.iokit.IOGraphicsFamily(575.1)[D47CA481-C5E5-3F03-9B04-6634DF5F3121]@0xffffff7f975b6000
dependency: com.apple.AppleGraphicsDeviceControl(5.1.16)[56FDE242-D4A6-3E8F-A81C-CE9BA61E3828]@0xffffff7f976cb000

BSD process name corresponding to current thread: kernel_task
Click to expand...
I had this on my previous MBP16
 
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