linux-kernel - Re: [5/6] 2.6.21-rc2: known regressions

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]

Message-Id: <1173168565.24738.273.camel@localhost.localdomain>
Date:	Tue, 06 Mar 2007 09:09:25 +0100
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Adrian Bunk <bunk@...sta.de>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Michal Piotrowski <michal.k.k.piotrowski@...il.com>,
	Emil Karlson <jkarlson@...hut.fi>,
	"Michael S. Tsirkin" <mst@...lanox.co.il>,
	Soeren Sonnenburg <kernel@....de>, Len Brown <lenb@...nel.org>
Subject: Re: [5/6] 2.6.21-rc2: known regressions

On Tue, 2007-03-06 at 08:25 +0100, Ingo Molnar wrote:
> The programming of periodic tick devices needs to be saved/restored 
> across suspend/resume - otherwise we might end up with a system coming 
> up that relies on getting a PIT (or HPET) interrupt, while those devices 
> default to 'no interrupts' after powerup. (To confuse things it worked 
> to a certain degree on some systems because the lapic gets initialized 
> as a side-effect of SMP bootup.)
> 
> This suspend / resume thing was dropped unintentionally during the 
> last-minute -mm code reshuffling.
> 
> Signed-off-by: Ingo Molnar <mingo@...e.hu>

Signed-off-by: Thomas Gleixner <tglx@...utronix.de>


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