From owner-freebsd-doc Fri Feb 2 21:10:21 2001 Delivered-To: freebsd-doc@freebsd.org Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 4262537B503 for ; Fri, 2 Feb 2001 21:10:02 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f135A1x88143; Fri, 2 Feb 2001 21:10:01 -0800 (PST) (envelope-from gnats) Received: from bazooka.unixfreak.org (bazooka.unixfreak.org [63.198.170.138]) by hub.freebsd.org (Postfix) with ESMTP id AE22937B491 for ; Fri, 2 Feb 2001 21:01:40 -0800 (PST) Received: from hornet.unixfreak.org (hornet [63.198.170.140]) by bazooka.unixfreak.org (Postfix) with ESMTP id 7A9933E02 for ; Fri, 2 Feb 2001 21:01:40 -0800 (PST) Received: (from dima@localhost) by hornet.unixfreak.org (8.11.1/8.11.1) id f1351eI92415; Fri, 2 Feb 2001 21:01:40 -0800 (PST) (envelope-from dima) Message-Id: <200102030501.f1351eI92415@hornet.unixfreak.org> Date: Fri, 2 Feb 2001 21:01:40 -0800 (PST) From: dima@unixfreak.org Reply-To: dima@unixfreak.org To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: docs/24823: [PATCH] New FAQ entry about top(1) not working (``nlist'' errors) Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Number: 24823 >Category: docs >Synopsis: [PATCH] New FAQ entry about top(1) not working (``nlist'' errors) >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-doc >State: open >Quarter: >Keywords: >Date-Required: >Class: change-request >Submitter-Id: current-users >Arrival-Date: Fri Feb 02 21:10:01 PST 2001 >Closed-Date: >Last-Modified: >Originator: Dima Dorfman >Release: FreeBSD 4.2-20010102-STABLE i386 >Organization: Private >Environment: Not relevant. >Description: If one loads the kernel directly from boot0 (not using /boot/loader), or if one screws up an upgrade and the kernel is out of synch with the userland, one can get weird errors from top(1) and some other programs about certain kernel symbols not being found. This seems to come up on -questions every few weeks; this FAQ entry should explain the cause and solution. >How-To-Repeat: Read -questions. >Fix: Apply the following to doc/en_US.ISO_8859-1/books/faq/book.sgml. Index: book.sgml =================================================================== RCS file: /st/src/FreeBSD/doc/en_US.ISO_8859-1/books/faq/book.sgml,v retrieving revision 1.140 diff -u -r1.140 book.sgml --- book.sgml 2001/01/18 01:14:24 1.140 +++ book.sgml 2001/01/30 01:34:16 @@ -4166,6 +4166,41 @@ + + + + I get the error nlist failed when running, + for example, top or + systat. + + + + The problem is that the application you are trying to run is + looking for a specific kernel symbol, but, for whatever reason, + cannot find it; this error stems from one of two problems: + + + + Your kernel and userland are not synchronized (i.e., you + built a new kernel but did not do an installworld, or vice + versa), and thus the symbol table is different from what the + user application thinks it is. If this is the case, simply + complete the upgrade process (see + /usr/src/UPDATING for the correct + sequence). + + + + You are not using /boot/loader to load + your kernel, but doing it directly from boot0 (see + &man.boot.8;). While there is nothing wrong with bypassing + /boot/loader, it generally does a better + job of making the kernel symbols available to user + applications. + + + + >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message