From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 76490] Hang during boot when DPM is on (R9 270X) Date: Sun, 30 Aug 2015 22:24:06 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1131315648==" Return-path: Received: from culpepper.freedesktop.org (unknown [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 235A56E2D0 for ; Sun, 30 Aug 2015 15:24:06 -0700 (PDT) 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 --===============1131315648== Content-Type: multipart/alternative; boundary="1440973446.038Ba38c3.20094"; charset="UTF-8" --1440973446.038Ba38c3.20094 Date: Sun, 30 Aug 2015 22:24:06 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" https://bugs.freedesktop.org/show_bug.cgi?id=76490 --- Comment #48 from Tobias Droste --- There is only one way to find out the values: Trial and error. Start with what works with other cards: { PCI_VENDOR_ID_ATI, , , , 0, 120000 }, Last value is mclk (memory) and the other is sclk (gpu). 0=use bios default. Values are in 10kHz (not sure why ) so 85000=850MHz, 120000=1.2GHz, .... I found it easier to first get a memory value that works. With that I could boot up to certain point (sometimes even to login!) and then it crashed. If a memory limit is enough than you're good after that. After I found a memory value that somewhat worked I tried different sclk values to get a system that actually boots and can run for a few hours. You don't have to fear anything because it will only limit the clocks if the bios clocks are actually higher, so there's nothing that can break. Not sure if there's a problem with too low values, but I don't think so. So it comes down to change values -> recompile kernel module -> reboot -> if it's still not working, start again. -- You are receiving this mail because: You are the assignee for the bug. --1440973446.038Ba38c3.20094 Date: Sun, 30 Aug 2015 22:24:06 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8"

Comment # 48 on bug 76490 from 
There is only one way to find out the values:
Trial and error.

Start with what works with other cards:
{ PCI_VENDOR_ID_ATI, <PCI_DEVICE_ID>, <PCI_SUBSYSTEM_VENDOR_ID>,
<PCI_SUBSYSTEM_DEVICE_ID>, 0, 120000 },

Last value is mclk (memory) and the other is sclk (gpu). 0=use bios default.
Values are in 10kHz (not sure why ) so 85000=850MHz, 120000=1.2GHz, .... 

I found it easier to first get a memory value that works. With that I could
boot up to certain point (sometimes even to login!) and then it crashed. If a
memory limit is enough than you're good after that. 
After I found a memory value that somewhat worked I tried different sclk values
to get a system that actually boots and can run for a few hours.

You don't have to fear anything because it will only limit the clocks if the
bios clocks are actually higher, so there's nothing that can break. Not sure if
there's a problem with too low values, but I don't think so.

So it comes down to change values -> recompile kernel module -> reboot -> if
it's still not working, start again.

You are receiving this mail because:
  • You are the assignee for the bug.
--1440973446.038Ba38c3.20094-- --===============1131315648== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHA6Ly9saXN0 cy5mcmVlZGVza3RvcC5vcmcvbWFpbG1hbi9saXN0aW5mby9kcmktZGV2ZWwK --===============1131315648==--