From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.sourceforge.net
Subject: [Bug 26872] Kernel 2.6.33 fails to suspend (bisected)
Date: Wed, 31 Mar 2010 04:19:11 -0700 (PDT) [thread overview]
Message-ID: <20100331111911.BABF413005D@annarchy.freedesktop.org> (raw)
In-Reply-To: <bug-26872-502@http.bugs.freedesktop.org/>
http://bugs.freedesktop.org/show_bug.cgi?id=26872
--- Comment #4 from Nix <nix@esperi.org.uk> 2010-03-31 04:19:11 PST ---
Comparison with other Radeon and KMS users indicates that this is almost
certainly r6xx-r7xx-specific. (rv3xx works, r3xx works, Intel works.)
(Well, either that or I'm the only person in the world who's seeing it: I
haven't found anyone else with a r6xx or r7xx who's trying to suspend, yet.)
--
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
--
next prev parent reply other threads:[~2010-03-31 11:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-03 21:37 [Bug 26872] New: Kernel 2.6.33 fails to suspend (semi-bisected) bugzilla-daemon
2010-03-03 21:38 ` [Bug 26872] " bugzilla-daemon
2010-03-04 23:40 ` [Bug 26872] Kernel 2.6.33 fails to suspend (bisected) bugzilla-daemon
2010-03-15 22:21 ` bugzilla-daemon
2010-03-31 11:19 ` bugzilla-daemon [this message]
2010-04-02 17:08 ` bugzilla-daemon
2010-04-03 1:11 ` bugzilla-daemon
2019-11-19 8:10 ` 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=20100331111911.BABF413005D@annarchy.freedesktop.org \
--to=bugzilla-daemon@freedesktop.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