From owner-freebsd-stable@FreeBSD.ORG Fri Nov 25 23:18:28 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 00ECE106566B for ; Fri, 25 Nov 2011 23:18:28 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: from mail-ww0-f50.google.com (mail-ww0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id 8AA158FC13 for ; Fri, 25 Nov 2011 23:18:27 +0000 (UTC) Received: by wwe5 with SMTP id 5so2840672wwe.31 for ; Fri, 25 Nov 2011 15:18:26 -0800 (PST) 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=sZAOA7xVSoH08T8oz9efIjwyZnw2HnAILjSWE1d+SOs=; b=VTQwHUzUboFJZQ49uImgUgbxPVG0TEFFQs7XKlORdlbTrPl6/gKUAAIYpcKXimW/LT h86uHU+YvHh33smBJCRcZAoo6YXfh241S5xMmY9glfPDP65k7hSgtNGfpmDp/0FtUPeM LaeLHeX7kw10afQbKsPTi9V7sEWg4TBRwZr8A= MIME-Version: 1.0 Received: by 10.180.81.73 with SMTP id y9mr36403850wix.37.1322261572583; Fri, 25 Nov 2011 14:52:52 -0800 (PST) Received: by 10.180.93.200 with HTTP; Fri, 25 Nov 2011 14:52:52 -0800 (PST) In-Reply-To: References: Date: Fri, 25 Nov 2011 14:52:52 -0800 Message-ID: From: Jack Vogel To: Daniel Kalchev Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-stable@freebsd.org Subject: Re: igb hang when cable unplugged 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: Fri, 25 Nov 2011 23:18:28 -0000 On Fri, Nov 25, 2011 at 1:18 PM, Daniel Kalchev wrote: > I am observing an transmit hang of the igb driver when the cable is > unplugged. It only recovers after unit reset, such as > > ifconfig igb0 down up > > This is with kernel > > FreeBSD xxx 8.2-STABLE FreeBSD 8.2-STABLE #0: Fri Sep 30 16:17:47 EEST > 2011 root@xxx:/usr/obj/usr/src/sys/GENERIC amd64 > > igb0: port > 0x3020-0x303f mem > 0xb1d60000-0xb1d7ffff,0xb1d40000-0xb1d5ffff,0xb1e04000-0xb1e07fff irq 37 at > device 0.0 on pci13 > igb0: Using MSIX interrupts with 9 vectors > igb0: [ITHREAD] > igb0: [ITHREAD] > igb0: [ITHREAD] > igb0: [ITHREAD] > igb0: [ITHREAD] > igb0: [ITHREAD] > igb0: [ITHREAD] > igb0: [ITHREAD] > igb0: [ITHREAD] > igb0: Ethernet address: 00:25:90:36:ee:7c > > The interface is quad port Supermicro branded PCI-E card with > > pciconf -vl > > igb0@pci0:13:0:0: class=0x020000 card=0x10c915d9 chip=0x10c98086 > rev=0x01 hdr=0x00 > vendor = 'Intel Corporation' > class = network > subclass = ethernet > igb1@pci0:13:0:1: class=0x020000 card=0x10c915d9 chip=0x10c98086 > rev=0x01 hdr=0x00 > vendor = 'Intel Corporation' > class = network > subclass = ethernet > igb2@pci0:16:0:0: class=0x020000 card=0x10c915d9 chip=0x10c98086 > rev=0x01 hdr=0x00 > vendor = 'Intel Corporation' > class = network > subclass = ethernet > igb3@pci0:16:0:1: class=0x020000 card=0x10c915d9 chip=0x10c98086 > rev=0x01 hdr=0x00 > vendor = 'Intel Corporation' > class = network > subclass = ethernet > > > Has anyone experience something like this? Is there solution? It is very > inconvenient to have to down/up the interfaces manually via the IPMI > console when such thing happens. > > Ya, don't unplug the cable .... :) Just a bit of holiday humor.... will look into the issue after the long weekend. Jack