Created attachment 135743 [details] dmesg output First off, I would like to thank the amdgpu developers. I was able to boot 4.15-rc1 on my RX Vega 64 and activate six displays (using two startech MST hubs). Kudos! I am however getting ~5 of these on boot: [ 122.039308] [drm:generic_reg_wait [amdgpu]] *ERROR* REG_WAIT timeout 10us * 3000 tries - dce110_stream_encoder_dp_blank line:930 [ 122.832825] [drm:generic_reg_wait [amdgpu]] *ERROR* REG_WAIT timeout 10us * 3000 tries - dce110_stream_encoder_dp_blank line:930 [ 123.428493] [drm:generic_reg_wait [amdgpu]] *ERROR* REG_WAIT timeout 10us * 3000 tries - dce110_stream_encoder_dp_blank line:930 [ 123.740053] [drm:generic_reg_wait [amdgpu]] *ERROR* REG_WAIT timeout 10us * 3000 tries - dce110_stream_encoder_dp_blank line:930 [ 134.681772] [drm:generic_reg_wait [amdgpu]] *ERROR* REG_WAIT timeout 10us * 3000 tries - dce110_stream_encoder_dp_blank line:930 The full text of the backtrace of each one is: [ 134.681772] [drm:generic_reg_wait [amdgpu]] *ERROR* REG_WAIT timeout 10us * 3000 tries - dce110_stream_encoder_dp_blank line:930 [ 134.681798] WARNING: CPU: 2 PID: 854 at drivers/gpu/drm/amd/amdgpu/../display/dc/dc_helper.c:168 generic_reg_wait+0xe8/0x120 [amdgpu] [ 134.681799] Modules linked in: rpcsec_gss_krb5 auth_rpcgss nfsv4 dns_resolver nfs lockd grace sunrpc fscache amdkfd amd_iommu_v2 wmi_bmof mxm_wmi amdgpu nls_iso8859_1 nls_cp437 vfat fat chash ttm edac_mce_amd xpad drm_kms_helper snd_usb_audio evdev ff_memless input_leds mousedev joydev led_class drm snd_usbmidi_lib kvm snd_hda_codec_realtek snd_rawmidi mac_hid snd_seq_device cdc_acm irqbypass snd_hda_codec_hdmi snd_hda_codec_generic igb syscopyarea sysfillrect snd_hda_intel sysimgblt ixgbe fb_sys_fops snd_hda_codec i2c_algo_bit snd_hda_core mdio snd_hwdep snd_pcm ptp pps_core snd_timer dca snd soundcore sp5100_tco tpm_tis tpm_tis_core pcspkr i2c_piix4 shpchp k10temp tpm wmi 8250_dw button acpi_cpufreq sch_fq_codel ip_tables x_tables ext4 crc16 mbcache jbd2 fscrypto algif_skcipher af_alg sd_mod dm_crypt [ 134.681830] dm_mod dax uas usb_storage hid_generic usbhid hid crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd glue_helper cryptd ccp xhci_pci ahci rng_core sha256_generic libahci nvme xhci_hcd sha1_generic libata nvme_core usbcore scsi_mod usb_common serio [ 134.681841] CPU: 2 PID: 854 Comm: Xorg Tainted: G W 4.15.0-rc1-g4fbd8d194f06 #1 [ 134.681842] Hardware name: Micro-Star International Co., Ltd. MS-7B09/X399 GAMING PRO CARBON AC (MS-7B09), BIOS 1.60 11/14/2017 [ 134.681843] task: ffff880ff1426740 task.stack: ffffc900077c4000 [ 134.681854] RIP: 0010:generic_reg_wait+0xe8/0x120 [amdgpu] [ 134.681855] RSP: 0018:ffffc900077c7850 EFLAGS: 00010297 [ 134.681856] RAX: 0000000000010200 RBX: 0000000000000bb9 RCX: 0000000000000000 [ 134.681857] RDX: 0000000000000000 RSI: ffff880ffc88dc08 RDI: ffff880ffc88dc08 [ 134.681857] RBP: 000000000000000a R08: 0000000000000000 R09: 0000000000000698 [ 134.681858] R10: 0000000000000002 R11: ffffffff821213ed R12: ffff880fe97e5700 [ 134.681858] R13: 0000000000004de2 R14: 0000000000010000 R15: 0000000000000000 [ 134.681859] FS: 00007f10e073d940(0000) GS:ffff880ffc880000(0000) knlGS:0000000000000000 [ 134.681860] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 134.681861] CR2: 000055e098cae098 CR3: 0000000fedb72000 CR4: 00000000003406e0 [ 134.681862] Call Trace: [ 134.681878] dce110_stream_encoder_dp_blank+0xd4/0x130 [amdgpu] [ 134.681890] dce110_disable_stream+0xf5/0x180 [amdgpu] [ 134.681902] core_link_disable_stream+0x51/0x240 [amdgpu] [ 134.681913] dce110_reset_hw_ctx_wrap+0x196/0x1a0 [amdgpu] [ 134.681926] dce110_apply_ctx_to_hw+0x4c/0x610 [amdgpu] [ 134.681938] dc_commit_state+0x37e/0x470 [amdgpu] [ 134.681953] amdgpu_dm_atomic_commit_tail+0x2ab/0x9a0 [amdgpu] [ 134.681957] ? __wake_up_common_lock+0x89/0xc0 [ 134.681967] ? amdgpu_bo_pin_restricted+0x1ac/0x290 [amdgpu] [ 134.681969] ? wait_for_common+0x151/0x180 [ 134.681970] ? wait_for_common+0x151/0x180 [ 134.681974] commit_tail+0x3a/0x70 [drm_kms_helper] [ 134.681976] drm_atomic_helper_commit+0xfc/0x110 [drm_kms_helper] [ 134.681979] drm_atomic_helper_set_config+0x80/0x90 [drm_kms_helper] [ 134.681983] __drm_mode_set_config_internal+0x61/0x110 [drm] [ 134.681988] drm_mode_setcrtc+0x3fb/0x5b0 [drm] [ 134.681992] ? drm_mode_getcrtc+0x170/0x170 [drm] [ 134.681995] drm_ioctl_kernel+0x59/0xb0 [drm] [ 134.681999] drm_ioctl+0x2cb/0x380 [drm] [ 134.682003] ? drm_mode_getcrtc+0x170/0x170 [drm] [ 134.682012] amdgpu_drm_ioctl+0x49/0x80 [amdgpu] [ 134.682015] do_vfs_ioctl+0xa1/0x610 [ 134.682018] ? __sys_recvmsg+0x4e/0x90 [ 134.682019] ? __sys_recvmsg+0x7d/0x90 [ 134.682020] SyS_ioctl+0x74/0x80 [ 134.682022] entry_SYSCALL_64_fastpath+0x1a/0x7d [ 134.682024] RIP: 0033:0x7f10ddfec387 [ 134.682024] RSP: 002b:00007ffd731fdf78 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 [ 134.682025] RAX: ffffffffffffffda RBX: 00005609cd1bc580 RCX: 00007f10ddfec387 [ 134.682026] RDX: 00007ffd731fdfb0 RSI: 00000000c06864a2 RDI: 0000000000000018 [ 134.682027] RBP: 0000000000000020 R08: 00000000000000b0 R09: 00005609cce07270 [ 134.682027] R10: 00007ffd731fe130 R11: 0000000000000246 R12: 00007ffd731fe3a0 [ 134.682028] R13: 00005609cd18e070 R14: 0000000000000000 R15: 00005609ccedbb50 [ 134.682029] Code: 48 c7 c7 92 b9 a8 a0 52 4c 8b 4c 24 58 48 c7 c2 e8 53 a8 a0 44 8b 44 24 50 e8 a5 08 e9 ff 41 83 7c 24 20 01 58 8b 44 24 08 74 02 <0f> ff 48 83 c4 10 5b 5d 41 5c 41 5d 41 5e 41 5f c3 c7 44 24 0c [ 134.682042] ---[ end trace dcc42fd11b517234 ]--- The hardware is an RX Vega 64 on a X399 Threadripper with a 1900X CPU. I am running linux 4.15-rc1 with libdrm 2.4.88 and xorg-server 1.19.5. I am happy to give additional feedback or test patches.
Created attachment 135744 [details] Xorg.0.log file
Created attachment 141688 [details] dmesg from 4.19-rc4 I still get a lot of entries like: [ 824.605349] [drm:generic_reg_wait [amdgpu]] *ERROR* REG_WAIT timeout 10us * 3000 tries - dce110_stream_encoder_dp_blank line:922 with 4.19-rc4. Are these concerning? Dmesg attached.
The issue is just getting fixed. Will show up soon.
Hi, I'm getting the same error on upstream 4.18, 4.19 and drm-fixes-4.20 whenever I hotplug a DP monitor. Can you point me to the patch that is supposed to fix this? I took a quick look at the mailing list and found "[PATCH] drm/amdgpu:Improves robustness of SOC15_WAIT_ON_RREG". Unfortunately this doesn't work for me. I also tried something similar as that patch but in generic_reg_wait(). Still no luck. Thanks Patrik
I got the same issue. My hardware is MSI X470 Gaming Plus AMD Ryzen 5 2600 XFX RX580 GTS Black Edition Log: gernot@pcname:~$ journalctl -b -p err -- Logs begin at Sun 2018-10-07 04:01:03 CEST, end at Mon 2019-01-28 15:51:03 CET. -- Jän 28 14:25:00 pcname kernel: Couldn't get size: 0x800000000000000e Jän 28 14:25:00 pcname kernel: MODSIGN: Couldn't get UEFI db list Jän 28 14:25:00 pcname kernel: Couldn't get size: 0x800000000000000e Jän 28 14:25:00 pcname kernel: Couldn't get size: 0x800000000000000e Jän 28 14:25:00 pcname kernel: amdgpu 0000:1d:00.0: Invalid PCI ROM header signature: expecting 0xaa55, got 0xffff Jän 28 14:25:00 pcname kernel: sd 10:0:0:0: [sdc] No Caching mode page found Jän 28 14:25:00 pcname kernel: sd 10:0:0:0: [sdc] Assuming drive cache: write through Jän 28 14:25:00 pcname kernel: sd 9:0:0:0: [sdd] No Caching mode page found Jän 28 14:25:00 pcname kernel: sd 9:0:0:0: [sdd] Assuming drive cache: write through Jän 28 14:25:00 pcname kernel: scsi 9:0:0:1: Wrong diagnostic page; asked for 1 got 8 Jän 28 14:25:00 pcname kernel: scsi 9:0:0:1: Failed to get diagnostic page 0x1 Jän 28 14:25:00 pcname kernel: scsi 9:0:0:1: Failed to bind enclosure -19 Jän 28 14:25:00 pcname kernel: sd 12:0:0:0: [sde] No Caching mode page found Jän 28 14:25:00 pcname kernel: sd 12:0:0:0: [sde] Assuming drive cache: write through Jän 28 14:25:00 pcname kernel: ses 14:0:0:1: Wrong diagnostic page; asked for 1 got 8 Jän 28 14:25:00 pcname kernel: ses 14:0:0:1: Failed to get diagnostic page 0x1 Jän 28 14:25:00 pcname kernel: ses 14:0:0:1: Failed to bind enclosure -19 Jän 28 14:25:00 pcname kernel: sd 14:0:0:0: [sdg] No Caching mode page found Jän 28 14:25:00 pcname kernel: sd 14:0:0:0: [sdg] Assuming drive cache: write through Jän 28 14:25:00 pcname kernel: ses 16:0:0:1: Wrong diagnostic page; asked for 1 got 8 Jän 28 14:25:00 pcname kernel: ses 16:0:0:1: Failed to get diagnostic page 0x1 Jän 28 14:25:00 pcname kernel: ses 16:0:0:1: Failed to bind enclosure -19 Jän 28 14:25:00 pcname kernel: sd 16:0:0:0: [sdj] No Caching mode page found Jän 28 14:25:00 pcname kernel: sd 16:0:0:0: [sdj] Assuming drive cache: write through Jän 28 14:25:05 pcname spice-vdagent[1727]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0 Jän 28 14:25:10 pcname colord-sane[1833]: io/hpmud/pp.c 627: unable to read device-id ret=-1 Jän 28 14:27:09 pcname spice-vdagent[2694]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0 Jän 28 14:27:09 pcname kernel: [drm:generic_reg_wait [amdgpu]] *ERROR* REG_WAIT timeout 10us * 3000 tries - dce110_stream_encoder_dp_blank line:935 Jän 28 14:27:09 pcname kernel: [drm:generic_reg_wait [amdgpu]] *ERROR* REG_WAIT timeout 10us * 3000 tries - dce110_stream_encoder_dp_blank line:935 Jän 28 14:27:33 pcname pulseaudio[2597]: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote app Jän 28 14:27:48 pcname kernel: [drm:generic_reg_wait [amdgpu]] *ERROR* REG_WAIT timeout 10us * 3000 tries - dce110_stream_encoder_dp_blank line:935 Jän 28 14:27:48 pcname kernel: [drm:generic_reg_wait [amdgpu]] *ERROR* REG_WAIT timeout 10us * 3000 tries - dce110_stream_encoder_dp_blank line:935 Jän 28 14:27:48 pcname kernel: [drm:generic_reg_wait [amdgpu]] *ERROR* REG_WAIT timeout 10us * 3000 tries - dce110_stream_encoder_dp_blank line:935 Jän 28 14:27:48 pcname kernel: [drm:generic_reg_wait [amdgpu]] *ERROR* REG_WAIT timeout 10us * 3000 tries - dce110_stream_encoder_dp_blank line:935
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/amd/issues/263.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.