* Ingo Molnar <mingo@elte.hu> wrote:

quoted text
> > OK, here's a version that's cleaner and suspends.  Resuming ... 
> > another story, it's currently broken on this ARM board (no 
> > relationship to this testing code).
> 
> yay! Threw this into my setup. It built fine with the new option 
> disabled and enabled as well. Unfortunately it said this:
> 
> [   23.509562] Calling initcall 0xc0c49e00: be_sleepy+0x0/0x170()
> [   23.515837] PM: no wakelarm-capable RTC
> [   23.517562] initcall 0xc0c49e00: be_sleepy+0x0/0x170() returned 0.
> 
> (oh, btw., a small typo: s/wakelarm/wakealarm/)
> 
> is "wakealarm" something generally available on PC RTCs? I'll try to 
> look into the BIOS setup, maybe it's just disabled ...

ok, there was indeed a "RTC Alarm: disabled" option in the BIOS. But no 
matter how many of those resume-alarm options i enabled, the kernel 
thinks there's no time capability:

 [   23.541565] Calling initcall 0xc0c49e00: be_sleepy+0x0/0x170()
 [   23.547840] PM: no wakelarm-capable RTC
 [   23.549566] initcall 0xc0c49e00: be_sleepy+0x0/0x170() returned 0.

i could set date/time of wakeup alarm in the BIOS, so i suspect the chip 
itself is capable of it. Bootlog and kernel config attached. (maybe i 
misconfigured something?)

	Ingo