[Kernel-packages] [Bug 1903969] Re: failed to boot to GUI: i915 0000:00:02.0: [drm] *ERROR* Link Training Unsuccessful
I Can confirm the same behavior on my machine
5.15.0-53-generic #59-Ubuntu SMP Mon Oct 17 18:53:30 UTC 2022 x86_64
x86_64 x86_64 GNU/Linux
I get
i915 :00:02.0: [drm] *ERROR* Sending link address failed with -5
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1903969
Title:
failed to boot to GUI: i915 :00:02.0: [drm] *ERROR* Link Training
Unsuccessful
Status in HWE Next:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in linux-oem-5.10 package in Ubuntu:
Invalid
Status in linux-oem-5.6 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Invalid
Status in linux-oem-5.10 source package in Focal:
Fix Released
Status in linux-oem-5.6 source package in Focal:
Won't Fix
Status in linux source package in Groovy:
Won't Fix
Status in linux-oem-5.10 source package in Groovy:
Invalid
Status in linux-oem-5.6 source package in Groovy:
Invalid
Status in linux source package in Hirsute:
Fix Released
Status in linux-oem-5.10 source package in Hirsute:
Invalid
Status in linux-oem-5.6 source package in Hirsute:
Invalid
Bug description:
[SRU Justification]
[Impact]
On platforms supported DP tunneling over USB 3.2 or so, a Retimer is
required on the host side to cover insertion loss. On such platforms the
rtimer firmware maybe configured to use LTTPR (Link Training Tunable PHY
Repeater) non-transparent mode only, which is only supported in drm-tip
currently. Without LTTPR support, link training may fail with following
error messages depending on the data path configuration:
i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful
i915 :00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun
[Fix]
Patchset https://www.spinics.net/lists/intel-gfx/msg248700.html
("drm/i915: Add support for LTTPR non-transparent link training mode")
is required to fix this issue. It has been landed to drm-tip and will
only be merged to mainline in v5.11.
Patchset https://patchwork.freedesktop.org/series/76993/ ("Plumb crtc
state to link training code") is included for link training functions
prototype changes.
[Test Case]
On Dell OptiPlex and WD19 docking station, use following steps to verify:
1. disconnect WD19 from OptiPlex, disconnect OptiPlex's power
2. attach OptiPlex's power cord
3. attach WD19's power cord
4. attach DP to WD19
5. attach WD19 to OptiPlex
6. boot up and check if boot to GUI directly
7. `dmesg` and check if aforementioned DRM link training error appears
[Where problems could occur]
The second patchset pulled for dependency doesn't have too much
effective changes but refactoring some translation functions, so very
unlikely to have regressions.
For the major part, LTTPR support, when LTTPR is either not detected or
not supported, it will fall back to use transparent mode as it was.
Otherwise, DP Standard recommends to use LTTPR non-transparent mode for
link training, so this should be the right way to have best hardware
support.
== original bug description ==
[Summary]
When the monitor ONLY is connected to the WD19 (DP port) and WD19 is
connected to the type c port than boot the machine, the monitor shows no video
output after loaded i915.
[Reproduce Steps]
1. connect power cable of WD19
2. connect DP cable from monitor to WD19
3. connect power cable to target system.
4. connect type c cable from WD19 to target system
5. boot up
[Results]
Expected: video output as there is only one monitor connected.
Actual: No video output.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.6.0-1033-oem 5.6.0-1033.35
ProcVersionSignature: Ubuntu 5.6.0-1033.35-oem 5.6.19
Uname: Linux 5.6.0-1033-oem x86_64
ApportVersion: 2.20.11-0ubuntu27.11
Architecture: amd64
CasperMD5CheckResult: skip
Date: Thu Nov 12 05:11:11 2020
DistributionChannelDescriptor:
# This is the distribution channel descriptor for the OEM CDs
# For more information see
http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-focal-amd64-20200502-85+fossa-metapod+X40
InstallationDate: Installed on 2020-11-03 (9 days ago)
InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary
20200502-05:58
SourcePackage: linux-signed-oem-5.6
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1903969/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1903969] Re: failed to boot to GUI: i915 0000:00:02.0: [drm] *ERROR* Link Training Unsuccessful
I seem to have the same problem in Jammy with the kernel
5.15.0-47-generic and with the latest firmware updates. The only
difference is dmesg speak of pipe B instead of pipe A:
[ 509.965244] i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful
[ 509.990694] i915 :00:02.0: [drm] *ERROR* CPU pipe B FIFO underrun
[ 510.270856] i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful
[ ]
Is that actually the same bug, or should I open a new one ?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1903969
Title:
failed to boot to GUI: i915 :00:02.0: [drm] *ERROR* Link Training
Unsuccessful
Status in HWE Next:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in linux-oem-5.10 package in Ubuntu:
Invalid
Status in linux-oem-5.6 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Invalid
Status in linux-oem-5.10 source package in Focal:
Fix Released
Status in linux-oem-5.6 source package in Focal:
Won't Fix
Status in linux source package in Groovy:
Won't Fix
Status in linux-oem-5.10 source package in Groovy:
Invalid
Status in linux-oem-5.6 source package in Groovy:
Invalid
Status in linux source package in Hirsute:
Fix Released
Status in linux-oem-5.10 source package in Hirsute:
Invalid
Status in linux-oem-5.6 source package in Hirsute:
Invalid
Bug description:
[SRU Justification]
[Impact]
On platforms supported DP tunneling over USB 3.2 or so, a Retimer is
required on the host side to cover insertion loss. On such platforms the
rtimer firmware maybe configured to use LTTPR (Link Training Tunable PHY
Repeater) non-transparent mode only, which is only supported in drm-tip
currently. Without LTTPR support, link training may fail with following
error messages depending on the data path configuration:
i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful
i915 :00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun
[Fix]
Patchset https://www.spinics.net/lists/intel-gfx/msg248700.html
("drm/i915: Add support for LTTPR non-transparent link training mode")
is required to fix this issue. It has been landed to drm-tip and will
only be merged to mainline in v5.11.
Patchset https://patchwork.freedesktop.org/series/76993/ ("Plumb crtc
state to link training code") is included for link training functions
prototype changes.
[Test Case]
On Dell OptiPlex and WD19 docking station, use following steps to verify:
1. disconnect WD19 from OptiPlex, disconnect OptiPlex's power
2. attach OptiPlex's power cord
3. attach WD19's power cord
4. attach DP to WD19
5. attach WD19 to OptiPlex
6. boot up and check if boot to GUI directly
7. `dmesg` and check if aforementioned DRM link training error appears
[Where problems could occur]
The second patchset pulled for dependency doesn't have too much
effective changes but refactoring some translation functions, so very
unlikely to have regressions.
For the major part, LTTPR support, when LTTPR is either not detected or
not supported, it will fall back to use transparent mode as it was.
Otherwise, DP Standard recommends to use LTTPR non-transparent mode for
link training, so this should be the right way to have best hardware
support.
== original bug description ==
[Summary]
When the monitor ONLY is connected to the WD19 (DP port) and WD19 is
connected to the type c port than boot the machine, the monitor shows no video
output after loaded i915.
[Reproduce Steps]
1. connect power cable of WD19
2. connect DP cable from monitor to WD19
3. connect power cable to target system.
4. connect type c cable from WD19 to target system
5. boot up
[Results]
Expected: video output as there is only one monitor connected.
Actual: No video output.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.6.0-1033-oem 5.6.0-1033.35
ProcVersionSignature: Ubuntu 5.6.0-1033.35-oem 5.6.19
Uname: Linux 5.6.0-1033-oem x86_64
ApportVersion: 2.20.11-0ubuntu27.11
Architecture: amd64
CasperMD5CheckResult: skip
Date: Thu Nov 12 05:11:11 2020
DistributionChannelDescriptor:
# This is the distribution channel descriptor for the OEM CDs
# For more information see
http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-focal-amd64-20200502-85+fossa-metapod+X40
InstallationDate: Installed on 2020-11-03 (9 days ago)
InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary
20200502-05:58
SourcePackage: linux-signed-oem-5.6
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1903969/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe :
[Kernel-packages] [Bug 1903969] Re: failed to boot to GUI: i915 0000:00:02.0: [drm] *ERROR* Link Training Unsuccessful
** Changed in: hwe-next
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1903969
Title:
failed to boot to GUI: i915 :00:02.0: [drm] *ERROR* Link Training
Unsuccessful
Status in HWE Next:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in linux-oem-5.10 package in Ubuntu:
Invalid
Status in linux-oem-5.6 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Invalid
Status in linux-oem-5.10 source package in Focal:
Fix Released
Status in linux-oem-5.6 source package in Focal:
Won't Fix
Status in linux source package in Groovy:
Won't Fix
Status in linux-oem-5.10 source package in Groovy:
Invalid
Status in linux-oem-5.6 source package in Groovy:
Invalid
Status in linux source package in Hirsute:
Fix Released
Status in linux-oem-5.10 source package in Hirsute:
Invalid
Status in linux-oem-5.6 source package in Hirsute:
Invalid
Bug description:
[SRU Justification]
[Impact]
On platforms supported DP tunneling over USB 3.2 or so, a Retimer is
required on the host side to cover insertion loss. On such platforms the
rtimer firmware maybe configured to use LTTPR (Link Training Tunable PHY
Repeater) non-transparent mode only, which is only supported in drm-tip
currently. Without LTTPR support, link training may fail with following
error messages depending on the data path configuration:
i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful
i915 :00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun
[Fix]
Patchset https://www.spinics.net/lists/intel-gfx/msg248700.html
("drm/i915: Add support for LTTPR non-transparent link training mode")
is required to fix this issue. It has been landed to drm-tip and will
only be merged to mainline in v5.11.
Patchset https://patchwork.freedesktop.org/series/76993/ ("Plumb crtc
state to link training code") is included for link training functions
prototype changes.
[Test Case]
On Dell OptiPlex and WD19 docking station, use following steps to verify:
1. disconnect WD19 from OptiPlex, disconnect OptiPlex's power
2. attach OptiPlex's power cord
3. attach WD19's power cord
4. attach DP to WD19
5. attach WD19 to OptiPlex
6. boot up and check if boot to GUI directly
7. `dmesg` and check if aforementioned DRM link training error appears
[Where problems could occur]
The second patchset pulled for dependency doesn't have too much
effective changes but refactoring some translation functions, so very
unlikely to have regressions.
For the major part, LTTPR support, when LTTPR is either not detected or
not supported, it will fall back to use transparent mode as it was.
Otherwise, DP Standard recommends to use LTTPR non-transparent mode for
link training, so this should be the right way to have best hardware
support.
== original bug description ==
[Summary]
When the monitor ONLY is connected to the WD19 (DP port) and WD19 is
connected to the type c port than boot the machine, the monitor shows no video
output after loaded i915.
[Reproduce Steps]
1. connect power cable of WD19
2. connect DP cable from monitor to WD19
3. connect power cable to target system.
4. connect type c cable from WD19 to target system
5. boot up
[Results]
Expected: video output as there is only one monitor connected.
Actual: No video output.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.6.0-1033-oem 5.6.0-1033.35
ProcVersionSignature: Ubuntu 5.6.0-1033.35-oem 5.6.19
Uname: Linux 5.6.0-1033-oem x86_64
ApportVersion: 2.20.11-0ubuntu27.11
Architecture: amd64
CasperMD5CheckResult: skip
Date: Thu Nov 12 05:11:11 2020
DistributionChannelDescriptor:
# This is the distribution channel descriptor for the OEM CDs
# For more information see
http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-focal-amd64-20200502-85+fossa-metapod+X40
InstallationDate: Installed on 2020-11-03 (9 days ago)
InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary
20200502-05:58
SourcePackage: linux-signed-oem-5.6
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1903969/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1903969] Re: failed to boot to GUI: i915 0000:00:02.0: [drm] *ERROR* Link Training Unsuccessful
This bug was fixed in the package linux - 5.10.0-14.15 --- linux (5.10.0-14.15) hirsute; urgency=medium * hirsute/linux: 5.10.0-14.15 -proposed tracker (LP: #1913724) * Restore palm ejection on multi-input devices (LP: #1913520) - HID: multitouch: Apply MT_QUIRK_CONFIDENCE quirk for multi-input devices * intel-hid is not loaded on new Intel platform (LP: #1907160) - platform/x86: intel-hid: add Rocket Lake ACPI device ID * Hirsute update: v5.10.11 upstream stable release (LP: #1913430) - scsi: target: tcmu: Fix use-after-free of se_cmd->priv - mtd: rawnand: gpmi: fix dst bit offset when extracting raw payload - mtd: rawnand: nandsim: Fix the logic when selecting Hamming soft ECC engine - i2c: tegra: Wait for config load atomically while in ISR - i2c: bpmp-tegra: Ignore unknown I2C_M flags - platform/x86: ideapad-laptop: Disable touchpad_switch for ELAN0634 - ALSA: seq: oss: Fix missing error check in snd_seq_oss_synth_make_info() - ALSA: hda/realtek - Limit int mic boost on Acer Aspire E5-575T - ALSA: hda/via: Add minimum mute flag - crypto: xor - Fix divide error in do_xor_speed() - dm crypt: fix copy and paste bug in crypt_alloc_req_aead - ACPI: scan: Make acpi_bus_get_device() clear return pointer on error - btrfs: don't get an EINTR during drop_snapshot for reloc - btrfs: do not double free backref nodes on error - btrfs: fix lockdep splat in btrfs_recover_relocation - btrfs: don't clear ret in btrfs_start_dirty_block_groups - btrfs: send: fix invalid clone operations when cloning from the same file and root - fs: fix lazytime expiration handling in __writeback_single_inode() - pinctrl: ingenic: Fix JZ4760 support - mmc: core: don't initialize block size from ext_csd if not present - mmc: sdhci-of-dwcmshc: fix rpmb access - mmc: sdhci-xenon: fix 1.8v regulator stabilization - mmc: sdhci-brcmstb: Fix mmc timeout errors on S5 suspend - dm: avoid filesystem lookup in dm_get_dev_t() - dm integrity: fix a crash if "recalculate" used without "internal_hash" - dm integrity: conditionally disable "recalculate" feature - drm/atomic: put state on error path - drm/syncobj: Fix use-after-free - drm/amdgpu: remove gpu info firmware of green sardine - drm/amd/display: DCN2X Find Secondary Pipe properly in MPO + ODM Case - drm/i915/gt: Prevent use of engine->wa_ctx after error - drm/i915: Check for rq->hwsp validity after acquiring RCU lock - ASoC: Intel: haswell: Add missing pm_ops - ASoC: rt711: mutex between calibration and power state changes - SUNRPC: Handle TCP socket sends with kernel_sendpage() again - HID: sony: select CONFIG_CRC32 - dm integrity: select CRYPTO_SKCIPHER - x86/hyperv: Fix kexec panic/hang issues - scsi: ufs: Relax the condition of UFSHCI_QUIRK_SKIP_MANUAL_WB_FLUSH_CTRL - scsi: ufs: Correct the LUN used in eh_device_reset_handler() callback - scsi: qedi: Correct max length of CHAP secret - scsi: scsi_debug: Fix memleak in scsi_debug_init() - scsi: sd: Suppress spurious errors when WRITE SAME is being disabled - riscv: Fix kernel time_init() - riscv: Fix sifive serial driver - riscv: Enable interrupts during syscalls with M-Mode - HID: logitech-dj: add the G602 receiver - HID: Ignore battery for Elan touchscreen on ASUS UX550 - clk: tegra30: Add hda clock default rates to clock driver - ALSA: hda/tegra: fix tegra-hda on tegra30 soc - riscv: cacheinfo: Fix using smp_processor_id() in preemptible - arm64: make atomic helpers __always_inline - xen: Fix event channel callback via INTX/GSI - x86/xen: Add xen_no_vector_callback option to test PCI INTX delivery - x86/xen: Fix xen_hvm_smp_init() when vector callback not available - dts: phy: fix missing mdio device and probe failure of vsc8541-01 device - dts: phy: add GPIO number and active state used for phy reset - riscv: defconfig: enable gpio support for HiFive Unleashed - drm/amdgpu/psp: fix psp gfx ctrl cmds - drm/amd/display: disable dcn10 pipe split by default - HID: logitech-hidpp: Add product ID for MX Ergo in Bluetooth mode - drm/amd/display: Fix to be able to stop crc calculation - drm/nouveau/bios: fix issue shadowing expansion ROMs - drm/nouveau/privring: ack interrupts the same way as RM - drm/nouveau/i2c/gm200: increase width of aux semaphore owner fields - drm/nouveau/mmu: fix vram heap sizing - drm/nouveau/kms/nv50-: fix case where notifier buffer is at offset 0 - io_uring: flush timeouts that should already have expired - libperf tests: If a test fails return non-zero - libperf tests: Fail when failing to get a tracepoint id - RISC-V: Set current memblock limit - RISC-V: Fix maximum allowed phsyical memory for RV32 - x86/xen: fix 'nopvspin' build error - nfsd: Fixes for nfsd4_encode_read_plus_data()
[Kernel-packages] [Bug 1903969] Re: failed to boot to GUI: i915 0000:00:02.0: [drm] *ERROR* Link Training Unsuccessful
** Tags added: originate-from-1892304
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1903969
Title:
failed to boot to GUI: i915 :00:02.0: [drm] *ERROR* Link Training
Unsuccessful
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-5.10 package in Ubuntu:
Invalid
Status in linux-oem-5.6 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Invalid
Status in linux-oem-5.10 source package in Focal:
Fix Released
Status in linux-oem-5.6 source package in Focal:
Won't Fix
Status in linux source package in Groovy:
Won't Fix
Status in linux-oem-5.10 source package in Groovy:
Invalid
Status in linux-oem-5.6 source package in Groovy:
Invalid
Status in linux source package in Hirsute:
In Progress
Status in linux-oem-5.10 source package in Hirsute:
Invalid
Status in linux-oem-5.6 source package in Hirsute:
Invalid
Bug description:
[SRU Justification]
[Impact]
On platforms supported DP tunneling over USB 3.2 or so, a Retimer is
required on the host side to cover insertion loss. On such platforms the
rtimer firmware maybe configured to use LTTPR (Link Training Tunable PHY
Repeater) non-transparent mode only, which is only supported in drm-tip
currently. Without LTTPR support, link training may fail with following
error messages depending on the data path configuration:
i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful
i915 :00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun
[Fix]
Patchset https://www.spinics.net/lists/intel-gfx/msg248700.html
("drm/i915: Add support for LTTPR non-transparent link training mode")
is required to fix this issue. It has been landed to drm-tip and will
only be merged to mainline in v5.11.
Patchset https://patchwork.freedesktop.org/series/76993/ ("Plumb crtc
state to link training code") is included for link training functions
prototype changes.
[Test Case]
On Dell OptiPlex and WD19 docking station, use following steps to verify:
1. disconnect WD19 from OptiPlex, disconnect OptiPlex's power
2. attach OptiPlex's power cord
3. attach WD19's power cord
4. attach DP to WD19
5. attach WD19 to OptiPlex
6. boot up and check if boot to GUI directly
7. `dmesg` and check if aforementioned DRM link training error appears
[Where problems could occur]
The second patchset pulled for dependency doesn't have too much
effective changes but refactoring some translation functions, so very
unlikely to have regressions.
For the major part, LTTPR support, when LTTPR is either not detected or
not supported, it will fall back to use transparent mode as it was.
Otherwise, DP Standard recommends to use LTTPR non-transparent mode for
link training, so this should be the right way to have best hardware
support.
== original bug description ==
[Summary]
When the monitor ONLY is connected to the WD19 (DP port) and WD19 is
connected to the type c port than boot the machine, the monitor shows no video
output after loaded i915.
[Reproduce Steps]
1. connect power cable of WD19
2. connect DP cable from monitor to WD19
3. connect power cable to target system.
4. connect type c cable from WD19 to target system
5. boot up
[Results]
Expected: video output as there is only one monitor connected.
Actual: No video output.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.6.0-1033-oem 5.6.0-1033.35
ProcVersionSignature: Ubuntu 5.6.0-1033.35-oem 5.6.19
Uname: Linux 5.6.0-1033-oem x86_64
ApportVersion: 2.20.11-0ubuntu27.11
Architecture: amd64
CasperMD5CheckResult: skip
Date: Thu Nov 12 05:11:11 2020
DistributionChannelDescriptor:
# This is the distribution channel descriptor for the OEM CDs
# For more information see
http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-focal-amd64-20200502-85+fossa-metapod+X40
InstallationDate: Installed on 2020-11-03 (9 days ago)
InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary
20200502-05:58
SourcePackage: linux-signed-oem-5.6
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1903969/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1903969] Re: failed to boot to GUI: i915 0000:00:02.0: [drm] *ERROR* Link Training Unsuccessful
** Changed in: linux-oem-5.10 (Ubuntu Focal)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1903969
Title:
failed to boot to GUI: i915 :00:02.0: [drm] *ERROR* Link Training
Unsuccessful
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-5.10 package in Ubuntu:
Invalid
Status in linux-oem-5.6 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Invalid
Status in linux-oem-5.10 source package in Focal:
Fix Released
Status in linux-oem-5.6 source package in Focal:
Won't Fix
Status in linux source package in Groovy:
Won't Fix
Status in linux-oem-5.10 source package in Groovy:
Invalid
Status in linux-oem-5.6 source package in Groovy:
Invalid
Status in linux source package in Hirsute:
In Progress
Status in linux-oem-5.10 source package in Hirsute:
Invalid
Status in linux-oem-5.6 source package in Hirsute:
Invalid
Bug description:
[SRU Justification]
[Impact]
On platforms supported DP tunneling over USB 3.2 or so, a Retimer is
required on the host side to cover insertion loss. On such platforms the
rtimer firmware maybe configured to use LTTPR (Link Training Tunable PHY
Repeater) non-transparent mode only, which is only supported in drm-tip
currently. Without LTTPR support, link training may fail with following
error messages depending on the data path configuration:
i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful
i915 :00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun
[Fix]
Patchset https://www.spinics.net/lists/intel-gfx/msg248700.html
("drm/i915: Add support for LTTPR non-transparent link training mode")
is required to fix this issue. It has been landed to drm-tip and will
only be merged to mainline in v5.11.
Patchset https://patchwork.freedesktop.org/series/76993/ ("Plumb crtc
state to link training code") is included for link training functions
prototype changes.
[Test Case]
On Dell OptiPlex and WD19 docking station, use following steps to verify:
1. disconnect WD19 from OptiPlex, disconnect OptiPlex's power
2. attach OptiPlex's power cord
3. attach WD19's power cord
4. attach DP to WD19
5. attach WD19 to OptiPlex
6. boot up and check if boot to GUI directly
7. `dmesg` and check if aforementioned DRM link training error appears
[Where problems could occur]
The second patchset pulled for dependency doesn't have too much
effective changes but refactoring some translation functions, so very
unlikely to have regressions.
For the major part, LTTPR support, when LTTPR is either not detected or
not supported, it will fall back to use transparent mode as it was.
Otherwise, DP Standard recommends to use LTTPR non-transparent mode for
link training, so this should be the right way to have best hardware
support.
== original bug description ==
[Summary]
When the monitor ONLY is connected to the WD19 (DP port) and WD19 is
connected to the type c port than boot the machine, the monitor shows no video
output after loaded i915.
[Reproduce Steps]
1. connect power cable of WD19
2. connect DP cable from monitor to WD19
3. connect power cable to target system.
4. connect type c cable from WD19 to target system
5. boot up
[Results]
Expected: video output as there is only one monitor connected.
Actual: No video output.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.6.0-1033-oem 5.6.0-1033.35
ProcVersionSignature: Ubuntu 5.6.0-1033.35-oem 5.6.19
Uname: Linux 5.6.0-1033-oem x86_64
ApportVersion: 2.20.11-0ubuntu27.11
Architecture: amd64
CasperMD5CheckResult: skip
Date: Thu Nov 12 05:11:11 2020
DistributionChannelDescriptor:
# This is the distribution channel descriptor for the OEM CDs
# For more information see
http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-focal-amd64-20200502-85+fossa-metapod+X40
InstallationDate: Installed on 2020-11-03 (9 days ago)
InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary
20200502-05:58
SourcePackage: linux-signed-oem-5.6
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1903969/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1903969] Re: failed to boot to GUI: i915 0000:00:02.0: [drm] *ERROR* Link Training Unsuccessful
** Tags added: originate-from-1894066
** Tags added: originate-from-1895638
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1903969
Title:
failed to boot to GUI: i915 :00:02.0: [drm] *ERROR* Link Training
Unsuccessful
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-5.10 package in Ubuntu:
Invalid
Status in linux-oem-5.6 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Invalid
Status in linux-oem-5.10 source package in Focal:
Fix Committed
Status in linux-oem-5.6 source package in Focal:
Won't Fix
Status in linux source package in Groovy:
Won't Fix
Status in linux-oem-5.10 source package in Groovy:
Invalid
Status in linux-oem-5.6 source package in Groovy:
Invalid
Status in linux source package in Hirsute:
In Progress
Status in linux-oem-5.10 source package in Hirsute:
Invalid
Status in linux-oem-5.6 source package in Hirsute:
Invalid
Bug description:
[SRU Justification]
[Impact]
On platforms supported DP tunneling over USB 3.2 or so, a Retimer is
required on the host side to cover insertion loss. On such platforms the
rtimer firmware maybe configured to use LTTPR (Link Training Tunable PHY
Repeater) non-transparent mode only, which is only supported in drm-tip
currently. Without LTTPR support, link training may fail with following
error messages depending on the data path configuration:
i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful
i915 :00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun
[Fix]
Patchset https://www.spinics.net/lists/intel-gfx/msg248700.html
("drm/i915: Add support for LTTPR non-transparent link training mode")
is required to fix this issue. It has been landed to drm-tip and will
only be merged to mainline in v5.11.
Patchset https://patchwork.freedesktop.org/series/76993/ ("Plumb crtc
state to link training code") is included for link training functions
prototype changes.
[Test Case]
On Dell OptiPlex and WD19 docking station, use following steps to verify:
1. disconnect WD19 from OptiPlex, disconnect OptiPlex's power
2. attach OptiPlex's power cord
3. attach WD19's power cord
4. attach DP to WD19
5. attach WD19 to OptiPlex
6. boot up and check if boot to GUI directly
7. `dmesg` and check if aforementioned DRM link training error appears
[Where problems could occur]
The second patchset pulled for dependency doesn't have too much
effective changes but refactoring some translation functions, so very
unlikely to have regressions.
For the major part, LTTPR support, when LTTPR is either not detected or
not supported, it will fall back to use transparent mode as it was.
Otherwise, DP Standard recommends to use LTTPR non-transparent mode for
link training, so this should be the right way to have best hardware
support.
== original bug description ==
[Summary]
When the monitor ONLY is connected to the WD19 (DP port) and WD19 is
connected to the type c port than boot the machine, the monitor shows no video
output after loaded i915.
[Reproduce Steps]
1. connect power cable of WD19
2. connect DP cable from monitor to WD19
3. connect power cable to target system.
4. connect type c cable from WD19 to target system
5. boot up
[Results]
Expected: video output as there is only one monitor connected.
Actual: No video output.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.6.0-1033-oem 5.6.0-1033.35
ProcVersionSignature: Ubuntu 5.6.0-1033.35-oem 5.6.19
Uname: Linux 5.6.0-1033-oem x86_64
ApportVersion: 2.20.11-0ubuntu27.11
Architecture: amd64
CasperMD5CheckResult: skip
Date: Thu Nov 12 05:11:11 2020
DistributionChannelDescriptor:
# This is the distribution channel descriptor for the OEM CDs
# For more information see
http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-focal-amd64-20200502-85+fossa-metapod+X40
InstallationDate: Installed on 2020-11-03 (9 days ago)
InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary
20200502-05:58
SourcePackage: linux-signed-oem-5.6
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1903969/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1903969] Re: failed to boot to GUI: i915 0000:00:02.0: [drm] *ERROR* Link Training Unsuccessful
** Tags added: originate-from-1907526
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1903969
Title:
failed to boot to GUI: i915 :00:02.0: [drm] *ERROR* Link Training
Unsuccessful
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-5.10 package in Ubuntu:
Invalid
Status in linux-oem-5.6 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Invalid
Status in linux-oem-5.10 source package in Focal:
Fix Committed
Status in linux-oem-5.6 source package in Focal:
Won't Fix
Status in linux source package in Groovy:
Won't Fix
Status in linux-oem-5.10 source package in Groovy:
Invalid
Status in linux-oem-5.6 source package in Groovy:
Invalid
Status in linux source package in Hirsute:
In Progress
Status in linux-oem-5.10 source package in Hirsute:
Invalid
Status in linux-oem-5.6 source package in Hirsute:
Invalid
Bug description:
[SRU Justification]
[Impact]
On platforms supported DP tunneling over USB 3.2 or so, a Retimer is
required on the host side to cover insertion loss. On such platforms the
rtimer firmware maybe configured to use LTTPR (Link Training Tunable PHY
Repeater) non-transparent mode only, which is only supported in drm-tip
currently. Without LTTPR support, link training may fail with following
error messages depending on the data path configuration:
i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful
i915 :00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun
[Fix]
Patchset https://www.spinics.net/lists/intel-gfx/msg248700.html
("drm/i915: Add support for LTTPR non-transparent link training mode")
is required to fix this issue. It has been landed to drm-tip and will
only be merged to mainline in v5.11.
Patchset https://patchwork.freedesktop.org/series/76993/ ("Plumb crtc
state to link training code") is included for link training functions
prototype changes.
[Test Case]
On Dell OptiPlex and WD19 docking station, use following steps to verify:
1. disconnect WD19 from OptiPlex, disconnect OptiPlex's power
2. attach OptiPlex's power cord
3. attach WD19's power cord
4. attach DP to WD19
5. attach WD19 to OptiPlex
6. boot up and check if boot to GUI directly
7. `dmesg` and check if aforementioned DRM link training error appears
[Where problems could occur]
The second patchset pulled for dependency doesn't have too much
effective changes but refactoring some translation functions, so very
unlikely to have regressions.
For the major part, LTTPR support, when LTTPR is either not detected or
not supported, it will fall back to use transparent mode as it was.
Otherwise, DP Standard recommends to use LTTPR non-transparent mode for
link training, so this should be the right way to have best hardware
support.
== original bug description ==
[Summary]
When the monitor ONLY is connected to the WD19 (DP port) and WD19 is
connected to the type c port than boot the machine, the monitor shows no video
output after loaded i915.
[Reproduce Steps]
1. connect power cable of WD19
2. connect DP cable from monitor to WD19
3. connect power cable to target system.
4. connect type c cable from WD19 to target system
5. boot up
[Results]
Expected: video output as there is only one monitor connected.
Actual: No video output.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.6.0-1033-oem 5.6.0-1033.35
ProcVersionSignature: Ubuntu 5.6.0-1033.35-oem 5.6.19
Uname: Linux 5.6.0-1033-oem x86_64
ApportVersion: 2.20.11-0ubuntu27.11
Architecture: amd64
CasperMD5CheckResult: skip
Date: Thu Nov 12 05:11:11 2020
DistributionChannelDescriptor:
# This is the distribution channel descriptor for the OEM CDs
# For more information see
http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-focal-amd64-20200502-85+fossa-metapod+X40
InstallationDate: Installed on 2020-11-03 (9 days ago)
InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary
20200502-05:58
SourcePackage: linux-signed-oem-5.6
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1903969/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1903969] Re: failed to boot to GUI: i915 0000:00:02.0: [drm] *ERROR* Link Training Unsuccessful
These patches have been merged into mainline via drm-next-2020-12-18 for
v5.11.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1903969
Title:
failed to boot to GUI: i915 :00:02.0: [drm] *ERROR* Link Training
Unsuccessful
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-5.10 package in Ubuntu:
Invalid
Status in linux-oem-5.6 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Invalid
Status in linux-oem-5.10 source package in Focal:
Fix Committed
Status in linux-oem-5.6 source package in Focal:
Won't Fix
Status in linux source package in Groovy:
Won't Fix
Status in linux-oem-5.10 source package in Groovy:
Invalid
Status in linux-oem-5.6 source package in Groovy:
Invalid
Status in linux source package in Hirsute:
In Progress
Status in linux-oem-5.10 source package in Hirsute:
Invalid
Status in linux-oem-5.6 source package in Hirsute:
Invalid
Bug description:
[SRU Justification]
[Impact]
On platforms supported DP tunneling over USB 3.2 or so, a Retimer is
required on the host side to cover insertion loss. On such platforms the
rtimer firmware maybe configured to use LTTPR (Link Training Tunable PHY
Repeater) non-transparent mode only, which is only supported in drm-tip
currently. Without LTTPR support, link training may fail with following
error messages depending on the data path configuration:
i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful
i915 :00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun
[Fix]
Patchset https://www.spinics.net/lists/intel-gfx/msg248700.html
("drm/i915: Add support for LTTPR non-transparent link training mode")
is required to fix this issue. It has been landed to drm-tip and will
only be merged to mainline in v5.11.
Patchset https://patchwork.freedesktop.org/series/76993/ ("Plumb crtc
state to link training code") is included for link training functions
prototype changes.
[Test Case]
On Dell OptiPlex and WD19 docking station, use following steps to verify:
1. disconnect WD19 from OptiPlex, disconnect OptiPlex's power
2. attach OptiPlex's power cord
3. attach WD19's power cord
4. attach DP to WD19
5. attach WD19 to OptiPlex
6. boot up and check if boot to GUI directly
7. `dmesg` and check if aforementioned DRM link training error appears
[Where problems could occur]
The second patchset pulled for dependency doesn't have too much
effective changes but refactoring some translation functions, so very
unlikely to have regressions.
For the major part, LTTPR support, when LTTPR is either not detected or
not supported, it will fall back to use transparent mode as it was.
Otherwise, DP Standard recommends to use LTTPR non-transparent mode for
link training, so this should be the right way to have best hardware
support.
== original bug description ==
[Summary]
When the monitor ONLY is connected to the WD19 (DP port) and WD19 is
connected to the type c port than boot the machine, the monitor shows no video
output after loaded i915.
[Reproduce Steps]
1. connect power cable of WD19
2. connect DP cable from monitor to WD19
3. connect power cable to target system.
4. connect type c cable from WD19 to target system
5. boot up
[Results]
Expected: video output as there is only one monitor connected.
Actual: No video output.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.6.0-1033-oem 5.6.0-1033.35
ProcVersionSignature: Ubuntu 5.6.0-1033.35-oem 5.6.19
Uname: Linux 5.6.0-1033-oem x86_64
ApportVersion: 2.20.11-0ubuntu27.11
Architecture: amd64
CasperMD5CheckResult: skip
Date: Thu Nov 12 05:11:11 2020
DistributionChannelDescriptor:
# This is the distribution channel descriptor for the OEM CDs
# For more information see
http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-focal-amd64-20200502-85+fossa-metapod+X40
InstallationDate: Installed on 2020-11-03 (9 days ago)
InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary
20200502-05:58
SourcePackage: linux-signed-oem-5.6
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1903969/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1903969] Re: failed to boot to GUI: i915 0000:00:02.0: [drm] *ERROR* Link Training Unsuccessful
oem-5.6 will be eol in two months, most likely too late to get a big
backport in it
** Changed in: linux-oem-5.6 (Ubuntu Focal)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1903969
Title:
failed to boot to GUI: i915 :00:02.0: [drm] *ERROR* Link Training
Unsuccessful
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-5.10 package in Ubuntu:
Invalid
Status in linux-oem-5.6 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Invalid
Status in linux-oem-5.10 source package in Focal:
Fix Committed
Status in linux-oem-5.6 source package in Focal:
Won't Fix
Status in linux source package in Groovy:
Won't Fix
Status in linux-oem-5.10 source package in Groovy:
Invalid
Status in linux-oem-5.6 source package in Groovy:
Invalid
Status in linux source package in Hirsute:
In Progress
Status in linux-oem-5.10 source package in Hirsute:
Invalid
Status in linux-oem-5.6 source package in Hirsute:
Invalid
Bug description:
[SRU Justification]
[Impact]
On platforms supported DP tunneling over USB 3.2 or so, a Retimer is
required on the host side to cover insertion loss. On such platforms the
rtimer firmware maybe configured to use LTTPR (Link Training Tunable PHY
Repeater) non-transparent mode only, which is only supported in drm-tip
currently. Without LTTPR support, link training may fail with following
error messages depending on the data path configuration:
i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful
i915 :00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun
[Fix]
Patchset https://www.spinics.net/lists/intel-gfx/msg248700.html
("drm/i915: Add support for LTTPR non-transparent link training mode")
is required to fix this issue. It has been landed to drm-tip and will
only be merged to mainline in v5.11.
Patchset https://patchwork.freedesktop.org/series/76993/ ("Plumb crtc
state to link training code") is included for link training functions
prototype changes.
[Test Case]
On Dell OptiPlex and WD19 docking station, use following steps to verify:
1. disconnect WD19 from OptiPlex, disconnect OptiPlex's power
2. attach OptiPlex's power cord
3. attach WD19's power cord
4. attach DP to WD19
5. attach WD19 to OptiPlex
6. boot up and check if boot to GUI directly
7. `dmesg` and check if aforementioned DRM link training error appears
[Where problems could occur]
The second patchset pulled for dependency doesn't have too much
effective changes but refactoring some translation functions, so very
unlikely to have regressions.
For the major part, LTTPR support, when LTTPR is either not detected or
not supported, it will fall back to use transparent mode as it was.
Otherwise, DP Standard recommends to use LTTPR non-transparent mode for
link training, so this should be the right way to have best hardware
support.
== original bug description ==
[Summary]
When the monitor ONLY is connected to the WD19 (DP port) and WD19 is
connected to the type c port than boot the machine, the monitor shows no video
output after loaded i915.
[Reproduce Steps]
1. connect power cable of WD19
2. connect DP cable from monitor to WD19
3. connect power cable to target system.
4. connect type c cable from WD19 to target system
5. boot up
[Results]
Expected: video output as there is only one monitor connected.
Actual: No video output.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.6.0-1033-oem 5.6.0-1033.35
ProcVersionSignature: Ubuntu 5.6.0-1033.35-oem 5.6.19
Uname: Linux 5.6.0-1033-oem x86_64
ApportVersion: 2.20.11-0ubuntu27.11
Architecture: amd64
CasperMD5CheckResult: skip
Date: Thu Nov 12 05:11:11 2020
DistributionChannelDescriptor:
# This is the distribution channel descriptor for the OEM CDs
# For more information see
http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-focal-amd64-20200502-85+fossa-metapod+X40
InstallationDate: Installed on 2020-11-03 (9 days ago)
InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary
20200502-05:58
SourcePackage: linux-signed-oem-5.6
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1903969/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1903969] Re: failed to boot to GUI: i915 0000:00:02.0: [drm] *ERROR* Link Training Unsuccessful
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1903969
Title:
failed to boot to GUI: i915 :00:02.0: [drm] *ERROR* Link Training
Unsuccessful
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-5.10 package in Ubuntu:
Invalid
Status in linux-oem-5.6 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Invalid
Status in linux-oem-5.10 source package in Focal:
Fix Committed
Status in linux-oem-5.6 source package in Focal:
New
Status in linux source package in Groovy:
Won't Fix
Status in linux-oem-5.10 source package in Groovy:
Invalid
Status in linux-oem-5.6 source package in Groovy:
Invalid
Status in linux source package in Hirsute:
In Progress
Status in linux-oem-5.10 source package in Hirsute:
Invalid
Status in linux-oem-5.6 source package in Hirsute:
Invalid
Bug description:
[SRU Justification]
[Impact]
On platforms supported DP tunneling over USB 3.2 or so, a Retimer is
required on the host side to cover insertion loss. On such platforms the
rtimer firmware maybe configured to use LTTPR (Link Training Tunable PHY
Repeater) non-transparent mode only, which is only supported in drm-tip
currently. Without LTTPR support, link training may fail with following
error messages depending on the data path configuration:
i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful
i915 :00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun
[Fix]
Patchset https://www.spinics.net/lists/intel-gfx/msg248700.html
("drm/i915: Add support for LTTPR non-transparent link training mode")
is required to fix this issue. It has been landed to drm-tip and will
only be merged to mainline in v5.11.
Patchset https://patchwork.freedesktop.org/series/76993/ ("Plumb crtc
state to link training code") is included for link training functions
prototype changes.
[Test Case]
On Dell OptiPlex and WD19 docking station, use following steps to verify:
1. disconnect WD19 from OptiPlex, disconnect OptiPlex's power
2. attach OptiPlex's power cord
3. attach WD19's power cord
4. attach DP to WD19
5. attach WD19 to OptiPlex
6. boot up and check if boot to GUI directly
7. `dmesg` and check if aforementioned DRM link training error appears
[Where problems could occur]
The second patchset pulled for dependency doesn't have too much
effective changes but refactoring some translation functions, so very
unlikely to have regressions.
For the major part, LTTPR support, when LTTPR is either not detected or
not supported, it will fall back to use transparent mode as it was.
Otherwise, DP Standard recommends to use LTTPR non-transparent mode for
link training, so this should be the right way to have best hardware
support.
== original bug description ==
[Summary]
When the monitor ONLY is connected to the WD19 (DP port) and WD19 is
connected to the type c port than boot the machine, the monitor shows no video
output after loaded i915.
[Reproduce Steps]
1. connect power cable of WD19
2. connect DP cable from monitor to WD19
3. connect power cable to target system.
4. connect type c cable from WD19 to target system
5. boot up
[Results]
Expected: video output as there is only one monitor connected.
Actual: No video output.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.6.0-1033-oem 5.6.0-1033.35
ProcVersionSignature: Ubuntu 5.6.0-1033.35-oem 5.6.19
Uname: Linux 5.6.0-1033-oem x86_64
ApportVersion: 2.20.11-0ubuntu27.11
Architecture: amd64
CasperMD5CheckResult: skip
Date: Thu Nov 12 05:11:11 2020
DistributionChannelDescriptor:
# This is the distribution channel descriptor for the OEM CDs
# For more information see
http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-focal-amd64-20200502-85+fossa-metapod+X40
InstallationDate: Installed on 2020-11-03 (9 days ago)
InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary
20200502-05:58
SourcePackage: linux-signed-oem-5.6
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1903969/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1903969] Re: failed to boot to GUI: i915 0000:00:02.0: [drm] *ERROR* Link Training Unsuccessful
Kernel in proposed solved the problem, system can now boot correctly
with monitor connected on WD19 docking, with docking connected on system
TBT port. Done 10 cold boot and 10 warm boot cycles, all pass.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1903969
Title:
failed to boot to GUI: i915 :00:02.0: [drm] *ERROR* Link Training
Unsuccessful
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-5.10 package in Ubuntu:
Invalid
Status in linux-oem-5.6 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Invalid
Status in linux-oem-5.10 source package in Focal:
Fix Committed
Status in linux-oem-5.6 source package in Focal:
New
Status in linux source package in Groovy:
Won't Fix
Status in linux-oem-5.10 source package in Groovy:
Invalid
Status in linux-oem-5.6 source package in Groovy:
Invalid
Status in linux source package in Hirsute:
In Progress
Status in linux-oem-5.10 source package in Hirsute:
Invalid
Status in linux-oem-5.6 source package in Hirsute:
Invalid
Bug description:
[SRU Justification]
[Impact]
On platforms supported DP tunneling over USB 3.2 or so, a Retimer is
required on the host side to cover insertion loss. On such platforms the
rtimer firmware maybe configured to use LTTPR (Link Training Tunable PHY
Repeater) non-transparent mode only, which is only supported in drm-tip
currently. Without LTTPR support, link training may fail with following
error messages depending on the data path configuration:
i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful
i915 :00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun
[Fix]
Patchset https://www.spinics.net/lists/intel-gfx/msg248700.html
("drm/i915: Add support for LTTPR non-transparent link training mode")
is required to fix this issue. It has been landed to drm-tip and will
only be merged to mainline in v5.11.
Patchset https://patchwork.freedesktop.org/series/76993/ ("Plumb crtc
state to link training code") is included for link training functions
prototype changes.
[Test Case]
On Dell OptiPlex and WD19 docking station, use following steps to verify:
1. disconnect WD19 from OptiPlex, disconnect OptiPlex's power
2. attach OptiPlex's power cord
3. attach WD19's power cord
4. attach DP to WD19
5. attach WD19 to OptiPlex
6. boot up and check if boot to GUI directly
7. `dmesg` and check if aforementioned DRM link training error appears
[Where problems could occur]
The second patchset pulled for dependency doesn't have too much
effective changes but refactoring some translation functions, so very
unlikely to have regressions.
For the major part, LTTPR support, when LTTPR is either not detected or
not supported, it will fall back to use transparent mode as it was.
Otherwise, DP Standard recommends to use LTTPR non-transparent mode for
link training, so this should be the right way to have best hardware
support.
== original bug description ==
[Summary]
When the monitor ONLY is connected to the WD19 (DP port) and WD19 is
connected to the type c port than boot the machine, the monitor shows no video
output after loaded i915.
[Reproduce Steps]
1. connect power cable of WD19
2. connect DP cable from monitor to WD19
3. connect power cable to target system.
4. connect type c cable from WD19 to target system
5. boot up
[Results]
Expected: video output as there is only one monitor connected.
Actual: No video output.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.6.0-1033-oem 5.6.0-1033.35
ProcVersionSignature: Ubuntu 5.6.0-1033.35-oem 5.6.19
Uname: Linux 5.6.0-1033-oem x86_64
ApportVersion: 2.20.11-0ubuntu27.11
Architecture: amd64
CasperMD5CheckResult: skip
Date: Thu Nov 12 05:11:11 2020
DistributionChannelDescriptor:
# This is the distribution channel descriptor for the OEM CDs
# For more information see
http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-focal-amd64-20200502-85+fossa-metapod+X40
InstallationDate: Installed on 2020-11-03 (9 days ago)
InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary
20200502-05:58
SourcePackage: linux-signed-oem-5.6
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1903969/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1903969] Re: failed to boot to GUI: i915 0000:00:02.0: [drm] *ERROR* Link Training Unsuccessful
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
focal' to 'verification-done-focal'. If the problem still exists, change
the tag 'verification-needed-focal' to 'verification-failed-focal'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: verification-needed-focal
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1903969
Title:
failed to boot to GUI: i915 :00:02.0: [drm] *ERROR* Link Training
Unsuccessful
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-5.10 package in Ubuntu:
Invalid
Status in linux-oem-5.6 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Invalid
Status in linux-oem-5.10 source package in Focal:
Fix Committed
Status in linux-oem-5.6 source package in Focal:
New
Status in linux source package in Groovy:
Won't Fix
Status in linux-oem-5.10 source package in Groovy:
Invalid
Status in linux-oem-5.6 source package in Groovy:
Invalid
Status in linux source package in Hirsute:
In Progress
Status in linux-oem-5.10 source package in Hirsute:
Invalid
Status in linux-oem-5.6 source package in Hirsute:
Invalid
Bug description:
[SRU Justification]
[Impact]
On platforms supported DP tunneling over USB 3.2 or so, a Retimer is
required on the host side to cover insertion loss. On such platforms the
rtimer firmware maybe configured to use LTTPR (Link Training Tunable PHY
Repeater) non-transparent mode only, which is only supported in drm-tip
currently. Without LTTPR support, link training may fail with following
error messages depending on the data path configuration:
i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful
i915 :00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun
[Fix]
Patchset https://www.spinics.net/lists/intel-gfx/msg248700.html
("drm/i915: Add support for LTTPR non-transparent link training mode")
is required to fix this issue. It has been landed to drm-tip and will
only be merged to mainline in v5.11.
Patchset https://patchwork.freedesktop.org/series/76993/ ("Plumb crtc
state to link training code") is included for link training functions
prototype changes.
[Test Case]
On Dell OptiPlex and WD19 docking station, use following steps to verify:
1. disconnect WD19 from OptiPlex, disconnect OptiPlex's power
2. attach OptiPlex's power cord
3. attach WD19's power cord
4. attach DP to WD19
5. attach WD19 to OptiPlex
6. boot up and check if boot to GUI directly
7. `dmesg` and check if aforementioned DRM link training error appears
[Where problems could occur]
The second patchset pulled for dependency doesn't have too much
effective changes but refactoring some translation functions, so very
unlikely to have regressions.
For the major part, LTTPR support, when LTTPR is either not detected or
not supported, it will fall back to use transparent mode as it was.
Otherwise, DP Standard recommends to use LTTPR non-transparent mode for
link training, so this should be the right way to have best hardware
support.
== original bug description ==
[Summary]
When the monitor ONLY is connected to the WD19 (DP port) and WD19 is
connected to the type c port than boot the machine, the monitor shows no video
output after loaded i915.
[Reproduce Steps]
1. connect power cable of WD19
2. connect DP cable from monitor to WD19
3. connect power cable to target system.
4. connect type c cable from WD19 to target system
5. boot up
[Results]
Expected: video output as there is only one monitor connected.
Actual: No video output.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.6.0-1033-oem 5.6.0-1033.35
ProcVersionSignature: Ubuntu 5.6.0-1033.35-oem 5.6.19
Uname: Linux 5.6.0-1033-oem x86_64
ApportVersion: 2.20.11-0ubuntu27.11
Architecture: amd64
CasperMD5CheckResult: skip
Date: Thu Nov 12 05:11:11 2020
DistributionChannelDescriptor:
# This is the distribution channel descriptor for the OEM CDs
# For more information see
http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-focal-amd64-20200502-85+fossa-metapod+X40
InstallationDate: Installed on 2020-11-03 (9 days ago)
InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary
20200502-05:58
SourcePackage: linux-signed-oem-5.6
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
[Kernel-packages] [Bug 1903969] Re: failed to boot to GUI: i915 0000:00:02.0: [drm] *ERROR* Link Training Unsuccessful
** Changed in: linux-oem-5.10 (Ubuntu Focal)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Groovy)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1903969
Title:
failed to boot to GUI: i915 :00:02.0: [drm] *ERROR* Link Training
Unsuccessful
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-5.10 package in Ubuntu:
Invalid
Status in linux-oem-5.6 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Invalid
Status in linux-oem-5.10 source package in Focal:
Fix Committed
Status in linux-oem-5.6 source package in Focal:
New
Status in linux source package in Groovy:
Won't Fix
Status in linux-oem-5.10 source package in Groovy:
Invalid
Status in linux-oem-5.6 source package in Groovy:
Invalid
Status in linux source package in Hirsute:
In Progress
Status in linux-oem-5.10 source package in Hirsute:
Invalid
Status in linux-oem-5.6 source package in Hirsute:
Invalid
Bug description:
[SRU Justification]
[Impact]
On platforms supported DP tunneling over USB 3.2 or so, a Retimer is
required on the host side to cover insertion loss. On such platforms the
rtimer firmware maybe configured to use LTTPR (Link Training Tunable PHY
Repeater) non-transparent mode only, which is only supported in drm-tip
currently. Without LTTPR support, link training may fail with following
error messages depending on the data path configuration:
i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful
i915 :00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun
[Fix]
Patchset https://www.spinics.net/lists/intel-gfx/msg248700.html
("drm/i915: Add support for LTTPR non-transparent link training mode")
is required to fix this issue. It has been landed to drm-tip and will
only be merged to mainline in v5.11.
Patchset https://patchwork.freedesktop.org/series/76993/ ("Plumb crtc
state to link training code") is included for link training functions
prototype changes.
[Test Case]
On Dell OptiPlex and WD19 docking station, use following steps to verify:
1. disconnect WD19 from OptiPlex, disconnect OptiPlex's power
2. attach OptiPlex's power cord
3. attach WD19's power cord
4. attach DP to WD19
5. attach WD19 to OptiPlex
6. boot up and check if boot to GUI directly
7. `dmesg` and check if aforementioned DRM link training error appears
[Where problems could occur]
The second patchset pulled for dependency doesn't have too much
effective changes but refactoring some translation functions, so very
unlikely to have regressions.
For the major part, LTTPR support, when LTTPR is either not detected or
not supported, it will fall back to use transparent mode as it was.
Otherwise, DP Standard recommends to use LTTPR non-transparent mode for
link training, so this should be the right way to have best hardware
support.
== original bug description ==
[Summary]
When the monitor ONLY is connected to the WD19 (DP port) and WD19 is
connected to the type c port than boot the machine, the monitor shows no video
output after loaded i915.
[Reproduce Steps]
1. connect power cable of WD19
2. connect DP cable from monitor to WD19
3. connect power cable to target system.
4. connect type c cable from WD19 to target system
5. boot up
[Results]
Expected: video output as there is only one monitor connected.
Actual: No video output.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.6.0-1033-oem 5.6.0-1033.35
ProcVersionSignature: Ubuntu 5.6.0-1033.35-oem 5.6.19
Uname: Linux 5.6.0-1033-oem x86_64
ApportVersion: 2.20.11-0ubuntu27.11
Architecture: amd64
CasperMD5CheckResult: skip
Date: Thu Nov 12 05:11:11 2020
DistributionChannelDescriptor:
# This is the distribution channel descriptor for the OEM CDs
# For more information see
http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-focal-amd64-20200502-85+fossa-metapod+X40
InstallationDate: Installed on 2020-11-03 (9 days ago)
InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary
20200502-05:58
SourcePackage: linux-signed-oem-5.6
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1903969/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1903969] Re: failed to boot to GUI: i915 0000:00:02.0: [drm] *ERROR* Link Training Unsuccessful
** Description changed:
[SRU Justification]
[Impact]
On platforms supported DP tunneling over USB 3.2 or so, a Retimer is
required on the host side to cover insertion loss. On such platforms the
rtimer firmware maybe configured to use LTTPR (Link Training Tunable PHY
Repeater) non-transparent mode only, which is only supported in drm-tip
currently. Without LTTPR support, link training may fail with following
error messages depending on the data path configuration:
- i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful
- i915 :00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun
+ i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful
+ i915 :00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun
[Fix]
Patchset https://www.spinics.net/lists/intel-gfx/msg248700.html
("drm/i915: Add support for LTTPR non-transparent link training mode")
is required to fix this issue. It has been landed to drm-tip and will
only included to mainline in v5.11.
Patchset https://patchwork.freedesktop.org/series/76993/ ("Plumb crtc
state to link training code") is included for link training functions
prototype changes.
[Test Case]
On Dell OptiPlex and WD19 docking station, use following steps to verify:
1. disconnect WD19 from OptiPlex, disconnect OptiPlex's power
2. attach OptiPlex's power cord
3. attach WD19's power cord
4. attach DP to WD19
5. attach WD19 to OptiPlex
6. boot up and check if boot to GUI directly
7. `dmesg` and check if aforementioned DRM link training error appears
- [Regression Potential]
+ [Where problems could occur]
The second patchset pulled for dependency doesn't have too much
effective changes but refactoring some translation functions, so very
unlikely to have regressions.
For the major part, LTTPR support, when LTTPR is either not detected or
not supported, it will fall back to use transparent mode as it was.
Otherwise, DP Standard recommends to use LTTPR non-transparent mode for
link training, so this should be the right way to have best hardware
support.
== original bug description ==
[Summary]
When the monitor ONLY is connected to the WD19 (DP port) and WD19 is
connected to the type c port than boot the machine, the monitor shows no video
output after loaded i915.
[Reproduce Steps]
1. connect power cable of WD19
2. connect DP cable from monitor to WD19
3. connect power cable to target system.
4. connect type c cable from WD19 to target system
5. boot up
[Results]
Expected: video output as there is only one monitor connected.
Actual: No video output.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.6.0-1033-oem 5.6.0-1033.35
ProcVersionSignature: Ubuntu 5.6.0-1033.35-oem 5.6.19
Uname: Linux 5.6.0-1033-oem x86_64
ApportVersion: 2.20.11-0ubuntu27.11
Architecture: amd64
CasperMD5CheckResult: skip
Date: Thu Nov 12 05:11:11 2020
DistributionChannelDescriptor:
# This is the distribution channel descriptor for the OEM CDs
# For more information see
http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-focal-amd64-20200502-85+fossa-metapod+X40
InstallationDate: Installed on 2020-11-03 (9 days ago)
InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary
20200502-05:58
SourcePackage: linux-signed-oem-5.6
UpgradeStatus: No upgrade log present (probably fresh install)
** Description changed:
[SRU Justification]
[Impact]
On platforms supported DP tunneling over USB 3.2 or so, a Retimer is
required on the host side to cover insertion loss. On such platforms the
rtimer firmware maybe configured to use LTTPR (Link Training Tunable PHY
Repeater) non-transparent mode only, which is only supported in drm-tip
currently. Without LTTPR support, link training may fail with following
error messages depending on the data path configuration:
i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful
i915 :00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun
[Fix]
Patchset https://www.spinics.net/lists/intel-gfx/msg248700.html
("drm/i915: Add support for LTTPR non-transparent link training mode")
is required to fix this issue. It has been landed to drm-tip and will
- only included to mainline in v5.11.
+ only be merged to mainline in v5.11.
Patchset https://patchwork.freedesktop.org/series/76993/ ("Plumb crtc
state to link training code") is included for link training functions
prototype changes.
[Test Case]
On Dell OptiPlex and WD19 docking station, use following steps to verify:
1. disconnect WD19 from OptiPlex, disconnect OptiPlex's power
2. attach OptiPlex's power cord
3. attach WD19's power cord
4. attach DP to WD19
5. attach WD19 to OptiPlex
6. boot up and check if boot to GUI directly
7. `dmesg` and check if aforementioned DRM link training error appears
[Where problems could
[Kernel-packages] [Bug 1903969] Re: failed to boot to GUI: i915 0000:00:02.0: [drm] *ERROR* Link Training Unsuccessful
SRU: https://lists.ubuntu.com/archives/kernel-
team/2020-November/115002.html (G & H)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1903969
Title:
failed to boot to GUI: i915 :00:02.0: [drm] *ERROR* Link Training
Unsuccessful
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-5.10 package in Ubuntu:
Invalid
Status in linux-oem-5.6 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Invalid
Status in linux-oem-5.10 source package in Focal:
In Progress
Status in linux-oem-5.6 source package in Focal:
New
Status in linux source package in Groovy:
New
Status in linux-oem-5.10 source package in Groovy:
Invalid
Status in linux-oem-5.6 source package in Groovy:
Invalid
Status in linux source package in Hirsute:
In Progress
Status in linux-oem-5.10 source package in Hirsute:
Invalid
Status in linux-oem-5.6 source package in Hirsute:
Invalid
Bug description:
[SRU Justification]
[Impact]
On platforms supported DP tunneling over USB 3.2 or so, a Retimer is
required on the host side to cover insertion loss. On such platforms the
rtimer firmware maybe configured to use LTTPR (Link Training Tunable PHY
Repeater) non-transparent mode only, which is only supported in drm-tip
currently. Without LTTPR support, link training may fail with following
error messages depending on the data path configuration:
i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful
i915 :00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun
[Fix]
Patchset https://www.spinics.net/lists/intel-gfx/msg248700.html
("drm/i915: Add support for LTTPR non-transparent link training mode")
is required to fix this issue. It has been landed to drm-tip and will
only included to mainline in v5.11.
Patchset https://patchwork.freedesktop.org/series/76993/ ("Plumb crtc
state to link training code") is included for link training functions
prototype changes.
[Test Case]
On Dell OptiPlex and WD19 docking station, use following steps to verify:
1. disconnect WD19 from OptiPlex, disconnect OptiPlex's power
2. attach OptiPlex's power cord
3. attach WD19's power cord
4. attach DP to WD19
5. attach WD19 to OptiPlex
6. boot up and check if boot to GUI directly
7. `dmesg` and check if aforementioned DRM link training error appears
[Regression Potential]
The second patchset pulled for dependency doesn't have too much
effective changes but refactoring some translation functions, so very
unlikely to have regressions.
For the major part, LTTPR support, when LTTPR is either not detected or
not supported, it will fall back to use transparent mode as it was.
Otherwise, DP Standard recommends to use LTTPR non-transparent mode for
link training, so this should be the right way to have best hardware
support.
== original bug description ==
[Summary]
When the monitor ONLY is connected to the WD19 (DP port) and WD19 is
connected to the type c port than boot the machine, the monitor shows no video
output after loaded i915.
[Reproduce Steps]
1. connect power cable of WD19
2. connect DP cable from monitor to WD19
3. connect power cable to target system.
4. connect type c cable from WD19 to target system
5. boot up
[Results]
Expected: video output as there is only one monitor connected.
Actual: No video output.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.6.0-1033-oem 5.6.0-1033.35
ProcVersionSignature: Ubuntu 5.6.0-1033.35-oem 5.6.19
Uname: Linux 5.6.0-1033-oem x86_64
ApportVersion: 2.20.11-0ubuntu27.11
Architecture: amd64
CasperMD5CheckResult: skip
Date: Thu Nov 12 05:11:11 2020
DistributionChannelDescriptor:
# This is the distribution channel descriptor for the OEM CDs
# For more information see
http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-focal-amd64-20200502-85+fossa-metapod+X40
InstallationDate: Installed on 2020-11-03 (9 days ago)
InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary
20200502-05:58
SourcePackage: linux-signed-oem-5.6
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1903969/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1903969] Re: failed to boot to GUI: i915 0000:00:02.0: [drm] *ERROR* Link Training Unsuccessful
SRU: https://lists.ubuntu.com/archives/kernel-
team/2020-November/114986.html (unstable & oem-5.10)
** Changed in: linux-oem-5.10 (Ubuntu Focal)
Importance: Undecided => High
** Changed in: linux-oem-5.10 (Ubuntu Focal)
Status: New => In Progress
** Changed in: linux-oem-5.10 (Ubuntu Focal)
Assignee: (unassigned) => You-Sheng Yang (vicamo)
** Changed in: linux (Ubuntu Focal)
Status: New => Invalid
** Description changed:
+ [SRU Justification]
+
+ [Impact]
+
+ On platforms supported DP tunneling over USB 3.2 or so, a Retimer is
+ required on the host side to cover insertion loss. On such platforms the
+ rtimer firmware maybe configured to use LTTPR (Link Training Tunable PHY
+ Repeater) non-transparent mode only, which is only supported in drm-tip
+ currently. Without LTTPR support, link training may fail with following
+ error messages depending on the data path configuration:
+
+ i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful
+ i915 :00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun
+
+ [Fix]
+
+ Patchset https://www.spinics.net/lists/intel-gfx/msg248700.html
+ ("drm/i915: Add support for LTTPR non-transparent link training mode")
+ is required to fix this issue. It has been landed to drm-tip and will
+ only included to mainline in v5.11.
+
+ Patchset https://patchwork.freedesktop.org/series/76993/ ("Plumb crtc
+ state to link training code") is included for link training functions
+ prototype changes.
+
+ [Test Case]
+
+ On Dell OptiPlex and WD19 docking station, use following steps to verify:
+ 1. disconnect WD19 from OptiPlex, disconnect OptiPlex's power
+ 2. attach OptiPlex's power cord
+ 3. attach WD19's power cord
+ 4. attach DP to WD19
+ 5. attach WD19 to OptiPlex
+ 6. boot up and check if boot to GUI directly
+ 7. `dmesg` and check if aforementioned DRM link training error appears
+
+ [Regression Potential]
+
+ The second patchset pulled for dependency doesn't have too much
+ effective changes but refactoring some translation functions, so very
+ unlikely to have regressions.
+
+ For the major part, LTTPR support, when LTTPR is either not detected or
+ not supported, it will fall back to use transparent mode as it was.
+ Otherwise, DP Standard recommends to use LTTPR non-transparent mode for
+ link training, so this should be the right way to have best hardware
+ support.
+
+ == original bug description ==
+
[Summary]
When the monitor ONLY is connected to the WD19 (DP port) and WD19 is
connected to the type c port than boot the machine, the monitor shows no video
output after loaded i915.
[Reproduce Steps]
1. connect power cable of WD19
2. connect DP cable from monitor to WD19
3. connect power cable to target system.
4. connect type c cable from WD19 to target system
5. boot up
[Results]
Expected: video output as there is only one monitor connected.
Actual: No video output.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.6.0-1033-oem 5.6.0-1033.35
ProcVersionSignature: Ubuntu 5.6.0-1033.35-oem 5.6.19
Uname: Linux 5.6.0-1033-oem x86_64
ApportVersion: 2.20.11-0ubuntu27.11
Architecture: amd64
CasperMD5CheckResult: skip
Date: Thu Nov 12 05:11:11 2020
DistributionChannelDescriptor:
- # This is the distribution channel descriptor for the OEM CDs
- # For more information see
http://wiki.ubuntu.com/DistributionChannelDescriptor
- canonical-oem-somerville-focal-amd64-20200502-85+fossa-metapod+X40
+ # This is the distribution channel descriptor for the OEM CDs
+ # For more information see
http://wiki.ubuntu.com/DistributionChannelDescriptor
+ canonical-oem-somerville-focal-amd64-20200502-85+fossa-metapod+X40
InstallationDate: Installed on 2020-11-03 (9 days ago)
InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary
20200502-05:58
SourcePackage: linux-signed-oem-5.6
UpgradeStatus: No upgrade log present (probably fresh install)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1903969
Title:
failed to boot to GUI: i915 :00:02.0: [drm] *ERROR* Link Training
Unsuccessful
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-5.10 package in Ubuntu:
Invalid
Status in linux-oem-5.6 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Invalid
Status in linux-oem-5.10 source package in Focal:
In Progress
Status in linux-oem-5.6 source package in Focal:
New
Status in linux source package in Groovy:
New
Status in linux-oem-5.10 source package in Groovy:
Invalid
Status in linux-oem-5.6 source package in Groovy:
Invalid
Status in linux source package in Hirsute:
In Progress
Status in linux-oem-5.10 source package in Hirsute:
Invalid
Status in linux-oem-5.6 source package in Hirsute:
Invalid
Bug description:
[SRU Justification]
[Impact]
[Kernel-packages] [Bug 1903969] Re: failed to boot to GUI: i915 0000:00:02.0: [drm] *ERROR* Link Training Unsuccessful
** Also affects: linux-oem-5.10 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem-5.10 (Ubuntu Groovy) Status: New => Invalid ** Changed in: linux-oem-5.6 (Ubuntu Groovy) Status: New => Invalid ** Changed in: linux-oem-5.6 (Ubuntu Hirsute) Status: New => Invalid ** Changed in: linux-oem-5.10 (Ubuntu Hirsute) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1903969 Title: failed to boot to GUI: i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux source package in Focal: New Status in linux-oem-5.10 source package in Focal: New Status in linux-oem-5.6 source package in Focal: New Status in linux source package in Groovy: New Status in linux-oem-5.10 source package in Groovy: Invalid Status in linux-oem-5.6 source package in Groovy: Invalid Status in linux source package in Hirsute: In Progress Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-oem-5.6 source package in Hirsute: Invalid Bug description: [Summary] When the monitor ONLY is connected to the WD19 (DP port) and WD19 is connected to the type c port than boot the machine, the monitor shows no video output after loaded i915. [Reproduce Steps] 1. connect power cable of WD19 2. connect DP cable from monitor to WD19 3. connect power cable to target system. 4. connect type c cable from WD19 to target system 5. boot up [Results] Expected: video output as there is only one monitor connected. Actual: No video output. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.6.0-1033-oem 5.6.0-1033.35 ProcVersionSignature: Ubuntu 5.6.0-1033.35-oem 5.6.19 Uname: Linux 5.6.0-1033-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Nov 12 05:11:11 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-metapod+X40 InstallationDate: Installed on 2020-11-03 (9 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 SourcePackage: linux-signed-oem-5.6 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1903969/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1903969] Re: failed to boot to GUI: i915 0000:00:02.0: [drm] *ERROR* Link Training Unsuccessful
** Also affects: linux (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Hirsute) Importance: Undecided Status: Incomplete ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Hirsute) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu Hirsute) Importance: Undecided => High ** Changed in: linux (Ubuntu Hirsute) Assignee: (unassigned) => You-Sheng Yang (vicamo) ** Also affects: linux-oem-5.6 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1903969 Title: failed to boot to GUI: i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.6 package in Ubuntu: New Status in linux source package in Focal: New Status in linux-oem-5.6 source package in Focal: New Status in linux source package in Groovy: New Status in linux-oem-5.6 source package in Groovy: New Status in linux source package in Hirsute: In Progress Status in linux-oem-5.6 source package in Hirsute: New Bug description: [Summary] When the monitor ONLY is connected to the WD19 (DP port) and WD19 is connected to the type c port than boot the machine, the monitor shows no video output after loaded i915. [Reproduce Steps] 1. connect power cable of WD19 2. connect DP cable from monitor to WD19 3. connect power cable to target system. 4. connect type c cable from WD19 to target system 5. boot up [Results] Expected: video output as there is only one monitor connected. Actual: No video output. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.6.0-1033-oem 5.6.0-1033.35 ProcVersionSignature: Ubuntu 5.6.0-1033.35-oem 5.6.19 Uname: Linux 5.6.0-1033-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Nov 12 05:11:11 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-metapod+X40 InstallationDate: Installed on 2020-11-03 (9 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 SourcePackage: linux-signed-oem-5.6 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1903969/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1903969] Re: failed to boot to GUI: i915 0000:00:02.0: [drm] *ERROR* Link Training Unsuccessful
PPA: https://launchpad.net/~vicamo/+archive/ubuntu/ppa-1903969 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1903969 Title: failed to boot to GUI: i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Bug description: [Summary] When the monitor ONLY is connected to the WD19 (DP port) and WD19 is connected to the type c port than boot the machine, the monitor shows no video output after loaded i915. [Reproduce Steps] 1. connect power cable of WD19 2. connect DP cable from monitor to WD19 3. connect power cable to target system. 4. connect type c cable from WD19 to target system 5. boot up [Results] Expected: video output as there is only one monitor connected. Actual: No video output. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.6.0-1033-oem 5.6.0-1033.35 ProcVersionSignature: Ubuntu 5.6.0-1033.35-oem 5.6.19 Uname: Linux 5.6.0-1033-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Nov 12 05:11:11 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-metapod+X40 InstallationDate: Installed on 2020-11-03 (9 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 SourcePackage: linux-signed-oem-5.6 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1903969/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1903969] Re: failed to boot to GUI: i915 0000:00:02.0: [drm] *ERROR* Link Training Unsuccessful
$ git bisect log git bisect start # old: [f8394f232b1eab649ce2df5c5f15b0e528c92091] Linux 5.10-rc3 git bisect old f8394f232b1eab649ce2df5c5f15b0e528c92091 # new: [c0f98d2f8b076bf3e3183aa547395f919c943a14] Merge tag 'drm-misc-next-2020-11-05' of git://anongit.freedesktop.org/drm/drm-misc into drm-next git bisect new c0f98d2f8b076bf3e3183aa547395f919c943a14 # old: [3cea11cd5e3b00d91caf0b4730194039b45c5891] Linux 5.10-rc2 git bisect old 3cea11cd5e3b00d91caf0b4730194039b45c5891 # old: [6a6e5988a2657cd0c91f6f1a3e7d194599248b6d] drm/ttm: replace last move_notify with delete_mem_notify git bisect old 6a6e5988a2657cd0c91f6f1a3e7d194599248b6d # new: [f566fdcd6cc49a9d5b5d782f56e3e7cb243f01b8] drm/i915: Force VT'd workarounds when running as a guest OS git bisect new f566fdcd6cc49a9d5b5d782f56e3e7cb243f01b8 # old: [b50b7991b739c6d63658e3324a01eaa0fafe8b7f] drm/i915/dg1: add more PCI ids git bisect old b50b7991b739c6d63658e3324a01eaa0fafe8b7f # old: [0a5991f5d022235ba085001e2a3926f83a0aed1b] drm/i915: Simplify the link training functions git bisect old 0a5991f5d022235ba085001e2a3926f83a0aed1b # new: [0dac17af0ab4e55b6b18a762141f255d3eea1e37] drm/i915/dg1: Enable DPLL for DG1 git bisect new 0dac17af0ab4e55b6b18a762141f255d3eea1e37 # new: [055f8458d95a38c20e8360634255f684378179eb] drm/i915: Force DPCD backlight mode for BOE 2270 panel git bisect new 055f8458d95a38c20e8360634255f684378179eb # old: [7b2a4ab8b0ef2a6dbec0b15d2cabf5a9e7acdf4c] drm/i915: Switch to LTTPR transparent mode link training git bisect old 7b2a4ab8b0ef2a6dbec0b15d2cabf5a9e7acdf4c # new: [b30edfd8d0b4b22f9c17c208064b39a3d93e6971] drm/i915: Switch to LTTPR non-transparent mode link training git bisect new b30edfd8d0b4b22f9c17c208064b39a3d93e6971 # first new commit: [b30edfd8d0b4b22f9c17c208064b39a3d93e6971] drm/i915: Switch to LTTPR non-transparent mode link training So this, https://patchwork.freedesktop.org/series/82449/ , patchset is the fix. * b30edfd8d0b4 drm/i915: Switch to LTTPR non-transparent mode link training * 7b2a4ab8b0ef drm/i915: Switch to LTTPR transparent mode link training * 9782f52ab5d6 drm/dp: Add LTTPR helpers * c43027a9a375 drm/i915: Factor out a helper to disable the DPCD training pattern * 0a5991f5d022 drm/i915: Simplify the link training functions * 6777a855d66d drm/i915: Fix DP link training pattern mask These six commits are required with additional dependency to https://patchwork.freedesktop.org/series/76993/ as well. Verified by cherry-picking these to a Ubuntu-5.10-5.10.0-3.4 kernel. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1903969 Title: failed to boot to GUI: i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful Status in HWE Next: New Status in linux package in Ubuntu: New Bug description: [Summary] When the monitor ONLY is connected to the WD19 (DP port) and WD19 is connected to the type c port than boot the machine, the monitor shows no video output after loaded i915. [Reproduce Steps] 1. connect power cable of WD19 2. connect DP cable from monitor to WD19 3. connect power cable to target system. 4. connect type c cable from WD19 to target system 5. boot up [Results] Expected: video output as there is only one monitor connected. Actual: No video output. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.6.0-1033-oem 5.6.0-1033.35 ProcVersionSignature: Ubuntu 5.6.0-1033.35-oem 5.6.19 Uname: Linux 5.6.0-1033-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Nov 12 05:11:11 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-metapod+X40 InstallationDate: Installed on 2020-11-03 (9 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 SourcePackage: linux-signed-oem-5.6 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1903969/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
