From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: dri-devel@lists.sourceforge.net
Cc: "Dave Airlie" <airlied@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
"pm list" <linux-pm@lists.linux-foundation.org>,
"Jérôme Glisse" <glisse@freedesktop.org>
Subject: Resume problem with radeon+KMS (2.6.34-rc2 and before)
Date: Sun, 21 Mar 2010 22:28:13 +0100 [thread overview]
Message-ID: <201003212228.13923.rjw@sisk.pl> (raw)
Hi,
Some time ago I reported a problem with resuming from suspend to RAM on
HP nx6325 with radeon+KMS.
The problem was that the first resume always failed if the suspend was started
from under X. Moreover, the resume went correctly until the last switch from
the framebuffer console (which was now controlled by the radeon driver as
well) to X that made the box hang hard.
However, if the first resume was started from the (radeon-controlled)
framebuffer console, the subsequent resume succeeded and all of the next
attempts to suspend/resume succeeded, _regardless_ of the way the suspend was
started.
At that time Dave thought it might be a problem with the nx6325's graphics
adapter that apparently was a crappy one, but today I found that _exactly_ the
same behavior was observable on Acer Ferrari One, which was quite different,
hardware-wise, from the old HP box. For this reason I think the problem is
related to the driver itself rather than to the hardware or firmware.
The problem is reproducible on both machines with the latest git kernel
and the user space radeon_drv.so from openSUSE 11.2 (it says
module version = 6.12.4 in the X log). The kernel and user space are 64-bit
on both machines. [For completness, the Acer box suspends and resumes
correctly with radeon.modeset=0 and "s2ram -f -p -m".]
Should I try a newer user space X driver? Or may the problem be related to
the 64-bitness somehow?
Rafael
next reply other threads:[~2010-03-21 21:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-21 21:28 Rafael J. Wysocki [this message]
2010-03-21 22:36 ` Resume problem with radeon+KMS (2.6.34-rc2 and before) Dave Airlie
2010-03-21 23:07 ` Rafael J. Wysocki
2010-03-21 23:10 ` Dave Airlie
2010-03-21 23:16 ` Rafael J. Wysocki
2010-03-21 23:35 ` 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=201003212228.13923.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.sourceforge.net \
--cc=glisse@freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.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