On Sat,  8 Sep 2007 09:29:18 -0700 (PDT) [EMAIL PROTECTED] 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: [EMAIL PROTECTED]
>         ReportedBy: [EMAIL PROTECTED]
> 
> 
> 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.
-
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to