linux-mips
[Top] [All Lists]

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

To: Matt Turner <mattst88@gmail.com>
Subject: Re: select() to /dev/rtc0 to wait for clock tick timed out
From: john stultz <johnstul@us.ibm.com>
Date: Fri, 19 Aug 2011 13:34:30 -0700
Cc: linux-mips@linux-mips.org
In-reply-to: <CAEdQ38H5NC6B+T=gsF4-8Ue2DA=rfrFCi_i+RKC-=DFijjK2=g@mail.gmail.com>
References: <CAEdQ38HGfd9YWE+WLuirE4Km6UE6N26toTj=-1BuXAQUux6t5g@mail.gmail.com> <1313777242.2970.131.camel@work-vm> <CAEdQ38F4zi76ug+ABZPnPLcLvGfUFRhr6SKzYCN+24Otq+qAAQ@mail.gmail.com> <1313783990.2970.136.camel@work-vm> <CAEdQ38H5NC6B+T=gsF4-8Ue2DA=rfrFCi_i+RKC-=DFijjK2=g@mail.gmail.com>
Sender: linux-mips-bounce@linux-mips.org
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




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