From: Dave Airlie <airlied@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: 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: Mon, 25 Feb 2013 16:21:40 +1000 [thread overview]
Message-ID: <CAPM=9txjG5rohsNbme=myrX+-Z5eucpEXYQMWqPQqN=5dNze8g@mail.gmail.com> (raw)
In-Reply-To: <CAPM=9tw_vfESbbH4dD9z8mAYVYcwmVs=n4BrRz4XBj1Rw1qrkw@mail.gmail.com>
On Mon, Feb 25, 2013 at 4:06 PM, Dave Airlie <airlied@gmail.com> 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.
>
> Cool, might have to lend Ben my retina to see if he can reproduce.
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.
Dave.
next prev parent reply other threads:[~2013-02-25 6:21 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 [this message]
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
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='CAPM=9txjG5rohsNbme=myrX+-Z5eucpEXYQMWqPQqN=5dNze8g@mail.gmail.com' \
--to=airlied@gmail.com \
--cc=airlied@linux.ie \
--cc=bskeggs@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).