From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Message-ID: <520A8749.9000406@gmx.de> Date: Tue, 13 Aug 2013 21:21:45 +0200 From: =?UTF-8?B?VG9yYWxmIEbDtnJzdGVy?= MIME-Version: 1.0 To: Greg KH CC: Linux Kernel , stable@vger.kernel.org Subject: Re: s2ram + X11 broken between 3.10.5 and 3.10.6 (i915) References: <520A5822.4080804@gmx.de> <20130813175949.GE7336@kroah.com> <520A7CB6.4020403@gmx.de> In-Reply-To: <520A7CB6.4020403@gmx.de> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: On 08/13/2013 08:36 PM, Toralf Förster wrote: > On 08/13/2013 07:59 PM, Greg KH wrote: >> On Tue, Aug 13, 2013 at 06:00:34PM +0200, Toralf Förster wrote: >>> At a ThinkPad T420 w/ a 32 bit stable Gentoo Linux and a started X11 >>> server an attempt to s2ram results in a blank scree, a gloomy blinking >>> power button and no syslog message or something helpful . If the system >>> is booting w/o X11 then s2ram works. >>> >>> s2ram in 3.10.5 works - and FWIW in 3.11-rc5 s2ram is fine. >> >> Can you run 'git bisect' to track it down to the offending patch? > Ick, I forgot that I patched the 3.10.X directory with: https://patchwork.kernel.org/patch/2827512/ patching that out now let s2ram works again in 3.10.6 (but s2disk is broken in 3.10.6, however I do not know, since when, nevertheless a different issue) -- MfG/Sincerely Toralf Förster pgp finger print: 7B1A 07F4 EC82 0F90 D4C2 8936 872A E508 7DB6 9DA3