dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.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	[thread overview]
Message-ID: <bug-67002-502-eZ0TrmKgKZ@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-67002-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 1569 bytes --]

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.

[-- Attachment #1.2: Type: text/html, Size: 2579 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

  parent reply	other threads:[~2013-07-24 20:05 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-17 15:10 [Bug 67002] New: evergreen: after resume from suspend-to-ram operation is really slow with the latest DPM changes bugzilla-daemon
2013-07-17 15:10 ` [Bug 67002] evergreen: after resume from suspend-to-ram operation is really slow with the latest DPM changes + gpu lockup bugzilla-daemon
2013-07-19 12:54 ` bugzilla-daemon
2013-07-19 15:35 ` bugzilla-daemon
2013-07-19 15:37 ` bugzilla-daemon
2013-07-19 16:51 ` bugzilla-daemon
2013-07-19 17:26 ` bugzilla-daemon
2013-07-19 17:44 ` bugzilla-daemon
2013-07-20 15:42 ` bugzilla-daemon
2013-07-24 10:07 ` bugzilla-daemon
2013-07-24 14:45 ` bugzilla-daemon
2013-07-24 20:05 ` bugzilla-daemon [this message]
2013-07-24 21:30 ` bugzilla-daemon
2013-07-27 21:24 ` bugzilla-daemon
2013-07-27 21:37 ` bugzilla-daemon
2019-11-19  8:36 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-67002-502-eZ0TrmKgKZ@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox