From owner-freebsd-net@FreeBSD.ORG Mon Jul 18 16:40:46 2011 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C146D106564A for ; Mon, 18 Jul 2011 16:40:46 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: from mail-vx0-f182.google.com (mail-vx0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id 750C68FC08 for ; Mon, 18 Jul 2011 16:40:46 +0000 (UTC) Received: by vxg33 with SMTP id 33so3218333vxg.13 for ; Mon, 18 Jul 2011 09:40:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=5i5rp1IxGnfmUmH5iY/0Pg7KCjMxcITVPHGt0TLOxoY=; b=IKyLDSulVU2CAu9PxNe1ZplZkp5RvserkZRSTpkyREV8v4VkoVCgp5g28ICkUoSeiG 8t+M+AlqGXe6B5FVdChdwhtOAEgfxacG1MIdrrTsY69voaD+75mjjw9+B02CAbcZ0/kL 1h3qobXQOI8SlK+bnaECITQr0XTx0owbqtcDE= MIME-Version: 1.0 Received: by 10.52.69.39 with SMTP id b7mr6068120vdu.264.1311007245572; Mon, 18 Jul 2011 09:40:45 -0700 (PDT) Received: by 10.52.187.66 with HTTP; Mon, 18 Jul 2011 09:40:45 -0700 (PDT) In-Reply-To: References: <379885BA631F4C7787C24E00A174B429@multiplay.co.uk> Date: Mon, 18 Jul 2011 09:40:45 -0700 Message-ID: From: Jack Vogel To: Steven Hartland Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-net@freebsd.org, Kevin Oberman Subject: Re: igb enable_aim or flow_control causing tcp stalls? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Jul 2011 16:40:46 -0000 I have no idea... but as a matter of principle I would see if updating to later code, both OS and especially the driver, reproduces the issue. Our validation group often has Linux as a link partner in testing, which can be good and bad, it actually sometimes has problems that FBSD on both sides doesn't. Jack On Mon, Jul 18, 2011 at 4:20 AM, Steven Hartland wrote: > ----- Original Message ----- From: "Kevin Oberman" > >> >> Use "tcpdump -s0 -w file.pcap host remote-system" to see how it fails. You >> may want to capture on both ends. Then use wireshark (in ports) to analyze >> the data. >> >> There are other tools to provide other types of analysis, depending on the >> type of problem. >> > > I've managed to get a capture from both ends but its doesn't really make > too > much sense to me. You can clearly see the stall which starts at the 2.1 > second > mark, and recovers at the 65 second mark but what's causing it is a > mystery. > > I've attached what I believe is the relevant a snippet from each trace. > > At this point I believe I've eliminated aim and flow_control as these where > both off when this test was preformed > > Any advice would be appreciated. > > The layout for this test was:- > Source (7.0-RELEASE-p2 on em0) -> Cisco 6509 -> supermicro blade -> Target > (8.2-RELEASE on igb0) > > I'm going to try and eliminate the Cisco next by going from two blades > on the local supermicro blade switch. > > Regards > Steve > > > > ==============================**================== > This e.mail is private and confidential between Multiplay (UK) Ltd. and the > person or entity to whom it is addressed. In the event of misdirection, the > recipient is prohibited from using, copying, printing or otherwise > disseminating it or any information contained in it. > In the event of misdirection, illegible or incomplete transmission please > telephone +44 845 868 1337 > or return the E.mail to postmaster@multiplay.co.uk. > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" >