* [Bug 69721] New: Can't reach maximum memory speed (or core speed) when using dpm=1 on r600g
@ 2013-09-23 16:13 bugzilla-daemon
2013-09-23 16:14 ` [Bug 69721] " bugzilla-daemon
` (9 more replies)
0 siblings, 10 replies; 11+ messages in thread
From: bugzilla-daemon @ 2013-09-23 16:13 UTC (permalink / raw)
To: dri-devel
[-- Attachment #1.1: Type: text/plain, Size: 1272 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=69721
Priority: medium
Bug ID: 69721
Assignee: dri-devel@lists.freedesktop.org
Summary: Can't reach maximum memory speed (or core speed) when
using dpm=1 on r600g
Severity: normal
Classification: Unclassified
OS: All
Reporter: alexandre.f.demers@gmail.com
Hardware: All
Status: NEW
Version: XOrg CVS
Component: DRM/Radeon
Product: DRI
After fixing bug 68235, it appears the maximum memory speed (or core speed)
can't always be reached. This situation depends on the voltage tweaking seen on
some cards. As an exemple, XFX HD-695X-ZNDC has the following maximum values:
max_sclk_vddc->80000, max_mclk_vddci->125000, max_mclk_vddc->125000.
However, the maximum memory clock value should be 130000 and the core clock
should be 83000.
As Alex Deucher explained: "This patch set works around the issue by limiting
the sclk and mclk to the highest levels listed in the clk/voltage dependency
tables. I'll need to dig a bit more internally to try and figure out how to
handle these clks properly."
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2801 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
^ permalink raw reply [flat|nested] 11+ messages in thread
* [Bug 69721] Can't reach maximum memory speed (or core speed) when using dpm=1 on r600g
2013-09-23 16:13 [Bug 69721] New: Can't reach maximum memory speed (or core speed) when using dpm=1 on r600g bugzilla-daemon
@ 2013-09-23 16:14 ` bugzilla-daemon
2013-09-23 16:15 ` bugzilla-daemon
` (8 subsequent siblings)
9 siblings, 0 replies; 11+ messages in thread
From: bugzilla-daemon @ 2013-09-23 16:14 UTC (permalink / raw)
To: dri-devel
[-- Attachment #1.1: Type: text/plain, Size: 283 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=69721
--- Comment #1 from Alexandre Demers <alexandre.f.demers@gmail.com> ---
That is with kernel 3.11.0 or 3.12-rc1 with the two patches proposed in bug
68235.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1319 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
^ permalink raw reply [flat|nested] 11+ messages in thread
* [Bug 69721] Can't reach maximum memory speed (or core speed) when using dpm=1 on r600g
2013-09-23 16:13 [Bug 69721] New: Can't reach maximum memory speed (or core speed) when using dpm=1 on r600g bugzilla-daemon
2013-09-23 16:14 ` [Bug 69721] " bugzilla-daemon
@ 2013-09-23 16:15 ` bugzilla-daemon
2013-09-23 23:03 ` [Bug 69721] Can't reach maximum memory speed (or core speed) when using dpm=1 on r600g on cards not sticking to reference board bugzilla-daemon
` (7 subsequent siblings)
9 siblings, 0 replies; 11+ messages in thread
From: bugzilla-daemon @ 2013-09-23 16:15 UTC (permalink / raw)
To: dri-devel
[-- Attachment #1.1: Type: text/plain, Size: 468 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=69721
Alexandre Demers <alexandre.f.demers@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
See Also| |https://bugs.freedesktop.or
| |g/show_bug.cgi?id=68235
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1150 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
^ permalink raw reply [flat|nested] 11+ messages in thread
* [Bug 69721] Can't reach maximum memory speed (or core speed) when using dpm=1 on r600g on cards not sticking to reference board
2013-09-23 16:13 [Bug 69721] New: Can't reach maximum memory speed (or core speed) when using dpm=1 on r600g bugzilla-daemon
2013-09-23 16:14 ` [Bug 69721] " bugzilla-daemon
2013-09-23 16:15 ` bugzilla-daemon
@ 2013-09-23 23:03 ` bugzilla-daemon
2014-09-22 4:30 ` bugzilla-daemon
` (6 subsequent siblings)
9 siblings, 0 replies; 11+ messages in thread
From: bugzilla-daemon @ 2013-09-23 23:03 UTC (permalink / raw)
To: dri-devel
[-- Attachment #1.1: Type: text/plain, Size: 679 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=69721
Alexandre Demers <alexandre.f.demers@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|Can't reach maximum memory |Can't reach maximum memory
|speed (or core speed) when |speed (or core speed) when
|using dpm=1 on r600g |using dpm=1 on r600g on
| |cards not sticking to
| |reference board
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1307 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
^ permalink raw reply [flat|nested] 11+ messages in thread
* [Bug 69721] Can't reach maximum memory speed (or core speed) when using dpm=1 on r600g on cards not sticking to reference board
2013-09-23 16:13 [Bug 69721] New: Can't reach maximum memory speed (or core speed) when using dpm=1 on r600g bugzilla-daemon
` (2 preceding siblings ...)
2013-09-23 23:03 ` [Bug 69721] Can't reach maximum memory speed (or core speed) when using dpm=1 on r600g on cards not sticking to reference board bugzilla-daemon
@ 2014-09-22 4:30 ` bugzilla-daemon
2014-09-22 14:18 ` bugzilla-daemon
` (5 subsequent siblings)
9 siblings, 0 replies; 11+ messages in thread
From: bugzilla-daemon @ 2014-09-22 4:30 UTC (permalink / raw)
To: dri-devel
[-- Attachment #1.1: Type: text/plain, Size: 1062 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=69721
Alexandre Demers <alexandre.f.demers@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |agd5f@yahoo.com
--- Comment #2 from Alexandre Demers <alexandre.f.demers@gmail.com> ---
Hi Alex.
A year ago, while we were struggling with dpm on Cayman, you implemented a fix
to limit the maximum memory and core speeds to the reference ones in the
clk/voltage dependency tables. Now that Cayman is working great, I'm wondering
if you would have the time "to dig a bit more internally to try and figure out
how to handle these clks properly" when a card is not using the reference
values? Is there a way to read the maximum speed from the video card bios or at
least to identify a card built to exceed the reference values?
I'm ready to test any patch you can throw at me.
Cheers!
Alexandre
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2604 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
^ permalink raw reply [flat|nested] 11+ messages in thread
* [Bug 69721] Can't reach maximum memory speed (or core speed) when using dpm=1 on r600g on cards not sticking to reference board
2013-09-23 16:13 [Bug 69721] New: Can't reach maximum memory speed (or core speed) when using dpm=1 on r600g bugzilla-daemon
` (3 preceding siblings ...)
2014-09-22 4:30 ` bugzilla-daemon
@ 2014-09-22 14:18 ` bugzilla-daemon
2014-09-22 16:19 ` bugzilla-daemon
` (4 subsequent siblings)
9 siblings, 0 replies; 11+ messages in thread
From: bugzilla-daemon @ 2014-09-22 14:18 UTC (permalink / raw)
To: dri-devel
[-- Attachment #1.1: Type: text/plain, Size: 231 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=69721
--- Comment #3 from Alex Deucher <agd5f@yahoo.com> ---
Did you try again after fixing the vddci setup?
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1132 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
^ permalink raw reply [flat|nested] 11+ messages in thread
* [Bug 69721] Can't reach maximum memory speed (or core speed) when using dpm=1 on r600g on cards not sticking to reference board
2013-09-23 16:13 [Bug 69721] New: Can't reach maximum memory speed (or core speed) when using dpm=1 on r600g bugzilla-daemon
` (4 preceding siblings ...)
2014-09-22 14:18 ` bugzilla-daemon
@ 2014-09-22 16:19 ` bugzilla-daemon
2014-09-22 16:31 ` bugzilla-daemon
` (3 subsequent siblings)
9 siblings, 0 replies; 11+ messages in thread
From: bugzilla-daemon @ 2014-09-22 16:19 UTC (permalink / raw)
To: dri-devel
[-- Attachment #1.1: Type: text/plain, Size: 850 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=69721
--- Comment #4 from Alexandre Demers <alexandre.f.demers@gmail.com> ---
(In reply to comment #3)
> Did you try again after fixing the vddci setup?
To my knowledge, the memory speed is still limited to 1250 instead of reaching
its maximum speed of 1300; the same thing goes for the core clock. I'll need to
have a look at the code, but the last time I had a look, we were still calling
btc_get_max_clock_from_voltage_dependency_table(), which was limiting the speed
to the reference values.
If I have time, I'll look at the code tonight and add some code to print values
that would be limited by btc_get_max_clock_from_voltage_dependency_table().
Other than this limitation, I have mostly no problem with my Cayman GPU.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1838 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
^ permalink raw reply [flat|nested] 11+ messages in thread
* [Bug 69721] Can't reach maximum memory speed (or core speed) when using dpm=1 on r600g on cards not sticking to reference board
2013-09-23 16:13 [Bug 69721] New: Can't reach maximum memory speed (or core speed) when using dpm=1 on r600g bugzilla-daemon
` (5 preceding siblings ...)
2014-09-22 16:19 ` bugzilla-daemon
@ 2014-09-22 16:31 ` bugzilla-daemon
2014-09-22 19:30 ` bugzilla-daemon
` (2 subsequent siblings)
9 siblings, 0 replies; 11+ messages in thread
From: bugzilla-daemon @ 2014-09-22 16:31 UTC (permalink / raw)
To: dri-devel
[-- Attachment #1.1: Type: text/plain, Size: 832 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=69721
--- Comment #5 from Alex Deucher <agd5f@yahoo.com> ---
(In reply to comment #4)
> (In reply to comment #3)
> > Did you try again after fixing the vddci setup?
>
> To my knowledge, the memory speed is still limited to 1250 instead of
> reaching its maximum speed of 1300; the same thing goes for the core clock.
> I'll need to have a look at the code, but the last time I had a look, we
> were still calling btc_get_max_clock_from_voltage_dependency_table(), which
> was limiting the speed to the reference values.
Right. I mean have you tried reverting that patch or just skipping the calls
to btc_get_max_clock_from_voltage_dependency_table(). I think they should work
fine now that vddci is fixed.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1866 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
^ permalink raw reply [flat|nested] 11+ messages in thread
* [Bug 69721] Can't reach maximum memory speed (or core speed) when using dpm=1 on r600g on cards not sticking to reference board
2013-09-23 16:13 [Bug 69721] New: Can't reach maximum memory speed (or core speed) when using dpm=1 on r600g bugzilla-daemon
` (6 preceding siblings ...)
2014-09-22 16:31 ` bugzilla-daemon
@ 2014-09-22 19:30 ` bugzilla-daemon
2014-09-23 4:43 ` bugzilla-daemon
2014-09-26 22:10 ` bugzilla-daemon
9 siblings, 0 replies; 11+ messages in thread
From: bugzilla-daemon @ 2014-09-22 19:30 UTC (permalink / raw)
To: dri-devel
[-- Attachment #1.1: Type: text/plain, Size: 972 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=69721
--- Comment #6 from Alexandre Demers <alexandre.f.demers@gmail.com> ---
(In reply to comment #5)
> (In reply to comment #4)
> > (In reply to comment #3)
> > > Did you try again after fixing the vddci setup?
> >
> > To my knowledge, the memory speed is still limited to 1250 instead of
> > reaching its maximum speed of 1300; the same thing goes for the core clock.
> > I'll need to have a look at the code, but the last time I had a look, we
> > were still calling btc_get_max_clock_from_voltage_dependency_table(), which
> > was limiting the speed to the reference values.
>
> Right. I mean have you tried reverting that patch or just skipping the
> calls to btc_get_max_clock_from_voltage_dependency_table(). I think they
> should work fine now that vddci is fixed.
Well that was one of the plans. ;) I'll try it later and let you know.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2101 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
^ permalink raw reply [flat|nested] 11+ messages in thread
* [Bug 69721] Can't reach maximum memory speed (or core speed) when using dpm=1 on r600g on cards not sticking to reference board
2013-09-23 16:13 [Bug 69721] New: Can't reach maximum memory speed (or core speed) when using dpm=1 on r600g bugzilla-daemon
` (7 preceding siblings ...)
2014-09-22 19:30 ` bugzilla-daemon
@ 2014-09-23 4:43 ` bugzilla-daemon
2014-09-26 22:10 ` bugzilla-daemon
9 siblings, 0 replies; 11+ messages in thread
From: bugzilla-daemon @ 2014-09-23 4:43 UTC (permalink / raw)
To: dri-devel
[-- Attachment #1.1: Type: text/plain, Size: 381 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=69721
--- Comment #7 from Alexandre Demers <alexandre.f.demers@gmail.com> ---
It seems to run as expected now. I've submitted a patch
(http://lists.freedesktop.org/archives/dri-devel/2014-September/068789.html).
Maybe it could/should be tested on other GPUs.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1388 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
^ permalink raw reply [flat|nested] 11+ messages in thread
* [Bug 69721] Can't reach maximum memory speed (or core speed) when using dpm=1 on r600g on cards not sticking to reference board
2013-09-23 16:13 [Bug 69721] New: Can't reach maximum memory speed (or core speed) when using dpm=1 on r600g bugzilla-daemon
` (8 preceding siblings ...)
2014-09-23 4:43 ` bugzilla-daemon
@ 2014-09-26 22:10 ` bugzilla-daemon
9 siblings, 0 replies; 11+ messages in thread
From: bugzilla-daemon @ 2014-09-26 22:10 UTC (permalink / raw)
To: dri-devel
[-- Attachment #1.1: Type: text/plain, Size: 587 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=69721
Alexandre Demers <alexandre.f.demers@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #8 from Alexandre Demers <alexandre.f.demers@gmail.com> ---
Closing since it should be fixed in kernel 3.18 (pull request from
drm-next-3.18).
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2272 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
^ permalink raw reply [flat|nested] 11+ messages in thread
end of thread, other threads:[~2014-09-26 22:10 UTC | newest]
Thread overview: 11+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2013-09-23 16:13 [Bug 69721] New: Can't reach maximum memory speed (or core speed) when using dpm=1 on r600g bugzilla-daemon
2013-09-23 16:14 ` [Bug 69721] " bugzilla-daemon
2013-09-23 16:15 ` bugzilla-daemon
2013-09-23 23:03 ` [Bug 69721] Can't reach maximum memory speed (or core speed) when using dpm=1 on r600g on cards not sticking to reference board bugzilla-daemon
2014-09-22 4:30 ` bugzilla-daemon
2014-09-22 14:18 ` bugzilla-daemon
2014-09-22 16:19 ` bugzilla-daemon
2014-09-22 16:31 ` bugzilla-daemon
2014-09-22 19:30 ` bugzilla-daemon
2014-09-23 4:43 ` bugzilla-daemon
2014-09-26 22:10 ` bugzilla-daemon
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.