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: <4F9AAE43.5080809@teksavvy.com>
Date:	Fri, 27 Apr 2012 10:33:39 -0400
From:	Mark Lord <kernel@...savvy.com>
To:	John Stultz <john.stultz@...aro.org>
CC:	richard -rw- weinberger <richard.weinberger@...il.com>,
	Linux Kernel <linux-kernel@...r.kernel.org>,
	rtc-linux@...glegroups.com,
	Alessandro Zummo <a.zummo@...ertech.it>,
	Greg Kroah-Hartman <greg@...ah.com>, stable@...r.kernel.org,
	Rabin Vincent <rabin.vincent@...ricsson.com>
Subject: Re: [REGRESSION] rtc/interface.c: kills suspend-to-ram

On 12-04-18 02:29 PM, John Stultz wrote:
> On 04/17/2012 06:29 PM, Mark Lord wrote:
>> I'll give the suggestions above a go when I get the system back.
>> Right now it's out on loan for application testing.
>>
>> And there is a simple workaround for that system, which I'm now using:
>> just disable the RTC Alarm in the BIOS and the issue goes away.
>> And as you point out, hwclock does seem to be diddling with the Alarm
>> for some reason, so I'm feeling this isn't so important any more.
>>
>> But as we've gone this far, I will instrument things as requested
>> when I get the system back in a few days.
> Once again, thanks so much for reporting the issue and help with testing! I know going through
> remote diagnostics is a pain, especially when you have a workaround. :)  Anyway, your help here is
> very much appreciated.

Mmm.. at this point I may not get that system back here again.
The fellow who has it wants to hang onto it.

So.. nothing.  :)

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