From owner-freebsd-current Thu Oct 19 15:21:17 2000 Delivered-To: freebsd-current@freebsd.org Received: from virtual-voodoo.com (virtual-voodoo.com [204.120.165.254]) by hub.freebsd.org (Postfix) with ESMTP id D5D6F37B4CF for ; Thu, 19 Oct 2000 15:21:14 -0700 (PDT) Received: (from steve@localhost) by virtual-voodoo.com (8.11.1/8.11.1) id e9JMLB908070; Thu, 19 Oct 2000 17:21:11 -0500 (EST) (envelope-from steve) Date: Thu, 19 Oct 2000 17:21:11 -0500 From: Steve Ames To: Bosko Milekic Cc: freebsd-current@FreeBSD.ORG Subject: Re: sockstat causing OS lockups Message-ID: <20001019172111.A78554@virtual-voodoo.com> References: <200010191452.e9JEqps50765@virtual-voodoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from bmilekic@dsuper.net on Thu, Oct 19, 2000 at 06:15:23PM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Oct 19, 2000 at 06:15:23PM -0400, Bosko Milekic wrote: > On Thu, 19 Oct 2000, Steve Ames wrote: > > admin# sockstat | grep -v '*.*' > > close(fstat): > > > > The OS locked up after that. > > I'm running -CURRENT from approximately 4 days ago and I am not > noticing this. It doesn't happen every time. But if you use the command a few times I can almost always force a lockup. If the command is never issued the system stays running. > You should have debugging enabled in your kernel, then you can > provide, at least, a stack trace. Please see the relevant handbook > section for more information. Right then. I'll see what I can dig up. -Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message