Date: Thu, 19 Oct 2000 20:00:15 -0500 From: Steve Ames <steve@virtual-voodoo.com> To: Dag-Erling Smorgrav <des@ofug.org> Cc: Bosko Milekic <bmilekic@dsuper.net>, freebsd-current@FreeBSD.ORG Subject: Re: sockstat causing OS lockups Message-ID: <20001019200015.A81517@virtual-voodoo.com> In-Reply-To: <xzp7l748i1r.fsf@flood.ping.uio.no>; from des@ofug.org on Fri, Oct 20, 2000 at 02:36:48AM %2B0200 References: <200010191452.e9JEqps50765@virtual-voodoo.com> <Pine.BSF.4.21.0010191813330.27986-100000@jehovah.technokratis.com> <20001019172111.A78554@virtual-voodoo.com> <xzp7l748i1r.fsf@flood.ping.uio.no>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Oct 20, 2000 at 02:36:48AM +0200, Dag-Erling Smorgrav wrote: > Steve Ames <steve@virtual-voodoo.com> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20001019200015.A81517>