From: John Stultz <john.stultz@linaro.org>
To: Mark Lord <kernel@teksavvy.com>
Cc: richard -rw- weinberger <richard.weinberger@gmail.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
rtc-linux@googlegroups.com,
Alessandro Zummo <a.zummo@towertech.it>,
Greg Kroah-Hartman <greg@kroah.com>,
stable@vger.kernel.org,
Rabin Vincent <rabin.vincent@stericsson.com>
Subject: Re: [REGRESSION] rtc/interface.c: kills suspend-to-ram
Date: Fri, 27 Apr 2012 12:22:12 -0700 [thread overview]
Message-ID: <4F9AF1E4.4000600@linaro.org> (raw)
In-Reply-To: <4F9AAE43.5080809@teksavvy.com>
On 04/27/2012 07:33 AM, Mark Lord wrote:
> 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. :)
Ok. Well, do let me know if you end up seeing anything similar. Thanks
again for your testing and bug reports.
thanks
-john
next prev parent reply other threads:[~2012-04-27 19:22 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-16 4:36 [REGRESSION] rtc/interface.c: kills suspend-to-ram Mark Lord
2012-04-16 13:55 ` Mark Lord
2012-04-16 14:23 ` richard -rw- weinberger
2012-04-16 14:23 ` richard -rw- weinberger
2012-04-16 15:42 ` Mark Lord
2012-04-16 15:49 ` richard -rw- weinberger
2012-04-16 15:49 ` richard -rw- weinberger
2012-04-16 15:57 ` Mark Lord
2012-04-16 19:45 ` John Stultz
2012-04-16 21:43 ` John Stultz
2012-04-17 2:30 ` Mark Lord
2012-04-17 5:13 ` John Stultz
2012-04-17 12:51 ` Mark Lord
2012-04-17 20:11 ` Mark Lord
2012-04-17 20:12 ` Mark Lord
2012-04-17 23:02 ` John Stultz
2012-04-18 1:29 ` Mark Lord
2012-04-18 18:29 ` John Stultz
2012-04-27 14:33 ` Mark Lord
2012-04-27 19:22 ` John Stultz [this message]
2012-04-16 19:44 ` John Stultz
2012-04-17 2:27 ` Mark Lord
2012-04-16 14:26 ` [rtc-linux] " Mark Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F9AF1E4.4000600@linaro.org \
--to=john.stultz@linaro.org \
--cc=a.zummo@towertech.it \
--cc=greg@kroah.com \
--cc=kernel@teksavvy.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rabin.vincent@stericsson.com \
--cc=richard.weinberger@gmail.com \
--cc=rtc-linux@googlegroups.com \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.