From owner-freebsd-ports@freebsd.org Wed Aug 24 16:04:17 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 916B1BC4DF0 for ; Wed, 24 Aug 2016 16:04:17 +0000 (UTC) (envelope-from freebsd-lists@gromit.dlib.vt.edu) Received: from gromit.dlib.vt.edu (gromit.dlib.vt.edu [128.173.126.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "gromit.dlib.vt.edu", Issuer "Chumby Certificate Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 726BA15E8 for ; Wed, 24 Aug 2016 16:04:17 +0000 (UTC) (envelope-from freebsd-lists@gromit.dlib.vt.edu) Received: from pmather.lib.vt.edu (pmather.lib.vt.edu [128.173.126.193]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by gromit.dlib.vt.edu (Postfix) with ESMTPSA id E116282 for ; Wed, 24 Aug 2016 11:54:34 -0400 (EDT) From: Paul Mather Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Subject: net-p2p/deluge now generates "ioctl sign-extension ioctl ffffffffc0206933" warnings Message-Id: <8ACCBC46-ECDD-4E6E-B0BB-6FC63D987DB7@gromit.dlib.vt.edu> Date: Wed, 24 Aug 2016 11:54:34 -0400 To: freebsd-ports@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) X-Mailer: Apple Mail (2.3124) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Aug 2016 16:04:17 -0000 I updated my FreeBSD/amd64 10-STABLE system yesterday to r304677. Ever = since, /usr/local/bin/deluged from the net-p2p/deluge port has been = generating these messages in my system logs: WARNING pid 54659 (python2.7): ioctl sign-extension ioctl = ffffffffc0206933 I rebuilt and reinstalled the port after the update just to make sure, = but the errors still appear. Has anyone else experienced this? Like I said, this only started = happening for me when I updated my system to r304677. :-( Cheers, Paul.=