Date: Fri, 25 Jun 2004 09:28:05 -0500 (CDT) From: "Conrad J. Sabatier" <conrads@cox.net> To: Robert Watson <rwatson@freebsd.org> Cc: freebsd-current@freebsd.org Subject: Re: fetch hangs on 6/24/04 current build Message-ID: <XFMail.20040625092805.conrads@cox.net> In-Reply-To: <Pine.NEB.3.96L.1040625100043.27139F-100000@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 25-Jun-2004 Robert Watson wrote: > > It might be interesting to look at the following: > > - Use sockstat/netstat to identify the fetch socket, and see whether > either the send of the receive queue contains some amount of > persistent, un-processed data. This would suggest if the > application was stalling and not reading, or that TCP was stalling > and not sending. > > - Use DDB to generate a stack trace of the fetch process in-kernel, > perhaps a few to see whether it's stuck in one place, and if so, > where. This would tell us what it's stuck doing. > > - Use ktrace to generate a trace of fetch and "see what it's doing" > when it appears to hang -- is it looping waiting for I/O, just > blocked in kernel, etc. Good suggestions all. Thanks, I'll try those. Incidentally, it does seem to be working better this morning. Perhaps it *was* just an ISP glitch. -- Conrad J. Sabatier <conrads@cox.net> -- "In Unix veritas"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?XFMail.20040625092805.conrads>