[Bug 37112] GPU lockup when trying to use profile based frequency switching

[Bug 37112] GPU lockup when trying to use profile based frequency switching

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=37112


Rafael J. Wysocki <rjw@sisk.pl> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |rjw@sisk.pl
          Component|Other                       |Video(DRI - non Intel)
         AssignedTo|power-management_other@kern |drivers_video-dri@kernel-bu
                   |el-bugs.osdl.org            |gs.osdl.org
            Product|Power Management            |Drivers




-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.

[Bug 37112] GPU lockup when trying to use profile based frequency switching

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=37112





--- Comment #5 from Hrvoje Senjan <hrvoje.senjan@gmail.com>  2011-06-11 06:45:28 ---
My first guess is , that kernel changes memory clock too low - with fglrx
lowest memory clock is at 400MHz , but with radeon module/low frequency it
changes it to 300MHz.

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.

[Bug 37112] GPU lockup when trying to use profile based frequency switching

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=37112


Rafał Miłecki <zajec5@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |zajec5@gmail.com




--- Comment #6 from Rafał Miłecki <zajec5@gmail.com>  2011-06-11 07:36:36 ---
(In reply to comment #5)
> My first guess is , that kernel changes memory clock too low - with fglrx
> lowest memory clock is at 400MHz , but with radeon module/low frequency it
> changes it to 300MHz.

Please, edit drivers/gpu/drm/radeon/radeon_pm.c, find:
> if (rdev->asic->set_memory_clock && (mclk != rdev->pm.current_mclk)) {
and make it
> if (0) {

Does it help?

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

[Bug 37112] GPU lockup when trying to use profile based frequency switching

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=37112





--- Comment #7 from Hrvoje Senjan <hrvoje.senjan@gmail.com>  2011-06-11 15:29:50 ---
Yes it helps! :)
Using default profile:
default engine clock: 600000 kHz
current engine clock: 594000 kHz
default memory clock: 500000 kHz
current memory clock: 495000 kHz
voltage: 1100 mV
PCIE lanes: 16

using low:
default engine clock: 600000 kHz
current engine clock: 109680 kHz
default memory clock: 500000 kHz
current memory clock: 495000 kHz
voltage: 900 mV
PCIE lanes: 16

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.

[Bug 37112] GPU lockup when trying to use profile based frequency switching

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=37112





--- Comment #8 from Hrvoje Senjan <hrvoje.senjan@gmail.com>  2011-06-11 15:38:06 ---
I forgot to say 2 things: a)i tried your suggestion with 3.0.0-rc2 ,b) NO
lockups :)

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.

[Bug 37112] GPU lockup when trying to use profile based frequency switching

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=37112





--- Comment #9 from Hrvoje Senjan <hrvoje.senjan@gmail.com>  2012-06-05 06:33:47 ---
(In reply to comment #6)
> (In reply to comment #5)
> > My first guess is , that kernel changes memory clock too low - with fglrx
> > lowest memory clock is at 400MHz , but with radeon module/low frequency it
> > changes it to 300MHz.
> 
> Please, edit drivers/gpu/drm/radeon/radeon_pm.c, find:
> > if (rdev->asic->set_memory_clock && (mclk != rdev->pm.current_mclk)) {
> and make it
> > if (0) {
> 
> Does it help?

@Rafał
Any progress on this bug?
It's a reall pain to recompile kerenels without powersaving :(

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

[Bug 37112] GPU lockup when trying to use profile based frequency switching

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=37112





--- Comment #10 from Hrvoje Senjan <hrvoje.senjan@gmail.com>  2012-08-27 23:19:31 ---
Just tried 3.6 rc2.
No lockups/hangs! There can be a screen flickering (mostly visible while
scrolling), but now dynpm works correctly:
cat /sys/kernel/debug/dri/0/radeon_pm_info
default engine clock: 600000 kHz
current engine clock: 297000 kHz
default memory clock: 500000 kHz
current memory clock: 396000 kHz
voltage: 900 mV
PCIE lanes: 16

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.

[Bug 37112] GPU lockup when trying to use profile based frequency switching

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=37112





--- Comment #11 from Hrvoje Senjan <hrvoje.senjan@gmail.com>  2012-08-28 02:22:19 ---
Still locks up with low profile.

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.

[Bug 37112] GPU lockup when trying to use profile based frequency switching

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=37112


Hrvoje Senjan <hrvoje.senjan@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
     Kernel Version|2.35-2.6.39                 |2.35-3.9-rc2
           Severity|normal                      |high




--- Comment #12 from Hrvoje Senjan <hrvoje.senjan@gmail.com>  2013-03-15 12:33:54 ---
Would really appreciate for some further info, the situation is the same with
low and mid methods, it tries to change the memory clock too low.
Thanks

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.

[Bug 37112] GPU lockup when trying to use profile based frequency switching

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=37112

Alan <alan@lxorguk.ukuu.org.uk> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |alan@lxorguk.ukuu.org.uk
     Kernel Version|2.35-3.9-rc2                |3.9-rc2

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

[Bug 37112] GPU lockup when trying to use profile based frequency switching

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=37112

Alex Deucher <alexdeucher@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |alexdeucher@gmail.com

--- Comment #13 from Alex Deucher <alexdeucher@gmail.com> ---
You should try the new dpm support in kernel 3.11 or newer.  Boot with
radeon.dpm=1 on the kernel command line in grub.  I don't plan to put any more
work into the old pm code.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.