From owner-freebsd-questions  Thu May 22 02:11:02 1997
Return-Path: <owner-questions>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id CAA11452
          for questions-outgoing; Thu, 22 May 1997 02:11:02 -0700 (PDT)
Received: from implode.root.com (implode.root.com [198.145.90.17])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA11447
          for <freebsd-questions@FreeBSD.ORG>; Thu, 22 May 1997 02:11:00 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by implode.root.com (8.8.5/8.8.5) with SMTP id CAA25541;
	Thu, 22 May 1997 02:11:59 -0700 (PDT)
Message-Id: <199705220911.CAA25541@implode.root.com>
X-Authentication-Warning: implode.root.com: localhost [127.0.0.1] didn't use HELO protocol
To: Bryce Newall <data@ds9.abac.com>
cc: FreeBSD Questions List <freebsd-questions@FreeBSD.ORG>
Subject: Re: Crash problems 
In-reply-to: Your message of "Thu, 22 May 1997 00:38:57 PDT."
             <Pine.LNX.3.96.970522002222.30340D-100000@ds9.abac.com> 
From: David Greenman <dg@root.com>
Reply-To: dg@root.com
Date: Thu, 22 May 1997 02:11:59 -0700
Sender: owner-questions@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

>options         BOUNCE_BUFFERS          #include support for DMA bounce buffers

   You don't need bounce buffers support, so you may as well kill this option.

>options         DIAGNOSTIC
># Used to help catch errors in certain types of programs
># when they compile, won't hurt anything, and can help.

   Actually, that's not what that option does. It adds some additional
diagnostic code which may or may not be well tested. This option is only
recommended for kernel developers who understand the ramifications of
using it.

>options         "MAX_USERS=300"

   That's not a real option.

># this list of network interfaces until the probes have been fixed. 
># Right now it appears that the ie0 must be probed before ep0. See
># revision 1.20 of this file.
>device vx0      

   The 3c905 (vx) driver has been in various states of working/not working.
If it is possible for you to try, you may wish to swap this out for a DEC
chip based card or an Intel Pro/100B.
   It would be useful if you could add options "DDB" to your kernel. You can
then escape to the debugger (ctrl-print_scrn) and do a "ps" to look at the
process states - the WMESG should be useful in determining why things are
hanging.

-DG

David Greenman
Core-team/Principal Architect, The FreeBSD Project