From owner-freebsd-stable  Tue Feb 26  9:33:28 2002
Delivered-To: freebsd-stable@freebsd.org
Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1])
	by hub.freebsd.org (Postfix) with ESMTP id BEF3737B417
	for <freebsd-stable@freebsd.org>; Tue, 26 Feb 2002 09:33:22 -0800 (PST)
Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30])
	by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id MAA08161;
	Tue, 26 Feb 2002 12:33:22 -0500 (EST)
Received: (from gallatin@localhost)
	by grasshopper.cs.duke.edu (8.11.6/8.9.1) id g1QHWqD07616;
	Tue, 26 Feb 2002 12:32:52 -0500 (EST)
	(envelope-from gallatin@cs.duke.edu)
From: Andrew Gallatin <gallatin@cs.duke.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15483.50883.994916.60895@grasshopper.cs.duke.edu>
Date: Tue, 26 Feb 2002 12:32:51 -0500 (EST)
To: Randy Bush <randy@psg.com>
Cc: FreeBSD Stable <freebsd-stable@freebsd.org>
Subject: Re: crashes on 4.5-RELEASE
In-Reply-To: <E16fl3l-0003rH-00@rip.psg.com>
References: <E16f076-0000Hd-00@rip.psg.com>
	<15481.13896.908803.910656@grasshopper.cs.duke.edu>
	<E16fl3l-0003rH-00@rip.psg.com>
X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-stable.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-stable>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-stable>
X-Loop: FreeBSD.ORG



OK, you're problem is different than mine..

Drew


Randy Bush writes:
 > >> desktop
 > >> asus cur-dls
 > >> scsi drives
 > >> xfree 4.1.0
 > >> occasional reboots.  but will lock up the scsi system in a day or three.
 > >> what i mean by lock up scsi is
 > >>   o screen is still alive, i can switch desktops, windows, ...
 > >>   o cursor movement is molasses
 > >>   o can type into any xterm
 > >>   o xterms to other hosts act normally
 > >>   o xterm to local host echo etc, but lock up if the command accesses
 > >>     disk
 > > Can you monitor the size of your FFS node malloc pool?  Eg:
 > 
 > 'normal'
 > 
 > % while true; do vmstat -m | fgrep FFS | fgrep -v USB; sleep 10; done
 >      FFS node  7222  1806K   2086K 85432K    12290    0     0  256
 >      FFS node  7223  1806K   2086K 85432K    12293    0     0  256
 >      FFS node  7225  1807K   2086K 85432K    12297    0     0  256
 >      FFS node  7223  1806K   2086K 85432K    12301    0     0  256
 >      FFS node  7229  1808K   2086K 85432K    12311    0     0  256
 >      FFS node  7225  1807K   2086K 85432K    12312    0     0  256
 > 
 > lockup!
 >      FFS node 29697  7425K   7431K 85432K   653356    0     0  256
 >      FFS node 29697  7425K   7431K 85432K   653360    0     0  256
 >      FFS node 29696  7424K   7431K 85432K   653362    0     0  256
 >      FFS node 29693  7424K   7431K 85432K   653365    0     0  256
 >      FFS node 29693  7424K   7431K 85432K   653368    0     0  256
 >      FFS node 29694  7424K   7431K 85432K   653372    0     0  256
 >      FFS node 29695  7424K   7431K 85432K   653373    0     0  256
 >      FFS node 29722  7431K   7431K 85432K   653403    0     0  256
 >      FFS node 29718  7430K   7431K 85432K   653409    0     0  256
 >      FFS node 29715  7429K   7431K 85432K   653418    0     0  256
 >      FFS node 29713  7429K   7431K 85432K   653419    0     0  256
 >      FFS node 29711  7428K   7431K 85432K   653422    0     0  256
 >      FFS node 29710  7428K   7431K 85432K   653423    0     0  256
 >      FFS node 29712  7428K   7431K 85432K   653425    0     0  256
 >      FFS node 29712  7428K   7431K 85432K   653426    0     0  256
 > 
 > randy

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