From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 67002] evergreen: after resume from suspend-to-ram operation is really slow with the latest DPM changes + gpu lockup Date: Wed, 24 Jul 2013 20:05:31 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0619548860==" Return-path: Received: from culpepper.freedesktop.org (unknown [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 3251EE5D0E for ; Wed, 24 Jul 2013 13:05:31 -0700 (PDT) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org Errors-To: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============0619548860== Content-Type: multipart/alternative; boundary="1374696331.1eCeb7de0.10803"; charset="us-ascii" --1374696331.1eCeb7de0.10803 Date: Wed, 24 Jul 2013 20:05:31 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" https://bugs.freedesktop.org/show_bug.cgi?id=67002 --- Comment #10 from jackdachef@gmail.com --- (In reply to comment #9) > Maybe unrelated to this bug report, but with today's Linus' master > (04012e3076943f17c8cfc77a196701c8f0b8964f) the only suspend/resume issue > left is that I get: > > [drm:rv770_stop_dpm] *ERROR* Could not force DPM to low. > > in dmesg upon resume. > > That is before the 'ring' and 'uvd' messages. It seems harmless, I didn't > notice any problems. It can switch power levels later on, play videos via > uvd... it just seems to try to do something with dpm too early in the resume > process. indeed - the recent changes made a difference I'm currently posting from the kernel running from resumed suspend-to-ram the only changes were that I set to "auto" echo auto > /sys/class/drm/card0/device/power_dpm_force_performance_level and am running that new kernel posted over at phoronix forums probably will try out with forced "low" profile/performance_level in the weekend and see if I get a similar message to yours now I need the box up and running for work will continue using it and see whether something strange occurs if that's the case I'll post it here otherwise it's running fine so far ... Thanks a lot to everyone for the fixes & work ! on a side-note: the hardlocks I experienced in the past might have been due to BFQ & some exotic setup/tweaks/additional patches that I'm using so perhaps no hardlocks with the DPM code so far :) -- You are receiving this mail because: You are the assignee for the bug. --1374696331.1eCeb7de0.10803 Date: Wed, 24 Jul 2013 20:05:31 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8"

Comment # 10 on bug 67002 from 
(In reply to comment #9)
> Maybe unrelated to this bug report, but with today's Linus' master
> (04012e3076943f17c8cfc77a196701c8f0b8964f) the only suspend/resume issue
> left is that I get:
> 
> [drm:rv770_stop_dpm] *ERROR* Could not force DPM to low.
> 
> in dmesg upon resume.
> 
> That is before the 'ring' and 'uvd' messages. It seems harmless, I didn't
> notice any problems. It can switch power levels later on, play videos via
> uvd... it just seems to try to do something with dpm too early in the resume
> process.

indeed - the recent changes made a difference

I'm currently posting from the kernel running from resumed suspend-to-ram

the only changes were

that I set to "auto"

 echo auto > /sys/class/drm/card0/device/power_dpm_force_performance_level

and am running that new kernel posted over at phoronix forums


probably will try out with forced "low" profile/performance_level in the
weekend and see if I get a similar message to yours

now I need the box up and running for work

will continue using it and see whether something strange occurs

if that's the case I'll post it here

otherwise it's running fine so far ...


Thanks a lot to everyone for the fixes & work ! 


on a side-note: the hardlocks I experienced in the past might have been due to
BFQ & some exotic setup/tweaks/additional patches that I'm using

so perhaps no hardlocks with the DPM code so far :)

You are receiving this mail because:
  • You are the assignee for the bug.
--1374696331.1eCeb7de0.10803-- --===============0619548860== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel --===============0619548860==--