macOS Sonoma 14.3 - sleep/wake problems

[n0scope]

Hi there!
I have running Sonoma. The OS itself is stable and have no problems with running. My main problem is that the sleep / wake does not work. Going to sleep is fine (it take little bit longer than I would anticipate), it stays asleep no problem. The problem is when I try to wake it up, the system reboots.

And second problem, not so significant for me (but would be nice if I could get solved), is that I when I try to boot Windows (11) from OpenCore I will only get black screen. The OS will boot, because I can hear Windows sounds but I only get black screen.

Specs.:
MB: MSI B450 Mortar Max (will update bios version, but fairly new)
CPU: 5800X
GPU: XFX RX6800

OpenCore version 0.9.9.

I would really appreceate any help.
Have a nice day, thanks!

 

[leesurone]

Hi there!
I have running Sonoma. The OS itself is stable and have no problems with running. My main problem is that the sleep / wake does not work. Going to sleep is fine (it take little bit longer than I would anticipate), it stays asleep no problem. The problem is when I try to wake it up, the system reboots.

And second problem, not so significant for me (but would be nice if I could get solved), is that I when I try to boot Windows (11) from OpenCore I will only get black screen. The OS will boot, because I can hear Windows sounds but I only get black screen.

Specs.:
MB: MSI B450 Mortar Max (will update bios version, but fairly new)
CPU: 5800X
GPU: XFX RX6800

OpenCore version 0.9.9.

I would really appreceate any help.
Have a nice day, thanks!

Your USB Port Mapping is the likely culprit that causing your system to reboot instead of waking up. MSI states you have these USB Ports:

AMD® B450 Chipset​

• 1 x USB 3.2 Gen2 (SuperSpeed USB 10Gbps) Type-C port on the back panel
• 1 x USB 3.2 Gen2 (SuperSpeed USB 10Gbps) Type-A port on the back panel
• 2 x USB 3.2 Gen1 (SuperSpeed USB) ports available through the internal USB 3.2 Gen1 connector
• 6 x USB 2.0 (High-speed USB) ports (2 Type-A ports on the back panel, 4 ports available through the internal USB 2.0 connectors) AMD® CPU

AMD® Processor​

• 4 x USB 3.2 Gen1 (SuperSpeed USB) Type-A ports on the back panel

You may not be using them, and that is okay but if you are, the 6 USB 2 ports are unaccounted for or incorrectly set as USB 3. If labeled correctly in your USBMap.kext you also have your WIFI/Bluetooth card set as USB3, being it is an internal port it should be set to 255.
I would spend a little more time with your port mapping but also look at what peripherals you have attached using USB, incorrect mapping is the most likely reason your system acts the way it is.

As far as Windows booting from Opencore if you have an separate drive where it is installed you can use the boards boot menu (press F11) to select that disk to see if that makes a difference. You can also try resetting the NVRAM before trying boot into Windows as well as trying to unplug the display cable once it boots and you can hear windows. Plugging it back in may cause it to reinitialize.

 

[n0scope]

Your USB Port Mapping is the likely culprit that causing your system to reboot instead of waking up. MSI states you have these USB Ports:

AMD® B450 Chipset​

• 1 x USB 3.2 Gen2 (SuperSpeed USB 10Gbps) Type-C port on the back panel
• 1 x USB 3.2 Gen2 (SuperSpeed USB 10Gbps) Type-A port on the back panel
• 2 x USB 3.2 Gen1 (SuperSpeed USB) ports available through the internal USB 3.2 Gen1 connector
• 6 x USB 2.0 (High-speed USB) ports (2 Type-A ports on the back panel, 4 ports available through the internal USB 2.0 connectors) AMD® CPU

AMD® Processor​

• 4 x USB 3.2 Gen1 (SuperSpeed USB) Type-A ports on the back panel

You may not be using them, and that is okay but if you are, the 6 USB 2 ports are unaccounted for or incorrectly set as USB 3. If labeled correctly in your USBMap.kext you also have your WIFI/Bluetooth card set as USB3, being it is an internal port it should be set to 255.
I would spend a little more time with your port mapping but also look at what peripherals you have attached using USB, incorrect mapping is the most likely reason your system acts the way it is.

As far as Windows booting from Opencore if you have an separate drive where it is installed you can use the boards boot menu (press F11) to select that disk to see if that makes a difference. You can also try resetting the NVRAM before trying boot into Windows as well as trying to unplug the display cable once it boots and you can hear windows. Plugging it back in may cause it to reinitialize.

Thanks for the reply, I will look into USB mapping one more time. Now that I thinking the problem could also be caused by USB hubs, where I have connected peripherals. I'll post update when I try.

About the Windows, I did try resetting the NVRAM and it did not help. Also I was booting to Windows by selecting from the board boot menu and it works no problem every time. I will try booting with OpenCore and unplug / plug the monitor as I haven't try that yet.
EDIT: After clearing NVRAM I was able to boot Windows no problem. (Thought I already tried that before... Well it is working now so no complains )

EDIT2: I tried to recreate the USBMap. And I had 2 port wrongly identified as USB3, I changed that but it did not help with the sleep unfortunately.

EDIT3: Ok, I managed to get error message after sleep / reboot and it seems to be something with GPU. Did anyone come across this problem?

panic(cpu 2 caller 0xffffff7f9d79b25e): "[40:0:0][PPLIB] Failed Power Play Resume. Shutting back down. TTL Error Message: {163420927955:[40:0:0] Error PSP: event_id=0x100211 event_info:type=3 hw_id=0 event_specific_tag=0x2 pData=0 data_size=0 [FW] psp_bootloader_load: failed
}{163420999115:[40:0:0] TTL Event source_id=2, event_id=0x900c0401, event_info:type= 3,hw_id=0 : swip_client_id= 6, swip_event_id=5 : (SW_IP_CLIENT_ID__PSP,EVENT__POWER_UP)} --> {163420927955:[40:0:0] Error PSP: event_id=0x100211 event_info:type=3 hw_id=0 event_specific_tag=0x2 pData=0 data_size=0 [FW] psp_bootloader_load: failed
}{163420999115:[40:0:0] TTL Event source_id=2, event_id=0x900c0401, event_info:type= 3,hw_id=0 : swip_client_id= 6, swip_event_id=5 : (SW_IP_CLIENT_ID__PSP,EVENT__POWER_UP)}.
" @AmdRadeonController.cpp:2022
Panicked task 0xffffff99f8e46638: 253 threads: pid 0: kernel_task
Backtrace (CPU 2), panicked thread: 0xffffff952fe76598, Frame : Return Address
0xfffffff3b5193800 : 0xffffff8011036c41 mach_kernel : _handle_debugger_trap + 0x4b1
0xfffffff3b5193850 : 0xffffff80111955c0 mach_kernel : _kdp_i386_trap + 0x110
0xfffffff3b5193890 : 0xffffff8011184d0c mach_kernel : _kernel_trap + 0x55c
0xfffffff3b5193910 : 0xffffff8010fd3971 mach_kernel : _return_from_trap + 0xc1
0xfffffff3b5193930 : 0xffffff8011036f2d mach_kernel : _DebuggerTrapWithState + 0x5d
0xfffffff3b5193a20 : 0xffffff80110365d3 mach_kernel : _panic_trap_to_debugger + 0x1e3
0xfffffff3b5193a80 : 0xffffff80117d8d0b mach_kernel : _panic + 0x84
0xfffffff3b5193b70 : 0xffffff7f9d79b25e com.apple.kext.AMDRadeonX6000Framebuffer : __ZN34AMDRadeonX6000_AmdRadeonController10doGPUPanicEPKcz + 0x1bc
0xfffffff3b5193c80 : 0xffffff7f9d75dc1e com.apple.kext.AMDRadeonX6000Framebuffer : __ZN33AMDRadeonX6000_AmdPowerPlayHelper4wakeEv + 0xc0
0xfffffff3b5193cc0 : 0xffffff7f9d79aa94 com.apple.kext.AMDRadeonX6000Framebuffer : __ZN34AMDRadeonX6000_AmdRadeonController4wakeEv + 0xa4
0xfffffff3b5193cf0 : 0xffffff7f9d77db0f com.apple.kext.AMDRadeonX6000Framebuffer : __ZN35AMDRadeonX6000_AmdRadeonFramebuffer6doWakeEv + 0x5b
0xfffffff3b5193d10 : 0xffffff7f9d77da4b com.apple.kext.AMDRadeonX6000Framebuffer : __ZN35AMDRadeonX6000_AmdRadeonFramebuffer19setSystemPowerStateENS_15AmdFbPowerStateE + 0x1f
0xfffffff3b5193d30 : 0xffffff7f9d77d846 com.apple.kext.AMDRadeonX6000Framebuffer : __ZN35AMDRadeonX6000_AmdRadeonFramebuffer18doPowerStateChangeENS_15AmdFbPowerStateE + 0x46
0xfffffff3b5193d60 : 0xffffff7fa5fb23b0 com.apple.iokit.IOGraphicsFamily : __ZN13IOFramebuffer14checkPowerWorkEj + 0x25e
0xfffffff3b5193df0 : 0xffffff7fa5fb2132 com.apple.iokit.IOGraphicsFamily : __ZN14IOFBController14checkPowerWorkEj + 0x9e
0xfffffff3b5193e20 : 0xffffff7fa5fb931d com.apple.iokit.IOGraphicsFamily : __ZN13IOFramebuffer10systemWorkEP8OSObjectP22IOInterruptEventSourcei + 0x111
0xfffffff3b5193ed0 : 0xffffff801170e90a mach_kernel : __ZN22IOInterruptEventSource12checkForWorkEv + 0x12a
0xfffffff3b5193f20 : 0xffffff801170d12e mach_kernel : __ZN10IOWorkLoop15runEventSourcesEv + 0x13e
0xfffffff3b5193f60 : 0xffffff801170c756 mach_kernel : __ZN10IOWorkLoop10threadMainEv + 0x36
0xfffffff3b5193fa0 : 0xffffff8010fd319e mach_kernel : _call_continuation + 0x2e
      Kernel Extensions in backtrace:
         com.apple.iokit.IOGraphicsFamily(598.0)[5E698968-E66C-372A-9AE4-99934BAF7A10]@0xffffff7fa5fa6000->0xffffff7fa5fd4fff
            dependency: com.apple.iokit.IOPCIFamily(2.9)[1B194276-D13F-32DD-8B6D-4751C1C73603]@0xffffff8013355000->0xffffff8013386fff
         com.apple.kext.AMDRadeonX6000Framebuffer(5.0.2)[42A3E9E7-E310-390D-86FA-D797E874DCDA]@0xffffff7f9d74d000->0xffffff7f9d9d5fff
            dependency: com.apple.AppleGraphicsDeviceControl(8.1.9)[D0372C4D-E33E-3899-9EA0-67FA180354E8]@0xffffff7fa544d000->0xffffff7fa5450fff
            dependency: com.apple.iokit.IOACPIFamily(1.4)[04DDFFBA-0499-3590-B6C5-C40851E28B4F]@0xffffff8012ee7000->0xffffff8012ee8fff
            dependency: com.apple.iokit.IOGraphicsFamily(598)[5E698968-E66C-372A-9AE4-99934BAF7A10]@0xffffff7fa5fa6000->0xffffff7fa5fd4fff
            dependency: com.apple.iokit.IOPCIFamily(2.9)[1B194276-D13F-32DD-8B6D-4751C1C73603]@0xffffff8013355000->0xffffff8013386fff

Process name corresponding to current thread (0xffffff952fe76598): kernel_task
Boot args: agdpmod=pikera keepsyms=1 swd_panic=1

Mac OS version:
23D56

Kernel version:
Darwin Kernel Version 23.3.0: Wed Dec 20 21:28:58 PST 2023; root:xnu-10002.81.5~7/RELEASE_X86_64
Kernel UUID: 8C96896D-43A3-3BF0-8F4C-4118DA6AC9AA
roots installed: 0
KernelCache slide: 0x0000000010c00000
KernelCache base:  0xffffff8010e00000
Kernel slide:      0x0000000010ce0000
Kernel text base:  0xffffff8010ee0000
__HIB  text base: 0xffffff8010d00000
System model name: MacPro7,1 (Mac-27AD2F918AE68F61)
System shutdown begun: NO
Panic diags file available: YES (0x0)
Hibernation exit count: 0

System uptime in nanoseconds: 167456693419
Last Sleep:           absolute           base_tsc          base_nano
  Uptime  : 0x00000026fd325f3f
  Sleep   : 0x00000024cc3fb848 0x0000000c3863e300 0x0000000000000000
  Wake    : 0x00000024deb57180 0x00000001172249de 0x00000024de3ca7f2
Compressor Info: 0% of compressed pages limit (OK) and 0% of segments limit (OK) with 0 swapfiles and OK swap space
Zone info:
  Zone map: 0xffffff805e80d000 - 0xffffffa05e80d000
  . PGZ   : 0xffffff805e80d000 - 0xffffff806280e000
  . VM    : 0xffffff806280e000 - 0xffffff852eb41000
  . RO    : 0xffffff852eb41000 - 0xffffff86c81a7000
  . GEN0  : 0xffffff86c81a7000 - 0xffffff8b944da000
  . GEN1  : 0xffffff8b944da000 - 0xffffff906080d000
  . GEN2  : 0xffffff906080d000 - 0xffffff952cb40000
  . GEN3  : 0xffffff952cb40000 - 0xffffff99f8e73000
  . DATA  : 0xffffff99f8e73000 - 0xffffffa05e80d000
  Metadata: 0xffffffa06081d000 - 0xffffffa08081d000
  Bitmaps : 0xffffffa08081d000 - 0xffffffa08681d000
  Extra   : 0 - 0

EDIT4: Turns out, that disabling RE-SIZE Bar in BIOS fixed the sleep issue. Is there anything I can try? For now I leave the re-size bar disabled but would be nice if it was possible to turn on as I game from time to time on windows.

Thanks for suggestions.