From: Andrew Morton <akpm@linux-foundation.org>
To: David Brownell <david-b@pacbell.net>,
Alessandro Zummo <a.zummo@towertech.it>,
linux-acpi@vger.kernel.org,
"linux-pm@lists.linux-foundation.org" <linux-pm@lists.linux-fo>
Cc: huffcslists@gmail.com, bugme-daemon@bugzilla.kernel.org
Subject: Re: [Bugme-new] [Bug 8995] New: /proc/acpi/alarm worked; update to 2.6.22.2 and /sys/class/rtc/rtc0/wakealarm don't
Date: Sat, 8 Sep 2007 17:29:11 -0700 [thread overview]
Message-ID: <20070908172911.7f9fc44f.akpm@linux-foundation.org> (raw)
In-Reply-To: <bug-8995-10286@http.bugzilla.kernel.org/>
On Sat, 8 Sep 2007 09:29:18 -0700 (PDT) bugme-daemon@bugzilla.kernel.org wrote:
> http://bugzilla.kernel.org/show_bug.cgi?id=8995
>
> Summary: /proc/acpi/alarm worked; update to 2.6.22.2 and
> /sys/class/rtc/rtc0/wakealarm don't
> Product: ACPI
> Version: 2.5
> KernelVersion: 2.6.22.2
> Platform: All
> OS/Version: Linux
> Tree: Mainline
> Status: NEW
> Severity: normal
> Priority: P1
> Component: Power-Sleep-Wake
> AssignedTo: acpi_power-sleep-wake@kernel-bugs.osdl.org
> ReportedBy: huffcslists@gmail.com
>
>
> Most recent kernel where this bug did not occur:2.6.20
> Distribution: FC6
> Hardware Environment: ASUS A8N-SLI mobo, Athlon 64 3200+, PATA Disk
> Software Environment: FC6, MythTV 0.20.2-164
> Problem Description:
> Change in kernel code from support for /proc/acpi/alarm to
> /sys/class/rtc/rtc0/wakealarm and supporting code borked working system. Will
> no longer wake at set time.
> Time set <> time reported by cat /sys.../wakealarm. Return value off by large
> constant. Note: Mobo doesn't support month, day, or year in alarm setting.
>
> Steps to reproduce:
> Before upgrade from 2.6.20 to 2.6.22.2, suspend-to-disk with powerdown to
> standby would wake at time echoed into /proc/acpi/alarm. Change of wakeup time
> setting code to echo 0 to /sys/class/rtc/rtc0/wakealarm followed by echo of
> seconds since epoch of desired wakeup time under 2.6.22.2 does not work.
> System will not wake up at specified time. Will wake by keyboard keystroke,
> such as Ctrl+Esc. Tried enabling APM (BIOS) alarm setting and all entries
> under /proc/acpi/wakeup (all on at once), but no improvement.
> Test sequence:
> # echo 0 > /sys/class/rtc/rtc0/wakealarm
> # t=`date +%s`; w=`expr $t + 60`; echo $w > /sys/class/rtc/rtc0/wakealarm
> # echo $w
> 1189268800
> # cat /sys/class/rtc/rtc0/wakealarm
> 2076101696
> # expr 2076101696 - 1189268800
> 886832896
> <invoke your favorite code to suspend to disk and power down system leaving
> standby power on>
> <wait>
> <wait some more>
> <hit power on button>
>
Guys, can we please work out where the problem lies here? Is it in the
new RTC code, ACPI or what?
Thanks.
next parent reply other threads:[~2007-09-09 0:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-8995-10286@http.bugzilla.kernel.org/>
2007-09-09 0:29 ` Andrew Morton [this message]
2007-09-09 11:32 ` [Bugme-new] [Bug 8995] New: /proc/acpi/alarm worked; update to 2.6.22.2 and /sys/class/rtc/rtc0/wakealarm don't Rafael J. Wysocki
2007-11-04 19:25 ` David Brownell
2007-11-04 19:56 ` Rafael J. Wysocki
[not found] ` <200711042056.56763.rjw@sisk.pl>
2007-11-05 16:11 ` David Brownell
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=20070908172911.7f9fc44f.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=a.zummo@towertech.it \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=david-b@pacbell.net \
--cc=huffcslists@gmail.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-pm@lists.linux-fo \
/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