From owner-freebsd-stable  Sun Feb 24 10:52:33 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 548AB37B400
	for <freebsd-stable@freebsd.org>; Sun, 24 Feb 2002 10:52:23 -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 NAA26877;
	Sun, 24 Feb 2002 13:52:22 -0500 (EST)
Received: (from gallatin@localhost)
	by grasshopper.cs.duke.edu (8.11.6/8.9.1) id g1OIpqu92016;
	Sun, 24 Feb 2002 13:51: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: <15481.13896.908803.910656@grasshopper.cs.duke.edu>
Date: Sun, 24 Feb 2002 13:51:52 -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: <E16f076-0000Hd-00@rip.psg.com>
References: <E16f076-0000Hd-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


Randy Bush writes:
 > just to add to the thread
 > 
 > 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:

#!/bin/csh 

while 1
      vmstat -m | fgrep FFS | fgrep -v NFS 
      sleep 60
end

You should see something like:

     FFS node 10398  5199K   5199K 79618K    16183    0     0  512
     FFS node 10398  5199K   5200K 79618K    16184    0     0  512
     FFS node 10398  5199K   5200K 79618K    16184    0     0  512
<..>

And see what it says at the point where you can not access your disks?


I recently saw a lockup (on alpha) which sounds similar to yours, &
the FFS node pool was exhausted.

Cheers,

Drew



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