Add an entry for the "nlist failed" message.
PR: docs/24823 Submitted by: Dima Dorfman <dima@unixfreak.org>
This commit is contained in:
Nik Clayton
parent
c05338fce2
commit
dc66b4e7b9
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=8755
2 changed files with 74 additions and 2 deletions
|
|
@ -11,7 +11,7 @@
|
||||||
|
|
||||||
<corpauthor>The FreeBSD Documentation Project</corpauthor>
|
<corpauthor>The FreeBSD Documentation Project</corpauthor>
|
||||||
|
|
||||||
<pubdate>$FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.141 2001/01/31 12:12:13 ben Exp $</pubdate>
|
<pubdate>$FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.142 2001/02/02 03:16:45 nik Exp $</pubdate>
|
||||||
|
|
||||||
<abstract>
|
<abstract>
|
||||||
<para>This is the FAQ for FreeBSD versions 2.X, 3.X, and 4.X.
|
<para>This is the FAQ for FreeBSD versions 2.X, 3.X, and 4.X.
|
||||||
|
|
@ -4166,6 +4166,42 @@ IO range check 0x00 activate 0x01</screen>
|
||||||
|
|
||||||
</answer>
|
</answer>
|
||||||
</qandaentry>
|
</qandaentry>
|
||||||
|
|
||||||
|
<qandaentry>
|
||||||
|
<question id="nlist-failed">
|
||||||
|
<para>I get the error <errorname>nlist failed</errorname> when
|
||||||
|
running, for example, <command>top</command> or
|
||||||
|
<command>systat</command>.</para>
|
||||||
|
</question>
|
||||||
|
|
||||||
|
<answer>
|
||||||
|
<para>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:</para>
|
||||||
|
|
||||||
|
<itemizedlist>
|
||||||
|
<listitem>
|
||||||
|
<para>Your kernel and userland are not synchronized (i.e., you
|
||||||
|
built a new kernel but did not do an
|
||||||
|
<maketarget>installworld</maketarget>, 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
|
||||||
|
<filename>/usr/src/UPDATING</filename> for the correct
|
||||||
|
sequence).</para>
|
||||||
|
</listitem>
|
||||||
|
|
||||||
|
<listitem>
|
||||||
|
<para>You are not using <command>/boot/loader</command> to load
|
||||||
|
your kernel, but doing it directly from boot2 (see
|
||||||
|
&man.boot.8;). While there is nothing wrong with bypassing
|
||||||
|
<command>/boot/loader</command>, it generally does a better
|
||||||
|
job of making the kernel symbols available to user
|
||||||
|
applications.</para>
|
||||||
|
</listitem>
|
||||||
|
</itemizedlist>
|
||||||
|
</answer>
|
||||||
|
</qandaentry>
|
||||||
</qandaset>
|
</qandaset>
|
||||||
</chapter>
|
</chapter>
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -11,7 +11,7 @@
|
||||||
|
|
||||||
<corpauthor>The FreeBSD Documentation Project</corpauthor>
|
<corpauthor>The FreeBSD Documentation Project</corpauthor>
|
||||||
|
|
||||||
<pubdate>$FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.141 2001/01/31 12:12:13 ben Exp $</pubdate>
|
<pubdate>$FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.142 2001/02/02 03:16:45 nik Exp $</pubdate>
|
||||||
|
|
||||||
<abstract>
|
<abstract>
|
||||||
<para>This is the FAQ for FreeBSD versions 2.X, 3.X, and 4.X.
|
<para>This is the FAQ for FreeBSD versions 2.X, 3.X, and 4.X.
|
||||||
|
|
@ -4166,6 +4166,42 @@ IO range check 0x00 activate 0x01</screen>
|
||||||
|
|
||||||
</answer>
|
</answer>
|
||||||
</qandaentry>
|
</qandaentry>
|
||||||
|
|
||||||
|
<qandaentry>
|
||||||
|
<question id="nlist-failed">
|
||||||
|
<para>I get the error <errorname>nlist failed</errorname> when
|
||||||
|
running, for example, <command>top</command> or
|
||||||
|
<command>systat</command>.</para>
|
||||||
|
</question>
|
||||||
|
|
||||||
|
<answer>
|
||||||
|
<para>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:</para>
|
||||||
|
|
||||||
|
<itemizedlist>
|
||||||
|
<listitem>
|
||||||
|
<para>Your kernel and userland are not synchronized (i.e., you
|
||||||
|
built a new kernel but did not do an
|
||||||
|
<maketarget>installworld</maketarget>, 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
|
||||||
|
<filename>/usr/src/UPDATING</filename> for the correct
|
||||||
|
sequence).</para>
|
||||||
|
</listitem>
|
||||||
|
|
||||||
|
<listitem>
|
||||||
|
<para>You are not using <command>/boot/loader</command> to load
|
||||||
|
your kernel, but doing it directly from boot2 (see
|
||||||
|
&man.boot.8;). While there is nothing wrong with bypassing
|
||||||
|
<command>/boot/loader</command>, it generally does a better
|
||||||
|
job of making the kernel symbols available to user
|
||||||
|
applications.</para>
|
||||||
|
</listitem>
|
||||||
|
</itemizedlist>
|
||||||
|
</answer>
|
||||||
|
</qandaentry>
|
||||||
</qandaset>
|
</qandaset>
|
||||||
</chapter>
|
</chapter>
|
||||||
|
|
||||||
|
|
|
||||||
Loading…
Reference in a new issue