Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • A amd
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 348
    • Issues 348
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • 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
  • #678
Closed
Open
Issue created Jan 18, 2016 by Bugzilla Migration User@bugzilla-migration

Sometimes wrong clk frequency of Display after dpms mode changes.

Submitted by t.g..@..n.info

Assigned to Default DRI bug account

Link to original bug (#93753)

Description

Created attachment 121103
Screenshot of failure

Sometimes after the deactivation of the screensaver or also on bootup the screen shows flickering noise and a duplicated screen image. (Attached there is the used test image and a screenshot of the failure image).

We tested on various kernel versions, latest kernel tested was 4.4.0. We run a customized debian image.

Further investigations showed, that in the failure scenario the measured clk frequency was only 25MHz but it should be 35MHz.

We also tried to deactivate dpms completly (radeon.dpm=0 in kernel parameters) and also turned the dpms off in the screensaver, but we still sometimes encounter the problem after a reboot.

Attached you will find a dmesg output with drm.debug=0xf activated.

We use a Radeon PALM on a AMD G-T40E 2x1GHz

Attachment 121103, "Screenshot of failure":
screenshot_failure

Assignee
Assign to
Time tracking