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

Code: 
panic(cpu 0 caller 0xffffff801d691b2c): Sleep transition timed out after 180 seconds while entering darkwake on way to sleep. Suspected bundle: com.apple.iokit.IOGraphicsFamily. Thread 0x74.
Backtracing specified thread
Backtrace (CPU 0), Frame : Return Address
0xffffff873263b900 : 0xffffff801d0471e8
0xffffff87551439b0 : 0xffffff801cf433f1
0xffffff8755143a20 : 0xffffff801cf41c2f
0xffffff8755143a70 : 0xffffff801d0442e9
0xffffff8755143ab0 : 0xffffff801d043b4b
0xffffff8755143ae0 : 0xffffff7fa0b99ced
0xffffff8755143b10 : 0xffffff7fa0bb2f75
0xffffff8755143b20 : 0xffffff7fa0b9ccb9
0xffffff8755143bb0 : 0xffffff7fa0ba2549
0xffffff8755143c50 : 0xffffff801d6020cf
0xffffff8755143cc0 : 0xffffff801d61a770
0xffffff8755143d60 : 0xffffff801d6028b9
0xffffff8755143db0 : 0xffffff801d617e1b
0xffffff8755143e50 : 0xffffff801d61424e
0xffffff8755143ea0 : 0xffffff801d611d40
0xffffff8755143ef0 : 0xffffff801d611bd9
0xffffff8755143f30 : 0xffffff801d62d43e
0xffffff8755143f70 : 0xffffff801d62ca36
0xffffff8755143fa0 : 0xffffff801cec713e
      Kernel Extensions in backtrace:
         com.apple.iokit.IOGraphicsFamily(575.1)[D47CA481-C5E5-3F03-9B04-6634DF5F3121]@0xffffff7fa0b91000->0xffffff7fa0be1fff
            dependency: com.apple.iokit.IOPCIFamily(2.9)[1B1F3BBB-9212-3CF9-94F8-8FEF0D3ACEC4]@0xffffff7f9d911000

Just had a new error.
 
Sanpete said:
All of you are contacting Apple about this, right?
Click to expand...
Yes, mine has been reported to Apple and they said to reset the SMC, PRAM and reinstall the OS.

I did all that and getting less restart kernel panic messages but not so frequently.

When I first got the crashes, it happened at least once a day.

Now it's about once a week.

Same message "Windows Server timeout"....

I run a 27" TB display in extended mode.
 
I sincerely hope everyone is contacting Apple and asking for this to be escalated to engineering. It is so disappointing to see these types of issues linger for years. The inclusion of the T2 chip is when all this started and yet Apple still hasn't fixed it.
 
  • Like
Reactions: g75d3, simonmet, obargy and 3 others
Sanpete said:
Don't think it's been established that this is an old issue.
Click to expand...
It's clearly been established as an old issue. A basic google search would show you that. It's been happening on the T2-based Macbooks since 2018.
[automerge]1585941241[/automerge]
solojazz said:
Just had a new error.
Click to expand...

Same, just a few minutes ago. It ran for a number of days without a crash (after resetting the SMC, which I believed fixed things.)

It's just depressing: it's a $2500+ laptop that I can't trust. I'm most likely returning it now, which is a shame. It's a lovely laptop minus the kernel panics.
 
  • Like
Reactions: simonmet, nitschi, Never mind and 2 others
FWIW, I just put my machine through a MacOS recovery, as a few users have reported it's helped. I'll let y'all know how it goes over the next few days.
 
Kernel panics have been happening as long as there have been kernels, long before 2018. That doesn't establish that these are the same kind as before. But if you think they are, then you should be reading and adding to the old threads on the old panics, not starting a new one.
 
solojazz said:
Code: 
panic(cpu 0 caller 0xffffff801d691b2c): Sleep transition timed out after 180 seconds while entering darkwake on way to sleep. Suspected bundle: com.apple.iokit.IOGraphicsFamily. Thread 0x74.
Backtracing specified thread
Backtrace (CPU 0), Frame : Return Address
0xffffff873263b900 : 0xffffff801d0471e8
0xffffff87551439b0 : 0xffffff801cf433f1
0xffffff8755143a20 : 0xffffff801cf41c2f
0xffffff8755143a70 : 0xffffff801d0442e9
0xffffff8755143ab0 : 0xffffff801d043b4b
0xffffff8755143ae0 : 0xffffff7fa0b99ced
0xffffff8755143b10 : 0xffffff7fa0bb2f75
0xffffff8755143b20 : 0xffffff7fa0b9ccb9
0xffffff8755143bb0 : 0xffffff7fa0ba2549
0xffffff8755143c50 : 0xffffff801d6020cf
0xffffff8755143cc0 : 0xffffff801d61a770
0xffffff8755143d60 : 0xffffff801d6028b9
0xffffff8755143db0 : 0xffffff801d617e1b
0xffffff8755143e50 : 0xffffff801d61424e
0xffffff8755143ea0 : 0xffffff801d611d40
0xffffff8755143ef0 : 0xffffff801d611bd9
0xffffff8755143f30 : 0xffffff801d62d43e
0xffffff8755143f70 : 0xffffff801d62ca36
0xffffff8755143fa0 : 0xffffff801cec713e
      Kernel Extensions in backtrace:
         com.apple.iokit.IOGraphicsFamily(575.1)[D47CA481-C5E5-3F03-9B04-6634DF5F3121]@0xffffff7fa0b91000->0xffffff7fa0be1fff
            dependency: com.apple.iokit.IOPCIFamily(2.9)[1B1F3BBB-9212-3CF9-94F8-8FEF0D3ACEC4]@0xffffff7f9d911000

Just had a new error.
Click to expand...

Exactly same kernel panic occurred to me. Do you use any peripheral for MacBook Pro 16"?

I am using LG 4K monitor (27UL850) beside on MBP 16" (5500 graphic).
 
crouch said:
FWIW, I just put my machine through a MacOS recovery, as a few users have reported it's helped. I'll let y'all know how it goes over the next few days.
Click to expand...
...and this didn't help either. Woke up this morning to find my machine had crashed & restarted.

Will research more today, but it's looking like I'm going to have to send the machine back as defective.
 
crouch said:
...and this didn't help either. Woke up this morning to find my machine had crashed & restarted.

Will research more today, but it's looking like I'm going to have to send the machine back as defective.
Click to expand...
Honestly considering how many people are reporting this issue, me included, I don't think it's something that different hardware will fix. We just have to wait for the next minor bug fix update which I'm sure will address this.
 
Hello

I would like to share one news related with this topic. In Korean community, there is a person who has a positive effect for this issue with the 'pmset' command in the terminal.

He said that fix this issue with below line of the command.

sudo pmset -a standby 0

And here is the link. (https://www.clien.net/service/board/cm_mac/14798452) (Korean)

Now, I will take some test with this option, but in my opinion, it makes some sense because I am getting this issue when i left my laptop more than 3 hours at least (in a sleep mode). And when you type pmset -g in the terminal, you can check the standbydelaylow is 10800. (10800s => 3 hours). So maybe there could bugs in the state change from 'standby' mode to 'sleep' mode.

I hope my guess is right and i will report my result with above.
 
  • Like
Reactions: obargy, nitschi, 4sallypat and 1 other person
This only started happening for me after upgrading to 10.15.4

What worked for me was to switch off Automatic Graphics Switching in Energy Saver

I haven't had a panic since then.
 
  • Like
Reactions: simonmet and crouch
oztechmuse said:
This only started happening for me after upgrading to 10.15.4

What worked for me was to switch off Automatic Graphics Switching in Energy Saver

I haven't had a panic since then.
Click to expand...
Awesome, thanks for that -- will try.

Did some more research yesterday -- there's a number of others who mentioned the same thing, that's it only after upgrading to 10.15.4 that the problem has started, and that disabling the "Enable Power Nap" feature on the same screen you're talking about (Energy Saver) helped fix things as well.
 
This is the software update to 10.15.3.
When I first installed the update going through System preferences, it messed up my computer. Downloading and installing the update again using the combo updater fixed the problem.
 
  • Like
Reactions: crouch
Tiolin said:
Hello

I would like to share one news related with this topic. In Korean community, there is a person who has a positive effect for this issue with the 'pmset' command in the terminal.

He said that fix this issue with below line of the command.

sudo pmset -a standby 0

And here is the link. (https://www.clien.net/service/board/cm_mac/14798452) (Korean)

Now, I will take some test with this option, but in my opinion, it makes some sense because I am getting this issue when i left my laptop more than 3 hours at least (in a sleep mode). And when you type pmset -g in the terminal, you can check the standbydelaylow is 10800. (10800s => 3 hours). So maybe there could bugs in the state change from 'standby' mode to 'sleep' mode.

I hope my guess is right and i will report my result with above.
Click to expand...

After this mode, I didn't get crush in 2 days.
 
  • Like
Reactions: crouch
Arrgghh. I went 10 days without any crashes or panics after doing an SMC reset, just got this - MacBook Pro 16" 2019 was idle with display off, NOT in hibernate or any other state.

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

Backtrace (CPU 2), Frame : Return Address
0xffffffa779a2b720 : 0xffffff8005d215cd
0xffffffa779a2b770 : 0xffffff8005e5a3c5
0xffffffa779a2b7b0 : 0xffffff8005e4bf7e
0xffffffa779a2b800 : 0xffffff8005cc7a40
0xffffffa779a2b820 : 0xffffff8005d20c97
0xffffffa779a2b920 : 0xffffff8005d21087
0xffffffa779a2b970 : 0xffffff80064c2ce8
0xffffffa779a2b9e0 : 0xffffff7f867a0ad5
0xffffffa779a2b9f0 : 0xffffff7f867a07fa
0xffffffa779a2ba10 : 0xffffff8006454f3e
0xffffffa779a2ba60 : 0xffffff7f8679fcfe
0xffffffa779a2bb60 : 0xffffff800645e163
0xffffffa779a2bca0 : 0xffffff8005e09bb2
0xffffffa779a2bdb0 : 0xffffff8005d27328
0xffffffa779a2be10 : 0xffffff8005cfdcc5
0xffffffa779a2be70 : 0xffffff8005d14aa2
0xffffffa779a2bf00 : 0xffffff8005e32605
0xffffffa779a2bfa0 : 0xffffff8005cc8226
Kernel Extensions in backtrace:
com.apple.driver.watchdog(1.0)[99A75EFF-7734-31A0-80BF-FF8288E30D9B]@0xffffff7f8679f000->0xffffff7f867a7fff

BSD process name corresponding to current thread: watchdogd
Boot args: chunklist-security-epoch=0 -chunklist-no-rev2-dev
 
I escalated with Apple - They sent me a new Macbook Pro 16" and I have yet to have a problem with the new one. You'll need to be very pushy and stern with them, but they sent me a new one before I sent back my old one because the stores are closed due to COVID-19. Make sure they don't try to get you to send your defected one back first... $2400 spent and one should not have to be without a laptop. Good luck yall

Add: I did not update my new one to the newest version of Catalina. I'm going to run on 10.15.3 until 10.15.5 is released (thats what I think caused the problem)
 
Last edited:
  • Like
Reactions: obargy and crouch
Sean Hoskins said:
I escalated with Apple - They sent me a new Macbook Pro 16" and I have yet to have a problem with the new one. You'll need to be very pushy and stern with them, but they sent me a new one before I sent back my old one because the stores are closed due to COVID-19. Make sure they don't try to get you to send your defected one back first... $2400 spent and one should not have to be without a laptop. Good luck yall

Add: I did not update my new one to the newest version of Catalina. I'm going to run on 10.15.3 until 10.15.5 is released (thats what I think caused the problem)
Click to expand...

How would a new machine help with what seems to be a software problem?
 
  • Like
Reactions: DrewyMcDrewface
bopshwop said:
How would a new machine help with what seems to be a software problem?
Click to expand...

You're right, it really didn't. I was still within my return window. So while it appeared to be a software problem, it still very well could have been a hardware problem/lemon, so I played it safe and had them send a new machine. Apple didn't really have much of an answer for why the crashes occurred except that "this isn't a common problem". I haven't had a problem with this one so far, but again I haven't downloaded 10.15.14.
 
  • Like
Reactions: obargy and crouch
So, it's been six days since my MacOS recovery...and my MBP 16" just kernel panicked again last night. The MacOS recovery didn't fix things after all.

Hopefully this truly is a 10.15.4 bug, and I don't have to return the machine.
 
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