dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 109340] HDMI output (DisplayPort-0) stops listing modes after using docking station DP output
Date: Sun, 13 Jan 2019 22:47:58 +0000	[thread overview]
Message-ID: <bug-109340-502@http.bugs.freedesktop.org/> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 3126 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=109340

            Bug ID: 109340
           Summary: HDMI output (DisplayPort-0) stops listing modes after
                    using docking station DP output
           Product: DRI
           Version: XOrg git
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/AMDgpu
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: zajec5@gmail.com

Created attachment 143092
  --> https://bugs.freedesktop.org/attachment.cgi?id=143092&action=edit
dmesg

I use following setup:
1) HP EliteBook 745 G5 with Ryzen 5 PRO 2500U
2) Docking station HP HSTNN-I11X
3) Monitor BenQ GW2260 (HDMI and no DisplayPort)
4) openSUSE Tumbleweed 
5) Self compiled kernel 4.20-rc3 from amd-staging-drm-next with patches:
drm/amd/display: Include names of all PP clock types
x86/MCE/AMD: Fix the thresholding machinery initialization order

My problem is that I can't use notebook's HDMI port (visible as DisplayPort-0)
after using DisplayPort output of docking station. HDMI detects monitor & gets
EDID but xrandr doesn't list any modes.


After booting without docking station & connecting monitor using HDMI port:
DisplayPort-0 connected (normal left inverted right x axis y axis)
   1920x1080     60.00 +  50.00    59.94  
   1680x1050     59.88  
   1600x900      60.00  
   1280x1024     60.02  
   1440x900      60.00  
   1280x800      59.91  
   1280x720      60.00    50.00    59.94  
   1024x768      60.00  
   800x600       60.32  
   720x576       50.00  
   720x480       60.00    59.94  
   640x480       60.00    59.94

After connecting docking station & monitor using DP port + HDMI adapter:
[drm] DM_MST: starting TM on aconnector: 00000000651bd996 [id: 57]
[drm] DM_MST: added connector: 00000000e1b7686d [id: 90] [master:
00000000651bd996]
[drm] DM_MST: added connector: 0000000078869ed2 [id: 94] [master:
00000000651bd996]
[drm] DM_MST: added connector: 00000000af4e5879 [id: 98] [master:
00000000651bd996]
[drm] amdgpu_dm_irq_schedule_work FAILED src 8
[drm] amdgpu_dm_irq_schedule_work FAILED src 8
[drm] amdgpu_dm_irq_schedule_work FAILED src 8

After disconnecting monitor & docking station:
[drm] DM_MST: stopping TM on aconnector: 00000000651bd996 [id: 57]
[drm] DM_MST: Disabling connector: 00000000e1b7686d [id: 90] [master:
00000000651bd996]
[drm] DM_MST: Disabling connector: 0000000078869ed2 [id: 94] [master:
00000000651bd996]
[drm] DM_MST: Disabling connector: 00000000af4e5879 [id: 98] [master:
00000000651bd996]

After connecting monitor using HDMI port:
xrandr: Output DisplayPort-0 is not disconnected but has no modes
(...)
DisplayPort-0 connected (normal left inverted right x axis y axis)


It's a bit weird since HDMI port (DisplayPort-0) seems to detect monitor being
connected & can get EDID. Is there some bug with enumerating available models
caused by DM_MST / TM?

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 4560 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2019-01-13 22:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-13 22:47 bugzilla-daemon [this message]
2019-01-13 22:52 ` [Bug 109340] HDMI output (DisplayPort-0) stops listing modes after using docking station DP output bugzilla-daemon
2019-01-13 22:53 ` bugzilla-daemon
2019-01-14  8:42 ` bugzilla-daemon
2019-01-14 10:46 ` bugzilla-daemon
2019-01-14 11:15 ` bugzilla-daemon
2019-01-14 12:04 ` bugzilla-daemon
2019-11-19  9:10 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-109340-502@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox