From: "Randy.Dunlap" <rddunlap@osdl.org>
To: "Aurélien GÉRÔME" <ag@roxor.cx>
Cc: linux-kernel@vger.kernel.org
Subject: Re: RTC Inappropriate ioctl for device
Date: Tue, 15 Feb 2005 08:48:31 -0800 [thread overview]
Message-ID: <421227DF.8060209@osdl.org> (raw)
In-Reply-To: <20050215111636.GO12421@roxor.cx>
Aurélien GÉRÔME wrote:
> On Mon, Feb 14, 2005 at 07:45:11PM -0800, Randy.Dunlap wrote:
>
>>Aurélien GÉRÔME wrote:
>>
>>>Hi,
>>>
>>>Having CONFIG_RTC=y, I tried on x86 the rtctest program found in
>>>linux-2.6.10/Documentation/rtc.txt. However, it failed at:
>>>
>>>ioctl(fd, RTC_UIE_ON, 0);
>>>
>>>with:
>>>
>>>ioctl: Inappropriate ioctl for device
>>>
>>>Did I miss something? Maybe something else conflicts with CONFIG_RTC?
>>>
>>>Cheers.
>>
>>Do you have an HPET timer enabled? That could cause a conflict.
>
>
> I have HPET timer enabled.
Please add/enable the second line here:
CONFIG_HPET_TIMER=y
# CONFIG_HPET_EMULATE_RTC is not set
and try it again.
>>Does /proc/interrupts report rtc interrupts increasing when you
>>run rtctest?
>>I.e., does the number of this line increase like this?
>>
>> 8: 131 IO-APIC-edge rtc
>
>
> I have no lines with rtc at the end, maybe due to HPET.
>
> Is it a known behaviour of RTC with HPET?
Apparently that's why a config option was added for it.
>>rtctest works for me (2.6.11-rc4). Maybe send me the strace
>>output when you run rtctest and your .config file.
>
>
> See attachment for strace and .config.
>
>
>>Oh, and your kernel boot log, maybe there are some rtc driver
>>messages in it.
>
>
> See attachment for kern.log.
>
> I have bzip2'ed kern.log and .config, since they were rather large.
--
~Randy
next prev parent reply other threads:[~2005-02-15 16:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-13 21:41 RTC Inappropriate ioctl for device Aurélien GÉRÔME
2005-02-15 3:45 ` Randy.Dunlap
2005-02-15 11:16 ` Aurélien GÉRÔME
2005-02-15 16:48 ` Randy.Dunlap [this message]
2005-02-15 19:35 ` Aurélien GÉRÔME
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=421227DF.8060209@osdl.org \
--to=rddunlap@osdl.org \
--cc=ag@roxor.cx \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox