From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Jon Nelson" Subject: Re: Stack Trace. Bad? Date: Wed, 7 Nov 2007 07:55:46 -0600 Message-ID: References: <20071107104900.GB14732@2ka.mipt.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: netdev@vger.kernel.org To: unlisted-recipients:; (no To-header on input) Return-path: Received: from ug-out-1314.google.com ([66.249.92.171]:43171 "EHLO ug-out-1314.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754254AbXKGNzs (ORCPT ); Wed, 7 Nov 2007 08:55:48 -0500 Received: by ug-out-1314.google.com with SMTP id z38so121600ugc for ; Wed, 07 Nov 2007 05:55:47 -0800 (PST) In-Reply-To: <20071107104900.GB14732@2ka.mipt.ru> Content-Disposition: inline Sender: netdev-owner@vger.kernel.org List-Id: netdev.vger.kernel.org On 11/7/07, Evgeniy Polyakov wrote: > Hi Jon. > > On Tue, Nov 06, 2007 at 02:23:03PM -0600, Jon Nelson (jnelson@jamponi.net) wrote: > > I was testing some network throughput today and ran into this. > > I should note that I've this motherboard has 2x MCP55 Ethernet and one > > of them works fine and the other one gives lots and lots of frame > > errors under load. > > > > The following is only an harmless informational message. > > Unless you get a _continuous_flood_ of these messages it means > > everything is working fine. Allocations from irqs cannot be > > perfectly reliable and the kernel is designed to handle that. > > md0_raid5: page allocation failure. order:2, mode:0x20 > > > > Call Trace: > > [] __alloc_pages+0x324/0x33d > > [] kmem_getpages+0x66/0x116 > > [] fallback_alloc+0x104/0x174 > > [] kmem_cache_alloc_node+0x9c/0xa8 > > [] __alloc_skb+0x65/0x138 > > [] :forcedeth:nv_alloc_rx_optimized+0x4d/0x18f > > What MTU for this card is? Forcedeth supports jumbo frames, but does it > in very unoptimized way, particulary by relying on the possibility to > allocate 2-order pages, which is wrong. > > So, set MTU to 1500 and things will be back into good shape. > I think adding fragments support is not a short-term solution because > of closed specs. The NIC is configured to use a 1500 byte MTU. -- Jon