| What | Removed | Added |
|---|---|---|
| Assignee | xorg-driver-ati@lists.x.org | dri-devel@lists.freedesktop.org |
| Product | xorg | DRI |
| Component | Driver/Radeon | DRM/Radeon |
| QA Contact | xorg-team@lists.x.org |
Please attach your dmesg output with radeon.dpm=3D1 explicitly= set.
Created a=
ttachment 128884 [details]
explicit dmesg setting with curruption
Created attachmen=
t 128885 [details]
explicit dmesg without forcing
Created attachment 128886 [details]
Without explictly setting dpm and without curruption
forced high performance mode
First I Have explicitly set radeon.dpm =3D 1 which did not sol= ve the problem. Then I have explicitly set radeon.dpm =3D 1 and forced High performance mod= e. It did not solve the problem either. Then finally I did not explicitly set radeon.dpm =3D 1 but it was enabled implicitly and i forced High performance mode and no more currupton. Curruption is gone after forcing high performance mode in dpm or disabling = dpm with radeon.dpm =3D 0 .=20 Please look into this.
Setting it explicitly just adds some additional debugging info= in the dmesg output.
| What | Removed | Added |
|---|---|---|
| Attachment #128816 mime type | text/x-log | text/plain |
Looks like the mclk switching isn't finishing within the vblan= k period. Do you have the problem with any other display modes or just 1920x1080?
The problem disappears after switching to a lower resolution l= ike 1280x1024 or 800x600 but comes back as soon as i revert to 1920x1080. Please look into t= his as it seems a large number of previous generation cards are affected by the issue. Lots of people who'll be trying out any new distro on any older comp= uter for basic tasks like web browsing, youtube videos, etc are affected.
Forcing dpm to high performance mode resolves the problem for = now.
| What | Removed | Added |
|---|---|---|
| Resolution | --- | MOVED |
| Status | NEW | RESOLVED |
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this = link to our GitLab instance: https://gitlab.freedesktop.org/drm/amd/issues/768.