Fwd: Does clock_gettime support CLOCK_REALTIME_ALARM and CLOCK_BOOTTIME_ALARM?

[Dan Horák]

forwarding a message from our Ruby maintainer asking for help

looks like a kernel problem, please see also
https://bugs.ruby-lang.org/issues/9008#note-3

Dan

-------- Původní zpráva --------
Předmět: 	Does clock_gettime support CLOCK_REALTIME_ALARM and 
CLOCK_BOOTTIME_ALARM?
Datum: 	Thu, 10 Oct 2013 13:48:01 +0200
Od: 	Vít Ondruch 
Komu: 	[e-mail]

Hi,

I am trying to build Ruby 2.1 for F21 and I observe following test
errors:

3) Error:
TestProcess#test_clock_getres_constants:
Errno::E524: Unknown error 524 - clock_getres
     /builddir/build/BUILD/ruby-2.1.0-preview1/test/ruby/test_process.rb:1752:in
`clock_getres' /builddir/build/BUILD/ruby-2.1.0-preview1/test/ruby/test_process.rb:1752:in
`block in
test_clock_getres_constants' /builddir/build/BUILD/ruby-2.1.0-preview1/test/ruby/test_process.rb:1749:in
`each' /builddir/build/BUILD/ruby-2.1.0-preview1/test/ruby/test_process.rb:1749:in
`test_clock_getres_constants'
   4) Error:
TestProcess#test_clock_gettime_constants:
Errno::E524: Unknown error 524 - clock_gettime
     /builddir/build/BUILD/ruby-2.1.0-preview1/test/ruby/test_process.rb:1676:in
`clock_gettime' /builddir/build/BUILD/ruby-2.1.0-preview1/test/ruby/test_process.rb:1676:in
`block in
test_clock_gettime_constants' /builddir/build/BUILD/ruby-2.1.0-preview1/test/ruby/test_process.rb:1673:in
`each' /builddir/build/BUILD/ruby-2.1.0-preview1/test/ruby/test_process.rb:1673:in
`test_clock_gettime_constants'

It looks like CLOCK_REALTIME_ALARM and CLOCK_BOOTTIME_ALARM are not
supported, but the error code is completely strange to me. According to
the documentation, it should return EINVAL.

http://pubs.opengroup.org/onlinepubs/9699919799/functions/clock_getres.html
  |
  | [EINVAL]
  | The clock_id argument does not specify a known clock.

Any help is appreciated.

Thanks

Vít

P.S. This is my upstream report: http://bugs.ruby-lang.org/issues/9008
P.S.2 I am not subscribed to this list, please keep me in the CC.

[Peter Robinson]

Hi Dan,

I suspect this is one for Jon/Kyle or others but looking through
kernel bits and patches it seems that these features are completely
agnostic to HW and in fact the patches [1] seem to have come from the
ARM community from Android Alarm Timers [2]. One thing I would check
is if on the particular platform being tested against has a RTC
registered. We build a few RTCs into the kernel and dozens of other
less common ones as modules.

Peter

[1] https://lkml.org/lkml/2011/4/19/553
[2] https://lwn.net/Articles/429925/

On Tue, Oct 15, 2013 at 7:26 AM, Dan Horák  wrote:
> forwarding a message from our Ruby maintainer asking for help
>
> looks like a kernel problem, please see also
> https://bugs.ruby-lang.org/issues/9008#note-3
>             Dan
>
> -------- Původní zpráva --------
> Předmět:        Does clock_gettime support CLOCK_REALTIME_ALARM and
> CLOCK_BOOTTIME_ALARM?
> Datum:  Thu, 10 Oct 2013 13:48:01 +0200
> Od:     Vít Ondruch 
> Komu:   [e-mail]
>
> Hi,
>
> I am trying to build Ruby 2.1 for F21 and I observe following test
> errors:
> Error:
>
> TestProcess#test_clock_getres_constants:
> Errno::E524: Unknown error 524 - clock_getres
>      /builddir/build/BUILD/ruby-2.1.0-preview1/test/ruby/test_process.rb:1752:in
> `clock_getres' /builddir/build/BUILD/ruby-2.1.0-preview1/test/ruby/test_process.rb:1752:in
> `block in
> test_clock_getres_constants' /builddir/build/BUILD/ruby-2.1.0-preview1/test/ruby/test_process.rb:1749:in
> `each' /builddir/build/BUILD/ruby-2.1.0-preview1/test/ruby/test_process.rb:1749:in
> `test_clock_getres_constants'
>    4) Error:
> TestProcess#test_clock_gettime_constants:
> Errno::E524: Unknown error 524 - clock_gettime
>      /builddir/build/BUILD/ruby-2.1.0-preview1/test/ruby/test_process.rb:1676:in
> `clock_gettime' /builddir/build/BUILD/ruby-2.1.0-preview1/test/ruby/test_process.rb:1676:in
> `block in
> test_clock_gettime_constants' /builddir/build/BUILD/ruby-2.1.0-preview1/test/ruby/test_process.rb:1673:in
> `each' /builddir/build/BUILD/ruby-2.1.0-preview1/test/ruby/test_process.rb:1673:in
> `test_clock_gettime_constants'
>
> It looks like CLOCK_REALTIME_ALARM and CLOCK_BOOTTIME_ALARM are not
> supported, but the error code is completely strange to me. According to
> the documentation, it should return EINVAL.
>
> http://pubs.opengroup.org/onlinepubs/9699919799/functions/clock_getres.html
>   |
>   | [EINVAL]
>   | The clock_id argument does not specify a known clock.
>
> Any help is appreciated.
>
> Thanks
>
> Vít
>
> P.S. This is my upstream report: http://bugs.ruby-lang.org/issues/9008
> P.S.2 I am not subscribed to this list, please keep me in the CC.
>
> arm mailing list
> [e-mail]
> https://admin.fedoraproject.org/mailman/listinfo/arm

[Dan Horák]

On Tue, 15 Oct 2013 12:38:17 +0100
Peter Robinson  wrote:
> Hi Dan,
>
> I suspect this is one for Jon/Kyle or others but looking through
> kernel bits and patches it seems that these features are completely
> agnostic to HW and in fact the patches [1] seem to have come from the
> ARM community from Android Alarm Timers [2]. One thing I would check
> is if on the particular platform being tested against has a RTC
> registered. We build a few RTCs into the kernel and dozens of other
> less common ones as modules.

I think https://lkml.org/lkml/2013/10/18/518 will be for Kyle, likely
we will need a backport to Fedora kernels

Dan
> Peter
>
> [1] https://lkml.org/lkml/2011/4/19/553
> [2] https://lwn.net/Articles/429925/
>
> On Tue, Oct 15, 2013 at 7:26 AM, Dan Horák  wrote:
> > forwarding a message from our Ruby maintainer asking for help
> >
> > looks like a kernel problem, please see also
> > https://bugs.ruby-lang.org/issues/9008#note-3
> >             Dan
> >
> > -------- Původní zpráva --------
> > Předmět:        Does clock_gettime support CLOCK_REALTIME_ALARM and
> > CLOCK_BOOTTIME_ALARM?
> > Datum:  Thu, 10 Oct 2013 13:48:01 +0200
> > Od:     Vít Ondruch 
> > Komu:   [e-mail]
> >
> > Hi,
> >
> > I am trying to build Ruby 2.1 for F21 and I observe following test
> > errors:
> > Error:
> >
> > TestProcess#test_clock_getres_constants:
> > Errno::E524: Unknown error 524 - clock_getres
> >      /builddir/build/BUILD/ruby-2.1.0-preview1/test/ruby/test_process.rb:1752:in
> > `clock_getres' /builddir/build/BUILD/ruby-2.1.0-preview1/test/ruby/test_process.rb:1752:in
> > `block in
> > test_clock_getres_constants' /builddir/build/BUILD/ruby-2.1.0-preview1/test/ruby/test_process.rb:1749:in
> > `each' /builddir/build/BUILD/ruby-2.1.0-preview1/test/ruby/test_process.rb:1749:in
> > `test_clock_getres_constants'
> >    4) Error:
> > TestProcess#test_clock_gettime_constants:
> > Errno::E524: Unknown error 524 - clock_gettime
> >      /builddir/build/BUILD/ruby-2.1.0-preview1/test/ruby/test_process.rb:1676:in
> > `clock_gettime' /builddir/build/BUILD/ruby-2.1.0-preview1/test/ruby/test_process.rb:1676:in
> > `block in
> > test_clock_gettime_constants' /builddir/build/BUILD/ruby-2.1.0-preview1/test/ruby/test_process.rb:1673:in
> > `each' /builddir/build/BUILD/ruby-2.1.0-preview1/test/ruby/test_process.rb:1673:in
> > `test_clock_gettime_constants'
> >
> > It looks like CLOCK_REALTIME_ALARM and CLOCK_BOOTTIME_ALARM are not
> > supported, but the error code is completely strange to me.
> > According to the documentation, it should return EINVAL.
> >
> > http://pubs.opengroup.org/onlinepubs/9699919799/functions/clock_getres.html
> >   |
> >   | [EINVAL]
> >   | The clock_id argument does not specify a known clock.
> >
> > Any help is appreciated.
> >
> > Thanks
> >
> > Vít
> >
> > P.S. This is my upstream report:
> > http://bugs.ruby-lang.org/issues/9008 P.S.2 I am not subscribed to
> > this list, please keep me in the CC.
> >
> > arm mailing list
> > [e-mail]
> > https://admin.fedoraproject.org/mailman/listinfo/arm