[Bug 16292] New: "Idle timed out, resetting engine" when running compiz.

[bugzilla-daemon at freedesktop.org]

http://bugs.freedesktop.org/show_bug.cgi?id=16292

           Summary: "Idle timed out, resetting engine" when running compiz.
           Product: xorg
           Version: git
          Platform: x86 (IA32)
        OS/Version: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Driver/Radeon
        AssignedTo: xorg-driver-ati at lists.x.org
        ReportedBy: peter at cs.unisa.edu.au
         QAContact: xorg-team at lists.x.org


[Moved from Bug 4989 to here]
Xorg.log 
http://bugs.freedesktop.org/attachment.cgi?id=17025

I see this bug on git master when running compiz and either starting a new
window or resizing a window. Doesn't happen when moving a window around.

lspci says:
00:08.0 VGA compatible controller: ATI Technologies Inc RV280 [Radeon 9200 PRO]
(rev 01)

The last messages are loads of the following, requiring a hard reset.

(EE) RADEON(0): RADEONWaitForIdleCP: CP idle -22
(EE) RADEON(0): Idle timed out, resetting engine...

I added a return statement into RADEONWaitForIdle so the machine doesn't lock
up anymore, but the timout message is of course still there.

whot at hyena:~/X11R7/driver/xf86-video-ati$> git diff
diff --git a/src/radeon_commonfuncs.c b/src/radeon_commonfuncs.c
index 58fe306..dbdaaf5 100644
--- a/src/radeon_commonfuncs.c
+++ b/src/radeon_commonfuncs.c
@@ -705,6 +705,7 @@ void FUNC_NAME(RADEONWaitForIdle)(ScrnInfoPtr pScrn)

            xf86DrvMsg(pScrn->scrnIndex, X_ERROR,
                       "Idle timed out, resetting engine...\n");
+            return;
            RADEONEngineReset(pScrn);
            RADEONEngineRestore(pScrn);


Comment from Michel Daenzer in Bug 4989:
> You're saying this change keeps things working despite the timeout messages? > If so, the timeout is probably just too short and needs to be extended. 
> Ideally, something like radeon_init_timeout()/radeon_timedout() should be 
> used, to make the actual timeout duration independent of how quickly the 
> various loops are processed.

Multiplying the timeout by 100 doesn't really change the situation, haven't
looked at radeon_init_timeout yet.


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.