[ntp:questions] ntpd failure on ioctl(I_SETSIG, S_INPUT): Bbad address

Harlan Stenn stenn at ntp.org
Sat Feb 7 02:18:59 UTC 2009

>>> In article <977AD296BDAF2F428CF7028F923E4A200AF1A3D6 at earth.impinj.com>, wayne.liu at impinj.com (Wayne Liu) writes:

Wayne> Hello All; I'm running the latest ntp-4.2.4p6 on Linux 2.6.18 and I
Wayne> got the following up front when I start ntpd: =========== ntpd
Wayne> 4.2.4p6 at 1.1549 Fri Feb 6 02:09:46 UTC 2009 (3) ....  setsockopt
Wayne> SO_TIMESTAMP enabled on fd 16 address bind() fd 16, family 2,
Wayne> port 123, addr, flags=0x89 addto_syslog: init_socket_sig:
Wayne> ioctl(I_SETSIG, S_INPUT) failed: Bad address ==========

Wayne> From the kernel code it seems that "Bad address" is due to I_SETSIG not
Wayne> being supported by sock as an ioctl cmd, which is then passed down to
Wayne> dev_ioctl underneath which rejects the arg S_INPUT as bad address.

Wayne> I noticed the code that invokes ioctl(I_SETSIG, S_INPUT) is gated by
Wayne> #ifdef USE_UDP_SIGPOLL, which the auto configure turns on.  But the
Wayne> kernel somehow thinks it's not supported.  Am I doing something wrong
Wayne> with the configure?  Or is there a Linux kernel version dependency
Wayne> that I'm missing.

The configure choices for USE_UDP_SIGPOLL were done a long time ago and
might have changed.

I'd appreciate learning how to discern the correct answer for your case.

I do not know what the correct answer is...
Harlan Stenn <stenn at ntp.org>
http://ntpforum.isc.org  - be a member!

More information about the questions mailing list