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.
--
MfG/Sincerely
Toralf Förster
pgp finger print: 7B1A 07F4 EC82 0F90 D4C2 8936 872A E508 7DB6 9DA3
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?
Also, does 3.11-rc5 work for you?
thanks,
greg k-h
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?
Ofc, but as a lazy guy still hoping that somebody points me to a
particular commit
> Also, does 3.11-rc5 work for you?
errm :
> - and FWIW in 3.11-rc5 s2ram is fine."
--
MfG/Sincerely
Toralf Förster
pgp finger print: 7B1A 07F4 EC82 0F90 D4C2 8936 872A E508 7DB6 9DA3
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