Date: Thu, 19 Oct 2000 17:21:11 -0500 From: Steve Ames <steve@virtual-voodoo.com> To: Bosko Milekic <bmilekic@dsuper.net> Cc: freebsd-current@FreeBSD.ORG Subject: Re: sockstat causing OS lockups Message-ID: <20001019172111.A78554@virtual-voodoo.com> In-Reply-To: <Pine.BSF.4.21.0010191813330.27986-100000@jehovah.technokratis.com>; from bmilekic@dsuper.net on Thu, Oct 19, 2000 at 06:15:23PM -0400 References: <200010191452.e9JEqps50765@virtual-voodoo.com> <Pine.BSF.4.21.0010191813330.27986-100000@jehovah.technokratis.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20001019172111.A78554>