Date: Tue, 4 May 2021 12:11:17 -0600 From: Warner Losh <imp@bsdimp.com> To: bob prohaska <fbsd@www.zefox.net> Cc: "freebsd-arm@freebsd.org" <freebsd-arm@freebsd.org>, FreeBSD Ports <freebsd-ports@freebsd.org> Subject: Re: Xoscope nuisance console messages on Pi4 running -current Message-ID: <CANCZdfoAmtt7mZsRsziMAFebFCwY6ANVsyPpYzs2zJe31q0Dbw@mail.gmail.com> In-Reply-To: <20210503063701.GA34665@www.zefox.net> References: <20210503063701.GA34665@www.zefox.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, May 3, 2021 at 12:38 AM bob prohaska <fbsd@www.zefox.net> wrote: > After a successful compile of audio/xoscope on a Pi4 running current a > stream of messages appeared on the console and in the security log > while xoscope was running: > > > +WARNING pid 26370 (xoscope): ioctl sign-extension ioctl ffffffffc0045006 > +WARNING pid 26370 (xoscope): ioctl sign-extension ioctl ffffffffc0045005 > +WARNING pid 26370 (xoscope): ioctl sign-extension ioctl ffffffffc0045002 > +WARNING pid 26370 (xoscope): ioctl sign-extension ioctl ffffffffc0045006 > +WARNING pid 26370 (xoscope): ioctl sign-extension ioctl ffffffffc0045005 > +WARNING pid 26370 (xoscope): ioctl sign-extension ioctl ffffffffc0045002 > > They seem to come at a fairly high rate and clutter the logfiles, but > apart from that nuisance nothing else seemed visibly amiss. > > Are they of any significance? > I fixed this a while ago, but some people copied our definitions which weren't sufficiently careful in using unsigned in places to avoid sign extension.... Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANCZdfoAmtt7mZsRsziMAFebFCwY6ANVsyPpYzs2zJe31q0Dbw>