From: David Brownell <david-b@pacbell.net>
To: Pavel Machek <pavel@ucw.cz>
Cc: Linux-pm mailing list <linux-pm@lists.osdl.org>,
linux-kernel@vger.kernel.org
Subject: Re: waking system up using RTC (was Re: rtcwakeup.c)
Date: Sat, 26 Aug 2006 17:04:04 -0700 [thread overview]
Message-ID: <200608261704.05017.david-b@pacbell.net> (raw)
In-Reply-To: <20060826214342.GB3784@elf.ucw.cz>
On Saturday 26 August 2006 2:43 pm, Pavel Machek wrote:
> Hi!
>
> > > Your new RTC driver seems to work for me (thinkpad x60), but no, I
> > > can't get wakeup using RTC to work:
> >
> > Does it work using /proc/acpi/alarm? In my experience, ACPI wakeup
> > doesn't work on Linux ... hence my pleasant surprise to see it work
>
> No, I could not get it working using /proc/acpi/alarm.
Then I suspect that's the root cause of your problem ... ACPI code,
in either Linux or your BIOS, is not sufficiently cooperative. All
that the rtc-acpi driver does is move the wakeup code, it doesn't
actually change what the /proc/acpi/alarm stuff does.
> No, machine actually suspends okay, it just does not wake up :-(.
The usual ACPI wakeup symptoms I've seen are the hardware giving the
signal, system starting to wake up, then botching somewhere early in
the resum. So I suspect you're not actually getting the hardware
wakeup signal ... as if maybe it wasn't set up correctly.
You may be able to tell your BIOS to do the alarm by itself, and
then test to see whether Linux handles the wakeup side OK.
> rtc-acpi 00:07: AT compatible RTC (S4wake) (y3k), 1 month alarm
Seems like Intel's chips won't do one year alarms ... so sad. :)
- Dave
next prev parent reply other threads:[~2006-08-27 0:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060725124941.GD5034@ucw.cz>
2006-08-26 14:59 ` waking system up using RTC (was Re: rtcwakeup.c) Pavel Machek
2006-08-26 21:15 ` David Brownell
2006-08-26 21:43 ` Pavel Machek
2006-08-27 0:04 ` David Brownell [this message]
2006-08-27 10:17 ` Pavel Machek
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=200608261704.05017.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.osdl.org \
--cc=pavel@ucw.cz \
/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