From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.sourceforge.net
Subject: [Bug 34102] radeon drm/kms: please use suspend/hibernate notifiers for allocating memory in suspend routines
Date: Tue, 3 May 2011 21:33:09 GMT [thread overview]
Message-ID: <201105032133.p43LX9jj017497@demeter1.kernel.org> (raw)
In-Reply-To: <bug-34102-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=34102
--- Comment #2 from Martin Steigerwald <Martin@Lichtvoll.de> 2011-05-03 21:33:06 ---
It depends on the view point. Compared with the pre KMS radeon driver this has
been a regression for me.
Thanks for trying to provide a workaround. I appreciate it.
I work-around this problem for now by using KDE 4.6 activities which make it
easy to close a set of application before hibernating and restoring them back
to their old state after resuming. Anyway, my next notebook will have 8 GB of
RAM and be 64-Bit, so this should not be much of the problem there. Just to
hint at you that a fix is not urgent for me. But I will have that T42 where the
problem happens at hand to test any workaround you provide.
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
------------------------------------------------------------------------------
WhatsUp Gold - Download Free Network Management Software
The most intuitive, comprehensive, and cost-effective network
management toolset available today. Delivers lowest initial
acquisition cost and overall TCO of any competing solution.
http://p.sf.net/sfu/whatsupgold-sd
--
_______________________________________________
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel
next prev parent reply other threads:[~2011-05-03 21:33 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-29 16:06 [Bug 34102] New: radeon drm/kms driver: please use suspend/hibernate notifiers for allocating memory in suspend routines bugzilla-daemon
2011-04-29 16:06 ` [Bug 34102] radeon drm/kms: " bugzilla-daemon
2011-05-03 20:45 ` bugzilla-daemon
2011-05-03 21:33 ` bugzilla-daemon [this message]
2011-05-03 21:44 ` bugzilla-daemon
2011-05-03 21:44 ` bugzilla-daemon
2011-05-04 14:23 ` bugzilla-daemon
2011-05-04 16:31 ` bugzilla-daemon
2011-05-04 19:37 ` bugzilla-daemon
2011-05-04 20:05 ` bugzilla-daemon
2011-05-05 19:53 ` bugzilla-daemon
2011-05-09 12:15 ` bugzilla-daemon
2011-05-09 15:15 ` bugzilla-daemon
2011-05-09 15:59 ` bugzilla-daemon
2011-05-09 19:06 ` bugzilla-daemon
2011-05-30 7:56 ` bugzilla-daemon
2012-06-13 15:05 ` bugzilla-daemon
2012-06-13 15:05 ` 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=201105032133.p43LX9jj017497@demeter1.kernel.org \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=dri-devel@lists.sourceforge.net \
/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