System wakeup by time not working anymore on 2.6.32
Hello,
I have a PC which I use as a harddisk videorecorder.
If unused it is powered down, so I put the time it is supposed to wake up for the next recording into /sys/class/rtc/rtc0/wakealarm. This has been working fine for some time.
After the upgrade to kernel 2.6.32 this stopped working, it doesn't wake up, though "cat /proc/driver/rtc" shows the correct data, like this:
rtc_time : 18:02:20rtc_date : 2009-12-03alrm_time : 18:05:38alrm_date : 2009-12-03alarm_IRQ : yesalrm_pending : no
24hr : yesperiodic_IRQ : noupdate_IRQ : noHPET_emulated : yesDST_enable : noperiodic_freq : 1024batt_status : okay
Any ideas?
Regards
Malte Schröder
Len Brown
reviewerQuoted 23 lines · Malte Schröder
Hello,
I have a PC which I use as a harddisk videorecorder.
If unused it is powered down, so I put the time it is supposed to wake up for the next recording into/sys/class/rtc/rtc0/wakealarm. This has been working fine for some time.
After the upgrade to kernel 2.6.32 this stopped working, it doesn't wake up, though "cat/proc/driver/rtc" shows the correct data, like this:
rtc_time: 18:02:20rtc_date: 2009-12-03alrm_time: 18:05:38alrm_date: 2009-12-03alarm_IRQ: yesalrm_pending: no
24hr : yesperiodic_IRQ: noupdate_IRQ: noHPET_emulated: yesDST_enable: noperiodic_freq: 1024batt_status: okay
Quoted 1 line
Any ideas?
offhand, no.
Is it possible to bisect?
thanks,
Len Brown, Intel Open Source Technology Center
Re: [REGRESSION] System wakeup by time not working anymore on 2.6.32 (bisected)
Quoted 2 lines · On Wed, 16 Dec 2009 23:12:10 -0500 (EST) Len Brown <[email protected]> wrote:
offhand, no.
Is it possible to bisect?
I managed to bisect it :)
abd6633c67925f90775bb74755f9c547e30f1f20 is the first bad commit commit abd6633c67925f90775bb74755f9c547e30f1f20
Author: David Härdeman <[email protected]> Date: Mon Sep 21 17:04:52 2009 -0700
pnp: add a shutdown method to pnp drivers
The shutdown method is used by the winbond cir driver to setup the hardware for wake-from-S5.
:040000 040000 139dee164ad8e41d197db5c2bce9f22c9f14eee0 220a88576f5019f87b1f73848536fef21882d518 M drivers
:040000 040000 1eee7adea06c20f301cfe1113a5b07e24e781ecb cb34aceb245225ce42834b3403f6b21dece23ae0 M include
Reverting abd6633c67925f90775bb74755f9c547e30f1f20 solves the problem for me.
Quoted 2 lines
thanks,
Len Brown, Intel Open Source Technology Center
Regards
Malte