From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 39714] New: Slow and choppy 3D performace on evergreen after pm-suspend
Date: Mon, 1 Aug 2011 05:12:17 -0700 (PDT) [thread overview]
Message-ID: <bug-39714-502@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=39714
Summary: Slow and choppy 3D performace on evergreen after
pm-suspend
Product: Mesa
Version: git
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/r600
AssignedTo: dri-devel@lists.freedesktop.org
ReportedBy: bugs.xorg@boris64.net
Created an attachment (id=49783)
--> (https://bugs.freedesktop.org/attachment.cgi?id=49783)
dmesg including pm-suspend event
I get very slow and choppy 3d performance after suspending my computer.
This is valid for glxgears (i-know-it's-not-a-benchmark), kwin and others.
After restarting the 3d application speed seems to be normal/ok again.
Example:
[glxgears output]
17641 frames in 5.0 seconds = 3528.125 FPS
18396 frames in 5.0 seconds = 3679.087 FPS
22768 frames in 5.0 seconds = 4553.543 FPS
18280 frames in 5.0 seconds = 3655.863 FPS
16051 frames in 5.0 seconds = 3210.111 FPS
16030 frames in 5.0 seconds = 3205.946 FPS
18157 frames in 5.0 seconds = 3628.626 FPS
18182 frames in 5.0 seconds = 3636.259 FPS
...
(-> pm-msuspend here <-)
...
12270 frames in 19.1 seconds = 641.561 FPS
4518 frames in 5.0 seconds = 903.255 FPS
4721 frames in 5.0 seconds = 944.181 FPS
4750 frames in 5.0 seconds = 949.833 FPS
4724 frames in 5.0 seconds = 944.745 FPS
4759 frames in 5.0 seconds = 951.687 FPS
4535 frames in 5.0 seconds = 905.757 FPS
4557 frames in 5.0 seconds = 911.264 FPS
[/glxgears output]
Used drivers+software:
-xorg-server-1.10.3
-mesa(r600g)/ddx/libdrm from git (latest)
-kernel-3.0.0
If you need more infos/logs, please do not hesitate to ask.
Thank you in advance!
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2011-08-01 12:12 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-01 12:12 bugzilla-daemon [this message]
2011-08-01 12:12 ` [Bug 39714] Slow and choppy 3D performace on evergreen after pm-suspend bugzilla-daemon
2011-08-01 12:13 ` bugzilla-daemon
2011-08-10 14:51 ` bugzilla-daemon
2011-08-31 13:43 ` bugzilla-daemon
2011-08-31 19:53 ` bugzilla-daemon
2011-08-31 19:53 ` bugzilla-daemon
2011-08-31 19:54 ` bugzilla-daemon
2011-08-31 19:55 ` bugzilla-daemon
2011-08-31 19:55 ` bugzilla-daemon
2011-08-31 19:55 ` bugzilla-daemon
2011-08-31 19:56 ` bugzilla-daemon
2011-08-31 19:56 ` bugzilla-daemon
2011-09-07 10:29 ` bugzilla-daemon
2011-09-25 15:34 ` bugzilla-daemon
2019-09-18 18:58 ` 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-39714-502@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 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.