Bug 108100 - RX480: HDMI display unavailable with amdgpu.dc=1, boot error drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc_resource.c:1721 dc_validate_stream+0xd5/0x100
Summary: RX480: HDMI display unavailable with amdgpu.dc=1, boot error drivers/gpu/drm/...
Status: NEW
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/AMDgpu (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium major
Assignee: Default DRI bug account
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-09-29 18:23 UTC by Jure Repinc
Modified: 2018-12-06 06:43 UTC (History)
3 users (show)

See Also:
i915 platform:
i915 features:


Attachments
dmesg-4.18.8 (249.76 KB, text/plain)
2018-09-29 18:23 UTC, Jure Repinc
no flags Details
dmesg-4.17.14 (74.41 KB, text/plain)
2018-09-29 18:24 UTC, Jure Repinc
no flags Details
lspci (8.83 KB, text/plain)
2018-09-29 18:24 UTC, Jure Repinc
no flags Details
dmidecode (26.97 KB, text/plain)
2018-09-29 18:25 UTC, Jure Repinc
no flags Details
dmesg-4.18.9 (242.46 KB, text/plain)
2018-10-06 14:27 UTC, Jure Repinc
no flags Details
Xorg.0.log (80.59 KB, text/plain)
2018-12-06 06:43 UTC, Jure Repinc
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jure Repinc 2018-09-29 18:23:56 UTC
Created attachment 141796 [details]
dmesg-4.18.8

I have just upgraded my kernel on openSUSE Tumbleweed from 4.17.14 to 4.18.8 and my display that is a Panasonic 4K/UHD TV (TX-55CX400E) is not detected anymore and not available after boot. I have to pass amdgpu.dc=0 kernel paramater to get it available again.

If I check dmesg I can see a lot of lines like the following repeated:

[  195.633367] WARNING: CPU: 0 PID: 1979 at drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc_resource.c:1721 dc_validate_stream+0xd5/0x100 [amdgpu]
[  195.633368] Modules linked in: fuse ccm af_packet iscsi_ibft iscsi_boot_sysfs bluetooth ecdh_generic msr nct6775 hwmon_vid intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm nls_iso8859_1 nls_cp437 vfat fat irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel arc4 iTCO_wdt eeepc_wmi asus_wmi aes_x86_64 snd_hda_codec_realtek snd_hda_codec_generic snd_hda_codec_hdmi iTCO_vendor_support mxm_wmi mt7601u sparse_keymap wmi_bmof snd_hda_intel mac80211 snd_hda_codec crypto_simd cryptd pcspkr snd_hda_core joydev glue_helper cfg80211 rfkill snd_hwdep snd_pcm snd_timer snd fan soundcore e1000e ptp pps_core wmi thermal mei_me pcc_cpufreq video i2c_i801 mei button acpi_pad btrfs libcrc32c xor zstd_decompress zstd_compress xxhash hid_logitech_hidpp hid_logitech_dj hid_generic
[  195.633403]  usbhid raid6_pq amdkfd amd_iommu_v2 amdgpu crc32c_intel sr_mod cdrom chash i2c_algo_bit gpu_sched drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops xhci_pci xhci_hcd ttm drm usbcore sg dm_multipath dm_mod scsi_dh_rdac scsi_dh_emc scsi_dh_alua efivarfs
[  195.633418] CPU: 0 PID: 1979 Comm: X Tainted: G        W         4.18.8-1-default #1 openSUSE Tumbleweed (unreleased)
[  195.633418] Hardware name: System manufacturer System Product Name/H170 PRO GAMING, BIOS 3805 05/16/2018
[  195.633459] RIP: 0010:dc_validate_stream+0xd5/0x100 [amdgpu]
[  195.633461] Code: aa aa c1 e2 04 89 d0 f7 e1 c1 ea 04 89 93 68 02 00 00 e9 74 ff ff ff 5b b8 06 00 00 00 5d 41 5c c3 d1 ea eb c1 83 f9 02 74 e2 <0f> 0b 89 c2 eb dc 6b d2 1e b9 ab aa aa aa 89 d0 f7 e1 c1 ea 04 eb 
[  195.633490] RSP: 0018:ffffb004c8fbbb78 EFLAGS: 00010297
[  195.633491] RAX: 0000000000091050 RBX: ffff97358c10f400 RCX: 0000000000000005
[  195.633492] RDX: 0000000000091050 RSI: ffff97358c10f400 RDI: ffff9735915a0080
[  195.633493] RBP: ffff97353c118e00 R08: 0000000000000000 R09: 00000000000004b0
[  195.633494] R10: ffff97358c10f400 R11: 0000000000000780 R12: ffff97358fe1b600
[  195.633495] R13: ffff972f0cd88a10 R14: 0000000000000000 R15: ffff972f0cd88800
[  195.633496] FS:  00007fcb3d8ab940(0000) GS:ffff9735b6c00000(0000) knlGS:0000000000000000
[  195.633497] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[  195.633498] CR2: 000056287912f3b8 CR3: 00000007ee834005 CR4: 00000000003606f0
[  195.633499] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[  195.633500] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
[  195.633500] Call Trace:
[  195.633545]  amdgpu_dm_connector_mode_valid+0x6d/0x1d0 [amdgpu]
[  195.633551]  drm_helper_probe_single_connector_modes+0x47f/0x690 [drm_kms_helper]
[  195.633565]  drm_mode_getconnector+0x3af/0x3d0 [drm]
[  195.633577]  ? drm_mode_connector_property_set_ioctl+0x30/0x30 [drm]
[  195.633586]  drm_ioctl_kernel+0x81/0xd0 [drm]
[  195.633595]  drm_ioctl+0x1da/0x360 [drm]
[  195.633604]  ? drm_mode_connector_property_set_ioctl+0x30/0x30 [drm]
[  195.633633]  amdgpu_drm_ioctl+0x49/0x80 [amdgpu]
[  195.633636]  do_vfs_ioctl+0x90/0x5e0
[  195.633638]  ? __fget+0x6e/0xa0
[  195.633641]  ksys_ioctl+0x60/0x90
[  195.633644]  __x64_sys_ioctl+0x16/0x20
[  195.633646]  do_syscall_64+0x60/0x110
[  195.633649]  entry_SYSCALL_64_after_hwframe+0x49/0xbe
[  195.633650] RIP: 0033:0x7fcb3c27baa7
[  195.633650] Code: 00 00 90 48 8b 05 f1 83 2c 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d c1 83 2c 00 f7 d8 64 89 01 48 
[  195.633679] RSP: 002b:00007ffff09eb918 EFLAGS: 00003246 ORIG_RAX: 0000000000000010
[  195.633682] RAX: ffffffffffffffda RBX: 00005575382a36c0 RCX: 00007fcb3c27baa7
[  195.633683] RDX: 00007ffff09eb950 RSI: 00000000c05064a7 RDI: 000000000000000d
[  195.633683] RBP: 00007ffff09eb950 R08: 00005575382a2ac0 R09: 0000000000000007
[  195.633684] R10: 00007fcb3c2dee90 R11: 0000000000003246 R12: 00000000c05064a7
[  195.633685] R13: 000000000000000d R14: 000000000000000d R15: 00007ffff09eb950
[  195.633688] ---[ end trace a58eb9c235a952c1 ]---

I also have another LCD monitor (Samsung SyncMaster 215TW) connected via DVI to the MSI Radeon RX 480 Gaming X 8G graphics card and that one works just fine.

I tried older kernels and it looks like the problem is here since 4.18.0.
Comment 1 Jure Repinc 2018-09-29 18:24:34 UTC
Created attachment 141797 [details]
dmesg-4.17.14
Comment 2 Jure Repinc 2018-09-29 18:24:59 UTC
Created attachment 141798 [details]
lspci
Comment 3 Jure Repinc 2018-09-29 18:25:21 UTC
Created attachment 141799 [details]
dmidecode
Comment 4 Jure Repinc 2018-10-06 14:27:20 UTC
Created attachment 141922 [details]
dmesg-4.18.9

dmesg on Linux 4.18.9, now with amdgpu.dc_log=1 that I just found out about
Comment 5 Jure Repinc 2018-11-15 22:48:05 UTC
I just upgraded to Linux kernel 4.19.1 and the problem is still present.
Comment 6 Jure Repinc 2018-11-30 10:56:58 UTC
Is there any other info I should provide so you can start fixing this bug?
Comment 7 Nicholas Kazlauskas 2018-11-30 13:47:17 UTC
(In reply to Jure Repinc from comment #6)
> Is there any other info I should provide so you can start fixing this bug?

Do you use X? Do you mind posting an xorg log?

It would help to have one from a session where you booted with amdgpu.dc=0.
Comment 8 Jure Repinc 2018-12-06 06:43:44 UTC
Created attachment 142738 [details]
Xorg.0.log

Xorg.0.log from Linux kernel 4.19.4


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.