public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Karol Kozimor <sziwan-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org>
To: Pavel Machek <pavel-+ZI9xUNit7I@public.gmane.org>
Cc: shaohua.li-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org,
	ronald.mythtv-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
	acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: /proc/acpi/alarm -- does it work or not?
Date: Wed, 28 Dec 2005 19:24:32 +0100	[thread overview]
Message-ID: <20051228182431.GA26207@hell.org.pl> (raw)
In-Reply-To: <20051226204305.GA2028-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>

Thus wrote Pavel Machek:
[...]

Last time I checked (2.6.15-rc[45]) it worked fine -- I use it routinely
for S3 stress-testing (speaking of which, my machine has just failed to
resume after some 20 days of uptime and > 150 S3 cycles).

> Here are my attempts: [Commands were typed one-after-another where it
> makes sense, and I left machine suspended for long enough -- timer
> should have expired]
> 
> root@amd:/proc/acpi# cat alarm
> 2005-12-00 01:03:24
> root@amd:/proc/acpi# echo '0-0-0 22:35:00' > alarm

You got it mixed up. It's either
"2005-12-28 19:50:00" for absolute or
"+0000-00-00 00:01:00" for relative.

RTC IRQ counter is incremented whenever the timer triggers, regardless of
whether the system is up or down (my system, at least).

HTH, best regards,

-- 
Karol 'sziwan' Kozimor
sziwan-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click

      parent reply	other threads:[~2005-12-28 18:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-26 20:43 /proc/acpi/alarm -- does it work or not? Pavel Machek
     [not found] ` <20051226204305.GA2028-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
2005-12-28 18:24   ` Karol Kozimor [this message]

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=20051228182431.GA26207@hell.org.pl \
    --to=sziwan-detuoxkzssqrdjvtcaxf/a@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=pavel-+ZI9xUNit7I@public.gmane.org \
    --cc=ronald.mythtv-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=shaohua.li-ral2JQCrhuEAvxtiuMwx3w@public.gmane.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox