From owner-freebsd-current@freebsd.org  Thu Feb 22 17:53:52 2018
Return-Path: <owner-freebsd-current@freebsd.org>
Delivered-To: freebsd-current@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9E15BF1B534
 for <freebsd-current@mailman.ysv.freebsd.org>;
 Thu, 22 Feb 2018 17:53:52 +0000 (UTC) (envelope-from ian@freebsd.org)
Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org
 [IPv6:2001:1900:2254:206a::50:5])
 by mx1.freebsd.org (Postfix) with ESMTP id 364186FCAB
 for <freebsd-current@freebsd.org>; Thu, 22 Feb 2018 17:53:52 +0000 (UTC)
 (envelope-from ian@freebsd.org)
Received: by mailman.ysv.freebsd.org (Postfix)
 id EB3BDF1B530; Thu, 22 Feb 2018 17:53:51 +0000 (UTC)
Delivered-To: current@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id D779DF1B52E
 for <current@mailman.ysv.freebsd.org>; Thu, 22 Feb 2018 17:53:51 +0000 (UTC)
 (envelope-from ian@freebsd.org)
Received: from outbound1a.eu.mailhop.org (outbound1a.eu.mailhop.org
 [52.58.109.202])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 5F2126FCA8
 for <current@freebsd.org>; Thu, 22 Feb 2018 17:53:51 +0000 (UTC)
 (envelope-from ian@freebsd.org)
X-MHO-User: 55ab1f02-17f9-11e8-91c6-33ffc249f3e8
X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information
X-Originating-IP: 67.177.211.60
X-Mail-Handler: DuoCircle Outbound SMTP
Received: from ilsoft.org (unknown [67.177.211.60])
 by outbound1.eu.mailhop.org (Halon) with ESMTPSA
 id 55ab1f02-17f9-11e8-91c6-33ffc249f3e8;
 Thu, 22 Feb 2018 17:53:50 +0000 (UTC)
Received: from rev (rev [172.22.42.240])
 by ilsoft.org (8.15.2/8.15.2) with ESMTP id w1MHrkDj064301;
 Thu, 22 Feb 2018 10:53:46 -0700 (MST) (envelope-from ian@freebsd.org)
Message-ID: <1519322026.91697.135.camel@freebsd.org>
Subject: Re: top: sysctl(vfs.bufspace...) expected 8, got 4
From: Ian Lepore <ian@freebsd.org>
To: "O. Hartmann" <ohartmann@walstatt.org>, current <current@freebsd.org>
Date: Thu, 22 Feb 2018 10:53:46 -0700
In-Reply-To: <20180222184218.2da3db1a@thor.intern.walstatt.dynvpn.de>
References: <CAG6CVpUxXgNe1ZoXrzthPcgO=SwDkg-4f-NyME=GTbvdLCiUjw@mail.gmail.com>
 <201802211818.w1LII7fh087166@pdx.rh.CN85.dnsmgr.net>
 <CACNAnaGuCT+0R3zeHbB=YEXu074f38JWLkJ8OrZAQ0boXrXTjw@mail.gmail.com>
 <20180221200551.718ab72f@thor.intern.walstatt.dynvpn.de>
 <20180222184218.2da3db1a@thor.intern.walstatt.dynvpn.de>
Content-Type: text/plain; charset="ISO-8859-1"
X-Mailer: Evolution 3.18.5.1 FreeBSD GNOME Team Port 
Mime-Version: 1.0
Content-Transfer-Encoding: 8bit
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.25
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Feb 2018 17:53:52 -0000

On Thu, 2018-02-22 at 18:41 +0100, O. Hartmann wrote:
> Am Wed, 21 Feb 2018 20:05:24 +0100
> "O. Hartmann" <o.hartmann@walstatt.org> schrieb:
> 
> > 
> > On CURRENT ( 12.0-CURRENT FreeBSD 12.0-CURRENT #196 r329679: Tue
> > Feb 20 23:06:15 CET
> > 2018 amd64) I'm honored by this nice bug when calling top:
> > 
> > top: sysctl(vfs.bufspace...) expected 8, got 4
> > 
> > 
> > Regards,
> > 
> > oh
> I still can not use "top", it quits with the error mentioned above.
> Whats is wrong with
> my setup?
> 

It seems like the two big candidates must be mismatch between kernel
and userland, or maybe 32/64-bit mismatch between the kernel and top.

What's the output of

  uname -pmUK
  file `which top`
  ldd `which top`

-- Ian