Bug 110317

Summary:

Second display does not show up on dock of Lenovo Helix 2

Product:

DRI

Reporter:

Uwe Dippel <udippel>

Component:

DRM/Intel

Assignee:

Intel GFX Bugs mailing list <intel-gfx-bugs>

Status:

RESOLVED WORKSFORME

QA Contact:

Intel GFX Bugs mailing list <intel-gfx-bugs>

Severity:

normal

Priority:

medium

CC:

intel-gfx-bugs, stanislav.lisovskiy

Version:

XOrg git

Hardware:

x86-64 (AMD64)

OS:

Linux (All)

Whiteboard:

Triaged

i915 platform:

BDW

i915 features:

display/HDMI

Attachments:

Description	Flags
dmesg with debug options, on dock not bringing up HDMI monitor	none

Description Uwe Dippel 2019-04-03 16:19:14 UTC

Created attachment 143855 [details]
dmesg with debug options, on dock not bringing up HDMI monitor

I'd like to refer to Bug 109750. This is not quite a duplicate, since it uses a very different dock. It shows a different behaviour, too, but likewise to said other report, in the end it doesn't bring up the display reliably. 
Otherwise it is an identical machine to the one in Bug 109750.

(Alas, no, I have no latest kernel/drmtip installed here. But since this never made any difference in all my DRM/Intel bugs, I do permit myself to start without this hassle.)

In this case, I plugged in the HDMI-monitor into that dock some minutes into the session. It shows some working activities before it fails, and never brings up the monitor in System Settings.

(Monitor plugged in)
[  929.894507] evdi: [D] evdi_detect:88 (dev=1) poll connector state: connected
[  929.894512] evdi: [D] evdi_painter_get_edid_copy:227 (dev=1) EDID valid
[  930.095015] evdi: [D] evdi_detect:88 (dev=1) poll connector state: connected
[  930.095020] evdi: [D] evdi_painter_get_edid_copy:227 (dev=1) EDID valid
[  930.403505] evdi: [D] evdi_detect:88 (dev=1) poll connector state: connected
[  930.403513] evdi: [D] evdi_painter_get_edid_copy:227 (dev=1) EDID valid
[  931.038495] evdi: [D] evdi_detect:88 (dev=1) poll connector state: connected
[  931.038500] evdi: [D] evdi_painter_get_edid_copy:227 (dev=1) EDID valid
[  931.724539] evdi: [D] evdi_detect:88 (dev=1) poll connector state: connected
[  931.724544] evdi: [D] evdi_painter_get_edid_copy:227 (dev=1) EDID valid
[  932.388490] evdi: [D] evdi_detect:88 (dev=1) poll connector state: connected
[  932.388495] evdi: [D] evdi_painter_get_edid_copy:227 (dev=1) EDID valid
[  933.042571] evdi: [D] evdi_detect:88 (dev=1) poll connector state: connected
[  933.042577] evdi: [D] evdi_painter_get_edid_copy:227 (dev=1) EDID valid
[  933.700501] evdi: [D] evdi_detect:88 (dev=1) poll connector state: connected
[  933.700506] evdi: [D] evdi_painter_get_edid_copy:227 (dev=1) EDID valid
(and so forth)

I order to help I started the standard kernel with the standard debug instructions, with the monitor plugged in from the very beginning. The dmesg can be found as attachment.

Comment 1 Lakshmi 2019-04-04 10:58:10 UTC

Stan, any comments? Still it would be good to see dmesg from drmtip?

Comment 2 Lakshmi 2019-05-02 12:04:53 UTC

@Uwe. Can you please verify this issue with drmtip https://cgit.freedesktop.org/drm-tip? 
Logs from drmtip will help during investigation.

Comment 3 Lakshmi 2019-05-29 11:33:06 UTC

@Uwe, any results from drmtip testing?

Comment 4 Lakshmi 2019-07-02 06:27:53 UTC

Test results from drm-tip is needed to investigate the issue.

No feedback for 2 months, closing as resolved works for me.
Please re-open if issue persists with latest drm-tip https://cgit.freedesktop.org/drm-tip and send dmesg from boot with kernel parameters drm.debug=0x1e log_buf_len=4M?

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.