lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Mon, 25 Feb 2013 19:45:45 -0800
From:	Greg KH <gregkh@...uxfoundation.org>
To:	Dave Airlie <airlied@...il.com>
Cc:	Ben Skeggs <bskeggs@...hat.com>, David Airlie <airlied@...ux.ie>,
	Martin Peres <martin.peres@...ri.fr>,
	dri-devel@...ts.freedesktop.org, linux-kernel@...r.kernel.org
Subject: Re: resume fails to light display on Macbook Pro Retina on 3.8-rc1

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@...uxfoundation.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.

thanks,

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ