Openmoko Bug #2318: rtcwake: /dev/rtc0 not enabled for wakeup events

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Openmoko Bug #2318: rtcwake: /dev/rtc0 not enabled for wakeup events

Openmoko Public Trac
#2318: rtcwake: /dev/rtc0 not enabled for wakeup events
-----------------------------+----------------------------------------------
 Reporter:  josch            |          Owner:  openmoko-kernel
     Type:  defect           |         Status:  new            
 Priority:  normal           |      Milestone:                
Component:  System Software  |        Version:  unspecified    
 Severity:  normal           |       Keywords:                
 Haspatch:  0                |      Blockedby:                
Estimated:                   |    Patchreview:                
 Blocking:                   |   Reproducible:                
-----------------------------+----------------------------------------------
 ~# rtcwake -s 20
 rtcwake: /dev/rtc0 not enabled for wakeup events

 expected behaviour: going to sleep, waking up after 20 seconds

 kernel:
 2.6.31 #293 PREEMPT Tue Nov 3 19:02:43 CET 2009 armv4tl GNU/Linux

 with debian unstable rootfs on sd

--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2318>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
Reply | Threaded
Open this post in threaded view
|

Re: Openmoko Bug #2318: rtcwake: /dev/rtc0 not enabled for wakeup events

Openmoko Public Trac
#2318: rtcwake: /dev/rtc0 not enabled for wakeup events
-----------------------------+----------------------------------------------
 Reporter:  josch            |          Owner:  openmoko-kernel
     Type:  defect           |         Status:  new            
 Priority:  normal           |      Milestone:                
Component:  System Software  |        Version:  unspecified    
 Severity:  normal           |       Keywords:                
 Haspatch:  0                |      Blockedby:                
Estimated:                   |    Patchreview:                
 Blocking:                   |   Reproducible:                
-----------------------------+----------------------------------------------

Comment(by lindi):

 sudo rtcwake -s 20 -m no
 sudo pm-suspend

 works for me on debian unstable with andy-tracking a3587e4ed77974ad. Can
 you try this?

--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2318#comment:1>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
Reply | Threaded
Open this post in threaded view
|

Re: Openmoko Bug #2318: rtcwake: /dev/rtc0 not enabled for wakeup events

Openmoko Public Trac
In reply to this post by Openmoko Public Trac
#2318: rtcwake: /dev/rtc0 not enabled for wakeup events
-----------------------------+----------------------------------------------
 Reporter:  josch            |          Owner:  openmoko-kernel
     Type:  defect           |         Status:  new            
 Priority:  normal           |      Milestone:                
Component:  System Software  |        Version:  unspecified    
 Severity:  normal           |       Keywords:                
 Haspatch:  0                |      Blockedby:                
Estimated:                   |    Patchreview:                
 Blocking:                   |   Reproducible:                
-----------------------------+----------------------------------------------

Comment(by josch):

 tried:
 uImage-2.6.28-andy-
 tracking+gitr119819+5a6ed99264c704e517ac312283c58204ee38fee5-r5-om-
 gta01.bin

 rtcwake -s 20 -m no
 pm-suspend

 works but

 rtcwake -s 20

 yields the same error as above

 =======================================
 on 2.6.31

 rtcwake -s 20 -m no
 pm-suspend

 doesnt give the original /dev/rtc0 error but doesnt wake up afterwards -
 but the same happens when just issuing

 pm-suspend

 without rtc so that is another bug report to be filed for the new kernel.

 i just would have had suspected rtcwake to be able to suspend itself
 without pm-suspend but as it seems to work on 2.6.28 with pm-suspend
 issued manually it is probably no kernel bug

--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2318#comment:2>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac