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: <20141222144814.GA11844@srcf.ucam.org>
Date:	Mon, 22 Dec 2014 14:48:14 +0000
From:	Matthew Garrett <mjg59@...f.ucam.org>
To:	Gabriele Mazzotta <gabriele.mzt@...il.com>
Cc:	platform-driver-x86@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: System automatically wakes up because of Intel Rapid Start
 Technology

Ok, I suspect I know what's going on here - the firmware is probably 
not cancelling the wakeup timer on resume, and on the second suspend 
makes the assumption that the OS has set the wakeup timer and so decides 
that the user wants the machine to wake up. We could add workaround code 
to the irst driver to handle that case, but that would involve it being 
rather more friendly with the system clock than we want. I think the 
right fix is probably to have the rtc driver reset the alarm on resume.

-- 
Matthew Garrett | mjg59@...f.ucam.org
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ