From owner-freebsd-current Thu Oct 19 15:11:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from falla.videotron.net (falla.videotron.net [205.151.222.106]) by hub.freebsd.org (Postfix) with ESMTP id 260AD37B4C5 for ; Thu, 19 Oct 2000 15:11:16 -0700 (PDT) Received: from modemcable213.3-201-24.mtl.mc.videotron.ca ([24.201.3.213]) by falla.videotron.net (Sun Internet Mail Server sims.3.5.1999.12.14.10.29.p8) with ESMTP id <0G2P0044L6YHIL@falla.videotron.net> for freebsd-current@FreeBSD.ORG; Thu, 19 Oct 2000 18:11:05 -0400 (EDT) Date: Thu, 19 Oct 2000 18:15:23 -0400 (EDT) From: Bosko Milekic Subject: Re: sockstat causing OS lockups In-reply-to: <200010191452.e9JEqps50765@virtual-voodoo.com> X-Sender: bmilekic@jehovah.technokratis.com To: Steve Ames Cc: freebsd-current@FreeBSD.ORG Message-id: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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. > That's just not normal :) Could someone give me the quick and dirty > on how I can provide additional details? This is on -CURRENT from > 10/16. 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. > The hardware is: [...] Regards, Bosko Milekic bmilekic@technokratis.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message