| Bug ID | 108704 |
|---|---|
| Summary | 4.19 amdgpu Tonga powerplay regressions |
| Product | DRI |
| Version | unspecified |
| Hardware | x86-64 (AMD64) |
| OS | All |
| Status | NEW |
| Severity | normal |
| Priority | medium |
| Component | DRM/AMDgpu |
| Assignee | dri-devel@lists.freedesktop.org |
| Reporter | daniel@constexpr.org |
Created attachment 142423 =
[details]
dmesg output
With Gentoo's 4.19.0 and 4.19.1 kernels, powerplay does not seem to be work=
ing
on my Radeon R9 380X card: 3D applications run noticeably slower than before
(but otherwise work fine) and there a number of errors in dmesg during star=
tup
and when trying to switch dpm states via sysfs.
Everything works fine with 4.18.17-gentoo.
Does this patch fix the issue? https://patchwo= rk.freedesktop.org/patch/259364/
FYI the patch did fix the same issue for me with an R9 380
| What | Removed | Added |
|---|---|---|
| Resolution | --- | NOTOURBUG |
| Status | NEW | RESOLVED |
| What | Removed | Added |
|---|---|---|
| CC | garththeisen@hotmail.com |
*** Bug 108778 has been marked as a du= plicate of this bug. ***
Could somebody please attach "sudo lspci -vvxxx" out= put for an affected system (for at least the root port and GPU, or the whole system if that's easier)?=
Created =
attachment 142530 [details]
lspci -vvxx output under 4.18.17-gentoo
Created attachment 14=
2617 [details]
dmesg output on Arch Linux
I think I'm affected by a similar issue. I'm using an AMD R9 380 on Arch Li=
nux
with the latest GNOME version. My main troubles are with dual-screen, which
started malfunctioning some days ago - maybe since the 4.19 kernel update,
although I'm unable to downgrade to an older kernel to confirm this.
| What | Removed | Added |
|---|---|---|
| CC | laurent.pointecouteau@gmail.com |
Created attachment 142618 [details]
sudo lspci -vvxxx on 4.19.2-arch1-1-ARCH
(In reply to Alex Deucher from comment #9) > Please try the patch in comment 1. I've applied the patch and there are no more amdgpu related errors showing = up in dmesg after booting. However, this has not fixed my dual-screen issues; = my HDMI TV displays "no signal" after booting while plugged in my co= mputer, and when trying to switch display modes using the GNOME control center, my DVI screen tends to get disabled and display "no signal" too, forcing= me to hard reboot. As far as I can tell, this is the same behavior than before using t= he patched kernel. So, my issues may not be related to this bug ticket after a= ll.
(In reply to Laurent Pointecouteau from comment #10) > (In reply to Alex Deucher from comment #9) > > Please try the patch in c= omment 1. >=20 > I've applied the patch and there are no more amdgpu related errors sho= wing > up in dmesg after booting. However, this has not fixed my dual-screen > issues; my HDMI TV displays "no signal" after booting while = plugged in my > computer, and when trying to switch display modes using the GNOME cont= rol > center, my DVI screen tends to get disabled and display "no signa= l" too, > forcing me to hard reboot. As far as I can tell, this is the same beha= vior > than before using the patched kernel. So, my issues may not be related= to > this bug ticket after all. Please file a different bug for the display issue.