| Summary: | Screens reorganise, failed to enable link training errors in dmesg about 60s after plugging in dock | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | DRI | Reporter: | Shaun <shaun> | ||||||||||
| Component: | DRM/Intel | Assignee: | Intel GFX Bugs mailing list <intel-gfx-bugs> | ||||||||||
| Status: | RESOLVED MOVED | QA Contact: | Intel GFX Bugs mailing list <intel-gfx-bugs> | ||||||||||
| Severity: | normal | ||||||||||||
| Priority: | medium | CC: | intel-gfx-bugs, manasi.d.navare | ||||||||||
| Version: | XOrg git | ||||||||||||
| Hardware: | x86-64 (AMD64) | ||||||||||||
| OS: | Linux (All) | ||||||||||||
| Whiteboard: | Triaged, ReadyForDev | ||||||||||||
| i915 platform: | CFL | i915 features: | display/DP | ||||||||||
| Attachments: |
|
||||||||||||
|
Description
Shaun
2019-02-19 10:05:57 UTC
Created attachment 143405 [details]
Full dmesg since boot with drm.debug=0xe
Captured a full dmesg with debug. Looks like the action kicks off at this point after a 60s gap consisting of only drm:drm_mode_addfb2 messages:
[ 91.442369] [drm:intel_get_hpd_pins.isra.13 [i915]] hotplug event received, stat 0x00400000, dig 0x10101210, pins 0x00000040, long 0x00000040
Created attachment 143406 [details]
xrandr --verbose
$ uname -a Linux shauns-laptop 4.20.10-042010-generic #201902150516 SMP Fri Feb 15 10:19:07 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux xorg version: 1:7.7+19ubuntu8 Created attachment 143407 [details]
lshw output
(In reply to Shaun from comment #1) > Created attachment 143405 [details] > Full dmesg since boot with drm.debug=0xe > > Captured a full dmesg with debug. Looks like the action kicks off at this > point after a 60s gap consisting of only drm:drm_mode_addfb2 messages: > > [ 91.442369] [drm:intel_get_hpd_pins.isra.13 [i915]] hotplug event > received, stat 0x00400000, dig 0x10101210, pins 0x00000040, long 0x00000040 Shaun, Can you attach full dmesg from boot. @Manasi can you help here with the existing logs? Yes, done. I also added xranadr and lshw output in code that's useful. Created attachment 143408 [details]
Full dmesg since boot with drm.debug=0xe (from kern.log)
Sorry, now I see why you asked. I didn't realise the log I uploaded was truncated. Looks like the same output was in kern.log
Would you please try to modify /etc/fwupd/daemon.conf to blacklist the dell plugin and reboot the machine? If that avoids this issue then I suspect it's this: https://github.com/hughsie/fwupd/issues/1105 https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1806323 https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1793965 Which I do feel is an i915 bug. Confirmed: after adding dell to the fwupdmgr modules blacklist, plugging in my dock no longer causes a screen shuffle. @Manasi, any suggestions from your side to this issue? Looking at the logs, I feel that just before the seeing the aux timeouts in inte_mst_pre_enable_dp(), after we call drm_dp_send_power_updown_phy to power up the port its probably not powering up yet, we need to check the ret of that call and keep calling until it succeeds before proceeding with link training. Manasi Also is it possible to upgrade your kernel on ubuntu to more recent kernel from drm-tip? The call drm_dp_send_power_updown_phy() might not even be present for 4.20 kernel and this might actually be the issue. Manasi -- 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/intel/issues/233. |
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.