Shutdown issue w/ asrock x399 Taichi

pkv

New member
Joined
Nov 14, 2021
Messages
10
Hi,
I'm booting successfully w/ opencore 8.0 , monterey 12.3.1. Everything is working, ethernet, wifi, bluetooth, audio, sleep except shutdown.
I've remapped USB w/ CorpNewt/USBRemap tool since it now supports AMD.
However I have issues where shutdown takes ages. It doesn't happen at all (I didn't wait longer than 10 minutes though).
So I've attempted to follow the guide here: https://dortania.github.io/OpenCore-Post-Install/usb/misc/shutdown.html
but to no avail.
The issue is that in my DSDT , the 70 entries for _PRW include no mention of any of the USB. There's no PMEE either.
So I can't apply the SSDT for fixing shutdown.
I've disabled HPET in the UEFI as well as restart on shutdown.


My specs:
asrock x399 Taichi
Threadripper 2950x
32 GB RAM
RX 560
MacPro 7,1 opencore 8.0
Monterey 12,3,1
 

Attachments

  • config.plist
    63.3 KB · Views: 1
  • EFI.zip
    32.4 MB · Views: 0

pkv

New member
Joined
Nov 14, 2021
Messages
10
Tried to fix it by adding nvram/7C436110-AB2A-4BBB-A880-FE41995C9F82/wake-failure = 0 as done there : https://forum.amd-osx.com/index.php...rt-at-monterey-booted-by-opencore-0-7-8.2612/
but it didn't work.
I didn't change the smbios though.

Also by waiting sufficiently, it did shutdown but then restarted. After the boot & login, I got this error message : Your computer was restarted because of a problem.
Here's the stacktrace which points to SMC :
panic(cpu 24 caller 0xffffff8011744986): watchdog timeout: no checkins from watchdogd in 304 seconds (5 totalcheckins since monitoring last enabled), shutdown in progress
Panicked task 0xffffff8b7baa4670: 215 threads: pid 0: kernel_task
Backtrace (CPU 24), panicked thread: 0xffffff8b7b568550, Frame : Return Address
0xffffffd0b6d8bb90 : 0xffffff800e283e2d mach_kernel : _handle_debugger_trap + 0x41d
0xffffffd0b6d8bbe0 : 0xffffff800e3e3cb6 mach_kernel : _kdp_i386_trap + 0x116
0xffffffd0b6d8bc20 : 0xffffff800e3d350d mach_kernel : _kernel_trap + 0x51d
0xffffffd0b6d8bc70 : 0xffffff800e223a60 mach_kernel : _return_from_trap + 0xe0
0xffffffd0b6d8bc90 : 0xffffff800e2841fd mach_kernel : _DebuggerTrapWithState + 0xad
0xffffffd0b6d8bdb0 : 0xffffff800e2839b6 mach_kernel : _panic_trap_to_debugger + 0x2b6
0xffffffd0b6d8be10 : 0xffffff800eb16573 mach_kernel : _panic_with_options + 0x89
0xffffffd0b6d8bf00 : 0xffffff8011744986 com.apple.driver.watchdog : __ZN10IOWatchdog14userspacePanicEP8OSObjectPvP25IOExternalMethodArguments.cold.1
0xffffffd0b6d8bf20 : 0xffffff801174428c com.apple.driver.watchdog : __ZN10IOWatchdog13newUserClientEP4taskPvjP12OSDictionaryPP12IOUserClient
0xffffffd0b6d8bf50 : 0xffffff800fa5d265 com.apple.driver.AppleSMC : __ZN16SMCWatchDogTimer14watchdogThreadEv + 0xbb
0xffffffd0b6d8bfa0 : 0xffffff800e22318e mach_kernel : _call_continuation + 0x2e
Kernel Extensions in backtrace:
com.apple.driver.watchdog(1.0)[01A90A91-CE41-37C4-A5C0-BBD735087472]@0xffffff8011742000->0xffffff8011744fff
com.apple.driver.AppleSMC(3.1.9)[EC43C1DD-09AB-36C4-877A-E53C8C34E6AE]@0xffffff800fa4e000->0xffffff800fa66fff
dependency: com.apple.driver.watchdog(1)[01A90A91-CE41-37C4-A5C0-BBD735087472]@0xffffff8011742000->0xffffff8011744fff
dependency: com.apple.iokit.IOACPIFamily(1.4)[CF250EA9-AE5C-3215-BCF5-763DB70A0228]@0xffffff8010960000->0xffffff8010961fff
dependency: com.apple.iokit.IOPCIFamily(2.9)[A436E92C-DE10-3718-AEF4-ED2A788A466A]@0xffffff8010e03000->0xffffff8010e2efff

Process name corresponding to current thread (0xffffff8b7b568550): kernel_task
Boot args: -v keepsyms=1 e1000=0 chunklist-security-epoch=0 -chunklist-no-rev2-dev

Mac OS version:
21E258

Kernel version:
Darwin Kernel Version 21.4.0: Fri Mar 18 00:45:05 PDT 2022; root:xnu-8020.101.4~15/RELEASE_X86_64
Kernel UUID: B6F8637B-0844-355F-8C82-60FA06149384
KernelCache slide: 0x000000000e000000
KernelCache base: 0xffffff800e200000
Kernel slide: 0x000000000e010000
Kernel text base: 0xffffff800e210000
__HIB text base: 0xffffff800e100000
System model name: MacPro7,1 (Mac-27AD2F918AE68F61)
System shutdown begun: YES
Panic diags file available: NO (0xe00002cd)
Hibernation exit count: 0

System uptime in nanoseconds: 341133484699
Last Sleep: absolute base_tsc base_nano
Uptime : 0x0000004f6da5cd76
Sleep : 0x0000000000000000 0x0000000000000000 0x0000000000000000
Wake : 0x0000000000000000 0x00000048ce83fe3e 0x0000000000000000
Compressor Info: 0% of compressed pages limit (OK) and 0% of segments limit (OK) with 0 swapfiles and OK swap space
Zone info:
Foreign : 0xffffff80170fe000 - 0xffffff801710c000
Native : 0xffffff804885d000 - 0xffffffa04885d000
Readonly: 0xffffff8515529000 - 0xffffff86aeec2000
Metadata: 0xfffffff7cddd5000 - 0xfffffff7ee0ed000
Bitmaps : 0xfffffff7ee0ed000 - 0xfffffff7fa0ed000
 

pkv

New member
Joined
Nov 14, 2021
Messages
10
I withdraw my claim it is fixed.
Things have improved because sometimes it shuts down fine; but from time to time it again locks up at shutdown while waiting for something to be released.
:unsure:
 

Edhawk

Active member
Joined
May 2, 2020
Messages
691
You motherboard has 2 x USB2 internal headers, each can provide 2 x USB2 ports. It is likely that the Bluetooth connection accounts one of the headers, as the BT header connector takes up the full space of the header.

That leaves 1 x USB2 header available, are you connecting any Case front ports to this header? If yes, then they also need to be set as 'Internal'. Specifically look at Ports Top3-USB2 and Top4-USB2. You have them set as USB2, that might be the issue, if they are served from the other USB2 header on the motherboard.

The USB2 headers are highlighted below.

X399 Taichi(L2).pngASRock >X399 Taichi motherboard - USB2 headers highlighted

Rear I/O ports are numbered as shown below.
X399 Taichi(L5).png Rear I/O plate for ASRock >X399 Taichi motherboard,

USB ports numbered to match your Hackintool image, just for clarity.
 
  • Like
Reactions: pkv

pkv

New member
Joined
Nov 14, 2021
Messages
10
You motherboard has 2 x USB2 internal headers, each can provide 2 x USB2 ports. It is likely that the Bluetooth connection accounts one of the headers, as the BT header connector takes up the full space of the header.

That leaves 1 x USB2 header available, are you connecting any Case front ports to this header? If yes, then they also need to be set as 'Internal'. Specifically look at Ports Top3-USB2 and Top4-USB2. You have them set as USB2, that might be the issue, if they are served from the other USB2 header on the motherboard.

The USB2 headers are highlighted below.

View attachment 5896ASRock >X399 Taichi motherboard - USB2 headers highlighted

@Edhawk good guess :) i use indeed the left usb 2 header for TOP3-USB2 & TOP4-USB2. The other USB2 header is unused though.
Changed them to Internal (type 255) ==> no change. :cry:
I tried disabling these two ports, but it didn't work either.

TOP1 & TOP2 are USB3 and come from a USB3 header. Should they be changed to internal too ?

I'm puzzled by the fact that in hackintool:
  • TOP4 (usb2)
  • TOP1 + TOP2 (usb3)
  • R9 (usb C)
  • R1 & R2 (usb3 but usb2 personalities)
are marked in green as active although there's no device connected.

Could the shutdown hanging be caused by one of these not being released ? I'm not seeing any port info in the backtrace.
 

Edhawk

Active member
Joined
May 2, 2020
Messages
691
There are 2 x USB3 headers on your motherboard, any ports served from these headers should be set as USB3, not as internal. So no you don’t need to change the 4 x ports designated Top1 and Top2.

If you are only using one of the two USB2 header connectors how is the Bluetooth device connected, via an external port? You have HS09 through which the BT is connected, set as internal, which port is this if not a header port?

if you have ports show as active but you aren’t connecting anything to these ports, then they may be the cause of your issues. I have not come across this issue, where ports show as active but aren’t activated by the insertion of a pen drive. Try disabling those ports, see if that changes how your system behaves.
 

pkv

New member
Joined
Nov 14, 2021
Messages
10
If you are only using one of the two USB2 header connectors how is the Bluetooth device connected, via an external port? You have HS09 through which the BT is connected, set as internal, which port is this if not a header port?
it's an Intel 3168 nvme https://ark.intel.com/content/www/us/en/ark/products/94854/intel-dual-band-wirelessac-3168.html
if I trust Anandtech review of the board https://www.anandtech.com/show/13137/the-asrock-x399-taichi-motherboard-review/3
It ensures both wifi ac + BT.
The intel spec does say that it relies on PCIE for the wifi and USB for BT.
The BT is through the PTCP chipset XHCI USB controller, which I assume is interconnected to the nvme 2230 port.
if you have ports show as active but you aren’t connecting anything to these ports, then they may be the cause of your issues. I have not come across this issue, where ports show as active but aren’t activated by the insertion of a pen drive. Try disabling those ports, see if that changes how your system behaves.
I tried disabling all of these.
Didn't work.

I find it odd that the DSDT doesn't have the entries needed to apply the shutdown patch from https://dortania.github.io/OpenCore-Post-Install/usb/misc/shutdown.html

I didn't have such issues on Catalina which I was running before the upgrade to Monterey. This is disheartening. Anyway it's not a major hassle, I'm still lucky the board works.
 

Edhawk

Active member
Joined
May 2, 2020
Messages
691
OK, your WiFi/BT card are connected via an M.2 slot on the motherboard. The M.2 slot has a USB2 port associated with it for the BT module to work. That is normal for a modern motherboard. I assumed the BT module was part of an Apple/Broadcom WiFi/BT card, with the BT module connected via one of the USB2 headers. So the BT module is fine.

Are the the Top3 and Top4 ports connected to a USB2 header?

You need to remember that you are using an Operating System from a 'closed environment' on a non-Apple system. So the DSDT.aml will only be configured to work with standard compatible OS's such as Windows and Linux. The Bios/DSDT.aml manufacturers won't have taken the board being used on macOS in to consideration when undertaking their work. So naturally there are going to be issues when using macOS on a non-Apple system.

Apple made some significant changes when they released Monterey, specifically with regards the Ethernet controllers and Bluetooth configuration. This was a major issue for a number of people when Monterey was initially released. The only system I own that uses an Intel WiFi/BT card is an old Skylake laptop. The BT still doesn't work correctly in Monterey on this laptop, so I installed Big Sur to another APFS Volume in order that I have working BT.
 

pkv

New member
Joined
Nov 14, 2021
Messages
10
Thanks a lot @Edhawk for all your input regarding my issue. Your knowledge is really impressive. I'll leave the issue aside for now. But i really appreciated your help. 👍
 
Top Bottom