Bug 87869 - Screen reset on external DVI monitors
Summary: Screen reset on external DVI monitors
Status: CLOSED WORKSFORME
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: XOrg git
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-12-30 16:53 UTC by Frank Laszlo
Modified: 2017-06-30 23:41 UTC (History)
1 user (show)

See Also:
i915 platform: HSW
i915 features: display/DP MST


Attachments
Xorg.0.log (28.52 KB, text/plain)
2014-12-31 12:21 UTC, Frank Laszlo
no flags Details
dmesg (1.01 MB, text/plain)
2014-12-31 12:58 UTC, Frank Laszlo
no flags Details
attachment-8252-0.html (1.53 KB, text/html)
2016-07-06 18:47 UTC, Frank Laszlo
no flags Details

Description Frank Laszlo 2014-12-30 16:53:50 UTC
I have a Dell Ultrabook E7440 using one of the Dell ePort docking stations with dual DVI outputs on it.

Periodically my screen will reset, almost like the resolution was changed. This only happens on the 2 monitors connected via DVI. the Xorg logs do not show any relevant information.

I upgraded to kernel 3.19.0-rc2 when the issue started occuring. I was originally running an older kernel that did not natively support both monitors. I had to use a modified libXinrama to span the display across both monitors.

Now, with 3.19, both monitors are properly detected, but this reset is rather annoying.

I believe this may be related to this bug:

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

Let me know what information needs to be provided to look into this.
Comment 1 Chris Wilson 2014-12-31 10:13:35 UTC
If you have xf86-video-intel-2.99.917 then the Xorg.0.log will be interesting just to check nothing is recorded. What wil be most useful I guess will be a drm.debug=6 dmesg from across the event.
Comment 2 Frank Laszlo 2014-12-31 12:21:07 UTC
Created attachment 111567 [details]
Xorg.0.log
Comment 3 Frank Laszlo 2014-12-31 12:23:21 UTC
(In reply to Chris Wilson from comment #1)
> If you have xf86-video-intel-2.99.917 then the Xorg.0.log will be
> interesting just to check nothing is recorded. What wil be most useful I
> guess will be a drm.debug=6 dmesg from across the event.

I'm actually running 2.99.916. Thats the latest my distro (opensuse) provided. I will try upgrading it and seeing if that has any effect.

I've attached my Xorg.0.log anyways. As I said, it doesn't really have anything useful in it. I've pasted my xrandr below as well to show my display configuration.

I'll check on the drm.debug and followup shortly with my findings.

Thanks


flaszlo@odin:/var/log> xrandr 
Screen 0: minimum 8 x 8, current 5760 x 1080, maximum 32767 x 32767
eDP1 connected 1920x1080+3840+0 (normal left inverted right x axis y axis) 309mm x 174mm
   1920x1080     60.02*+
   1400x1050     59.98  
   1280x1024     60.02  
   1280x960      60.00  
   1024x768      60.00  
   800x600       60.32    56.25  
   640x480       59.94  
DP1 disconnected (normal left inverted right x axis y axis)
DP2 connected primary 1920x1080+1920+0 (normal left inverted right x axis y axis) 477mm x 268mm
   1920x1080     60.00*+
   1280x1024     75.02    60.02  
   1152x864      75.00  
   1024x768      75.08    60.00  
   800x600       75.00    60.32  
   640x480       75.00    60.00  
   720x400       70.08  
DP3 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 477mm x 268mm
   1920x1080     60.00*+
   1280x1024     75.02    60.02  
   1152x864      75.00  
   1024x768      75.08    60.00  
   800x600       75.00    60.32  
   640x480       75.00    60.00  
   720x400       70.08  
DP4 disconnected (normal left inverted right x axis y axis)
HDMI1 disconnected (normal left inverted right x axis y axis)
HDMI2 disconnected (normal left inverted right x axis y axis)
VIRTUAL1 disconnected (normal left inverted right x axis y axis)
Comment 4 Frank Laszlo 2014-12-31 12:58:41 UTC
Created attachment 111575 [details]
dmesg
Comment 5 Frank Laszlo 2014-12-31 13:01:02 UTC
(In reply to Chris Wilson from comment #1)
> If you have xf86-video-intel-2.99.917 then the Xorg.0.log will be
> interesting just to check nothing is recorded. What wil be most useful I
> guess will be a drm.debug=6 dmesg from across the event.

Ok. Upgraded to 2.99.917, and enabled drm.debug in my boot options.

I've attached the dmesg output. I ran dmesg immediately after I noticed a screen reset.

Let me know if there is anything else you would like me to try.

Thanks for your help.
Comment 6 Frank Laszlo 2015-10-26 18:40:44 UTC
FYI. This issue is still occurring. We can reproduce on several E7440 laptops in the office. It seems to popup on kernels >= 3.19. I've tried all the way up to the latest stable version (4.2.4) with the same results.

I consider myself pretty handy when it comes to UNIX/Linux, but this one has me puzzled. As far as I can tell, there is either a bug in the driver, or a problem with the hardware docks. I've tried several docks with the same result.

Oddly enough, we have some users with the E7450, one model newer, who do not have this problem at all.
Comment 7 cprigent 2015-11-17 17:22:14 UTC
Bug scrub:
Decrease priority.
Comment 8 Dhinakaran Pandiyan 2016-07-06 18:46:03 UTC
Thanks for reporting the issue. Are you still seeing this with the latest kernel?
 Can you please try the drm-intel-nightly kernel and attach dmesg with drm.debug=0x1e?
Comment 9 Frank Laszlo 2016-07-06 18:47:54 UTC
Created attachment 124937 [details]
attachment-8252-0.html

Hello,

Actually. I stopped using the docking station since I could not find a
viable workaround. I can attempt to test in the next couple weeks to see if
the issue is resolved. Thanks

On Wed, Jul 6, 2016 at 2:46 PM, <bugzilla-daemon@freedesktop.org> wrote:

> *Comment # 8 <https://bugs.freedesktop.org/show_bug.cgi?id=87869#c8> on
> bug 87869 <https://bugs.freedesktop.org/show_bug.cgi?id=87869> from
> Dhinakaran Pandiyan <dhinakaran.pandiyan@intel.com> *
>
> Thanks for reporting the issue. Are you still seeing this with the latest
> kernel?
>  Can you please try the drm-intel-nightly kernel and attach dmesg with
> drm.debug=0x1e?
>
> ------------------------------
> You are receiving this mail because:
>
>    - You reported the bug.
>
>
Comment 10 Dhinakaran Pandiyan 2016-07-06 21:07:08 UTC
Great, thanks!
Comment 11 dog 2016-11-02 22:22:19 UTC
Has there been an opportunity to retest?  What was seen using the latest upstream driver?
Comment 12 Jari Tahvanainen 2017-03-29 11:52:12 UTC
Timeout - marking resolved+worksforme. Please reopen if problem still exists with the latest kernel from drm-tip.


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.