From owner-freebsd-stable@FreeBSD.ORG Sat Nov 19 18:02:39 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 907E016A41F for ; Sat, 19 Nov 2005 18:02:39 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 43CB743D45 for ; Sat, 19 Nov 2005 18:02:38 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id 4B97A46B83; Sat, 19 Nov 2005 13:02:38 -0500 (EST) Date: Sat, 19 Nov 2005 18:02:38 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Laurent In-Reply-To: <437F6315.4000403@gmail.com> Message-ID: <20051119180128.X82553@fledge.watson.org> References: <437F6315.4000403@gmail.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-stable@freebsd.org Subject: Re: [FreeBSD6] kinfo_size mismatch X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Nov 2005 18:02:39 -0000 On Sat, 19 Nov 2005, Laurent wrote: > I've recently upgraded my AMD64 FreeBSD station from 5.4 to 6.0 using > the handbook method. > > Everything seems to work OK but I have the message after repeating every > second on tty1 after I log on X : > > kvm_open : kinfo_proc size mismatch (expected 912 got 1088). > > After some search on Internet I gave an eye to /usr/src/sys/sys/user.h > for kinfo_proc_size values, but the right value (1088) is already set > for amd64. > > So I don't know how to solve this problem, and I'm quite afraid to touch > some souce code on my system. This is almost certainly a mismatch between the kernel version and a monitoring tool that is trying to inspect kernel state (specifically, retrieve process lists). If your buildworld/installworld doesn't match your kernel version, then you need to rebuild and make sure everything is in sync. If it does, it's probably a third-party package that is out of sync and needs updating. Robert N M Watson