From owner-freebsd-net@FreeBSD.ORG Wed Mar 19 19:48:57 2014 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6FC44C16 for ; Wed, 19 Mar 2014 19:48:57 +0000 (UTC) Received: from mail-qc0-x241.google.com (mail-qc0-x241.google.com [IPv6:2607:f8b0:400d:c01::241]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 339533EE for ; Wed, 19 Mar 2014 19:48:57 +0000 (UTC) Received: by mail-qc0-f193.google.com with SMTP id e16so3470554qcx.0 for ; Wed, 19 Mar 2014 12:48:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=JwZDKGEGgCzYdv++N21sNICJZ+E0+8Hc2lBl0QtT25w=; b=EOwUBDvS5Yr1yX2uHsJ8rIh6AbvjSlFlLOmsEpHYVT5vVPVlax5X9SfYrW09napFIT P9dQfE+P05xqpS8u1BuvgccfdAZ54R545vJb6vsNwULcSHX8hMdDW7j3HBtGinVYU+Qh LkCjcUrcVh2IKpH2MZ/iiQauF/gc4ChsQ/znDF06scD+psAWEgs1p2PUmbsyQRDpb6+u ZHDKCiY6OkZDgkN757IAnTICAbjoN8VI/GwNYLVK0/dSUDAtnvzs3NPAmlQnoM/YYUna IxijnyvrWJMBjVjkw5zsVffwWrduqtKPR300VN1syXi4QL2PPte6/jGTLWb37qfksJle rk0A== MIME-Version: 1.0 X-Received: by 10.140.29.68 with SMTP id a62mr29099630qga.57.1395258536475; Wed, 19 Mar 2014 12:48:56 -0700 (PDT) Received: by 10.96.79.97 with HTTP; Wed, 19 Mar 2014 12:48:56 -0700 (PDT) Date: Wed, 19 Mar 2014 16:48:56 -0300 Message-ID: Subject: Network loss From: Christopher Forgeron To: freebsd-net@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Mar 2014 19:48:57 -0000 Hello, I'm replying on the "9.2 ixgbe tx queue hang" thread, and wanted to tie in here the fact that I was able to replicate this problem with iSCSI only, no NFS. I assume the conversation will continue on the other thread. Johan Kooijman @ Sat Mar 1 08:55:14 UTC 2014 > >I think NFS is part of the issue here. Everybody that seems to have this >issue is running NFS. On top of that: the setup I'm having issues with, >didn't have any issues for months when we were running istgt instead of NFS.