| Bug ID | 91294 |
|---|---|
| Summary | [R7 370] DPM and power profile change crash the system |
| Product | DRI |
| Version | unspecified |
| Hardware | x86-64 (AMD64) |
| OS | Linux (All) |
| Status | NEW |
| Severity | major |
| Priority | medium |
| Component | DRM/Radeon |
| Assignee | dri-devel@lists.freedesktop.org |
| Reporter | elia.argentieri@openmailbox.org |
Created attachment 117032 [details] dmesg | grep radeon with radeon.dpm=0 My system is unable to boot with an MSI R7 370 Armor 2X unless I put radeon.dpm=0 (or nomodeset) to the boot parameter. Also any change to the power profile results in an immediate lock up with blank screen or, sometimes, black and white vertical stripes. I think my issue is related with #77394 and #76490. Probably wrong frequency or voltages given that the MSI R7 370 Gaming 4G (which is the better version with higher frequency) works with DPM (http://www.phoronix.com/scan.php?page=article&item=linux-411-gallium&num=1) Tested with Linux 3.16, 4.0 and 4.1. lspci -nnk | grep VGA: 01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Curacao PRO [Radeon R7 370 / R9 270/370 OEM] [1002:6811] (rev 81)
Please attach your full dmesg output and xorg log. Also attach a copy of your vbios. (as root) (use lspci to get the bus id) cd /sys/bus/pci/devices/<pci bus id> echo 1 > rom cat rom > /tmp/vbios.rom echo 0 > rom
Created attachment 117035 [details]
VBIOS MSI R7 370 Armor 2X
| What | Removed | Added |
|---|---|---|
| Attachment #117032 is obsolete | 1 |
Created attachment 117036 [details]
Full dmesg with radeon.dpm=0
Created attachment 117048 [details] [review] Fix by adding a line to si_dpm_quirk_list Adding this line made my card work with DPM enabled, but I'm not sure about mclk value. This card is supposed to have a 5600 MHz video memory according to MSI's site. However Catalyst reports a frequency of 1400 MHz. Tomorrow, I'll play with this values.
| What | Removed | Added |
|---|---|---|
| See Also | https://bugs.freedesktop.org/show_bug.cgi?id=76490 |
| What | Removed | Added |
|---|---|---|
| See Also | https://bugs.freedesktop.org/show_bug.cgi?id=92260 |
I have a MSI R7 370 Armor 2x as well and like to report that the suggested workaround does not help in my case. During the boot process the mouse pointer is briefly visible but then the screen goes black. I can use the desktop with radeon.dpm=0. I am returning this card and sticking to my Radeon 6570 for now.
I decided to try to add the quirk line to the debian 4.2.3 kernel source currently in sid and this time I booted into a stable desktop. The line from Elia works.
(In reply to Paul Frederiks from comment #7) > I decided to try to add the quirk line to the debian 4.2.3 kernel source > currently in sid and this time I booted into a stable desktop. The line from > Elia works. It works, but clocks are really lower than normal. I think that if we use values from MSI R7 370 Gaming 2G we would be able to make it work with even a bit higher clocks. Or we could modify VBios of the card with vendor/model values with ones from that card mentioned before and make the system use all the things for that card.
Indeed I also tried with higher clock speeds like 1400 and 1300, but all my attempts had the same outcome. I don't really understand why an higher clock frequency would lock completely the system as the radeon module is loaded... I think MSI is doing nasty things like putting a limit inside their firmware to make the GPU unusable with higher frequencies. I won't ever buy again an MSI product.
| What | Removed | Added |
|---|---|---|
| See Also | https://bugs.freedesktop.org/show_bug.cgi?id=94692 |
I'm happy to report that I did not need to patch the kernel af= ter upgrading to kernel 4.5.0 from debian unstable.
| What | Removed | Added |
|---|---|---|
| Resolution | --- | FIXED |
| Status | NEW | RESOLVED |
This issue is finally fixed for MSI R7 370 Armor 2X with linux= 4.10 master. See https://bugs.freedesktop.org/show_bug.c= gi?id=3D76490.