On Fri, Aug 19, 2011 at 3:59 PM, john stultz <johnstul@xxxxxxxxxx> wrote: > On Fri, 2011-08-19 at 15:41 -0400, Matt Turner wrote: >> On Fri, Aug 19, 2011 at 2:07 PM, john stultz <johnstul@xxxxxxxxxx> wrote: >> > On Fri, 2011-08-19 at 00:16 -0400, Matt Turner wrote: >> > thanks >> > -john >> >> Counting 5 update (1/sec) interrupts from reading /dev/rtc0: >> >> ... and then it doesn't count. >> >> Would it help if I tried to bisect this? (Is there an easy way to >> bisect 2.6.37..master with my patches applied to each iteration?) > > I suspect bisecting won't help too much, as I've reworked a good chunk > of the generic rtc code in 2.6.38, so its not likely to be one small > change. > > How about this modified (cutting out the UIE testing) version of the > Documentation/rtc.txt test below? > > I'm basically trying to find out if the alarm functionality is actually > working or not, since with 2.6.38+ we use the one-shot style alarm mode > to trigger UIE interrupts. > > thanks > -john 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... 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. Thanks, MAtt
