Add TGL+ SAGV display support
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
HWE Next |
Fix Released
|
Undecided
|
Unassigned | ||
linux (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Focal |
Invalid
|
Undecided
|
Unassigned | ||
Groovy |
Invalid
|
Undecided
|
Unassigned | ||
linux-oem-5.6 (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Focal |
Fix Released
|
High
|
You-Sheng Yang | ||
Groovy |
Invalid
|
Undecided
|
Unassigned |
Bug Description
[SRU Justification]
[Impact]
On platforms with UHD panel, massive drawing area updates may cause
screen to flash as half-baked render buffers with black areas being
renedered.
[Fix]
This turns out to be the lack of full support to Intel System Agent
Geyserville (SAGV), which has been landed to kernel v5.8. The required
fix resides in https:/
seems a rolling set that its early parts have been committed separatedly
several times. This patchset also depends on
https:/
global state handling more standardized.
[Test Case]
1. Trigger massive rect updates, e.g. cat a lengthy file in xterm, dump
kernel git history, etc.
2. Observe if screen flashes with half black panes, sometimes black
stripes, etc.
[Regression Potential]
Medium. This is to backport a new feature landed to kernel early this
year, even there is no later fixes patch found so far, it could still
introduce incompatibility to older kernels. So far it behaves on both
UHD and other lower resolutions.
========== Original Bug Description ==========
On platforms with UHD panel, massive drawing area updates may cause
screen to flash as half-baked render buffers with black areas being
renedered.
[Reproduce Steps]
1. boot to GUI
2. generate massive screen updates by `while true; do dmesg; done` or so
[Results]
Expected Result:
Text output correctly rendered on xterm smoothly
Actual Result:
Screen flashes with black strides, etc.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.6
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
CasperMD5CheckR
DistributionCha
# This is the distribution channel descriptor for the OEM CDs
# For more information see http://
canonical-
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2020-08-07 (6 days ago)
InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58
IwConfig:
lo no wireless extensions.
enx00e04c6801fa no wireless extensions.
MachineType: Dell Inc. XPS 13 9310
Package: linux (not installed)
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=
ProcVersionSign
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageV
linux-
linux-
linux-firmware 1.187.2
RfKill:
Tags: focal
Uname: Linux 5.6.0-1020-oem x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: True
dmi.bios.date: 07/30/2020
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 0.2.9
dmi.board.vendor: Dell Inc.
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.
dmi.product.family: XPS
dmi.product.name: XPS 13 9310
dmi.product.sku: 0991
dmi.sys.vendor: Dell Inc.
CVE References
Changed in linux-oem-5.6 (Ubuntu Groovy): | |
status: | New → Invalid |
Changed in linux-oem-5.6 (Ubuntu Focal): | |
assignee: | nobody → You-Sheng Yang (vicamo) |
importance: | Undecided → High |
status: | New → In Progress |
tags: | added: oem-priority originate-from-1890495 somerville |
Changed in linux (Ubuntu Focal): | |
status: | Incomplete → Invalid |
tags: | added: apport-collected focal |
description: | updated |
Changed in linux-oem-5.6 (Ubuntu Focal): | |
status: | In Progress → Fix Committed |
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
apport-collect 1891451
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the Ubuntu Kernel Team.