From owner-freebsd-net@FreeBSD.ORG Mon Feb 25 18:29:33 2013 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id DD01E5BB for ; Mon, 25 Feb 2013 18:29:33 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: from mail-ve0-f182.google.com (mail-ve0-f182.google.com [209.85.128.182]) by mx1.freebsd.org (Postfix) with ESMTP id A2972DC3 for ; Mon, 25 Feb 2013 18:29:33 +0000 (UTC) Received: by mail-ve0-f182.google.com with SMTP id ox1so2454913veb.41 for ; Mon, 25 Feb 2013 10:29:27 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=CRUDoAAwPSftbUNpl9teVJDX+l/OVTMSmvcL8P0S8fo=; b=RIJOZENq6Nb339+KUqq+pId7HcmdCyLBLQIv/NI85+/dz9S9vbHMFPTbBovsvMz9pK pnNRpNl7vlG8wWmPOugFic3Wr4EPKzcAUZat10WPLxfeLh2xXnMMrqfV/ZyQAEKj09nv m4lFstv2CPH61BlsOZTQ+PvmSt2pNRyP3Ss+QJRnTW22ERHFcRqpOcUZTMpFmyM403c2 u97YIF5mFOEoaIVbtw5noJllrS+DYWhDsp+U0t0Bsk9ghBEpxQ8PFYl8X7M6wJUokWUD GrClIKUt64K9hN/031MJPkZNs5bdakn4n53jD0ysZfVo4yaZKVH2AEUas5j8vCOV5+HY bWNw== MIME-Version: 1.0 X-Received: by 10.52.66.41 with SMTP id c9mr8948730vdt.32.1361816967742; Mon, 25 Feb 2013 10:29:27 -0800 (PST) Received: by 10.220.191.132 with HTTP; Mon, 25 Feb 2013 10:29:27 -0800 (PST) In-Reply-To: <512BAA60.3060703@biostat.wisc.edu> References: <512BAA60.3060703@biostat.wisc.edu> Date: Mon, 25 Feb 2013 10:29:27 -0800 Message-ID: Subject: Re: igb network lockups From: Jack Vogel To: "Christopher D. Harrison" Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: freebsd-net@freebsd.org X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 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, 25 Feb 2013 18:29:33 -0000 I've not heard of this problem, but I think most users do not use ALTQ, and we (Intel) do not test using it. Can it be eliminated from the equation? Jack On Mon, Feb 25, 2013 at 10:16 AM, Christopher D. Harrison < harrison@biostat.wisc.edu> wrote: > I recently have been experiencing network "freezes" and network "lockups" > on our Freebsd 9.1 systems which are running zfs and nfs file servers. > I upgraded from 9.0 to 9.1 about 2 months ago and we have been having > issues with almost bi-monthly. The issue manifests in the system becomes > unresponsive to any/all nfs clients. The system is not resource bound as > our I/O is low to disk and our network is usually in the 20mbit/40mbit > range. We do notice a correlation between temporary i/o spikes and > network freezes but not enough to send our system in to "lockup" mode for > the next 5min. Currently we have 4 igb nics in 2 aggr's with 8 queue's > per nic and our dev.igb reports: > > dev.igb.3.%desc: Intel(R) PRO/1000 Network Connection version - 2.3.4 > > I am almost certain the problem is with the ibg driver as a friend is also > experiencing the same problem with the same intel igb nic. He has > addressed the issue by restarting the network using netif on his systems. > According to my friend, once the network interfaces get cleared, everything > comes back and starts working as expected. > > I have noticed an issue with the igb driver and I was looking for thoughts > on how to help address this problem. > http://freebsd.1045724.n5.**nabble.com/em-igb-if-transmit-** > drbr-and-ALTQ-td5760338.html > > Thoughts/Ideas are greatly appreciated!!! > > -C > > ______________________________**_________________ > 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 > " >