From mboxrd@z Thu Jan  1 00:00:00 1970
From: Seth Forshee <seth.forshee@canonical.com>
Subject: Re: radeon issues on MacBook Pro 8,2
Date: Fri, 20 Jan 2012 15:12:14 -0600
Message-ID: <20120120211214.GC8162@ubuntu-macmini>
References: <20120119171808.GB23144@ubuntu-macmini>
 <CADnq5_MiLE0XSpbrd66003DVxdR9c4MgQav3BD+bWtrKvbf+7Q@mail.gmail.com>
 <20120119205317.GC23144@ubuntu-macmini>
 <20120120155318.GA8162@ubuntu-macmini>
 <CADnq5_NNpwsPoEP0_fzSJ9LQKfaHPJx90yObXKYHO39xLWM6sQ@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: QUOTED-PRINTABLE
Return-path: <linux-kernel-owner@vger.kernel.org>
Content-Disposition: inline
In-Reply-To: <CADnq5_NNpwsPoEP0_fzSJ9LQKfaHPJx90yObXKYHO39xLWM6sQ@mail.gmail.com>
Sender: linux-kernel-owner@vger.kernel.org
To: Alex Deucher <alexdeucher@gmail.com>
Cc: Dave Airlie <airlied@redhat.com>, Alex Deucher <alexander.deucher@amd.com>, dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
List-Id: dri-devel@lists.freedesktop.org

On Fri, Jan 20, 2012 at 02:38:37PM -0500, Alex Deucher wrote:
> On Fri, Jan 20, 2012 at 10:53 AM, Seth Forshee
> <seth.forshee@canonical.com> wrote:
> > On Thu, Jan 19, 2012 at 02:53:17PM -0600, Seth Forshee wrote:
> >> > > =C2=A02. Occasional long delays when suspending. When this hap=
pens 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* at=
ombios stuck executing D44E (len 62, WS 0, PS 0) @ 0xD46A
> >> > >
> >> > > =C2=A0 =C2=A0Sometimes one of suspend or resume hangs complete=
ly, but I can't
> >> > > =C2=A0 =C2=A0tell which and am not sure whether or not it's re=
lated. I'm also
> >> > > =C2=A0 =C2=A0testing a Mac Mini with the exact same card which=
 does not seem to
> >> > > =C2=A0 =C2=A0suffer from this issue.
> >> > >
> >> > > =C2=A0 =C2=A0I ran a bisections that identified f8d0edd (drm/r=
adeon/kms: improve
> >> > > =C2=A0 =C2=A0DP detect logic) as introducing problems with sus=
pend, and reverting
> >> > > =C2=A0 =C2=A0this patch on top of 3.2.1 does seem to eliminate=
 both issues.
> >> > >
> >> >
> >> > That patch doesn't really affect the modesetting paths directly;=
 it
> >> > looks like a red herring to me.
> >>
> >> Perhaps. I just started a run of 200 s3 cycles with the patch reve=
rted
> >> to see if I can reproduce the issues. I can usually trigger the pr=
oblem
> >> with 15 or fewer s3 cycles.
> >
> > The machine completed 200 s3 cycles with the patch reverted without=
 long
> > 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.
> >
> > I added a printout of the connector status resulting from the logic=
 that
> > was changed by f8d0edd. With the logic prior to this commit it
> > consistently returns the status as disconnected, which is correct a=
s I
> > have nothing connected. But with the improved logic the status is
> > sometimes reported as connected, and these coincide with the atombi=
os
> > errors.
> >
>=20
> Do any of the disconnected displayport connectors get misdetected as
> connected during normal operation or does it only happen during
> suspend/resume?

So far I've only seen them during suspend/resume.