From: Nigel Cunningham <ncunningham@crca.org.au>
To: LKML <linux-kernel@vger.kernel.org>, airlied@gmail.com
Subject: 2.6.35 Radeon KMS power management regression?
Date: Tue, 01 Jun 2010 16:23:35 +1000 [thread overview]
Message-ID: <4C04A767.8000209@crca.org.au> (raw)
Hi all.
Just wondering if anyone else has tried to hibernate while using Radeon
KMS and a tree with Dave's post 2.6.34 patches? My 32 bit P4 based
system (with an RV250 card) is hanging at the atomic copy, with the
following backtrace
hibernation_snapshot
dpm_suspend_start
async_synchronize_full
async_synchronize_cookie
async_synchronize_cookie_domain
I've been trying to bisect, but this computer is being painfully slow,
so I haven't been making much progress. 2.6.34 with the same config is
fine, and my bisection progress so far seems to be pointing at the merge
I mentioned above.
Nigel
next reply other threads:[~2010-06-01 6:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-01 6:23 Nigel Cunningham [this message]
2010-06-01 6:33 ` 2.6.35 Radeon KMS power management regression? Dave Airlie
2010-06-01 6:43 ` Nigel Cunningham
2010-06-01 6:57 ` Nigel Cunningham
2010-06-01 22:32 ` Rafael J. Wysocki
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=4C04A767.8000209@crca.org.au \
--to=ncunningham@crca.org.au \
--cc=airlied@gmail.com \
--cc=linux-kernel@vger.kernel.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