The problem persists and has been there for a long time now. The only visibile solution has been to replace logic boards. And some of the time this does not address it either (probably because those are refurbished). Given its age I would lodge a request with Apple to adrdress your individual issue while its still covered and so new. Work with them and insist that you need a working laptop and see if you can get it resolved rather than letting it go on. You should not need to disable apples own controls to get a stable laptop.
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.
MacOS Catalina 10.15.3 - crash panic(cpu 0 caller 0xffffff801faa2d1c): Sleep transition timed out after 180 seconds while calling power state change
- Thread starter andeug
- Start date
- Sort by reaction score
Do you have any external devices attached to the computer when the crash happened?
could you eleborate on how this occured? Was it with external monitor connected? During wake from sleep? What version of catalina are you running?
New here and I am facing the same problem with less than 2-month old Mac Mini I7 3.2GHz. Have been with Apple-support online and local Apple store checked both hardware and clean-install of OS in the past three weeks. Nothing helps. I setup new account, with no software installed, only connected to my own internal Ethernet which is isolated from internet completely, connected to LG TV through HDMI cable, problem persisted.
panic(cpu 0 caller 0xffffff800a49092c): Sleep transition timed out after 180 seconds while calling power state change callbacks. Suspected bundle: com.apple.iokit.IONetworkingFamily. Thread 0x10e3.
panic(cpu 0 caller 0xffffff800a49092c): Sleep transition timed out after 180 seconds while calling power state change callbacks. Suspected bundle: com.apple.iokit.IONetworkingFamily. Thread 0x10e3.
The question I have is does any one encounter one here purchase their computer directly from Apple Store, and is not refurbished? Mine is brand new but purchased from a third-party vendor.
@MacMiniDavid Yes i think you will find there are a number reported here. Some have even had their logic boards replaced by Apple and the problem persists. Stand your ground and see what happens. Fundamentally its broken and the answer from Apple appears to be user error.
Hi, thank you very much in responding my questions. I just want to reaffirm that at least some of the Mac products which suffered this problem are genuine product directly bought from Apple Store. Mine is supposed to be genuine product but I purchased it through a third-party vendor.
Hi all,
Hardware: MacBook Pro (16-inch, 2019)
Software: macOS, 15.7 (19H2)
Purchased direct from Apple
Problem: freeze, quick fan burst and crash followed by these types of errors:
Can be reproduced by using USB-C ports (TBH the only times I experience this issue)
Hope it's useful
Sincerely
Hardware: MacBook Pro (16-inch, 2019)
Software: macOS, 15.7 (19H2)
Purchased direct from Apple
Problem: freeze, quick fan burst and crash followed by these types of errors:
Code:
panic(cpu 0 caller 0xffffff80030c1eff): assertion failed: ifp->if_sndbyte_total >= len, file: /AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Sources/xnu/xnu-6153.141.2/bsd/netinet/in_pcb.c, line: 3965Can be reproduced by using USB-C ports (TBH the only times I experience this issue)
Hope it's useful
Sincerely
I did contact apple support. The call center person had me remove all my login items (goggle drive, dashlane, default folder x, cisco webex) and then restart and deliberately sleep. After 3 minutes the computer woke from sleep and the support person concluded that the problem was with one of the login items that I use. She recommended that I reinstall these items one at a time and see when the problem reappears at which time the most recently restored login item can be identified as the offending software. I did explain that this problem has been reported by many other people using different configurations of login items and that it had been present for at least two cycles of minor releases of the OS. She recommended that, if I continue to have difficulty, I should reinstall the OS.
While these individual steps seem reasonable the overall impression is that no one in Apple has a clue.
I am ordering a linux laptop. Once it is working I plan to sell my 16 inch 2019 Apple Macbook Pro (2.3 GHz 8Core i9; 32 GB; 1TB; 8GB Radeon 5500M) for scrap.
While these individual steps seem reasonable the overall impression is that no one in Apple has a clue.
I am ordering a linux laptop. Once it is working I plan to sell my 16 inch 2019 Apple Macbook Pro (2.3 GHz 8Core i9; 32 GB; 1TB; 8GB Radeon 5500M) for scrap.
Sounds like its under warranty. I'd keep complaining or ask for your $ back. Make Apple work for the Apple Care $ (if you have it). However agree that Apple seem to have limited to no idea which is why these threads have been running for over a year. There are similar threads on Apple communities but seems no Apple reps there either and providing feedback does nothing.
There is no suggested fix. It seems likely that all effort is being directed towards the new (AppleARM supporting) version development. I do not expect that the problem will be fixed but it may be that the new release will not be susceptible to this particular form of failure.
Although it is likely a post hoc ergo proptor hoc fallacy, removing Karabiner Elements (cf. here) has made my current setup more stable. I have had no crashes in the past few weeks. But, as I said...
Although it is likely a post hoc ergo proptor hoc fallacy, removing Karabiner Elements (cf. here) has made my current setup more stable. I have had no crashes in the past few weeks. But, as I said...
FYI I think this issue is related to [that] issue
If true then hooray for BS!
[that]: https://forums.macrumors.com/thread...after-unplugging-the-dock-it-crashes.2248336/
If true then hooray for BS!
[that]: https://forums.macrumors.com/thread...after-unplugging-the-dock-it-crashes.2248336/
Last edited:
Having same issue here on a Mac Pro 5,1 running Mac OS Majove, 10.14.16
UUID: BA925359-3715-4C66-8145-88B36F369528
Stackshot Reason: Sleep transition timed out after 180 seconds while entering darkwake on way to sleep. Suspected bundle: com.apple.driver.usb.AppleUSBXHCI. Thread 0x21ac9.
Failure code:: 0x5f838579 00000031
Using an external monitor, nothing connected to USB ports, 4 internal drives only.
Any fix for this?
Kind regards
UUID: BA925359-3715-4C66-8145-88B36F369528
Stackshot Reason: Sleep transition timed out after 180 seconds while entering darkwake on way to sleep. Suspected bundle: com.apple.driver.usb.AppleUSBXHCI. Thread 0x21ac9.
Failure code:: 0x5f838579 00000031
Using an external monitor, nothing connected to USB ports, 4 internal drives only.
Any fix for this?
Kind regards
I have seen this issue twice now on my new M1 MacBook Pro with Big Sur 11.0.1
Both times I have had this issue my MacBook Pro was not falling asleep and I manually told it to sleep. Like when a video is open in a Chrome tab or something and sleep is being ignored. Shortly after sleeping I saw the monitor come back on and my Mac was rebooting.
Both times I have had this issue my MacBook Pro was not falling asleep and I manually told it to sleep. Like when a video is open in a Chrome tab or something and sleep is being ignored. Shortly after sleeping I saw the monitor come back on and my Mac was rebooting.
I asked for help from this thread around September for this recurring issue. The Mac was brand-new so I got online help from Apple support after multiple OS reinstallation. They instructed me to turn off the force sleep mode from General setting, and for the first night, the computer did not restart since my purchase. Later on I noticed that the third-party vendor had a very fine print on their advertising, indicating the one of the elements has been upgraded with a more advanced specs. I also noticed that with the same specification, the Mac I owned could not run a software as my friend’s supposed to be identical Mac did without triggering the fan activated (An application with intensive floating point computation). With this performance inferiority, I decided to return this brand new Mac by sucking in 10% cost penalty. Later on Apple sales guided me how to order an official product on Apple online store. The new Mac came in, and under the manufacturing default settings, the issue reported here only occurred once, over the three weeks the computer was with me. Interesting enough, the official product was able to run the demanding software mentioned above with advanced parameters without fan being triggered. I recalled the Apple online support mentioned to me what was experienced by me was a hardware issue even the machine passed the hardware QC test conducted by local Apple Technical Support. I suspected that the specific elements upgraded may have jeopardized the optimal performance of a highly optimized equipment.
I see this, too, on MacOS 10.15.7 with Mid 2014 MacBook Pro, and thought it was related to using external USB disk connected to one of the USB ports. At least I have seen it overnight only when a USB disk is connected. This happens using different types of USB disks and with and without a USB hub. Since I have not run for days without a USB disk, I cannot be sure. Also this was updated from Mojave and earlier, so cannot be sure something has been left over... However, Mojave has been exceptionally stable with no panics...
As far as I'm concerned the problems started in September. My computer crashes every night while it is unplugged. After analyzing the log files, it is clear that the problem is related to hibernation. I deleted /var/vm/sleepimage thinking it might be corrupted but without success. For the moment the only solution to avoid crashes is to deactivate the hybernation mode via this command: sudo pmset hibernatemode 0
MacBook Pro (Retina, 15-inch, Mid 2014)
Catalina 10.15.7
MD
MacBook Pro (Retina, 15-inch, Mid 2014)
Catalina 10.15.7
MD
Thanks! I will try running with the setting of "hibernatemode 0" which would appear to simply prevent saving memory to the file you indicate. From the manpage for pmset:
hibernatemode = 0 by default on desktops. The system will not back memory up to persistent storage. The
system must wake from the contents of memory; the system will lose context on power loss. This is, his-
torically, plain old sleep.
hibernatemode = 0 by default on desktops. The system will not back memory up to persistent storage. The
system must wake from the contents of memory; the system will lose context on power loss. This is, his-
torically, plain old sleep.
Reading the man page again, it seem that standby and autopoweroff need also to be set to 0 to fully deactivate hibernation.
Whether or not a hibernation image gets written is also dependent on
the values of standby and autopoweroff
For example, on desktops that support standby a hibernation image will be written after the specified standbydelay
time. To disable hibernation images completely, ensure hibernatemode standby and autopoweroff are all set to 0.
Whether or not a hibernation image gets written is also dependent on
the values of standby and autopoweroff
For example, on desktops that support standby a hibernation image will be written after the specified standbydelay
time. To disable hibernation images completely, ensure hibernatemode standby and autopoweroff are all set to 0.
No crash tonight. The output of pmset -g on my mabook pro.
System-wide power settings:
Currently in use:
standbydelaylow 10800
standby 0
halfdim 1
hibernatefile /var/vm/sleepimage
powernap 0
gpuswitch 2
disksleep 10
standbydelayhigh 86400
sleep 1
autopoweroffdelay 259200
hibernatemode 0
autopoweroff 0
ttyskeepawake 1
displaysleep 2
highstandbythreshold 50
acwake 0
lidwake 1
And the 3 commands to turn off completely hibernation :
sudo pmset hibernatemode 0
sudo pmset autopoweroff 0
sudo pmset standby 0
System-wide power settings:
Currently in use:
standbydelaylow 10800
standby 0
halfdim 1
hibernatefile /var/vm/sleepimage
powernap 0
gpuswitch 2
disksleep 10
standbydelayhigh 86400
sleep 1
autopoweroffdelay 259200
hibernatemode 0
autopoweroff 0
ttyskeepawake 1
displaysleep 2
highstandbythreshold 50
acwake 0
lidwake 1
And the 3 commands to turn off completely hibernation :
sudo pmset hibernatemode 0
sudo pmset autopoweroff 0
sudo pmset standby 0