| 2020-11-12 10:17:29 |
You-Sheng Yang |
bug |
|
|
added bug |
| 2020-11-12 10:18:10 |
You-Sheng Yang |
bug |
|
|
added subscriber Canonical Hardware Enablement |
| 2020-11-12 10:18:15 |
You-Sheng Yang |
tags |
amd64 apport-bug focal |
amd64 apport-bug focal oem-priority originate-from-1901008 somerville |
|
| 2020-11-12 10:30:12 |
Ubuntu Kernel Bot |
linux (Ubuntu): status |
New |
Incomplete |
|
| 2020-11-17 07:40:50 |
You-Sheng Yang |
nominated for series |
|
Ubuntu Groovy |
|
| 2020-11-17 07:40:50 |
You-Sheng Yang |
bug task added |
|
linux (Ubuntu Groovy) |
|
| 2020-11-17 07:40:50 |
You-Sheng Yang |
nominated for series |
|
Ubuntu Hirsute |
|
| 2020-11-17 07:40:50 |
You-Sheng Yang |
bug task added |
|
linux (Ubuntu Hirsute) |
|
| 2020-11-17 07:40:50 |
You-Sheng Yang |
nominated for series |
|
Ubuntu Focal |
|
| 2020-11-17 07:40:50 |
You-Sheng Yang |
bug task added |
|
linux (Ubuntu Focal) |
|
| 2020-11-17 07:41:00 |
You-Sheng Yang |
linux (Ubuntu Hirsute): status |
Incomplete |
In Progress |
|
| 2020-11-17 07:41:06 |
You-Sheng Yang |
linux (Ubuntu Hirsute): importance |
Undecided |
High |
|
| 2020-11-17 07:41:09 |
You-Sheng Yang |
linux (Ubuntu Hirsute): assignee |
|
You-Sheng Yang (vicamo) |
|
| 2020-11-17 07:41:18 |
You-Sheng Yang |
bug task added |
|
linux-oem-5.6 (Ubuntu) |
|
| 2020-11-24 06:05:54 |
You-Sheng Yang |
bug task added |
|
linux-oem-5.10 (Ubuntu) |
|
| 2020-11-24 06:06:23 |
You-Sheng Yang |
linux-oem-5.10 (Ubuntu Groovy): status |
New |
Invalid |
|
| 2020-11-24 06:06:52 |
You-Sheng Yang |
linux-oem-5.6 (Ubuntu Groovy): status |
New |
Invalid |
|
| 2020-11-24 06:07:05 |
You-Sheng Yang |
linux-oem-5.6 (Ubuntu Hirsute): status |
New |
Invalid |
|
| 2020-11-24 06:07:30 |
You-Sheng Yang |
linux-oem-5.10 (Ubuntu Hirsute): status |
New |
Invalid |
|
| 2020-11-24 09:13:02 |
You-Sheng Yang |
linux-oem-5.10 (Ubuntu Focal): importance |
Undecided |
High |
|
| 2020-11-24 09:13:02 |
You-Sheng Yang |
linux-oem-5.10 (Ubuntu Focal): status |
New |
In Progress |
|
| 2020-11-24 09:13:02 |
You-Sheng Yang |
linux-oem-5.10 (Ubuntu Focal): assignee |
|
You-Sheng Yang (vicamo) |
|
| 2020-11-24 09:13:27 |
You-Sheng Yang |
linux (Ubuntu Focal): status |
New |
Invalid |
|
| 2020-11-24 09:16:15 |
You-Sheng Yang |
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) |
[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 0000:00:02.0: [drm] *ERROR* Link Training Unsuccessful
i915 0000: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) |
|
| 2020-11-24 11:18:25 |
You-Sheng Yang |
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 0000:00:02.0: [drm] *ERROR* Link Training Unsuccessful
i915 0000: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) |
[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 0000:00:02.0: [drm] *ERROR* Link Training Unsuccessful
i915 0000: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
[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) |
|
| 2020-11-24 11:20:30 |
You-Sheng Yang |
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 0000:00:02.0: [drm] *ERROR* Link Training Unsuccessful
i915 0000: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
[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) |
[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 0000:00:02.0: [drm] *ERROR* Link Training Unsuccessful
i915 0000: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) |
|
| 2020-11-25 13:54:53 |
Timo Aaltonen |
linux-oem-5.10 (Ubuntu Focal): status |
In Progress |
Fix Committed |
|
| 2020-11-25 13:55:05 |
Timo Aaltonen |
linux (Ubuntu Groovy): status |
New |
Won't Fix |
|
| 2020-11-27 16:52:17 |
Ubuntu Kernel Bot |
tags |
amd64 apport-bug focal oem-priority originate-from-1901008 somerville |
amd64 apport-bug focal oem-priority originate-from-1901008 somerville verification-needed-focal |
|
| 2020-11-30 05:21:53 |
You-Sheng Yang |
tags |
amd64 apport-bug focal oem-priority originate-from-1901008 somerville verification-needed-focal |
amd64 apport-bug focal oem-priority originate-from-1901008 somerville verification-done-focal |
|
| 2020-12-03 08:49:55 |
Timo Aaltonen |
linux-oem-5.6 (Ubuntu Focal): status |
New |
Won't Fix |
|
| 2020-12-10 17:47:35 |
m |
bug |
|
|
added subscriber m |
| 2020-12-31 02:24:12 |
koba |
tags |
amd64 apport-bug focal oem-priority originate-from-1901008 somerville verification-done-focal |
amd64 apport-bug focal oem-priority originate-from-1901008 originate-from-1907526 somerville verification-done-focal |
|
| 2020-12-31 02:37:17 |
koba |
tags |
amd64 apport-bug focal oem-priority originate-from-1901008 originate-from-1907526 somerville verification-done-focal |
amd64 apport-bug focal oem-priority originate-from-1894066 originate-from-1901008 originate-from-1907526 somerville verification-done-focal |
|
| 2020-12-31 02:40:37 |
koba |
tags |
amd64 apport-bug focal oem-priority originate-from-1894066 originate-from-1901008 originate-from-1907526 somerville verification-done-focal |
amd64 apport-bug focal oem-priority originate-from-1894066 originate-from-1895638 originate-from-1901008 originate-from-1907526 somerville verification-done-focal |
|
| 2021-01-05 13:07:12 |
Timo Aaltonen |
linux-oem-5.10 (Ubuntu Focal): status |
Fix Committed |
Fix Released |
|
| 2021-01-11 05:55:37 |
koba |
tags |
amd64 apport-bug focal oem-priority originate-from-1894066 originate-from-1895638 originate-from-1901008 originate-from-1907526 somerville verification-done-focal |
amd64 apport-bug focal oem-priority originate-from-1892304 originate-from-1894066 originate-from-1895638 originate-from-1901008 originate-from-1907526 somerville verification-done-focal |
|
| 2021-02-19 23:03:37 |
Launchpad Janitor |
linux (Ubuntu Hirsute): status |
In Progress |
Fix Released |
|
| 2022-09-05 10:24:44 |
Timo Aaltonen |
hwe-next: status |
New |
Fix Released |
|
| 2022-09-23 08:40:23 |
Frédéric Grosshans |
bug |
|
|
added subscriber Frédéric Grosshans |
