From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 100666] amdgpu coolers never stoping linux Date: Wed, 28 Feb 2018 02:36:43 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1772925162==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id DC7596E60B for ; Wed, 28 Feb 2018 02:36:42 +0000 (UTC) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============1772925162== Content-Type: multipart/alternative; boundary="15197854020.9B0Bd2c7C.2924" Content-Transfer-Encoding: 7bit --15197854020.9B0Bd2c7C.2924 Date: Wed, 28 Feb 2018 02:36:42 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated https://bugs.freedesktop.org/show_bug.cgi?id=3D100666 --- Comment #11 from Luke McKee --- In this case it was on topic. The link explains how to use fancontrol script from lm_sensors to work around fan control issues. I saw on another ticket = when I first posted here that dc=3D1 fixed the fancontrol issues. Finally I got = dc=3D1 working and still it doesn't resolve the dpm fancontrol issues on my platfo= rm. https://github.com/kobalicek/amdtweak as root # ./amdtweak --card 0 --verbose --extract-bios /tmp/amdbios.bin fails. The sysfs shows that the powerplay tables are not proper too. [ 4969.713277] resource sanity check: requesting [mem 0x000c0000-0x000dffff= ], which spans more than PCI Bus 0000:00 [mem 0x000c0000-0x000c3fff window] [ 4969.713283] caller pci_map_rom+0x66/0xf0 mapping multiple BARs [ 4969.713289] amdgpu 0000:01:00.0: Invalid PCI ROM header signature: expec= ting 0xaa55, got 0xffff If it can't read it's powerplay table because it can't read the bios maybe that's why there is all these problems. (In reply to Alex Deucher from comment #9) >=20 > Please stop posting this on every bug report. https://bugs.freedesktop.org/show_bug.cgi?id=3D100666#c0 Also the users above on this ticket above here when they grepped their dmesg wouldn't have output any powerplay mes.sages because they grepped radeon instead of amdgpu [ 10.124232] amdgpu: [powerplay]=20 failed to send message 309 ret is 254=20 [ 10.124248] amdgpu: [powerplay]=20 failed to send pre message 14e ret is 254=20 Maybe Denis could confirm or deny if this is in his dmesg? --=20 You are receiving this mail because: You are the assignee for the bug.= --15197854020.9B0Bd2c7C.2924 Date: Wed, 28 Feb 2018 02:36:42 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated

Comme= nt # 11 on bug 10066= 6 from Luke McKee 
In this case it was on topic. The link explains how to use fan=
control script
from lm_sensors to work around fan control issues. I saw on another ticket =
when
I first posted here that dc=3D1 fixed the fancontrol issues. Finally I got =
dc=3D1
working and still it doesn't resolve the dpm fancontrol issues on my platfo=
rm.

https://github.com/kobali=
cek/amdtweak
as root
# ./amdtweak  --card 0 --verbose --extract-bios /tmp/amdbios.bin
fails. The sysfs shows that the powerplay tables are not proper too.

[ 4969.713277] resource sanity check: requesting [mem 0x000c0000-0x000dffff=
],
which spans more than PCI Bus 0000:00 [mem 0x000c0000-0x000c3fff window]
[ 4969.713283] caller pci_map_rom+0x66/0xf0 mapping multiple BARs
[ 4969.713289] amdgpu 0000:01:00.0: Invalid PCI ROM header signature: expec=
ting
0xaa55, got 0xffff

If it can't read it's powerplay table because it can't read the bios maybe
that's why there is all these problems.


 (In reply to Alex Deucher from com=
ment #9)
>=20
> Please stop posting this on every bug report.

https://bugs.freedesktop.org/show_b=
ug.cgi?id=3D100666#c0
Also the users above on this ticket above here when they grepped their dmesg
wouldn't have output any powerplay mes.sages because they grepped radeon
instead of amdgpu

[   10.124232] amdgpu: [powerplay]=20
                failed to send message 309 ret is 254=20
[   10.124248] amdgpu: [powerplay]=20
                failed to send pre message 14e ret is 254=20

Maybe Denis could confirm or deny if this is in his dmesg?

You are receiving this mail because:
  • You are the assignee for the bug.
= --15197854020.9B0Bd2c7C.2924-- --===============1772925162== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVsCg== --===============1772925162==--