linux-mips
[Top] [All Lists]

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

To: john stultz <johnstul@us.ibm.com>
Subject: Re: select() to /dev/rtc0 to wait for clock tick timed out
From: Matt Turner <mattst88@gmail.com>
Date: Fri, 19 Aug 2011 16:56:13 -0400
Cc: linux-mips@linux-mips.org
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=PR/0EucgNe6xS3ONP7fI5kjy6FcrtJTB3LGIW1qPR0w=; b=OljYtI6K8G7uiHHfv/YdfnD+Rh7zGylF2hGdE1hJxhoqOzSqbLtPkA8g++I0Nlk/DI 4s8/MKkn12j1gj5uMGdDR/h6WjUkTvBdVJVH0s+o/U8eLjYk3stPeYvRMXJKBflMWU3+ q2k5m5+FSfn30lz0PmmAYMxjYviSkd5D0vx8s=
In-reply-to: <1313786070.2970.144.camel@work-vm>
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> <1313786070.2970.144.camel@work-vm>
Sender: linux-mips-bounce@linux-mips.org
On Fri, Aug 19, 2011 at 4:34 PM, john stultz <johnstul@us.ibm.com> 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

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