[Top] [All Lists]

Re: select() to /dev/rtc0 to wait for clock tick timed out

To: john stultz <>
Subject: Re: select() to /dev/rtc0 to wait for clock tick timed out
From: Matt Turner <>
Date: Fri, 19 Aug 2011 16:06:32 -0400
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=OSn6QV41RgeYDeLg1ptEoWCrge3sU4FgbBHifHF8pN4=; b=EnfAAF/3CciDEW6QtGKU0maazzSVQ6dU+2Sqr5caLFb1MeTdWEVtLysxG5YxkAzi/j SoRB2HNw9Hn2EpBy9fumgZViaz8Oq5leePjEk+3o4mFne0olfBVSKzV2XQyHILNGDfM3 s3LrY68GDQ0WjZ87XOubPeJ8UT/QnAfhtoo0o=
In-reply-to: <1313783990.2970.136.camel@work-vm>
References: <> <1313777242.2970.131.camel@work-vm> <> <1313783990.2970.136.camel@work-vm>
On Fri, Aug 19, 2011 at 3:59 PM, john stultz <> wrote:
> On Fri, 2011-08-19 at 15:41 -0400, Matt Turner wrote:
>> On Fri, Aug 19, 2011 at 2:07 PM, john stultz <> 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.


<Prev in Thread] Current Thread [Next in Thread>