From owner-freebsd-stable@FreeBSD.ORG Wed Jul 5 17:48:19 2006 Return-Path: X-Original-To: stable@FreeBSD.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4594116A4E0 for ; Wed, 5 Jul 2006 17:48:19 +0000 (UTC) (envelope-from cswiger@mac.com) Received: from pi.codefab.com (pi.codefab.com [199.103.21.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4137843D6B for ; Wed, 5 Jul 2006 17:48:11 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from localhost (localhost [127.0.0.1]) by pi.codefab.com (Postfix) with ESMTP id C2E9C5FCC; Wed, 5 Jul 2006 13:48:10 -0400 (EDT) X-Virus-Scanned: amavisd-new at codefab.com Received: from pi.codefab.com ([127.0.0.1]) by localhost (pi.codefab.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0YINCiM3DGwb; Wed, 5 Jul 2006 13:48:10 -0400 (EDT) Received: from [199.103.21.238] (pan.codefab.com [199.103.21.238]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by pi.codefab.com (Postfix) with ESMTP id 1025D5C2E; Wed, 5 Jul 2006 13:48:10 -0400 (EDT) In-Reply-To: <86C10E7655AA8C2D8C433AAC@[10.0.0.90]> References: <86C10E7655AA8C2D8C433AAC@[10.0.0.90]> Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Charles Swiger Date: Wed, 5 Jul 2006 13:48:07 -0400 To: Justin T. Gibbs X-Mailer: Apple Mail (2.752.2) Cc: stable@FreeBSD.org Subject: Re: fetch hangs on AMD64 RELENG_6 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Jul 2006 17:48:19 -0000 On Jul 5, 2006, at 1:42 PM, Justin T. Gibbs wrote: > I'm seeing fetch hang under AMD64/RELENG_6 when fetching data > from several different sites. An i386 machine sitting next to it > running current from a few weeks back is not showing this problem > when fetching the same files. [ ... ] > Any hints on how I might help debug the problem? Using tcpdump to look at the traffic would be a useful starting point. :-) -- -Chuck