Bug 104653 - eDP display corrupt from Xserver boot
Summary: eDP display corrupt from Xserver boot
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 major
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard: ReadyForDev
Keywords:
Depends on:
Blocks:
 
Reported: 2018-01-16 10:27 UTC by Rory O'Siochain
Modified: 2018-04-20 15:53 UTC (History)
2 users (show)

See Also:
i915 platform: HSW
i915 features: display/eDP


Attachments
Xrandr verbose output (10.92 KB, text/plain)
2018-01-16 10:27 UTC, Rory O'Siochain
no flags Details
Dmesg output (59.46 KB, text/plain)
2018-01-16 10:29 UTC, Rory O'Siochain
no flags Details
Xorg output (21.11 KB, text/plain)
2018-01-16 10:30 UTC, Rory O'Siochain
no flags Details
DP-1 displaying correctly (109.23 KB, image/png)
2018-01-16 10:32 UTC, Rory O'Siochain
no flags Details
eDP-1 corrupted display under Wayland (monitor still partially functional) (109.10 KB, image/png)
2018-01-16 10:33 UTC, Rory O'Siochain
no flags Details
eDP-1 corrupted display under Xserver (monitor not functional) (115.13 KB, image/png)
2018-01-16 10:34 UTC, Rory O'Siochain
no flags Details
Dmesg with drm.debug=0xe grub parameter (59.61 KB, text/plain)
2018-01-16 16:11 UTC, Rory O'Siochain
no flags Details
dmesg with drm debug output (129.88 KB, text/plain)
2018-01-16 16:34 UTC, Rory O'Siochain
no flags Details
Kernel 4.15.0-rc8 dmesg (106.13 KB, text/plain)
2018-01-16 18:50 UTC, Rory O'Siochain
no flags Details
attachment-24966-0.html (2.33 KB, text/html)
2018-01-19 15:29 UTC, Rory O'Siochain
no flags Details

Description Rory O'Siochain 2018-01-16 10:27:50 UTC
Created attachment 136748 [details]
Xrandr verbose output

Running Ubuntu 17.10, my machine has two external displays which are shown as DP-1 and eDP-1 in xrandr (verbose output attached). Both monitors display correctly for the BIOS and initial purple screen before the Ubuntu splash. Additionally, the same is true various using liveUSB sticks, the monitor displays correctly until the OS boot splash. 

Once the Ubuntu loading screen begins, the display becomes corrupted. This is true using both Xserver and Wayland on Ubuntu 17.10.
Comment 1 Rory O'Siochain 2018-01-16 10:29:14 UTC
Created attachment 136749 [details]
Dmesg output

Dmesg output
Comment 2 Rory O'Siochain 2018-01-16 10:30:41 UTC
Created attachment 136750 [details]
Xorg output
Comment 3 Rory O'Siochain 2018-01-16 10:32:30 UTC
Created attachment 136751 [details]
DP-1 displaying correctly
Comment 4 Rory O'Siochain 2018-01-16 10:33:30 UTC
Created attachment 136752 [details]
eDP-1 corrupted display under Wayland (monitor still partially functional)
Comment 5 Rory O'Siochain 2018-01-16 10:34:01 UTC
Created attachment 136753 [details]
eDP-1 corrupted display under Xserver (monitor not functional)
Comment 6 Rory O'Siochain 2018-01-16 10:37:32 UTC
Hardware is Haswell 4010U with Intel Graphics 4400.

Dual display functions correctly on Win10, but not on any of several Linux distros attempted.
Comment 7 Elizabeth 2018-01-16 15:58:56 UTC
Hello Rory, could you please attach dmesg with debug information, drm.debug=0xe parameter on grub. Thanks.
Comment 8 Rory O'Siochain 2018-01-16 16:11:35 UTC
Created attachment 136776 [details]
Dmesg with drm.debug=0xe grub parameter

Hi Elizabeth, 
Thank you for looking at this. Attached should be dmesg with drm.debug=0xe flag set by editing /etc/default/grub. If this is not the correct way to set the flag let me know and I will correct.
Rory
Comment 9 Rory O'Siochain 2018-01-16 16:34:14 UTC
Created attachment 136778 [details]
dmesg with drm debug output

Apologies, update-grub command not run for previous dmesg output. Updated output attached.
Comment 10 Rory O'Siochain 2018-01-16 16:38:16 UTC
Comment on attachment 136776 [details]
Dmesg with drm.debug=0xe grub parameter

Please disregard this output
Comment 11 Elizabeth 2018-01-16 16:50:46 UTC
If you have the opportunity could you reproduce with this branch https://cgit.freedesktop.org/drm-tip and attach dmesg with debug information with it. Thanks again.
Comment 12 Elizabeth 2018-01-16 16:51:42 UTC
Also when attaching new logs, you can mark as obsoletes the old logs.
Comment 13 Rory O'Siochain 2018-01-16 18:50:50 UTC
Created attachment 136781 [details]
Kernel 4.15.0-rc8 dmesg

Hi, the attached should be the debug output built using the drm-tip branch.
Comment 14 Jani Nikula 2018-01-19 15:14:35 UTC
(In reply to Rory O'Siochain from comment #0)
> Running Ubuntu 17.10, my machine has two external displays which are shown
> as DP-1 and eDP-1 in xrandr (verbose output attached). 

What machine is this? eDP is supposed to be the local flat panel of a laptop, not an external display.
Comment 15 Rory O'Siochain 2018-01-19 15:29:41 UTC
Created attachment 136849 [details]
attachment-24966-0.html

This machine is an all in one device for use as a point of sale. It has both front and rear facing monitors. The monitors connect directly to the motherboard and not externally - apologies if my description was incorrect/confusing. Both monitors function correctly running Windows and upon initial boot, so it doesn't seem to be an invalid configuration.


> On 19 Jan 2018, at 15:14, bugzilla-daemon@freedesktop.org wrote:
> 
> 
> Comment # 14 <https://bugs.freedesktop.org/show_bug.cgi?id=104653#c14> on bug 104653 <https://bugs.freedesktop.org/show_bug.cgi?id=104653> from Jani Nikula <mailto:jani.nikula@intel.com>
> (In reply to Rory O'Siochain from comment #0 <x-msg://4/show_bug.cgi?id=104653#c0>)
> > Running Ubuntu 17.10, my machine has two external displays which are shown
> > as DP-1 and eDP-1 in xrandr (verbose output attached). 
> 
> What machine is this? eDP is supposed to be the local flat panel of a laptop,
> not an external display.
> 
> You are receiving this mail because:
> You reported the bug.
> You are on the CC list for the bug.
Comment 16 Rory O'Siochain 2018-01-26 18:20:09 UTC
Hi, would anyone be able to point me in the right direction in terms of getting this resolved? I'm not familiar with the kernel but if someone could point me in the right direction, I can look to put a patch together myself?

Many thanks,
Rory
Comment 17 Jani Nikula 2018-02-15 14:54:24 UTC
So there's nothing out of the ordinary in the dmesg. I can't make heads or tails about the pictures of the corrupted output. Some ideas, try them separately:

Please attach /sys/kernel/debug/dri/0/i915_vbt.

Please disable DP-1 and see if that makes a difference on eDP-1.

Please try booting with i915.fastboot=1. Does it work until the first modeset? Does it fail after the first modeset?

Do you have i915 built into the kernel? Can you try it as a module?
Comment 18 Jani Saarinen 2018-03-29 07:11:02 UTC
First of all. Sorry about spam.
This is mass update for our bugs. 

Sorry if you feel this annoying but with this trying to understand if bug still valid or not.
If bug investigation still in progress, please ignore this and I apologize!

If you think this is not anymore valid, please comment to the bug that can be closed.
If you haven't tested with our latest pre-upstream tree(drm-tip), can you do that also to see if issue is valid there still and if you cannot see issue there, please comment to the bug.
Comment 19 Jani Saarinen 2018-04-20 15:53:22 UTC
Closing, please re-open if still occurs.


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.