linux-kernel - Re: can't resume from ACPI S3 with TICK

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

Message-ID: <1294767150.4981.3.camel@Tachyon>
Date:	Tue, 11 Jan 2011 10:32:30 -0700
From:	"James C. Georgas" <james.georgas@...oo.ca>
To:	Borislav Petkov <bp@...64.org>
Cc:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"Herrmann3, Andreas" <Andreas.Herrmann3@....com>
Subject: Re: can't resume from ACPI S3 with TICK_ONESHOT

On Tue, 2011-01-11 at 15:13 +0100, Borislav Petkov wrote:
> Ok, I don't see anything irregular here. Can you try booting the
> original tickless (NO_HZ) configuration without the "nohpet" boot option
> and wait >= 5 mins after resume to see whether your machine comes to
> life afterall. The 5min means we want to wait until the 32-bit HPET
> counter overflows to see whether the timer gets programmed with an event
> in the past right after resume.
> 
> Thanks.
> 

Yeah, it woke up eventually. I went away for about half an hour, and
when I came back, the system was on again. Do you want a more accurate
measurement of the time it took?

James

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