From owner-freebsd-stable@FreeBSD.ORG Fri Nov 11 08:32:21 2011 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 86F5C1065670 for ; Fri, 11 Nov 2011 08:32:21 +0000 (UTC) (envelope-from wjw@digiware.nl) Received: from mail.digiware.nl (mail.ip6.digiware.nl [IPv6:2001:4cb8:1:106::2]) by mx1.freebsd.org (Postfix) with ESMTP id 1FD8D8FC0C for ; Fri, 11 Nov 2011 08:32:20 +0000 (UTC) Received: from rack1.digiware.nl (localhost.digiware.nl [127.0.0.1]) by mail.digiware.nl (Postfix) with ESMTP id 3F458153434; Fri, 11 Nov 2011 09:32:19 +0100 (CET) X-Virus-Scanned: amavisd-new at digiware.nl Received: from mail.digiware.nl ([127.0.0.1]) by rack1.digiware.nl (rack1.digiware.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aRfNbLMY4JBS; Fri, 11 Nov 2011 09:32:13 +0100 (CET) Received: from [192.168.10.10] (vaio [192.168.10.10]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mail.digiware.nl (Postfix) with ESMTPSA id 9FE42153433; Fri, 11 Nov 2011 09:32:13 +0100 (CET) Message-ID: <4EBCDD8E.3070508@digiware.nl> Date: Fri, 11 Nov 2011 09:32:14 +0100 From: Willem Jan Withagen User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20111105 Thunderbird/8.0 MIME-Version: 1.0 To: Joshua Boyd References: <4EBB97DF.3020803@digiware.nl> <20111110095041.GA73812@icarus.home.lan> <4EBBBACE.3020900@digiware.nl> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "stable@freebsd.org" , "Vogel, Jack" , Jeremy Chadwick Subject: Re: em0 watchdog timeout 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, 11 Nov 2011 08:32:22 -0000 On 10-11-2011 23:25, Joshua Boyd wrote: > On Thu, Nov 10, 2011 at 6:51 AM, Willem Jan Withagen > wrote: > > em0@pci0:0:25:0: class=0x020000 card=0x10bd15d9 > chip=0x10bd8086 rev=0x02 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Intel 82566DM Gigabit Ethernet Adapter (82566DM)' > class = network > subclass = ethernet > bar [10] = type Memory, range 32, base 0xdf900000, size > 131072, enabled > bar [14] = type Memory, range 32, base 0xdf924000, size 4096, > enabled > bar [18] = type I/O Port, range 32, base 0x1820, size 32, enabled > cap 01[c8] = powerspec 2 supports D0 D3 current D0 > cap 05[d0] = MSI supports 1 message, 64 bit enabled with 1 message > cap 13[e0] = PCI Advanced Features: FLR TP > > > And note that this problem only raises it nasty head very few weeks... > > > I have had the same problem, as shown here: > > http://lists.freebsd.org/pipermail/freebsd-stable/2011-June/063092.html > > According to your pciconf output, your card either doesn't support > MSI-X, or you have MSI-X disabled. > > Check the hw.pci.enable_msix sysctl and make sure that it is set to 1. > Also check to make sure there aren't any BIOS settings blocking MSI-X. > > Apparently the older Intel gigabit cards don't support MSI-X, and as > such get starved. I checked and hw.pci.enable_msix=1, so that is on. Any hints what to look for in the BIOS settings that might block MSI-X?? I'll also be ugrading the bios this weekend to if that will enable MSI-X. Another solution would be to get a new version Intel Ethernet card? And stick it in a PIC-X slot? Or would that again suffer from starvation. And as a side question: Why would that starvation actually "crash" the driver/device? --WjW