From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 34491] New: Resuming from Suspend to RAM causes poor 2D performance
Date: Sat, 19 Feb 2011 15:30:21 -0800 (PST) [thread overview]
Message-ID: <bug-34491-8800@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=34491
Summary: Resuming from Suspend to RAM causes poor 2D
performance
Product: xorg
Version: 7.4
Platform: x86 (IA32)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Driver/nouveau
AssignedTo: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
ReportedBy: shiningarcanine-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
QAContact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org
Created an attachment (id=43562)
--> (https://bugs.freedesktop.org/attachment.cgi?id=43562)
dmesg kernel log following a boot, suspend to RAM and then resume
I am using KDE 4.6.0 on Gentoo Linux's testing tree with the Linux 2.6.38-rc5
kernel. Resuming from a suspend to RAM kills 2D performance. This issue also
occurs with Linux 2.6.38-rc4.
I discovered this while I was testing a power management patch for Martin
Peres. His patch provided a proc interface for changing my card's performance
level. If I set the performance level and suspend to RAM, the system will not
resume at all and I cannot even ssh into it. Without setting a performance
level with his patch applied, the system will resume from a suspend to RAM, but
2D performance is awful. Resuming from a suspend to RAM also results in poor 2D
performance even if his patch is not applied.
There are some messages in the dmesg kernel log that seem to describe what is
going wrong, but I do not understand them. I have attached the output.
--
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-02-19 23:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-19 23:30 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
[not found] ` <bug-34491-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2011-02-20 0:43 ` [Bug 34491] Resuming from Suspend to RAM causes poor 2D performance bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-12-05 21:57 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-12-05 21:57 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-18 18:09 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
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-34491-8800@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon-cc+yj3umiyqdupfqwhejaq@public.gmane.org \
--cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.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.