On Fri, Aug 19, 2011 at 4:34 PM, john stultz <johnstul@xxxxxxxxxx> wrote: > On Fri, 2011-08-19 at 16:06 -0400, Matt Turner wrote: >> Nope, just hangs. >> >> Current RTC date/time is 19-8-2011, 00:20:51. >> Alarm time now set to 00:20:56. >> Waiting 5 seconds for alarm... > > Ok. That confirms the alarm irq isn't working. > >> Would it at least help if I booted 2.6.37 to confirm that this test >> program works there? I'd hate to waste a bunch of your time only to >> find out that it's a problem with my patches. > > Yea, that's probably a good idea. > > From there we can instrument the code to see why the alarm irq isn't > working. > > Thanks again for the testing! > -john With 2.6.37 the original rtctest program gives RTC Driver Test Example. RTC_UIE_ON ioctl: Invalid argument and the modified version hangs in the same way. :( With 2.6.37, hwclock did work: bcm91250a-be ~ # date Fri Aug 19 16:52:21 EDT 2011 bcm91250a-be ~ # hwclock --systohc bcm91250a-be ~ # date 082016522011 Sat Aug 20 16:52:00 EDT 2011 bcm91250a-be ~ # hwclock --hctosys bcm91250a-be ~ # date Fri Aug 19 16:53:02 EDT 2011 With 3.1.0-rc2+, it does not bcm91250a-be ~ # date Fri Aug 19 16:54:32 EDT 2011 bcm91250a-be ~ # hwclock --systohc select() to /dev/rtc0 to wait for clock tick timed out bcm91250a-be ~ # date 082016542011 Sat Aug 20 16:54:00 EDT 2011 bcm91250a-be ~ # hwclock --hctosys select() to /dev/rtc0 to wait for clock tick timed out bcm91250a-be ~ # date Sat Aug 20 16:54:11 EDT 2011 So, even if the alarm never worked, there is some sort of regression here. Thanks, Matt
