Date: Fri, 25 Jun 2004 10:03:58 -0400 (EDT) From: Robert Watson <rwatson@freebsd.org> To: "Conrad J. Sabatier" <conrads@cox.net> Cc: freebsd-current@freebsd.org Subject: Re: fetch hangs on 6/24/04 current build Message-ID: <Pine.NEB.3.96L.1040625100043.27139F-100000@fledge.watson.org> In-Reply-To: <XFMail.20040625071821.conrads@cox.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 25 Jun 2004, Conrad J. Sabatier wrote: > I tried switching to wget, using "FETCH_CMD=wget -v -c" in > /etc/make.conf, and got the most bizarre behavior, something I've never > seen before. wget would fail each time, complaining about "invalid > option --". Very strange. 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. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Principal Research Scientist, McAfee Research
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.NEB.3.96L.1040625100043.27139F-100000>