[Bug 108460] screen behind docking station doesn't work properly during boot

[bugzilla-daemon at freedesktop.org]

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

Stanislav Lisovskiy <stanislav.lisovskiy at intel.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Assignee|intel-gfx-bugs at lists.freede |stanislav.lisovskiy at intel.c
                   |sktop.org                   |om
         Whiteboard|Triaged, ReadyForDev        |Triaged

--- Comment #4 from Stanislav Lisovskiy <stanislav.lisovskiy at intel.com> ---
Would be nice to attach also Xserver and gdm logs to see if they got
correspondent uevents and got connector states updated properly. 
There are no such problems with Ubuntu 16/18 at least with the same kernel.
I've seen a similar bug and the problem was that gdm sometimes simply didn't
initiate modeset for some connectors.

>From the logs I see here:

cat bug-108460.log | grep -iE "(status updated)|(mode_setcrtc)|(session opened
for user)"
Oct 16 23:24:53 jberg1-mobl2.ger.corp.intel.com kernel:
[drm:drm_helper_probe_single_connector_modes [drm_kms_helper]]
[CONNECTOR:83:eDP-1] status updated from unknown to connected
Oct 16 23:24:53 jberg1-mobl2.ger.corp.intel.com kernel:
[drm:drm_helper_probe_single_connector_modes [drm_kms_helper]]
[CONNECTOR:91:DP-1] status updated from unknown to disconnected
Oct 16 23:24:53 jberg1-mobl2.ger.corp.intel.com kernel:
[drm:drm_helper_probe_single_connector_modes [drm_kms_helper]]
[CONNECTOR:102:DP-2] status updated from unknown to connected
Oct 16 23:24:54 jberg1-mobl2.ger.corp.intel.com kernel:
[drm:drm_helper_probe_single_connector_modes [drm_kms_helper]]
[CONNECTOR:149:DP-3] status updated from unknown to connected
Oct 16 23:24:54 jberg1-mobl2.ger.corp.intel.com kernel:
[drm:drm_helper_probe_single_connector_modes [drm_kms_helper]]
[CONNECTOR:109:DP-4] status updated from unknown to disconnected
Oct 16 23:24:55 jberg1-mobl2.ger.corp.intel.com kernel: [drm:drm_mode_setcrtc
[drm]] [CRTC:45:pipe A]
Oct 16 23:24:55 jberg1-mobl2.ger.corp.intel.com kernel: [drm:drm_mode_setcrtc
[drm]] [CONNECTOR:83:eDP-1]
Oct 16 23:24:55 jberg1-mobl2.ger.corp.intel.com kernel: [drm:drm_mode_setcrtc
[drm]] [CRTC:45:pipe A]
Oct 16 23:24:55 jberg1-mobl2.ger.corp.intel.com kernel: [drm:drm_mode_setcrtc
[drm]] [CONNECTOR:83:eDP-1]
Oct 16 23:24:55 jberg1-mobl2.ger.corp.intel.com kernel: [drm:drm_mode_setcrtc
[drm]] [CRTC:63:pipe B]
Oct 16 23:24:55 jberg1-mobl2.ger.corp.intel.com kernel: [drm:drm_mode_setcrtc
[drm]] [CONNECTOR:102:DP-2]
Oct 16 23:24:55 jberg1-mobl2.ger.corp.intel.com kernel: [drm:drm_mode_setcrtc
[drm]] [CRTC:63:pipe B]
Oct 16 23:24:55 jberg1-mobl2.ger.corp.intel.com kernel: [drm:drm_mode_setcrtc
[drm]] [CONNECTOR:102:DP-2]
Oct 16 21:25:26 jberg1-mobl2.ger.corp.intel.com systemd[1520]:
pam_unix(systemd-user:session): session opened for user gdm by (uid=0)
Oct 16 21:25:26 jberg1-mobl2.ger.corp.intel.com gdm-launch-environment][1456]:
pam_unix(gdm-launch-environment:session): session opened for user gdm by
(uid=0)
Oct 16 21:25:30 jberg1-mobl2.ger.corp.intel.com systemd[1831]:
pam_unix(systemd-user:session): session opened for user jberg1 by (uid=0)
Oct 16 21:25:30 jberg1-mobl2.ger.corp.intel.com sshd[1716]:
pam_unix(sshd:session): session opened for user jberg1 by (uid=0)
Oct 16 21:25:38 jberg1-mobl2.ger.corp.intel.com kernel: [drm:drm_mode_setcrtc
[drm]] [CRTC:45:pipe A]
Oct 16 21:25:38 jberg1-mobl2.ger.corp.intel.com kernel: [drm:drm_mode_setcrtc
[drm]] [CONNECTOR:83:eDP-1]
Oct 16 21:25:38 jberg1-mobl2.ger.corp.intel.com kernel: [drm:drm_mode_setcrtc
[drm]] [CRTC:63:pipe B]
Oct 16 21:25:38 jberg1-mobl2.ger.corp.intel.com kernel: [drm:drm_mode_setcrtc
[drm]] [CONNECTOR:102:DP-2]
Oct 16 21:25:38 jberg1-mobl2.ger.corp.intel.com kernel: [drm:drm_mode_setcrtc
[drm]] [CRTC:81:pipe C]
Oct 16 21:25:38 jberg1-mobl2.ger.corp.intel.com kernel: [drm:drm_mode_setcrtc
[drm]] [CONNECTOR:149:DP-3]

As you can see the kernel updates status to connected for eDP-1, DP-2, DP-3,
but we get drm_mode_setcrtc only for eDP-1, DP-2 before you login. Then we
finally get 
drm_mode_setcrtc for all of the connectors, after login. drm_mode_setcrtc is
initiated by DRM_IOCTL_MODE_SETCRTC ioctl which sent from XServer after gdm
requests it.Kernel doesn't initiate it by itself. Also I bet xrandr would show
that all connectors are in connected state - then this is most likely more a
gdm/XServer issue, rather than kernel.

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are the QA Contact for the bug.
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20181017/0ba14e6c/attachment.html>