From mboxrd@z Thu Jan 1 00:00:00 1970 From: Seth Forshee Subject: Re: radeon issues on MacBook Pro 8,2 Date: Fri, 20 Jan 2012 09:53:18 -0600 Message-ID: <20120120155318.GA8162@ubuntu-macmini> References: <20120119171808.GB23144@ubuntu-macmini> <20120119205317.GC23144@ubuntu-macmini> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: Content-Disposition: inline In-Reply-To: <20120119205317.GC23144@ubuntu-macmini> Sender: linux-kernel-owner@vger.kernel.org To: Alex Deucher , Dave Airlie , Alex Deucher , dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org Cc: Seth Forshee List-Id: dri-devel@lists.freedesktop.org On Thu, Jan 19, 2012 at 02:53:17PM -0600, Seth Forshee wrote: > > > =C2=A02. Occasional long delays when suspending. When this happen= s I see > > > =C2=A0 =C2=A0messages like following in dmesg: > > > > > > =C2=A0 =C2=A0 =C2=A0[drm:atom_op_jump] *ERROR* atombios stuck in = loop for more than 5secs aborting > > > =C2=A0 =C2=A0 =C2=A0[drm:atom_execute_table_locked] *ERROR* atomb= ios stuck executing D44E (len 62, WS 0, PS 0) @ 0xD46A > > > > > > =C2=A0 =C2=A0Sometimes one of suspend or resume hangs completely,= but I can't > > > =C2=A0 =C2=A0tell which and am not sure whether or not it's relat= ed. I'm also > > > =C2=A0 =C2=A0testing a Mac Mini with the exact same card which do= es not seem to > > > =C2=A0 =C2=A0suffer from this issue. > > > > > > =C2=A0 =C2=A0I ran a bisections that identified f8d0edd (drm/rade= on/kms: improve > > > =C2=A0 =C2=A0DP detect logic) as introducing problems with suspen= d, and reverting > > > =C2=A0 =C2=A0this patch on top of 3.2.1 does seem to eliminate bo= th issues. > > > > >=20 > > That patch doesn't really affect the modesetting paths directly; it > > looks like a red herring to me. >=20 > Perhaps. I just started a run of 200 s3 cycles with the patch reverte= d > to see if I can reproduce the issues. I can usually trigger the probl= em > with 15 or fewer s3 cycles. The machine completed 200 s3 cycles with the patch reverted without lon= g delays, hangs, or any atombios error messages. Without reverting it doesn't get through many at all before experiencing the errors and long delays or hangs.=20 I added a printout of the connector status resulting from the logic tha= t was changed by f8d0edd. With the logic prior to this commit it consistently returns the status as disconnected, which is correct as I have nothing connected. But with the improved logic the status is sometimes reported as connected, and these coincide with the atombios errors. Seth