From: Greg KH <gregkh@linuxfoundation.org>
To: James Courtier-Dutton <james.dutton@gmail.com>
Cc: Dave Airlie <airlied@gmail.com>, Ben Skeggs <bskeggs@redhat.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 16:02:36 -0800 [thread overview]
Message-ID: <20130228000236.GA2216@kroah.com> (raw)
In-Reply-To: <CAAMvbhEAcLuE+5KGP13wCc8nVBp1Eq-UPtaUD7c5oGVq8io8Lw@mail.gmail.com>
On Wed, Feb 27, 2013 at 11:27:30PM +0000, James Courtier-Dutton wrote:
> On 26 February 2013 18:11, James Courtier-Dutton <james.dutton@gmail.com> wrote:
> > On 26 February 2013 17:35, Greg KH <gregkh@linuxfoundation.org> 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...
> >>
> >
> > If it helps, I have a similar resume problem here.
> > 3.7.8 good
> > 3.8.0 bad
> >
> > Laptop with no nvidia, no amd graphics, just Intel Graphics 4000, 3rd
> > Gen I5 CPU.
>
> Problem: "Backlight not coming on after resume."
> git finally bisected for my Samsung Serial 7 Laptop.
> Bisecting: 0 revisions left to test after this (roughly 0 steps)
> [cf0a6584aa6d382f802f2c3cacac23ccbccde0cd] drm/i915: write backlight
> harder <- This is the problem commit. Seems that fixing some
> machines breaks others, based on the existing comments on that patch.
Hm, so, 3.8.0 works for you, but 3.8.1-rc1 doesn't? Or are you saying
Linus's tree doesn't work for you?
As you have a different issue here than the nvidia hardware I was
dealing with, you might want to try to start over with a new thread and
the needed info, and the needed people on it (i.e. the i915
maintainers and mailing list.)
thanks,
greg k-h
next prev parent reply other threads:[~2013-02-28 0:02 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 [this message]
2013-02-28 0:31 ` James Courtier-Dutton
2013-02-27 4:02 ` Greg KH
2013-02-27 9:25 ` Ben Skeggs
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=20130228000236.GA2216@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=airlied@gmail.com \
--cc=airlied@linux.ie \
--cc=bskeggs@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=james.dutton@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox