Dave Airlie wrote:
On Mon, Feb 9, 2009 at 8:07 AM, etienne <etienne.basset@xxxxxxxxxxxxxx> wrote:
Rafael J. Wysocki wrote:
This message has been generated automatically as a part of a report
of recent regressions.
The following bug entry is on the current list of known regressions
from 2.6.28. Please verify if it still should be listed and let me know
(either way).
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=12613
Subject : [Suspend regression][DRM, RADEON]
Submitter : etienne <etienne.basset@xxxxxxxxxxxxxx>
Date : 2009-01-28 22:00 (12 days old)
First-Bad-Commit:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=a9d51a5ad1154b5b20add1e8d30a5564f8aabbe9
References : http://marc.info/?l=linux-kernel&m=123318030419558&w=4
http://marc.info/?l=linux-kernel&m=123334865404574&w=4
hello,
yes it's still present in -rc4
But I noticed that when I switch off KDE4.2 desktop effects, suspend to ram
is 100% reliable with 2.6.29-rc4
With 2.6.28, STR is 100% reliable with or without desktop effects
Hi Etienne,
Can you try commenting out the calls to the radeon_suspend and
radeon_resume hooks in radeon_drv.c?
Dave.
Hi Dave,
I just tested that and I didn't change anything (cannot STR/resume with
desktop effect, STR/resume OK without desktop effects)
thanks,
Etienne
the patch i used, to verify i understood you ;)
diff --git a/drivers/gpu/drm/radeon/radeon_drv.c
b/drivers/gpu/drm/radeon/radeon
index fef2078..805b367 100644
--- a/drivers/gpu/drm/radeon/radeon_drv.c
+++ b/drivers/gpu/drm/radeon/radeon_drv.c
@@ -90,8 +90,8 @@ static struct drm_driver driver = {
.postclose = radeon_driver_postclose,
.lastclose = radeon_driver_lastclose,
.unload = radeon_driver_unload,
- .suspend = radeon_suspend,
- .resume = radeon_resume,
+/* .suspend = radeon_suspend,
+ .resume = radeon_resume, */
.get_vblank_counter = radeon_get_vblank_counter,
.enable_vblank = radeon_enable_vblank,
.disable_vblank = radeon_disable_vblank,
--
To unsubscribe from this list: send the line "unsubscribe kernel-testers" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
