linux-kernel - Re: 2.6.27-rc6: nohz + s2ram = need to press keys to get progress

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>] [day] [month] [year] [list]

Message-ID: <20080914154902.GA30891@rhlx01.hs-esslingen.de>
Date:	Sun, 14 Sep 2008 17:49:02 +0200
From:	Andreas Mohr <andi@...as.de>
To:	Thomas Gleixner <tglx@...utronix.de>
Cc:	kernel list <linux-kernel@...r.kernel.org>,
	Linux-pmmailinglist@...x01.hs-esslingen.de
Subject: Re: 2.6.27-rc6: nohz + s2ram = need to press keys to get progress

<linux-pm@...ts.osdl.org>, "Rafael J. Wysocki" <rjw@...k.pl>, Pavel
Machek <pavel@...e.cz>
Bcc: 
Subject: Re: 2.6.27-rc6: nohz + s2ram = need to press keys to get progress
Reply-To: 
In-Reply-To: <alpine.LFD.1.10.0809122111480.13819@...llo.tec.linutronix.de>
X-Priority: none

Hi,

> did this happen between rc5 and rc6 ?

On Sun Sept 7 you told me privately that a full git pull of
linus tree would get me the whole clockevent patch series as well,
so I did that at most one day later and this git status quo was
buggy for me here, too (no s2r progress without external events).
Of course I blamed that problem on my own pretty experimental azf3328
clock_event_device work, but apparently not so ;)

So all this is is a "me too" for a state right after the recent clockevent
patch series, not sure when this started.
I did not _notice_ such trouble for any pretty recent kernel right before
this series, though (in particular the noop fixes alone did not exhibit that,
I think).

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