CaseySJ
Moderator
- Joined
- Nov 11, 2018
- Messages
- 22,222
- Motherboard
- Asus ProArt Z690-Creator
- CPU
- i7-12700K
- Graphics
- RX 6800 XT
- Mac
- Classic Mac
- Mobile Phone
Disabling the Thunderbolt controller in BIOS did not help, unfortunately.Could you try sleep/wake with Thunderbolt controller off from BIOS?
I compared the detailed system log immediate after wake-from-sleep between:
- X570 Taichi with AMD Ryzen 9 3900X
- B550 Vision D with AMD Ryzen 7 3700X
- Both are running Big Sur Public Beta 3
In this screenshot we see the log messages that start as soon as the system WAKES from sleep. The GOOD log is on the LEFT. The BAD log on the right. In the yellow box we see the transition from SLEEP_STATE to ON_STATE. So this means that the B550 Vision D is indeed waking up.
MacOS starts the wake process. But immediately we see a possible problem with SMCAMDProcessor.kext on the right. There is no mention of this in the X570 boot log.
Suspicion #1: Does SMCAMDProcessor.kext need to be modified to fully support B550? UPDATE: This board appears to have IT8795E chips, which is supported by VirtualSMC. Additionally, running the system without SMCAMDProcessor.kext still allows the system to sleep, but not to wake.
In the next screenshot we see additional issues on the B550 Vision D that do not appear in the wake log from X570:
- There's a flood of mDNSResponder notifications. It seems that WiFi could not be re-enabled.
- All of the USB 2.0 ports (PO9, PO10, PO11) have a "timeout". There are no such logs for USB 3.0 ports.
- In the X570 wake log, there is no mention of "AppleUSB20XHCI", which means no issue at all with USB 2 ports.
Moving along, we see more clear evidence of WiFi reactivation failure. On the left (X570 Taichi) we see that WiFi has resumed properly, but none of those logs appear in the B550 wake log.
Suspicion #2b: WiFi does not resume on the B550 Vision D. Again, there could be one single root cause that is having multiple downstream consequences.
Finally -- and this is particularly damning -- the B550 wake log has over 10,000 lines of zone_map_exhausted. But the X570 wake log has ZERO such logs!
Suspicion #3: These may also be a domino effect from some initial problem.
Last edited: