From mboxrd@z Thu Jan 1 00:00:00 1970
From: bugzilla-daemon@freedesktop.org
Subject: [Bug 97220] miss detect monitor. dell UP3214Q
Date: Fri, 05 Aug 2016 19:49:44 +0000
Message-ID:
Bug ID
97220
Summary
miss detect monitor. dell UP3214Q
Product
DRI
Version
XOrg git
Hardware
Other
OS
All
Status
NEW
Severity
normal
Priority
medium
Component
DRM/AMDgpu-pro
Assignee
dri-devel@lists.freedesktop.org
Reporter
ken@kenjo.org
Created attachment 125565 [details]<=
/span>
dmesg
Dell UP3214Q is a MST Monitor and proper detection is needed for it to oper=
ate
in 60HZ mode.
It is miss detected and only show up as supporting 30Hz max.
Created attachment 125568 [detai=
ls]
xorg log
| What | Removed | Added |
|---|---|---|
| Attachment #125568 mime type | text/x-log | text/plain |
Anything I can help with ?? more debug logs anything ?? It's really annoying having a large 4k monitor and have only 30Hz refresh r= ate.
So I tried latest=20 git://people.freedesktop.org/~agd5f/linux branch amd-staging-4.12 still not working.=20 aug 15 23:17:39 brix kernel: [drm] Atomic commit: SET crtc id 0: [ffff99ef99e9c000] aug 15 23:17:39 brix kernel: [drm] dc_commit_context: 1 streams aug 15 23:17:39 brix kernel: [drm] core_stream 0xecc4d400: src: 0, 0, 1920, 2160; dst: 0, 0, 1920, 2160, colorSpace aug 15 23:17:39 brix kernel: [drm] pix_clk_khz: 277250, h_total: 20= 80, v_total: 2222, pixelencoder:1, displ aug 15 23:17:39 brix kernel: [drm] sink name: DELL UP3214Q, serial: 808857680 aug 15 23:17:39 brix kernel: [drm] link: 2 aug 15 23:17:39 brix kernel: [drm] dce_get_required_clocks_state: clocks unsupported aug 15 23:17:39 brix kernel: ------------[ cut here ]------------ aug 15 23:17:39 brix kernel: WARNING: CPU: 2 PID: 2269 at drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc_link_dp. aug 15 23:17:39 brix kernel: Modules linked in: xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 ip aug 15 23:17:39 brix kernel: crypto_simd glue_helper serdev cryptd btqca snd_seq_device btintel snd_timer bluetoot aug 15 23:17:39 brix kernel: CPU: 2 PID: 2269 Comm: gnome-shell Not tainted 4.12.0+ #1 aug 15 23:17:39 brix kernel: Hardware name: MSI MS-7976/Z170A GAMING M7 (MS-7976), BIOS 1.I0 04/25/2017 aug 15 23:17:39 brix kernel: task: ffff99eff420dc00 task.stack: ffffa9bc87484000 aug 15 23:17:39 brix kernel: RIP: 0010:decide_link_settings+0xc4/0x170 [amd= gpu] aug 15 23:17:39 brix kernel: RSP: 0018:ffffa9bc874877c8 EFLAGS: 00010293 aug 15 23:17:39 brix kernel: RAX: 0000000000658830 RBX: ffff99efecc4d400 RC= X: ffff99ef99bfec00 aug 15 23:17:39 brix kernel: RDX: ffff99ef98d8e800 RSI: 0000000000000000 RD= I: 0000000000000000 aug 15 23:17:39 brix kernel: RBP: ffffa9bc874877d8 R08: 000000000001f160 R0= 9: ffffffffc03b0352 aug 15 23:17:39 brix kernel: R10: ffffd5edef67c3c0 R11: 0000000000000001 R1= 2: ffffa9bc874877ec aug 15 23:17:39 brix kernel: R13: ffff99ef98d6a800 R14: ffff99eff4140000 R1= 5: ffff99eff4140158 aug 15 23:17:39 brix kernel: FS: 00007f4fd59d4ac0(0000) GS:ffff99f02ec80000(0000) knlGS:0000000000000000 aug 15 23:17:39 brix kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050= 033 aug 15 23:17:39 brix kernel: CR2: 00007fff7300dfd8 CR3: 0000000bde63d000 CR= 4: 00000000003406e0 aug 15 23:17:39 brix kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR= 2: 0000000000000000 aug 15 23:17:39 brix kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR= 7: 0000000000000400 aug 15 23:17:39 brix kernel: Call Trace: aug 15 23:17:39 brix kernel: enable_link_dp+0x4e/0x260 [amdgpu] aug 15 23:17:39 brix kernel: core_link_enable_stream+0x419/0x470 [amdgpu] aug 15 23:17:39 brix kernel: apply_single_controller_ctx_to_hw+0x2d1/0x3b0 [amdgpu] aug 15 23:17:39 brix kernel: dce110_apply_ctx_to_hw+0x37f/0x700 [amdgpu] aug 15 23:17:39 brix kernel: ? amdgpu_cgs_read_register+0x14/0x20 [amdgpu] aug 15 23:17:39 brix kernel: ? generic_reg_get+0x2d/0x60 [amdgpu] aug 15 23:17:39 brix kernel: dc_commit_context_no_check+0xdc/0x2b0 [amdgpu] aug 15 23:17:39 brix kernel: dc_commit_context+0xc5/0xd0 [amdgpu] aug 15 23:17:39 brix kernel: amdgpu_dm_atomic_commit_tail+0x246/0xa40 [amd= gpu] aug 15 23:17:39 brix kernel: ? amdgpu_bo_pin_restricted+0xa0/0x2f0 [amdgpu] aug 15 23:17:39 brix kernel: ? amdgpu_bo_ref+0x1e/0x30 [amdgpu] aug 15 23:17:39 brix kernel: ? dm_plane_helper_prepare_fb+0xd2/0x210 [amdg= pu] aug 15 23:17:39 brix kernel: commit_tail+0x3f/0x70 [drm_kms_helper] aug 15 23:17:39 brix kernel: drm_atomic_helper_commit+0xa4/0xf0 [drm_kms_helper] aug 15 23:17:39 brix kernel: amdgpu_dm_atomic_commit+0x90/0xa0 [amdgpu] aug 15 23:17:39 brix kernel: drm_atomic_commit+0x4b/0x50 [drm] aug 15 23:17:39 brix kernel: drm_atomic_helper_set_config+0x70/0xa0 [drm_kms_helper] aug 15 23:17:39 brix kernel: __drm_mode_set_config_internal+0x65/0x110 [dr= m] aug 15 23:17:39 brix kernel: drm_mode_setcrtc+0x479/0x630 [drm] aug 15 23:17:39 brix kernel: drm_ioctl+0x213/0x4d0 [drm] aug 15 23:17:39 brix kernel: ? drm_mode_getcrtc+0x180/0x180 [drm] aug 15 23:17:39 brix kernel: amdgpu_drm_ioctl+0x4f/0x90 [amdgpu] aug 15 23:17:39 brix kernel: do_vfs_ioctl+0xa5/0x600 aug 15 23:17:39 brix kernel: SyS_ioctl+0x79/0x90 aug 15 23:17:39 brix kernel: entry_SYSCALL_64_fastpath+0x1e/0xa9 aug 15 23:17:39 brix kernel: RIP: 0033:0x7f4fd2b884d7 aug 15 23:17:39 brix kernel: RSP: 002b:00007ffd416104d8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 aug 15 23:17:39 brix kernel: RAX: ffffffffffffffda RBX: 000055f642afa090 RC= X: 00007f4fd2b884d7 aug 15 23:17:39 brix kernel: RDX: 00007ffd41610510 RSI: 00000000c06864a2 RD= I: 0000000000000008 aug 15 23:17:39 brix kernel: RBP: 000055f642a8dad0 R08: 0000000000000000 R0= 9: 000055f6448b1fe0 aug 15 23:17:39 brix kernel: R10: 00007f4fac004370 R11: 0000000000000246 R1= 2: 0000000000000000 aug 15 23:17:39 brix kernel: R13: 0000000000000003 R14: 000055f642afe2e0 R1= 5: 000055f642b02420 aug 15 23:17:39 brix kernel: Code: 41 c1 e0 04 44 39 c0 0f 86 af 00 00 00 8= 3 fe 02 74 ba 44 69 c2 00 2f 0d 00 44 39 aug 15 23:17:39 brix kernel: ---[ end trace 10a2ce4aaa0f9cae ]---
I believe this is a tiled display. Correct me if I'm wrong. Th= is means that besides MST support (where we still have to iron out some bugs) this display also requires tiled display support which we currently don't have.
I have no idea what a tiled display is. If I use the Intel display port I get or more correctly used to get two displays that I could then combine with xrandr into one larger. Now the ker= nel driver presents just the combined one directly no need to manually do anyth= ing.
(In reply to kenneth johansson from comment #6) > I have no idea what a tiled display is. I believe it means, that there are actually two panels. > If I use the Intel display port I get or more co= rrectly used to get two > displays that I could then combine with xrandr into one larger. Now the > kernel driver presents just the combined one directly no need to manua= lly do > anything. I have the same monitor. With Linux 4.17 and 4.18 at least GDM 3.28 and 3.30 are correctly displayed over the full screen. Could you please retest? PS: The monitor, unfortunately, only gives problems with the free drivers (Intel and AMDGPU) and firmware (UEFI of MSI B350M MORTAR (MS-7A37)). I bel= ieve it=E2=80=99s the monitor firmware, but my colleagues say, they do *not* hav= e any problems with the proprietary Nvidia drivers and Microsoft Windows. So, it= =E2=80=99s either a bug in the free drivers, or the proprietary drivers work around it somehow. Here are my bug reports for that. I do not know if these are specific drive= rs bugs or in the generic DRM code. [1]: https://bugs.freedesktop.org/show_bug.= cgi?id=3D107607 [2]: https://bugs.freedesktop.org/show_bug.= cgi?id=3D107845
| What | Removed | Added |
|---|---|---|
| Status | NEW | RESOLVED |
| Resolution | --- | MOVED |
-- 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/9.