From owner-freebsd-current Thu Oct 19 18: 0:26 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 7CA4837B479 for ; Thu, 19 Oct 2000 18:00:23 -0700 (PDT) Received: (from steve@localhost) by virtual-voodoo.com (8.11.1/8.11.1) id e9K10Fu23549; Thu, 19 Oct 2000 20:00:15 -0500 (EST) (envelope-from steve) Date: Thu, 19 Oct 2000 20:00:15 -0500 From: Steve Ames To: Dag-Erling Smorgrav Cc: Bosko Milekic , freebsd-current@FreeBSD.ORG Subject: Re: sockstat causing OS lockups Message-ID: <20001019200015.A81517@virtual-voodoo.com> References: <200010191452.e9JEqps50765@virtual-voodoo.com> <20001019172111.A78554@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 des@ofug.org on Fri, Oct 20, 2000 at 02:36:48AM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Oct 20, 2000 at 02:36:48AM +0200, Dag-Erling Smorgrav wrote: > Steve Ames writes: > > On Thu, Oct 19, 2000 at 06:15:23PM -0400, Bosko Milekic wrote: > > > On Thu, 19 Oct 2000, Steve Ames wrote: > > > 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. > > The sockstat(8) author does not have this problem, even though he runs > sockstat(8) quite often on both -STABLE and -CURRENT systems (including > bleeding-edge-hot-off-the-cvsup-server-CURRENT) *grin* I certainly haven't ruled out the possibility of crack induced hysteria. I'm reading the kerneldebug handbook section and will get some traces. -Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message