From mboxrd@z Thu Jan 1 00:00:00 1970
From: bugzilla-daemon@bugzilla.kernel.org
Subject: [Bug 16273] suspend/resume failure with radeon kms driver
Date: Fri, 16 Jul 2010 22:03:07 GMT
Message-ID: <201007162203.o6GM37fg004252@demeter.kernel.org>
References:
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path:
In-Reply-To:
List-Unsubscribe: ,
List-Archive:
List-Post:
List-Help:
List-Subscribe: ,
Errors-To: dri-devel-bounces@lists.sourceforge.net
To: dri-devel@lists.sourceforge.net
List-Id: dri-devel@lists.freedesktop.org
https://bugzilla.kernel.org/show_bug.cgi?id=16273
Jose Marino changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #27025|0 |1
is obsolete| |
--- Comment #5 from Jose Marino 2010-07-16 22:01:43 ---
Created an attachment (id=27132)
--> (https://bugzilla.kernel.org/attachment.cgi?id=27132)
dmesg after suspend/resume test (debug test)
I was able to get more info about this bug.
I added an early return in the radeon resume routine with this patch applied on
top of f469461df6ff822f71b8737bda86eea20f16ff93
--- a/drivers/gpu/drm/radeon/radeon_device.c
+++ b/drivers/gpu/drm/radeon/radeon_device.c
@@ -799,6 +799,10 @@ int radeon_resume_kms(struct drm_device *dev)
radeon_pm_resume(rdev);
radeon_restore_bios_scratch_regs(rdev);
+ printk(KERN_INFO "radeon: **TEST** resume early\n");
+ release_console_sem();
+ return -1;
+
/* turn on display hw */
list_for_each_entry(connector, &dev->mode_config.connector_list, head)
{
drm_helper_connector_dpms(connector, DRM_MODE_DPMS_ON);
I booted this kernel and did a suspend/resume cycle, saved the dmesg and
rebooted. After the resume the display was black but I was able to save the
dmesg and start the reboot. The laptop locked up on reboot.
There are some new interesting error messages in the dmesg:
[drm:radeon_ring_write] *ERROR* radeon: writting more dword to ring than
expected !
[drm:r100_ring_test] *ERROR* radeon: ring test failed
(sracth(0x15E4)=0xFFFFFFFF)
[drm:r100_cp_init] *ERROR* radeon: cp isn't working (-22).
radeon 0000:01:00.0: failled initializing CP (-22).
I attach the full dmesg just in case.
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
------------------------------------------------------------------------------
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
--