From: Ben Skeggs <bskeggs@redhat.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Dave Airlie <airlied@gmail.com>, David Airlie <airlied@linux.ie>,
Martin Peres <martin.peres@labri.fr>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: resume fails to light display on Macbook Pro Retina on 3.8-rc1
Date: Wed, 27 Feb 2013 19:25:35 +1000 [thread overview]
Message-ID: <1361957135.3358.0.camel@localhost> (raw)
In-Reply-To: <20130227040251.GA1081@kroah.com>
On Tue, 2013-02-26 at 20:02 -0800, Greg KH wrote:
> On Tue, Feb 26, 2013 at 09:35:14AM -0800, Greg KH wrote:
> > On Mon, Feb 25, 2013 at 07:45:45PM -0800, Greg KH wrote:
> > > On Mon, Feb 25, 2013 at 02:32:43PM -0800, Greg KH wrote:
> > > > On Mon, Feb 25, 2013 at 04:06:02PM +1000, Dave Airlie wrote:
> > > > > On Mon, Feb 25, 2013 at 3:52 PM, Greg KH <gregkh@linuxfoundation.org> wrote:
> > > > > > Hi Ben,
> > > > > >
> > > > > > My Macbook Pro Retina fails to resume properly on 3.8. I tracked this
> > > > > > down to commit 6c5a04249d7afeea3e0ed971e7813f84e29a1706 (drm/nvd0/disp:
> > > > > > move link training helpers into core as display methods)
> > > > > >
> > > > > > Anything I can try to help solve this?
> > > > > >
> > > > > > Note, I'm using the Intel driver as the main controller for this laptop,
> > > > > > well, I think I am, my xorg log is attached.
> > > > >
> > > > > No you are using the nvidia, the efi always boots nvidia enabled now.
> > > >
> > > > Really? When did that change? I thought I wanted to be using the Intel
> > > > chip to save battery life.
> > > >
> > > > > btw I just tested my drm-next tree on mine and it resumed the display
> > > > > fine, something oopsed a few seconds later that I haven't tracked down
> > > > >
> > > > > git://git.freedesktop.org/~airlied/linux drm-next
> > > > >
> > > > > I'll be sending it to Linus this evening or tomorrow morning, once I
> > > > > fix my tree.
> > > >
> > > > Ok, I'll test again when it hits Linus's tree, and if that works, it
> > > > would be good to try to work out what patch fixes it to get them into
> > > > the 3.8-stable series so that others don't run into the same problem.
> > >
> > > I've tested Linus's tree now (I'm guessing it has all of your changes in
> > > it), and it works!
> > >
> > > I see a bunch of patches marked for the stable branch, so I'll try those
> > > out and see if they fix the problem. If not, I'll let you and Ben know.
> >
> > I've applied the radeon patches tagged for -stable and tested that on
> > 3.8.0, but that doesn't solve the resume problem. Any ideas of anything
> > else I can do to test this? Doing a "backwards" git-bisect is a pain,
> > but I guess I can do that to try to track down what patch fixed this, if
> > that's the only idea people have...
>
> Ok, after getting my brain warped by doing a reverse 'git bisect', I
> tracked it down to commit ac8cc241a81941932da44993242e68c62e115ec7
> (drm/nv50/devinit: reverse the logic for running encoder init scripts)
> as the patch that solves the problem.
>
> So, I tried applying that patch on 3.8.1-rc1, but ran into the efifb bug
> that Dave fixed already, which took me a while, so I've queued that up
> for 3.8.1. Then I determined that it really also needs commit
> f3ed1048715f2edc10c4dda6148b60e93f6282ed (drm/nouveau/bios: parse
> external transmitter type if off-chip) and commit
> 8e992c8d9eebc2bd3246252ee5c0422dbbbce7ae (drm/nouveau/bios: store a
> type/mask hash in parsed dcb data) in order to build properly.
>
> With those three patches, plus the efifb fix, I can now properly boot,
> and suspend and resume my macbook on 3.8.1-rc1. Just like I can on
> Linus's tree.
>
> So, Ben, Dave, any objection to me including these 3 nouveau patches in
> the 3.8.1-final release?
Thanks for taking the time to track down exactly what's needed here. I
believe those three should be safe to apply.
Ben.
>
> thanks,
>
> greg k-h
next prev parent reply other threads:[~2013-02-27 9:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-25 5:52 resume fails to light display on Macbook Pro Retina on 3.8-rc1 Greg KH
2013-02-25 6:06 ` Dave Airlie
2013-02-25 6:21 ` Dave Airlie
2013-02-25 22:32 ` Greg KH
2013-02-26 3:45 ` Greg KH
2013-02-26 17:35 ` Greg KH
2013-02-26 18:11 ` James Courtier-Dutton
2013-02-26 18:22 ` Greg KH
2013-02-27 23:27 ` James Courtier-Dutton
2013-02-28 0:02 ` Greg KH
2013-02-28 0:31 ` James Courtier-Dutton
2013-02-27 4:02 ` Greg KH
2013-02-27 9:25 ` Ben Skeggs [this message]
2013-02-27 17:09 ` Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1361957135.3358.0.camel@localhost \
--to=bskeggs@redhat.com \
--cc=airlied@gmail.com \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.peres@labri.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.