[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <AANLkTinJfQCEcqHy8oc8+F+yrmY_AkhPLCdZ7R95tk6H@mail.gmail.com>
Date: Thu, 20 Jan 2011 22:24:56 +0100
From: Geert Uytterhoeven <geert@...ux-m68k.org>
To: John Stultz <john.stultz@...aro.org>
Cc: David Daney <ddaney@...iumnetworks.com>,
Andreas Schwab <schwab@...ux-m68k.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Alessandro Zummo <a.zummo@...ertech.it>,
Thomas Gleixner <tglx@...utronix.de>
Subject: Re: RTC seems broken on 2.6.38-rc1 for RTCs lacking alarms.
On Thu, Jan 20, 2011 at 22:16, John Stultz <john.stultz@...aro.org> wrote:
> On Thu, 2011-01-20 at 12:51 -0800, David Daney wrote:
>> open("/dev/rtc0", O_RDONLY|O_LARGEFILE) = 3
>> ioctl(3, PRESTO_GETMOUNT or RTC_UIE_ON, 0) = 0
>> _newselect(4, [3], NULL, NULL, {5, 0}) = 0 (Timeout)
>> write(2, "select() to /dev/rtc0 to wait for"..., 55select() to /dev/rtc0
>> to wait for clock tick timed out
>> ) = 55
>> ioctl(3, PRESTO_SETPID or RTC_UIE_OFF, 0) = 0
>> close(3) = 0
>> exit_group(1) = ?
>>
>>
>> The hwclock program is asking to put the clock in UIE mode and then
>> does a select() on it. Since the alarm doesn't work, the select times out.
>>
>> Previously the ioctl(RTC_UIE_ON) would return EINVAL:
>
> Ah. Good diagnosis! Let me try to get a patch for you and Andreas to
> test.
I'm also seeing this on m68k (ARAnyM, rtc-generic).
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@...ux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists