Asrock 5700 XT Taichi fails to boot/hangs when a fifth monitor is connected

eri..@..il.com said:

I believe I have found the issue (although need to setup to compile to test). In https://github.com/torvalds/linux/blob/master/drivers/gpu/drm/amd/amdgpu/amdgpu.h, line 187:
#define AMDGPUFB_CONN_LIMIT 4

I believe this should be set to 6 to support the Asrock 5700 XT Taichi, or any other card that is released with more than four ports.

This is still an issue on kernel 5.6.7, Mesa 20.0.5, and llvm 10.0.0; and not just with the ASRock RX 5700XT Taichi. This appears to be across all 5700XT units (I have the MSI Evoke, confirmed issue; an acquaintance has the same issue on a Sapphire? model) (and it could be across the rest of the Navi cards as well- I have no hardware to test that however) and will occur using DisplayPort chaining and/or MST hubs on cards with only 4 ports, and as confirmed by the original bug submitter also occurs when using only 5 of the 6 ports directly on the cards for higher-end variants, with no splitter or hub involved. Card and monitors work as expected under Windows, no issues using 6 displays. This does not appear to be an issue with the GCN cards (tried an RX580 with the exact same setup, same MST hub, etc, and will confirm tests done by someone else with a Vega 56 later this week).

Overall resolution does not seem to matter, with higher resolution setups working fine (1x4K@60hz, 1x1440p@95hz and 2x3160x1080@60hz; all through DP or with any monitor connected the HDMI out) and lower resolution setups still failing as soon as a 5th monitor is connected (5x1080p@60hz;mix of Displayport and HDMI in various configs for testing). Adding a 5th or more monitors results in this issue.

I have not tested these cards with an Intel CPU/Chipset yet, again due to lack of hardware available to me, but seeing as the Ryzen 1700 with an X470 chipset works with 5+ monitors with an RX580 but has this issue with the 5700XT, this seems less likely to matter.

This has been tested by myself across several distros, all 64-bit, including Fedora 31 and 32, Ubuntu 20.04, and Pop_OS (which was a bit older, kernel 5.3 I believe). This issue persisted on both LiveUSB boots, and on installations to a local hard drive that were then booted directly. This issue seems to have been around since Navi support was released, with it still appearing in the distro running the 5.3 kernel.

In 5.6.7, adding a 5th monitor once already booted freezes the display, and CTRL+ALT+F# shortcut does not take you to a new TTY as it should. However, after the freeze that occurswhen plugging in monitor 5, I am still able to ssh into my desktop and get any necessary logs, etc. dmesg seems reporting an issue within the amdgpu driver. I can attach a snippet below

   63.501191] WARNING: CPU: 15 PID: 1864 at drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:6604 amdgpu_dm_atomic_commit_tail+0x216e/0x22f0 [amdgpu]
[   63.501191] Modules linked in: xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_nat_tftp nf_conntrack_tftp tun bridge stp llc nft_objref nf_conntrack_netbios_ns nf_conntrack_broadcast nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject nft_ct nf_tables_set nft_chain_nat nf_tables ebtable_nat ebtable_broute ip6table_nat ip6table_mangle ip6table_raw ip6table_security iptable_nat nf_nat nf_conntrack rfkill nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c iptable_mangle iptable_raw iptable_security ip_set nfnetlink ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter nct6775 hwmon_vid sunrpc squashfs zstd_decompress loop snd_hda_codec_realtek ppdev snd_hda_codec_generic edac_mce_amd ledtrig_audio uvcvideo snd_hda_codec_hdmi videobuf2_vmalloc kvm_amd videobuf2_memops snd_hda_intel videobuf2_v4l2 snd_intel_dspcfg videobuf2_common snd_usb_audio kvm snd_hda_codec snd_hda_core snd_usbmidi_lib snd_rawmidi snd_hwdep snd_seq snd_seq_device
[   63.501207]  irqbypass snd_pcm videodev snd_timer snd crct10dif_pclmul sp5100_tco joydev crc32_pclmul mc soundcore ccp pcspkr ghash_clmulni_intel wmi_bmof i2c_piix4 k10temp parport_pc parport gpio_amdpt gpio_generic vboxnetadp(OE) vboxnetflt(OE) binfmt_misc vboxdrv(OE) ip_tables hid_logitech_hidpp amdgpu amd_iommu_v2 gpu_sched i2c_algo_bit ttm drm_kms_helper drm crc32c_intel uas hid_apple usb_storage r8169 hid_plantronics hid_logitech_dj wmi pinctrl_amd fuse
[   63.501219] CPU: 15 PID: 1864 Comm: gnome-shell Tainted: G        W  OE     5.6.7-300.fc32.x86_64 #1
[   63.501220] Hardware name: Micro-Star International Co., Ltd. MS-7B79/X470 GAMING PLUS (MS-7B79), BIOS A.G0 11/11/2019
[   63.501280] RIP: 0010:amdgpu_dm_atomic_commit_tail+0x216e/0x22f0 [amdgpu]
[   63.501281] Code: ff ff 41 8b 4c 24 60 48 c7 c2 a0 21 ac c0 bf 02 00 00 00 48 c7 c6 a8 a1 b3 c0 e8 3d 5e d5 ff 4d 8b 57 08 e9 0d e0 ff ff 0f 0b <0f> 0b e9 54 ef ff ff 0f 0b e9 6c ef ff ff 48 8b 85 98 fd ff ff 48
[   63.501282] RSP: 0018:ffffb056c246f9b0 EFLAGS: 00010002
[   63.501283] RAX: 0000000000000002 RBX: 0000000000000c47 RCX: ffff966fe8e95970
[   63.501283] RDX: 0000000000000001 RSI: 0000000000000202 RDI: ffff966ffa883158
[   63.501284] RBP: ffffb056c246fc70 R08: ffffb056c246f90c R09: 0000000000000000
[   63.501284] R10: ffffb056c246f938 R11: ffffb056c246f93c R12: 0000000000000202
[   63.501284] R13: ffff966f8ef89900 R14: ffff966fe8e95800 R15: ffff966feeb28400
[   63.501285] FS:  00007f424ad29d00(0000) GS:ffff966ffebc0000(0000) knlGS:0000000000000000
[   63.501286] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[   63.501286] CR2: 00001439ed111000 CR3: 00000007b1c2e000 CR4: 00000000003406e0
[   63.501286] Call Trace:
[   63.501298]  commit_tail+0x94/0x130 [drm_kms_helper]
[   63.501304]  drm_atomic_helper_commit+0x113/0x140 [drm_kms_helper]
[   63.501308]  drm_atomic_helper_legacy_gamma_set+0x123/0x180 [drm_kms_helper]
[   63.501319]  drm_mode_gamma_set_ioctl+0x14c/0x200 [drm]
[   63.501327]  ? drm_color_lut_check+0xa0/0xa0 [drm]
[   63.501334]  drm_ioctl_kernel+0x86/0xd0 [drm]
[   63.501342]  drm_ioctl+0x206/0x390 [drm]
[   63.501350]  ? drm_color_lut_check+0xa0/0xa0 [drm]
[   63.501352]  ? selinux_file_ioctl+0x122/0x1c0
[   63.501385]  amdgpu_drm_ioctl+0x49/0x80 [amdgpu]
[   63.501387]  ksys_ioctl+0x82/0xc0
[   63.501388]  __x64_sys_ioctl+0x16/0x20
[   63.501390]  do_syscall_64+0x5b/0xf0
[   63.501392]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
[   63.501393] RIP: 0033:0x7f424e93347b
[   63.501395] Code: 0f 1e fa 48 8b 05 1d aa 0c 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d ed a9 0c 00 f7 d8 64 89 01 48
[   63.501395] RSP: 002b:00007fff192ee4c8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
[   63.501396] RAX: ffffffffffffffda RBX: 00007fff192ee500 RCX: 00007f424e93347b
[   63.501396] RDX: 00007fff192ee500 RSI: 00000000c02064a5 RDI: 0000000000000009
[   63.501396] RBP: 00000000c02064a5 R08: 000055ed3ce067d0 R09: 000055ed39d90990
[   63.501397] R10: 000055ed39df8960 R11: 0000000000000246 R12: 000055ed39df8960
[   63.501397] R13: 0000000000000009 R14: 0000000000000100 R15: 000055ed3cde4590
[   63.501399] ---[ end trace e8c5a83815b29f1d ]---

This issue hasn't had any activity since 2020-05-04. The AMD driver stack changes rapidly and contains lots of shared code across products so it's possible that it has already been fixed. Please upgrade to a current stable kernel and userspace stack and try again. If you still experience this issue with the latest driver stack, please capture relevant logging and open a new issue referring back to this one.

closed

Asrock 5700 XT Taichi fails to boot/hangs when a fifth monitor is connected

Submitted by eri..@..il.com

Description

Designs

Child items ...

Activity

Admin message

Admin message

Asrock 5700 XT Taichi fails to boot/hangs when a fifth monitor is connected

Submitted by eri..@..il.com

Description

Activity