From owner-freebsd-questions  Sun Aug 20  5:56:34 2000
Delivered-To: freebsd-questions@freebsd.org
Received: from merganser.its.uu.se (merganser.its.uu.se [130.238.6.236])
	by hub.freebsd.org (Postfix) with ESMTP id 1D43037B423
	for <questions@freebsd.org>; Sun, 20 Aug 2000 05:56:31 -0700 (PDT)
Received: from regulus.student.UU.SE ([130.238.5.2]:34585 "HELO
        ertr1013.student.uu.se") by merganser.its.uu.se with SMTP
	id <S209120AbQHTMz7>; Sun, 20 Aug 2000 14:55:59 +0200
Received: (qmail 78901 invoked by uid 1001); 20 Aug 2000 12:56:08 -0000
Date:   Sun, 20 Aug 2000 14:56:07 +0200
From: Erik Trulsson <ertr1013@student.uu.se>
To: Rob <rpd@core.com>
Cc: questions@freebsd.org
Subject: Re: top: nlist failed
Message-ID: <20000820145607.A78863@student.uu.se>
Mail-Followup-To: Rob <rpd@core.com>, questions@freebsd.org
References: <000701c00a9f$0da57940$412c28d0@mencken>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <000701c00a9f$0da57940$412c28d0@mencken>; from rpd@core.com on Sun, Aug 20, 2000 at 05:06:19AM -0700
Sender: owner-freebsd-questions@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Sun, Aug 20, 2000 at 05:06:19AM -0700, Rob wrote:
> Dear "questions,"
> 
> I have an aggravating problem involving FreeBSD 4.1-RELEASE (a problem
> that began under 4.0-RELEASE).  Basically, I can't run any of my memory-
> related system tools, such as `top', `swapinfo', or `vmstat'.
> 
>      $ top
>      top: nlist failed
>      $ swapinfo
>      swapinfo: undefined symbol: _numvnodes
>      $ vmstat
>      vmstat: undefined symbols:
>       _cp_time _kmemstatistics _bucket _zlist 
> 
> At this point, you are probably thinking that I upgraded my kernel
> without the utilities.  But I just upgraded from 4.0-RELEASE to
> 4.1-RELEASE (kernel and system) and the problem is still there.
> 
> Originally, under 4.0-RELEASE, everything had been working fine.  Then
> one day, all of a sudden, those problems cropped up.  I had rebuilt my
> kernel from source, so I thought I might have accidentally pulled
> something other than 4.0-RELEASE kernel sources from the cvsup server.
> Rather than doing a `make world', I used the `/stand/sysinstall' method
> to do a binary upgrade to 4.1-RELEASE, which otherwise works fine.
> 
> What's going on here?  Any help would be greatly appreciated.
> 

I had exactly the same problems after upgrading a machine from 3.4 to
4.1-stable.
On this machine I had used the file /boot.config to load the kernel directly
instead of letting loader(8) do it. When I removed that file (and rebooted)
things worked correctly.
I don't know why this worked in my case but it did.
(If that is not the cause of your problem I am afraid I can't help you.)


-- 
<Insert your favourite quote here.>
Erik Trulsson
ertr1013@student.uu.se



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message