linux-kernel - Re: 3.5-rcX: wakeup after s2ram doesn't work after a longer sleep time

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, 16 Jul 2012 15:50:22 +0200
From:	Toralf Förster <toralf.foerster@....de>
To:	"Rafael J. Wysocki" <rjw@...k.pl>
CC:	Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Re: 3.5-rcX: wakeup after s2ram doesn't work after a longer sleep
 time

On 07/15/2012 10:21 PM, Rafael J. Wysocki wrote:
> On Sunday, July 15, 2012, Toralf Förster wrote:
>> My ThinkPad T400 (Gentoo Linux booted from an external USB drive) does
>> not wake up after s2ram, if the  sleep time was longer than about 1 hour.
>> I'm unsure whether this started after 3.5-rc5, at least with -rc7 I
>> observed this now several times. Unfortunately it is not 100% reproduceable.
>>
>> 3.4.x works flawlessly.
>>
>> Any idea whether a particular commit could be the culprit ? (Bisecting
>> such an issue is a night mare)
> 
> Please check
> 
> commit 5baefd6d84163443215f4a99f6a20f054ef11236
> Author: John Stultz <johnstul@...ibm.com>
> Date:   Tue Jul 10 18:43:25 2012 -0400
> 
>     hrtimer: Update hrtimer base offsets each hrtimer_interrupt
> 
> Thanks,
> Rafael
> 

No,
reverting doesn#t help.

I can r2ram several times in a row w/o problems, if the sleep time as
within seconds.
After 20 min however the system doesn't came back (the internal hard
disk spins up, but the sleep-state-led is still on).


-- 
MfG/Sincerely
Toralf Förster
pgp finger print: 7B1A 07F4 EC82 0F90 D4C2 8936 872A E508 7DB6 9DA3


--
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/