From owner-freebsd-net@FreeBSD.ORG Wed Aug 11 17:05:25 2010 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 6FEF91065673 for ; Wed, 11 Aug 2010 17:05:25 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: from mail-pz0-f54.google.com (mail-pz0-f54.google.com [209.85.210.54]) by mx1.freebsd.org (Postfix) with ESMTP id 409128FC0C for ; Wed, 11 Aug 2010 17:05:25 +0000 (UTC) Received: by pzk7 with SMTP id 7so146336pzk.13 for ; Wed, 11 Aug 2010 10:05:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=qB8kJ7mi62MfDjPGe77rd3KbJl4uOJGL3fHcF8LYjc4=; b=pPT58pMciYI/7nJvB/2eCt/j1tGfYAfXiQm7shceBJ1nsDSCPQuEnZpkepUgORRpgC Fb+jlVQGVJPzrL4/ROzpS/L5ExHvMmikb8Xpc5jWUJfrYz5Qn6NeTC8Pjp3aPi9vkwsb UOSt0dSrmhNn6G5717hJ7h1LVOuAgt6Z7TZd0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=T80/7YLYI1h/7zEfPCgIDSEcHMjgHitAudGStB2kz5XZGNbWW8fJRyuVl4rlqmuIKp L/96iNCnmXmV11uM6BEwJ0ZSWrTP698CE8gToBdTYhMn1ULNNsLUNW4qsoeQ7BHKxrtO c4DBvF2ZI1ysJ9cIhDVa353fJlxuRvcfMji1s= MIME-Version: 1.0 Received: by 10.142.47.3 with SMTP id u3mr2277188wfu.76.1281546321008; Wed, 11 Aug 2010 10:05:21 -0700 (PDT) Received: by 10.142.200.19 with HTTP; Wed, 11 Aug 2010 10:05:20 -0700 (PDT) In-Reply-To: <20100811164318.GB15858@michelle.cdnetworks.com> References: <20100810213754.GH6960@michelle.cdnetworks.com> <20100811164318.GB15858@michelle.cdnetworks.com> Date: Wed, 11 Aug 2010 10:05:20 -0700 Message-ID: From: Jack Vogel To: pyunyh@gmail.com Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-net@freebsd.org, Victor Ophof Subject: Re: "RX ring hdr initialization error" 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: Wed, 11 Aug 2010 17:05:25 -0000 Why would you set the ring size so large? On a home system you should be fine with 1024 or even 512. If you have a panic on boot reconfigure the kernel so em is not static, then load it as a module after boot and tune it that way, once you have it tweaked you can make it static again if you wish. Jack On Wed, Aug 11, 2010 at 9:43 AM, Pyun YongHyeon wrote: > On Wed, Aug 11, 2010 at 10:19:11AM +0200, Victor Ophof wrote: > > > > > > > > From: pyunyh@gmail.com > > Date: Tue, 10 Aug 2010 14:37:54 -0700 > > To: mr4hughz@hotmail.com > > CC: jfv@freebsd.org; freebsd-net@freebsd.org > > Subject: Re: "RX ring hdr initialization error" > > > > On Tue, Aug 10, 2010 at 12:52:56PM +0200, Victor Ophof wrote: > > > > > > > > > > > > > > > Hi > > > > > > I've bought a asus M4a78-EM Motherboard. to build a NAS on, > > > thinking the onboard Realtek would be sufficant speed > > > unfortunatly the onboard fives 16/31 mbs at best > > > > > > ps later It improved with enabeling "polling" in the kernel (duh) > > > > > > so I had a PCI intel GT nic around, what gave intermittent tcp/ip > connections in a other machine (ESXi) > > > unfortunatly this was the same with Freebsd (card issue?) The card is > still in the machine > > > even with the Intel supplied BSD driver > > > > > > now I bought a PCIe intel CT nic, put it in and the kernel panic with > > > "RX ring hdr initialization error" > > > so replaced the intel with the freebsd one by doing > > > intel overwrites the freebsd one /boot/kernel/if_em.ko > > > # cd /usr/src/sys/modules/em/ && make obj depend all install > > > (was already in the kernel) > > > > > > > > > still panic > > > anybody got some idea's howto fix ? > > > > > --- reaction pyunyh --- > > I have been using the attached patch for em(4)/igb(4) controllers. > > These drivers explicitly calls panic(9) when memory allocation > > failure happens. I don't think it's good idea to panic the box > > under resource shortage condition as it's common to see this > > situation on heavily loaded servers. > > > > The patch does not solve the one issue yet. The panic caused by > > RX buffer allocation failure condition which in turn means you're > > allocating a lot of buffers. Reduce number of descriptors if you > > increased that too high and see whether the issue could be gone. > > ---/reaction pyunyh ---What buffers /descriptors I need to reduce? I have > 2gb ram and set the following in /boot/loader.conf vm.kmem_size_max="1024m" > > The loader tunables are hw.em.txd and hw.em.rxd. I thought you > increased TX/RX descriptor size to large value(e.g. 4096). > > > vm.kmem_size="1024m" > > #vfs.zfs.prefetch_disable=1 > > vm.kmem_size="2048M" > > vfs.zfs.arc_min="1024M" > > vfs.zfs.arc_max="1536M" > > vfs.zfs.vdev.min_pending=2 > > vfs.zfs.vdev.max_pending=8 > > vfs.zfs.txg.timeout=5 > > aio_load="YES" > > ahci_load="YES" > > > > I guess zfs consumed a lot of memory such that em(4) was not able > to allocate RX buffers. It seems there is nothing can be done in > this case unless some memory is reclaimed from zfs. I'm not > familiar with zfs internals but others can comment on this. > > However the patch should fix the panic under these resource > shortage situation. > _______________________________________________ > 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" >