https://bugzilla.novell.com/show_bug.cgi?id=826248 https://bugzilla.novell.com/show_bug.cgi?id=826248#c0 Summary: Radeon memory clock is set incorrectly with profile based PM Classification: openSUSE Product: openSUSE Factory Version: 13.1 Milestone 2 Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers@forge.provo.novell.com ReportedBy: hrvoje.senjan@gmail.com QAContact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/29.0.1541.0 Safari/537.36 SUSE/29.0.1541.0 Reporting this also here (don't know what is our kernel bug policy cause this is a pure upstream bug, but maybe some suse kernel wizard will know better ;-), https://bugzilla.kernel.org/show_bug.cgi?id=37112. Problem occurs "only" with low/mid profiles as memory frequency is wrongly set. E.g. with my mobility 3650 (RV635), lowest memory frequency should go to 396000 kHz, but with mentioned methods it goes as low as 296000, therefore, too low. What is strange/interesting is that memory is set correctly with dynpm, but that method doesn't set the engine clock low enough for a usable laptop in summer :-) Reproducible: Always Steps to Reproduce: 1. echo low > /sys/class/drm/card0/device/power_profile Actual Results: GPU hang Expected Results: Cool laptop Let me know if i can provide further info. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.