Display goes blank soon after boot on dell xps13 on linux-image-4.18.0-10-generic

[Alexey Bazhin]

Display goes blank soon after boot on dell xps13 with linux-image-4.18.0-10-generic.

linux-image-4.18.0-7-generic working fine.

dmesg outputs:
[drm:intel_dp_start_link_train [i915]] *ERROR* [CONNECTOR:71:eDP-1] Link Training failed at link rate = 540000, lane count = 4

probably related to https://patchwork.kernel.org/patch/10633295/

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: linux-image-4.18.0-10-generic 4.18.0-10.11
ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
Uname: Linux 4.18.0-7-generic x86_64
ApportVersion: 2.20.10-0ubuntu13
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: baz 2265 F.... pulseaudio
CurrentDesktop: XFCE
Date: Mon Oct 15 14:25:35 2018
EcryptfsInUse: Yes
HibernationDevice: RESUME=/dev/mapper/cryptswap1
InstallationDate: Installed on 2018-03-01 (227 days ago)
InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180301)
MachineType: Dell Inc. XPS 13 9360
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-7-generic root=/dev/mapper/system-root ro quiet splash crashkernel=384M-:128M vt.handoff=1
RelatedPackageVersions:
 linux-restricted-modules-4.18.0-7-generic N/A
 linux-backports-modules-4.18.0-7-generic N/A
 linux-firmware 1.175
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/09/2018
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.9.0
dmi.board.name: 02PG84
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvr2.9.0:bd07/09/2018:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn02PG84:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 13 9360
dmi.product.sku: 082A
dmi.sys.vendor: Dell Inc.

[Shun Terabayashi (shunonymous)]

Created attachment 141757
full dmesg

Kernel is 4.18.8, 4.18.9(Arch), mainline(AUR), and drm/drm-intel(https://github.com/shunonymous/aur-linux-drm-intel-git).
My laptop displays nothing in builtin monitor when launching Wayland compositor.(weston, mutter)
It displays by connecting or disconnecting external monitor (by HDMI) (mutter. weston doesn't work).
startx works without any problem.

I tried to revert https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=399334708b4f07b107094e5db4a390f0f25d2d4f on mainline, this symptom was disappeared.

Machine: Razer Blade Stealth (2016 Later, UHD Model, w/o any eGPU)
External Display: LG 27UD88-W (3840x2160) connected with HDMI
OS: Arch Linux

[Lakshminarayana-vudum (lakshminarayana-vudum)]

Shun, Can you apply following path and test if the issue is still existing?
(https://bugs.freedesktop.org/attachment.cgi?id=141229).

If the issue persists, send dmesg from boot with kernel parameters drm.debug=0x1e log_buf_len=4M. This way we know more information about the bug.

[Shun Terabayashi (shunonymous)]

I re-tested on latest drm/drm-intel (without patch), this issue is not exist.

[Lakshminarayana-vudum (lakshminarayana-vudum)]

Thankyou for your feedback. I will resolve this bug as worksforme.

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This change was made by a bot.

[Cristian Aravena Romero (caravena)]

Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.19 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19-rc8

[Alexey Bazhin (baz-irc)]

linux-image-4.18.0-7-generic has no problem
linux-image-4.18.0-10-generic has problem

will try mainline later

[Alexey Bazhin (baz-irc)]

same problem with linux-image-unsigned-4.19.0-041900rc8-generic

[Kai-Heng Feng (kaihengfeng)]

Is it possible for you to find the first bad 4.19-rc* kernel in [1]?

[1]http://kernel.ubuntu.com/~kernel-ppa/mainline/

[Alexey Bazhin (baz-irc)]

rc2 is fine, rc3 has the problem

[Alexey Bazhin (baz-irc)]

it seems this commit is causing the problem
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/gpu/drm/i915/intel_dp.c?id=399334708b4f07b107094e5db4a390f0f25d2d4f

[Alexey Bazhin (baz-irc)]

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

[Karolherbst-g (karolherbst-g)]

this is actually an issue on the 4.18.8 and newer.

Those commits need to be applied to 4.18 to fix this regression:

9ebd8202393dde9d3678c9ec162c1aa63ba17eac
f24f6eb95807bca0dbd8dc5b2f3a4099000f4472

regression was caused by

399334708b4f07b107094e5db4a390f0f25d2d4f

[Karolherbst-g (karolherbst-g)]

I think the same applies for the upcoming 4.19 as well.

[Jani-nikula (jani-nikula)]

(In reply to Karol Herbst from comment #4)
> this is actually an issue on the 4.18.8 and newer.
>
> Those commits need to be applied to 4.18 to fix this regression:
>
> 9ebd8202393dde9d3678c9ec162c1aa63ba17eac

commit 9ebd8202393dde9d3678c9ec162c1aa63ba17eac
Author: Dhinakaran Pandiyan <email address hidden>
Date: Thu Sep 27 13:57:30 2018 -0700

    drm/i915/dp: Fix link retraining comment in intel_dp_long_pulse()

> f24f6eb95807bca0dbd8dc5b2f3a4099000f4472

commit f24f6eb95807bca0dbd8dc5b2f3a4099000f4472
Author: Dhinakaran Pandiyan <email address hidden>
Date: Thu Sep 27 13:57:31 2018 -0700

    drm/i915/dp: Restrict link retrain workaround to external monitors

> regression was caused by
>
> 399334708b4f07b107094e5db4a390f0f25d2d4f

commit 399334708b4f07b107094e5db4a390f0f25d2d4f
Author: Jan-Marek Glogowski <email address hidden>
Date: Sat Aug 25 15:10:35 2018 -0400

    drm/i915: Re-apply "Perform link quality check, unconditionally during long pulse"

[Jani-nikula (jani-nikula)]

The commits are headed upstream and tagged with appropriate tags to be backported to stable kernels. Please let us know if the fixes don't show up in v4.18 in a few weeks.

Thanks for the report, closing.