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

vett93

macrumors 6502
Original poster
Jul 27, 2014
279
40
California
I got up this morning and found my MP rebooted itself over night in sleep mode. I put it in sleep mode before going to bed last night. Can someone please take at the below error message and explain what caused the crash?

panic(cpu 0 caller 0xffffff80023d51f7): "AMDFramebufferSI::setPowerState(0xffffff93c5e7a800 : 0xffffff7f9cb4dc1c, 1 -> 0) timed out after 45984 ms"@/System/Volumes/Data/SWE/macOS/BuildRoots/d7e177bcf5/Library/Caches/com.apple.xbs/Sources/xnu/xnu-7195.141.2/iokit/Kernel/IOServicePM.cpp:5382
Backtrace (CPU 0), Frame : Return Address
0xffffffc1abd63ac0 : 0xffffff8001c8e04d
0xffffffc1abd63b10 : 0xffffff8001dd4e13
0xffffffc1abd63b50 : 0xffffff8001dc540a
0xffffffc1abd63ba0 : 0xffffff8001c32a2f
0xffffffc1abd63bc0 : 0xffffff8001c8d86d
0xffffffc1abd63ce0 : 0xffffff8001c8db63
0xffffffc1abd63d50 : 0xffffff800249dc0a
0xffffffc1abd63dc0 : 0xffffff80023d51f7
0xffffffc1abd63e10 : 0xffffff80023d4b19
0xffffffc1abd63e20 : 0xffffff80023edc5e
0xffffffc1abd63e60 : 0xffffff80023d3898
0xffffffc1abd63e80 : 0xffffff8001cd4605
0xffffffc1abd63ef0 : 0xffffff8001cd5574
0xffffffc1abd63fa0 : 0xffffff8001c3213e

Process name corresponding to current thread: kernel_task

Mac OS version:
20G95

Kernel version:
Darwin Kernel Version 20.6.0: Wed Jun 23 00:26:31 PDT 2021; root:xnu-7195.141.2~5/RELEASE_X86_64
Kernel UUID: FECBF22B-FBBE-36DE-9664-F12A7DD41D3D
KernelCache slide: 0x0000000001a00000
KernelCache base: 0xffffff8001c00000
Kernel slide: 0x0000000001a10000
Kernel text base: 0xffffff8001c10000
__HIB text base: 0xffffff8001b00000
System model name: MacPro6,1 (Mac-F60DEB81FF30ACF6)
System shutdown begun: NO
Panic diags file available: YES (0x0)
Hibernation exit count: 0

System uptime in nanoseconds: 111732622539289
Last Sleep: absolute base_tsc base_nano
Uptime : 0x0000659ec746c68b
Sleep : 0x00006571da4120d8 0x0000000054e71744 0x000061e1915f8834
Wake : 0x00006571eb402126 0x0000000053c058de 0x00006571e8287146
last started kext at 32178590215: >!AActuatorDriver 4440.3 (addr 0xffffff8002dd1000, size 28672)
loaded kexts:
>!ATopCaseHIDEventDriver 4050.1
@filesystems.autofs 3.0
@fileutil 20.036.15
>AudioAUUC 1.70
>!APlatformEnabler 2.7.0d0
>!AUpstreamUserClient 3.6.8
>!AMCCSControl 1.14
>AGPM 122.1
>X86PlatformShim 1.0.0
@kext.AMDFramebuffer 4.0.6
@kext.AMDRadeonX4000 4.0.6
@kext.AMDRadeonServiceManager 4.0.6
>!AGraphicsDevicePolicy 6.3.5
@AGDCPluginDisplayMetrics 6.3.5
>pmtelemetry 1
|IOUserEthernet 1.0.1
>usb.!UUserHCI 1
>!AHDAHardwareConfigDriver 283.15
|IO!BSerialManager 8.0.5d7
>!AHDA 283.15
@Dont_Steal_Mac_OS_X 7.0.0
>!AHV 1
>!ADiskImages2 1
>eficheck 1
>ACPI_SMC_PlatformPlugin 1.0.0
>!A!ISlowAdaptiveClocking 4.0.0
>!ALPC 3.1
>!AThunderboltIP 4.0.3
@kext.AMD7000!C 4.0.6
>!AFIVRDriver 4.1.0
>!A!IMCEReporter 115
>!AMGPUPowerControl 6.3.5
|IO!BUSBDFU 8.0.5d7
|SCSITaskUserClient 436.140.1
>!AFileSystemDriver 3.0.1
@filesystems.tmpfs 1
@filesystems.hfs.kext 556.100.11
@BootCache 40
@!AFSCompression.!AFSCompressionTypeZlib 1.0.0
@!AFSCompression.!AFSCompressionTypeDataless 1.0.0d1
@filesystems.apfs 1677.141.1
>AirPort.BrcmNIC 1400.1.1
>!AAHCIPort 346.100.2
|!ABCM5701Ethernet 11.0.0
@private.KextAudit 1.0
>!AACPIEC 6.1
>!ARTC 2.0
>!AACPIButtons 6.1
>!AHPET 1.8
>!ASMBIOS 2.1
>!AAPIC 1.7
>!A!ICPUPowerManagementClient 222.0.0
@!ASystemPolicy 2.0.0
@nke.applicationfirewall 311
|IOKitRegistryCompatibility 1
|EndpointSecurity 1
>!A!ICPUPowerManagement 222.0.0
>!AActuatorDriver 4440.3
>!AMultitouchDriver 4440.3
>!AInputDeviceSupport 4400.35
>!AHS!BDriver 4050.1
>IO!BHIDDriver 8.0.5d7
@plugin.IOAVBDiscoveryPlugin 940.4
@kext.triggers 1.0
>!ASMBus!C 1.0.18d1
@kext.AMDRadeonX4030HWLibs 1.0
|IOAccelerator!F2 442.9
@kext.AMDRadeonX4000HWServices 4.0.6
|IOSerial!F 11
|IOAVB!F 940.4
|IOEthernetAVB!C 1.1.0
>DspFuncLib 283.15
@kext.OSvKernDSPLib 529
@!AGPUWrangler 6.3.5
>IOPlatformPluginLegacy 1.0.0
|IOSlowAdaptiveClocking!F 1.0.0
>X86PlatformPlugin 1.0.0
>IOPlatformPlugin!F 6.0.0d8
@plugin.IOgPTPPlugin 985.2
>!UAudio 405.39
>!ASMBusPCI 1.0.14d1
@kext.AMDSupport 4.0.6
@!AGraphicsDeviceControl 6.3.5
>!AHDA!C 283.15
|IOHDA!F 283.15
|IOAudio!F 300.6.1
@vecLib.kext 1.2.0
>!AThunderboltEDMSink 5.0.3
>!AThunderboltDPOutAdapter 8.1.4
>!AGraphicsControl 6.3.5
>!ABacklightExpert 1.1.0
|IONDRVSupport 585.1
|IOGraphics!F 585.1
|Broadcom!BHost!CUSBTransport 8.0.5d7
|IO!BHost!CUSBTransport 8.0.5d7
|IO!BHost!CTransport 8.0.5d7
>usb.IOUSBHostHIDDevice 1.2
>usb.cdc 5.0.0
>usb.networking 5.0.0
>usb.!UHostCompositeDevice 1.2
>usb.!UHub 1.2
>!AThunderboltDPInAdapter 8.1.4
>!AThunderboltDPAdapter!F 8.1.4
>!AThunderboltPCIDownAdapter 4.1.1
>!ABSDKextStarter 3
|IOSurface 290.8.1
@filesystems.hfs.encodings.kext 1
>!AXsanScheme 3
>!AThunderboltNHI 7.2.8
|IOThunderbolt!F 9.3.2
>usb.!UHostPacketFilter 1.0
>usb.!UXHCIPCI 1.2
>usb.!UXHCI 1.2
|IONVMe!F 2.1.0
|IO80211!F 1200.12.2b1
|IOSkywalk!F 1
>corecapture 1.0.4
|IOUSB!F 900.4.2
|IOAHCI!F 294.100.1
>mDNSOffloadUserClient 1.0.1b8
>usb.!UEHCIPCI 1.2
>usb.!UEHCI 1.2
>!AEFINVRAM 2.1
>!AEFIRuntime 2.1
|IOSMBus!F 1.1
|IOHID!F 2.0.0
$!AImage4 3.0.0
|IOTimeSync!F 985.2
|IONetworking!F 3.4
>DiskImages 493.0.0
|IO!B!F 8.0.5d7
|IOReport!F 47
|IO!BPacketLogger 8.0.5d7
$quarantine 4
$sandbox 300.0
@Kext.!AMatch 1.0.0d1
|CoreAnalytics!F 1
>!ASSE 1.0
>!AKeyStore 2
>!UTDM 511.141.1
|IOUSBMass!SDriver 184.140.2
|IOSCSIBlockCommandsDevice 436.140.1
|IO!S!F 2.1
|IOSCSIArchitectureModel!F 436.140.1
>!AMobileFileIntegrity 1.0.5
@kext.CoreTrust 1
>!AFDEKeyStore 28.30
>!AEffaceable!S 1.0
>!ACredentialManager 1.0
>KernelRelayHost 1
|IOUSBHost!F 1.2
>!UHostMergeProperties 1.2
>usb.!UCommon 1.0
>!ABusPower!C 1.0
>!ASEPManager 1.0.1
>IOSlaveProcessor 1
>!AACPIPlatform 6.1
>!ASMC 3.1.9
|IOPCI!F 2.9
|IOACPI!F 1.4
>watchdog 1
@kec.pthread 1
@kec.corecrypto 11.1
@kec.Libm 1
 

now i see it

macrumors G4
Jan 2, 2002
11,252
24,272
No need to read the logs. Historically. Sleep has been unreliable on the Mac forever. On some machines it works pretty good, on others its a time bomb. I'm always surprised when it works and the computer doesn't crash. (MacBook).
My motto with Mac Sleep is: only use it if you don't care if it crashes.
If you're working on an important project, never use it ever. Save your files and shut down at the end of each day
 
  • Like
Reactions: DrMickeyLauer

th0masp

macrumors 6502a
Mar 16, 2015
851
517
Not my experience at all across 7-8 Macs spanning about 16 years. Zero sleep issues here - ever. Same for the PC btw. - I never shut anything down like in the old days.
 

KeesMacPro

macrumors 65816
Nov 7, 2019
1,453
596
Sleep has been unreliable on the Mac forever. On some machines it works pretty good, on others its a time bomb.
Are you sure about that?
IMHO and based on experience for more than 2 decades with several (different) Mac devices , I'd say something is definitely wrong when wake/sleep issues occur.
 

tsialex

Contributor
Jun 13, 2016
13,455
13,601
Did you ever checked the build date of your Mac Pro? If it's one manufactured more than 5 or 6 years ago, the RTC battery probably needs to be replaced. If the BR2032C RTC battery is below 2.95V, the RTC time counters start to become stuck and this is a KP magnet when waking from sleep.

If you run coconutbattery, it will show the first day of the week that your Mac was built based on the serial number decoding, for the real build date you need to dump the BootROM and check the MLB sector.
 
  • Like
Reactions: mikas and vett93

vett93

macrumors 6502
Original poster
Jul 27, 2014
279
40
California
Did you ever checked the build date of your Mac Pro? If it's one manufactured more than 5 or 6 years ago, the RTC battery probably needs to be replaced. If the BR2032C RTC battery is below 2.95V, the RTC time counters start to become stuck and this is a KP magnet when waking from sleep.

If you run coconutbattery, it will show the first day of the week that your Mac was built based on the serial number decoding, for the real build date you need to dump the BootROM and check the MLB sector.
I am pretty sure that my MP is more than 6 years old. I bought it in early 2014!

I checked battery replacement on ifixit. It is a 31 step process!! I don't think I am handy enough to take it apart like the instructions: Mac Pro Late 2013 CMOS Battery Replacement - iFixit Repair Guide
 

MisterAndrew

macrumors 68030
Sep 15, 2015
2,895
2,390
Portland, Ore.
It should be moderately safe to replace the CMOS battery in the 6,1 because it doesn't involve separating the CPU riser card from the thermal core. I think that's really the only dangerous part to work with, besides not routing ribbon cables correctly and kinking them. The best option is to take it to the Apple store and have them do it (if that's what they determine the problem is.)
 
  • Like
Reactions: mikas

vett93

macrumors 6502
Original poster
Jul 27, 2014
279
40
California
It should be moderately safe to replace the CMOS battery in the 6,1 because it doesn't involve separating the CPU riser card from the thermal core. I think that's really the only dangerous part to work with, besides not routing ribbon cables correctly and kinking them. The best option is to take it to the Apple store and have them do it (if that's what they determine the problem is.)

I think you are right. I just replaced the CMOS battery in my 6,1. It is indeed doable.
 
  • Like
Reactions: mikas

mikas

macrumors 6502a
Sep 14, 2017
898
648
Finland
My 6,1 crashed a lot at first, I bought it maybe a year ago.
I am experiencing good uptimes now without sleeping my main 6,1. Earlier I did put it to sleep, and it crashed a lot. I've got an eGPU setup, and my eGPU doesn't like sleeps either, so I am going to go without sleep anyways.

I am gonna change those old RTC batteries as soon as I next time get in to any of my macs (=when i've got spare time enough). I've got some BR2032 now, instead of CR2032.
 

tsialex

Contributor
Jun 13, 2016
13,455
13,601
My 6,1 crashed a lot at first, I bought it maybe a year ago.
I am experiencing good uptimes now without sleeping my main 6,1. Earlier I did put it to sleep, and it crashed a lot. I've got an eGPU setup, and my eGPU doesn't like sleeps either, so I am going to go without sleep anyways.

I am gonna change those old RTC batteries as soon as I next time get in to any of my macs (=when i've got spare time enough). I've got some BR2032 now, instead of CR2032.
I have a hunch that it's not always the graphic subsystem that causes all the reported crashes of MP6,1 here on MR, I've always been curious about the percentage of the MP6,1 crashes that are caused by the RTC battery being dead or dying.
 
  • Like
Reactions: mikas

mikas

macrumors 6502a
Sep 14, 2017
898
648
Finland
Thanks Alex, I have grabbed that exact information from your posts, and will report about that later on.
 

vett93

macrumors 6502
Original poster
Jul 27, 2014
279
40
California
I have a hunch that it's not always the graphic subsystem that causes all the reported crashes of MP6,1 here on MR, I've always been curious about the percentage of the MP6,1 crashes that are caused by the RTC battery being dead or dying.

Another source that may cause MP6,1 to eject USB drives/devices is USB 3.2 device. USB 3.2 devices can draw more currents than MP6,1 USB 3.0 ports were designed to deliver. After replacing the CMOS battery and using USB 3.2 drives with their external power adapters, my MP6,1 has been very stable!

However, I am jumping ship to Windows machines and just bought a high-end prebuilt gaming PC. It is as quiet as my MP6,1. (and as expensive too!) But I need Nvidia GPU for my deep learning software development these days. Apple's M1 GPU and AMD GPU are not suitable for it.

I want to take the moment to thank Alex for the extended support over the years. I bought this MP6,1 when it first came out. Now it has been more stable than ever before. The support from Alex and others on this forum have been very helpful!
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.