Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • A amd
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1,282
    • Issues 1,282
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • drm
  • amd
  • Issues
  • #693

Closed
Open
Created Feb 05, 2019 by Bugzilla Migration User@bugzilla-migration

Regression: short time display corruption during resume

Submitted by Rafał Miłecki

Assigned to Default DRI bug account

Link to original bug (#109554)

Description

I use HP EliteBook 745 G5 with Ryzen 5 PRO 2500U.

Starting with the:
commit 009d9ed6c4b7b84dbff8314d74233da9237a4560
Author: Rex Zhu Rex.Zhu@amd.com
Date: Sun Sep 30 17:37:27 2018 +0800

drm/amdgpu: Change AI gfx/sdma/smu init sequence

initialize gfx/sdma before dpm features enabled.

Acked-by: Alex Deucher alexander.deucher@amd.com
Signed-off-by: Rex Zhu Rex.Zhu@amd.com
Signed-off-by: Alex Deucher alexander.deucher@amd.com

During most resumes from RAM I see a display with black screen & some corruptions for a 1 second or less.

This is not critical but since it's a tracked regression I decided to report it with a hope it's something easy & possible to fix. After that second (or less) displays shows an expected image (KDE lock screen) and everything works normal afterwards.

This problem still exists in the 5.0.0-rc3.

Assignee
Assign to
Time tracking