Contribute
Register

Gigabyte Z490 Vision D (Thunderbolt 3) + i5-10400 + AMD RX 580

I use the headless mode for the iGPU, but the video signal goes from the 6800XT to the motherboard passthrough then out from the TB port into my Caldigit dock.
Please try this experiment:
  • Disable Thunderbolt SSDT by unchecking the ‘Enable’ box. The SSDT is primarily used for hot plug, which is not strictly necessary.
  • Connect GPU to DP-In as before, and connect monitor to one of the Thunderbolt ports.
  • Boot the system. Does it still crash shortly after logging in?
 
Please try this experiment:
  • Disable Thunderbolt SSDT by unchecking the ‘Enable’ box. The SSDT is primarily used for hot plug, which is not strictly necessary.
  • Connect GPU to DP-In as before, and connect monitor to one of the Thunderbolt ports.
  • Boot the system. Does it still crash shortly after logging in?
So close, but yes, it crashes immediately after logging in? Would it be possible to use the older SSDT from Z390? I doubt that is possible, but I am desperate to get my Thunderbolt port to work. Works fine in my Windows, so I am suspecting it's some sort of conflict with macOS Beta 4.
 
So close, but yes, it crashes immediately after logging in? Would it be possible to use the older SSDT from Z390? I doubt that is possible, but I am desperate to get my Thunderbolt port to work. Works fine in my Windows, so I am suspecting it's some sort of conflict with macOS Beta 4.
Does it crash with other Thunderbolt devices ?
What’s connected to the dock? Does it crash if just the dock (without any attached peripherals) is connected?
Can be something attached to the dock is causing the issue?
 
Does it crash with other Thunderbolt devices ?
What’s connected to the dock? Does it crash if just the dock (without any attached peripherals) is connected?
Can be something attached to the dock is causing the issue?
Yes, as soon as anything Thunderbolt is connected, it kernel panics. I just tried with just dock with nothing attached. Still freezes and restarts. I am not sure if it's hardware related as everything works fine on the Windows side.

One more thing: My screen never goes to sleep either. I am about to do a complete reinstall. Not sure if that is going to fix anything, but may be worth a try. Has anyone had any issue with Thunderbolt on this board? I had no issues with Z390.

Here's the crash report:

panic(cpu 2 caller 0xffffff8007c9f846): [iokit.OSNumber]: element modified after free (off:0, val:0x1400ffffffffffff, sz:40, ptr:0xffffff87090a3000, prot:zero)
0: 0x1400ffffffffffff
8: 0x0045000860b200ee
16: 0x1140004045843100
24: 0xa8c01e01a8c00932
32: 0x1d009c7eb3a6ff01
Backtrace (CPU 2), Frame : Return Address
0xffffffa19cd53540 : 0xffffff800748e0dd mach_kernel : _handle_debugger_trap + 0x3fd
0xffffffa19cd53590 : 0xffffff80075d4f33 mach_kernel : _kdp_i386_trap + 0x143
0xffffffa19cd535d0 : 0xffffff80075c552a mach_kernel : _kernel_trap + 0x55a
0xffffffa19cd53620 : 0xffffff8007432a2f mach_kernel : _return_from_trap + 0xff
0xffffffa19cd53640 : 0xffffff800748d8fd mach_kernel : _DebuggerTrapWithState + 0xad
0xffffffa19cd53760 : 0xffffff800748dbf3 mach_kernel : _panic_trap_to_debugger + 0x273
0xffffffa19cd537d0 : 0xffffff8007c9d81a mach_kernel : _panic + 0x54
0xffffffa19cd53840 : 0xffffff8007c9f846 mach_kernel : _kheap_temp_leak_panic + 0x1b7c
0xffffffa19cd53cc0 : 0xffffff80074ecad6 mach_kernel : _work_interval_port_type_render_server + 0x4446
0xffffffa19cd53d30 : 0xffffff8007b772f1 mach_kernel : __ZNK8OSNumber9MetaClass5allocEv + 0x21
0xffffffa19cd53d40 : 0xffffff8007b77654 mach_kernel : __ZN8OSNumber10withNumberEyj + 0x24
0xffffffa19cd53d70 : 0xffffff800b30e0f6 ru.joedm.SMCSuperIO : __ZN10SMCSuperIO15quickRescheduleEv + 0x386
0xffffffa19cd53dc0 : 0xffffff800b30d876 ru.joedm.SMCSuperIO : __ZN10SMCSuperIO12detectDeviceEv + 0x2266
0xffffffa19cd53de0 : 0xffffff8007bf4465 mach_kernel : __ZN18IOTimerEventSource15timeoutSignaledEPvS0_ + 0xa5
0xffffffa19cd53e50 : 0xffffff8007bf4366 mach_kernel : __ZN18IOTimerEventSource17timeoutAndReleaseEPvS0_ + 0xc6
0xffffffa19cd53e80 : 0xffffff80074d46c5 mach_kernel : _thread_call_delayed_timer + 0x4a5
0xffffffa19cd53ef0 : 0xffffff80074d5634 mach_kernel : _thread_call_delayed_timer + 0x1414
0xffffffa19cd53fa0 : 0xffffff800743213e mach_kernel : _call_continuation + 0x2e
Kernel Extensions in backtrace:
ru.joedm.SMCSuperIO(1.2.3)[90895019-DB93-3E6C-95A2-E9F0C02915B7]@0xffffff800b308000->0xffffff800b324fff
dependency: as.vit9696.Lilu(1.5.3)[A4C0AB78-C141-3DC5-812F-93408D94A4D7]@0xffffff800b235000->0xffffff800b25ffff
dependency: as.vit9696.VirtualSMC(1.2.3)[72DED745-B559-3CB5-9F88-CD9531E38098]@0xffffff800b263000->0xffffff800b279fff
dependency: com.apple.iokit.IOACPIFamily(1.4)[17374C68-E837-3A87-BC8C-1870E7C0836E]@0xffffff8009a42000->0xffffff8009a43fff

Process name corresponding to current thread: kernel_task
Boot args: keepsyms=1 dart=0 debug=0x100 agdpmod=pikera alcid=11

Mac OS version:
20F5065a

Kernel version:
Darwin Kernel Version 20.5.0: Tue May 4 22:32:58 PDT 2021; root:xnu-7195.121.3~4/RELEASE_X86_64
Kernel UUID: 54102A61-CD81-3528-AE3A-0853D9358B51
KernelCache slide: 0x0000000007200000
KernelCache base: 0xffffff8007400000
Kernel slide: 0x0000000007210000
Kernel text base: 0xffffff8007410000
__HIB text base: 0xffffff8007300000
System model name: iMac20,2 (Mac-AF89B6D9451A490B)
System shutdown begun: NO
Panic diags file available: YES (0x0)
Hibernation exit count: 0

System uptime in nanoseconds: 6882740026226
Last Sleep: absolute base_tsc base_nano
Uptime : 0x0000064283464048
Sleep : 0x000005ac2aa827ba 0x0000000190d3c6c4 0x0000050c92f408d8
Wake : 0x000005ac36345625 0x000000019192d8b4 0x000005ac2f4b1d17
 
Yes, as soon as anything Thunderbolt is connected, it kernel panics. I just tried with just dock with nothing attached. Still freezes and restarts. I am not sure if it's hardware related as everything works fine on the Windows side.

One more thing: My screen never goes to sleep either. I am about to do a complete reinstall. Not sure if that is going to fix anything, but may be worth a try. Has anyone had any issue with Thunderbolt on this board? I had no issues with Z390.

Here's the crash report:

panic(cpu 2 caller 0xffffff8007c9f846): [iokit.OSNumber]: element modified after free (off:0, val:0x1400ffffffffffff, sz:40, ptr:0xffffff87090a3000, prot:zero)
0: 0x1400ffffffffffff
8: 0x0045000860b200ee
16: 0x1140004045843100
24: 0xa8c01e01a8c00932
32: 0x1d009c7eb3a6ff01
Backtrace (CPU 2), Frame : Return Address
0xffffffa19cd53540 : 0xffffff800748e0dd mach_kernel : _handle_debugger_trap + 0x3fd
0xffffffa19cd53590 : 0xffffff80075d4f33 mach_kernel : _kdp_i386_trap + 0x143
0xffffffa19cd535d0 : 0xffffff80075c552a mach_kernel : _kernel_trap + 0x55a
0xffffffa19cd53620 : 0xffffff8007432a2f mach_kernel : _return_from_trap + 0xff
0xffffffa19cd53640 : 0xffffff800748d8fd mach_kernel : _DebuggerTrapWithState + 0xad
0xffffffa19cd53760 : 0xffffff800748dbf3 mach_kernel : _panic_trap_to_debugger + 0x273
0xffffffa19cd537d0 : 0xffffff8007c9d81a mach_kernel : _panic + 0x54
0xffffffa19cd53840 : 0xffffff8007c9f846 mach_kernel : _kheap_temp_leak_panic + 0x1b7c
0xffffffa19cd53cc0 : 0xffffff80074ecad6 mach_kernel : _work_interval_port_type_render_server + 0x4446
0xffffffa19cd53d30 : 0xffffff8007b772f1 mach_kernel : __ZNK8OSNumber9MetaClass5allocEv + 0x21
0xffffffa19cd53d40 : 0xffffff8007b77654 mach_kernel : __ZN8OSNumber10withNumberEyj + 0x24
0xffffffa19cd53d70 : 0xffffff800b30e0f6 ru.joedm.SMCSuperIO : __ZN10SMCSuperIO15quickRescheduleEv + 0x386
0xffffffa19cd53dc0 : 0xffffff800b30d876 ru.joedm.SMCSuperIO : __ZN10SMCSuperIO12detectDeviceEv + 0x2266
0xffffffa19cd53de0 : 0xffffff8007bf4465 mach_kernel : __ZN18IOTimerEventSource15timeoutSignaledEPvS0_ + 0xa5
0xffffffa19cd53e50 : 0xffffff8007bf4366 mach_kernel : __ZN18IOTimerEventSource17timeoutAndReleaseEPvS0_ + 0xc6
0xffffffa19cd53e80 : 0xffffff80074d46c5 mach_kernel : _thread_call_delayed_timer + 0x4a5
0xffffffa19cd53ef0 : 0xffffff80074d5634 mach_kernel : _thread_call_delayed_timer + 0x1414
0xffffffa19cd53fa0 : 0xffffff800743213e mach_kernel : _call_continuation + 0x2e
Kernel Extensions in backtrace:
ru.joedm.SMCSuperIO(1.2.3)[90895019-DB93-3E6C-95A2-E9F0C02915B7]@0xffffff800b308000->0xffffff800b324fff
dependency: as.vit9696.Lilu(1.5.3)[A4C0AB78-C141-3DC5-812F-93408D94A4D7]@0xffffff800b235000->0xffffff800b25ffff
dependency: as.vit9696.VirtualSMC(1.2.3)[72DED745-B559-3CB5-9F88-CD9531E38098]@0xffffff800b263000->0xffffff800b279fff
dependency: com.apple.iokit.IOACPIFamily(1.4)[17374C68-E837-3A87-BC8C-1870E7C0836E]@0xffffff8009a42000->0xffffff8009a43fff

Process name corresponding to current thread: kernel_task
Boot args: keepsyms=1 dart=0 debug=0x100 agdpmod=pikera alcid=11

Mac OS version:
20F5065a

Kernel version:
Darwin Kernel Version 20.5.0: Tue May 4 22:32:58 PDT 2021; root:xnu-7195.121.3~4/RELEASE_X86_64
Kernel UUID: 54102A61-CD81-3528-AE3A-0853D9358B51
KernelCache slide: 0x0000000007200000
KernelCache base: 0xffffff8007400000
Kernel slide: 0x0000000007210000
Kernel text base: 0xffffff8007410000
__HIB text base: 0xffffff8007300000
System model name: iMac20,2 (Mac-AF89B6D9451A490B)
System shutdown begun: NO
Panic diags file available: YES (0x0)
Hibernation exit count: 0

System uptime in nanoseconds: 6882740026226
Last Sleep: absolute base_tsc base_nano
Uptime : 0x0000064283464048
Sleep : 0x000005ac2aa827ba 0x0000000190d3c6c4 0x0000050c92f408d8
Wake : 0x000005ac36345625 0x000000019192d8b4 0x000005ac2f4b1d17
Hmm. from your crash log, I wonder if SMCSuperIO.kext might be where the problem lies? Perhaps as an experiment try disabling that kext?

I’ve never had any Thunderbolt problems with the Z490 Vision D. I’ve just had to tweak some of the Thunderbolt BIOS settings, like disabling security, ensuring gpio3 force pwr is enabled, stuff like that. But never any crashes.
 
Managed to get a hold of a Sapphire Nitro+ Vega 64 and can't get my hack to wake from sleep. I'll come back to fans running at full speed and a frozen screen. Occurs on fresh installs of both Catalina and Big Sur. Sleep was working fine beforehand on iGPU, so perhaps a hardware problem with the graphics card?

Attached is the log on reboot.
 

Attachments

  • sleeplog.txt
    3.3 KB · Views: 33
Managed to get a hold of a Sapphire Nitro+ Vega 64 and can't get my hack to wake from sleep. I'll come back to fans running at full speed and a frozen screen. Occurs on fresh installs of both Catalina and Big Sur. Sleep was working fine beforehand on iGPU, so perhaps a hardware problem with the graphics card?

Attached is the log on reboot.
Vega is notorious for this issue. If you visit the Post-Installation —> Graphics forum you will find a pinned guide for creating custom fan and power properties for Vega. That would be the first step to take.
 
Vega is notorious for this issue. If you visit the Post-Installation —> Graphics forum you will find a pinned guide for creating custom fan and power properties for Vega. That would be the first step to take.
Just set up the PP tables and still having the same issue. Seems like the system will lock entirely if left alone for about 5 minutes.
 
Just set up the PP tables and still having the same issue. Seems like the system will lock entirely if left alone for about 5 minutes.
Which version of macOS are you running?

Please try this:
  • Run Activity Monitor from Utilities folder
  • Sort the list by % CPU
  • Leave the system alone and wait 5 minutes for it to crash
  • Take a photo of the Activity Monitor window
  • What are the top 2 or 3 processes?
 
Which version of macOS are you running?

Please try this:
  • Run Activity Monitor from Utilities folder
  • Sort the list by % CPU
  • Leave the system alone and wait 5 minutes for it to crash
  • Take a photo of the Activity Monitor window
  • What are the top 2 or 3 processes?
Well this is kind of odd: before looking at Activity Monitor, I removed agdpmod=pikera as I read this was a Navi-only boot flag. Then I took a look at Activity Monitor and saw mediaanalysisd spiking so I disabled iCloud Photos as well, then did a reboot. Bad idea changing two things at one time, but one of them worked as it seems my system will properly sleep now.
 
Back
Top