Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 8 Nov 2001 09:41:21 -0500 (EST)
From:      mwlucas@blackhelicopters.org
To:        FreeBSD-gnats-submit@freebsd.org
Subject:   docs/31854: new error for FAQ
Message-ID:  <200111081441.JAA08204@blackhelicopters.org>

next in thread | raw e-mail | index | archive | help

>Number:         31854
>Category:       docs
>Synopsis:       new error for FAQ
>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:   Thu Nov 08 06:50:01 PST 2001
>Closed-Date:
>Last-Modified:
>Originator:     Michael Lucas
>Release:        FreeBSD 3.5-STABLE i386
>Organization:
None
>Environment:

today's -doc tree

>Description:

new error for FAQ.  Researched in mailing list archives to develop
full answer, expanding on Matt Dillon's recent answer on this topic.
(Have any docproj members considered just following Matt Dillon around
and writing down everything he says? :-)

>How-To-Repeat:


>Fix:

*** en_US.ISO8859-1/books/faq/book.sgml-dist	Thu Nov  8 07:46:11 2001
--- en_US.ISO8859-1/books/faq/book.sgml	Thu Nov  8 09:38:27 2001
***************
*** 4429,4434 ****
--- 4429,4453 ----
            </para>
          </answer>
        </qandaentry>
+ 
+       <qandaentry>
+         <question id="indefinite-wait-buffer">
+           <para>What does the error <errorname>swap_pager: indefinite
+             wait buffer:</errorname> mean?</para>
+         </question>
+ 
+         <answer>
+           <para>This means that a process is trying to page memory to
+             disk, and the page attempt has hung trying to access the
+             disk for more than 20 seconds.  It might be caused by bad
+             blocks on the disk drive, disk wiring, cables, or any
+             other disk I/O-related hardware.  If the drive itself is
+             actually bad, you will also see disk errors in
+             <filename>/var/log/messages</filename> and in the output
+             of <command>dmesg</command>.  Otherwise, check your cables
+             and connections.</para>
+         </answer>
+       </qandaentry>
      </qandaset>
    </chapter>
  
>Release-Note:
>Audit-Trail:
>Unformatted:

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




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200111081441.JAA08204>