Multi screen with Asus MB16AMT crash my system

If none of the more specific forums is the right place to ask

Multi screen with Asus MB16AMT crash my system

Postby SkilleR666 » 2020-07-10 21:28

Hi,

I recently added a Asus MB16AMT to my setup. The problem is my system lead to crash completely when doing some stuff, like launching a game or simply changing the display setup in xfce. Sometime the game launch without crash, sometimes it crash, the same for changing screen settings. If i let only my 2 main screen, all crash are gone.

My GPU is AMD 5700 XT.

About the software :
- Debian sid (kernel 5.7.0-1) + xfce
- amdgpu from sid repo

When crash happen, here what is show in log :
Code: Select all
Jul 10 23:29:19 UNKNOWN-PC kernel: [11052.259727] WARNING: CPU: 4 PID: 14368 at drivers/gpu/drm/amd/amdgpu/../display/dc/dcn20/dcn20_hwseq.c:109 dcn20_setup_gsl_group_as_lock+0x7f/0x200 [amdgpu]
Jul 10 23:29:19 UNKNOWN-PC kernel: [11052.259728] Modules linked in: fuse vboxnetadp(OE) vboxnetflt(OE) tun vboxdrv(OE) binfmt_misc snd_usb_audio snd_usbmidi_lib snd_rawmidi snd_seq_device mc hid_multitouch dm_crypt nls_ascii snd_hda_codec_realtek nls_cp437 snd_hda_codec_generic edac_mce_amd vfat fat ledtrig_audio snd_hda_codec_hdmi snd_hda_intel snd_intel_dspcfg snd_hda_codec eeepc_wmi kvm_amd asus_wmi snd_hda_core battery kvm sparse_keymap rfkill snd_hwdep xpad dm_mod irqbypass joydev ff_memless video snd_pcm wmi_bmof pcspkr sp5100_tco ccp k10temp snd_timer watchdog snd rng_core soundcore sg evdev acpi_cpufreq ip_tables x_tables autofs4 ext4 crc16 mbcache jbd2 crc32c_generic sd_mod t10_pi crc_t10dif crct10dif_generic hid_generic usbhid hid uas usb_storage amdgpu crct10dif_pclmul crct10dif_common crc32_pclmul crc32c_intel gpu_sched ttm ghash_clmulni_intel drm_kms_helper ahci libahci cec xhci_pci libata xhci_hcd drm aesni_intel usbcore mxm_wmi libaes igb scsi_mod crypto_simd cryptd glue_helper i2c_piix4 dca ptp mfd_core
Jul 10 23:29:19 UNKNOWN-PC kernel: [11052.259754]  pps_core i2c_algo_bit usb_common wmi gpio_amdpt gpio_generic button
Jul 10 23:29:19 UNKNOWN-PC kernel: [11052.259758] CPU: 4 PID: 14368 Comm: kworker/u64:2 Tainted: G        W  OE     5.7.0-1-amd64 #1 Debian 5.7.6-1
Jul 10 23:29:19 UNKNOWN-PC kernel: [11052.259759] Hardware name: System manufacturer System Product Name/CROSSHAIR VI HERO, BIOS 7704 12/16/2019
Jul 10 23:29:19 UNKNOWN-PC kernel: [11052.259768] Workqueue: events_unbound commit_work [drm_kms_helper]
Jul 10 23:29:19 UNKNOWN-PC kernel: [11052.259841] RIP: 0010:dcn20_setup_gsl_group_as_lock+0x7f/0x200 [amdgpu]
Jul 10 23:29:19 UNKNOWN-PC kernel: [11052.259842] Code: 84 d2 74 47 84 c0 75 26 48 8b 87 30 03 00 00 0f b6 80 70 02 00 00 a8 01 0f 84 dc 00 00 00 a8 02 74 55 a8 04 0f 84 f7 00 00 00 <0f> 0b 0f 0b 48 8b 44 24 28 65 48 33 04 25 28 00 00 00 0f 85 59 01
Jul 10 23:29:19 UNKNOWN-PC kernel: [11052.259843] RSP: 0018:ffffb8da08e47a50 EFLAGS: 00010202
Jul 10 23:29:19 UNKNOWN-PC kernel: [11052.259844] RAX: 0000000000000007 RBX: ffff92ef94720660 RCX: 0000000000000000
Jul 10 23:29:19 UNKNOWN-PC kernel: [11052.259844] RDX: 0000000000000001 RSI: ffff92ef94720660 RDI: ffff92f1ba430000
Jul 10 23:29:19 UNKNOWN-PC kernel: [11052.259845] RBP: 0000000000000001 R08: ffffb8da08e47a4c R09: 0000000000000000
Jul 10 23:29:19 UNKNOWN-PC kernel: [11052.259845] R10: 0000000000000000 R11: ffffb8da08e474e0 R12: 0000000000000001
Jul 10 23:29:19 UNKNOWN-PC kernel: [11052.259846] R13: ffff92f1ba430000 R14: 0000000000000000 R15: ffff92ef9114f800
Jul 10 23:29:19 UNKNOWN-PC kernel: [11052.259847] FS:  0000000000000000(0000) GS:ffff92f1ce900000(0000) knlGS:0000000000000000
Jul 10 23:29:19 UNKNOWN-PC kernel: [11052.259847] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jul 10 23:29:19 UNKNOWN-PC kernel: [11052.259848] CR2: 00007ff079d34000 CR3: 00000003aa564000 CR4: 0000000000340ee0
Jul 10 23:29:19 UNKNOWN-PC kernel: [11052.259849] Call Trace:
Jul 10 23:29:19 UNKNOWN-PC kernel: [11052.259923]  dcn20_pipe_control_lock+0x1ac/0x1c0 [amdgpu]
Jul 10 23:29:19 UNKNOWN-PC kernel: [11052.259991]  dc_commit_updates_for_stream+0xbef/0x18b0 [amdgpu]
Jul 10 23:29:19 UNKNOWN-PC kernel: [11052.260038]  ? amdgpu_display_get_crtc_scanoutpos+0x85/0x190 [amdgpu]
Jul 10 23:29:19 UNKNOWN-PC kernel: [11052.260108]  amdgpu_dm_atomic_commit_tail+0xb4c/0x1ff0 [amdgpu]
Jul 10 23:29:19 UNKNOWN-PC kernel: [11052.260114]  ? __switch_to_asm+0x40/0x70
Jul 10 23:29:19 UNKNOWN-PC kernel: [11052.260115]  ? __switch_to_asm+0x34/0x70
Jul 10 23:29:19 UNKNOWN-PC kernel: [11052.260115]  ? __switch_to_asm+0x40/0x70
Jul 10 23:29:19 UNKNOWN-PC kernel: [11052.260116]  ? __switch_to_asm+0x34/0x70
Jul 10 23:29:19 UNKNOWN-PC kernel: [11052.260117]  ? __switch_to_asm+0x40/0x70
Jul 10 23:29:19 UNKNOWN-PC kernel: [11052.260117]  ? __switch_to_asm+0x34/0x70
Jul 10 23:29:19 UNKNOWN-PC kernel: [11052.260118]  ? __switch_to_asm+0x40/0x70
Jul 10 23:29:19 UNKNOWN-PC kernel: [11052.260119]  ? __switch_to_asm+0x34/0x70
Jul 10 23:29:19 UNKNOWN-PC kernel: [11052.260119]  ? __switch_to_asm+0x40/0x70
Jul 10 23:29:19 UNKNOWN-PC kernel: [11052.260120]  ? __switch_to_asm+0x34/0x70
Jul 10 23:29:19 UNKNOWN-PC kernel: [11052.260121]  ? __switch_to_asm+0x40/0x70
Jul 10 23:29:19 UNKNOWN-PC kernel: [11052.260121]  ? __switch_to_asm+0x34/0x70
Jul 10 23:29:19 UNKNOWN-PC kernel: [11052.260122]  ? __switch_to_asm+0x40/0x70
Jul 10 23:29:19 UNKNOWN-PC kernel: [11052.260123]  ? __switch_to_asm+0x34/0x70
Jul 10 23:29:19 UNKNOWN-PC kernel: [11052.260124]  ? __switch_to_asm+0x40/0x70
Jul 10 23:29:19 UNKNOWN-PC kernel: [11052.260124]  ? __switch_to_asm+0x34/0x70
Jul 10 23:29:19 UNKNOWN-PC kernel: [11052.260125]  ? __switch_to_asm+0x40/0x70
Jul 10 23:29:19 UNKNOWN-PC kernel: [11052.260126]  ? __switch_to_asm+0x34/0x70
Jul 10 23:29:19 UNKNOWN-PC kernel: [11052.260126]  ? __switch_to_asm+0x40/0x70
Jul 10 23:29:19 UNKNOWN-PC kernel: [11052.260127]  ? __switch_to_asm+0x34/0x70
Jul 10 23:29:19 UNKNOWN-PC kernel: [11052.260128]  ? __switch_to_asm+0x40/0x70
Jul 10 23:29:19 UNKNOWN-PC kernel: [11052.260128]  ? __switch_to_asm+0x34/0x70
Jul 10 23:29:19 UNKNOWN-PC kernel: [11052.260129]  ? __switch_to_asm+0x40/0x70
Jul 10 23:29:19 UNKNOWN-PC kernel: [11052.260130]  ? __switch_to_asm+0x34/0x70
Jul 10 23:29:19 UNKNOWN-PC kernel: [11052.260130]  ? __switch_to_asm+0x40/0x70
Jul 10 23:29:19 UNKNOWN-PC kernel: [11052.260132]  ? _cond_resched+0x15/0x30
Jul 10 23:29:19 UNKNOWN-PC kernel: [11052.260133]  ? wait_for_completion_timeout+0x36/0x100
Jul 10 23:29:19 UNKNOWN-PC kernel: [11052.260134]  ? __switch_to_asm+0x34/0x70
Jul 10 23:29:19 UNKNOWN-PC kernel: [11052.260135]  ? __switch_to_asm+0x40/0x70
Jul 10 23:29:19 UNKNOWN-PC kernel: [11052.260135]  ? __switch_to_asm+0x34/0x70
Jul 10 23:29:19 UNKNOWN-PC kernel: [11052.260143]  commit_tail+0x94/0x130 [drm_kms_helper]
Jul 10 23:29:19 UNKNOWN-PC kernel: [11052.260146]  process_one_work+0x1b4/0x380
Jul 10 23:29:19 UNKNOWN-PC kernel: [11052.260148]  worker_thread+0x50/0x3c0
Jul 10 23:29:19 UNKNOWN-PC kernel: [11052.260149]  kthread+0xf9/0x130
Jul 10 23:29:19 UNKNOWN-PC kernel: [11052.260150]  ? process_one_work+0x380/0x380
Jul 10 23:29:19 UNKNOWN-PC kernel: [11052.260152]  ? kthread_park+0x90/0x90
Jul 10 23:29:19 UNKNOWN-PC kernel: [11052.260153]  ret_from_fork+0x22/0x40
Jul 10 23:29:19 UNKNOWN-PC kernel: [11052.260154] ---[ end trace 548d68be83cea53e ]---


After searching i found that people have similar output in log with 5700 XT, but they only have their log filled up, the system don't crash :
https://gitlab.freedesktop.org/drm/amd/-/issues/912

Hope someone can help me to figure out this problem ;)
SkilleR666
 
Posts: 10
Joined: 2020-02-06 12:55

Re: Multi screen with Asus MB16AMT crash my system

Postby Head_on_a_Stick » 2020-07-10 22:15

The firmware in sid is too old for the 5700XT (nice card btw, 7nm ftw!), grab the newer Navi stuff from kernel.org's git repository. Search the boards if you need more detail, this card has cropped up in several threads.
Black Lives Matter

Debian buster-backports ISO image: for new hardware support
User avatar
Head_on_a_Stick
 
Posts: 12647
Joined: 2014-06-01 17:46
Location: /dev/chair

Re: Multi screen with Asus MB16AMT crash my system

Postby SkilleR666 » 2020-07-11 04:34

Hi,

Actually i do have the one from kernel.org, i saw before buying the card than firmware on sid was not up to date.

Well after checking their is a commit dated to 19/06 that change navi10 files :
https://git.kernel.org/pub/scm/linux/ke ... 089c9e8db1

So with new firmware the problem will be gone ?

Edit : i've updated to the latest firmware from kernel.org, after reboot ive played with xfce screen settings, and crash happen again :(
SkilleR666
 
Posts: 10
Joined: 2020-02-06 12:55

Re: Multi screen with Asus MB16AMT crash my system

Postby Head_on_a_Stick » 2020-07-11 10:04

Black Lives Matter

Debian buster-backports ISO image: for new hardware support
User avatar
Head_on_a_Stick
 
Posts: 12647
Joined: 2014-06-01 17:46
Location: /dev/chair

Re: Multi screen with Asus MB16AMT crash my system

Postby SkilleR666 » 2020-07-11 10:21

Thanks, but this guy have problem since beginning of using is 5700 XT, and also he is the problem (not using separate second power line). My power line are separated, and i have a Seasonic Prime 750.

For me the problem is present only when the third screen is attached, i've no crash at all on dual screen.

Edit :
With the lastest navi10 firmware i'm no more spammed with the warning "dcn20_hwseq.c:109 dcn20_setup_gsl_group_as_lock+0x7f/0x200 [amdgpu]", but if the third screen is connected and i play with display settings or launch a game, i get the warning and the system crash
SkilleR666
 
Posts: 10
Joined: 2020-02-06 12:55


Return to General Questions

Who is online

Users browsing this forum: No registered users and 23 guests

fashionable