Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 4 Aug 2017 13:06:00 -0700 (PDT)
From:      Christian Kujau <lists@nerdbynature.de>
To:        Per olof Ljungmark <peo@intersonic.se>
Cc:        freebsd-questions@freebsd.org
Subject:   Re: ioctl sign-extensio on amd64 (again)
Message-ID:  <alpine.DEB.2.21.1.1708041257500.22141@trent.utfs.org>
In-Reply-To: <444dc69b-c586-7e0b-61c8-77a2bc722516@intersonic.se>
References:  <444dc69b-c586-7e0b-61c8-77a2bc722516@intersonic.se>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
On Fri, 4 Aug 2017, Per olof Ljungmark wrote:
> In building a camera system with multimedia/motion, syslog is filled up with,
> kernel: WARNING pid 72755 (motion): ioctl sign-extension ioctl
> ffffffffc0585611
> 
> After som googling this appears to be a long standing problem with some python
> stuff and amd64.
> 
> My question is, how can I get rid of the messages? Motion works as expected, I
> just do not want this filling up the logs.

Short of disabling the printf in sys_ioctl() in sys/kern/sys_generic.c, 
the Right Thing To Do™ would be to fix multimedia/motion not to issue
those erroneous ioctls. This was reported (and sometimes fixed) for other 
applications too:

* sysutils/duplicity-devel/ throws ioctl sign-extension ioctl ffffffff80087467
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=152770

* mt(8): ioctl sign-extension warnings from some mt commands on 64-bit
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=147938

* Fix fcntl module to accept 'unsigned long' type commands for ioctl(2).
  https://bugs.python.org/issue25026

Maybe the respective commits could shed some light on how to do this for 
multimedia/motion?

Christian.
-- 
BOFH excuse #417:

Computer room being moved.  Our systems are down for the weekend.



Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?alpine.DEB.2.21.1.1708041257500.22141>