Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755505AbXIDRHJ (ORCPT ); Tue, 4 Sep 2007 13:07:09 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752160AbXIDRG6 (ORCPT ); Tue, 4 Sep 2007 13:06:58 -0400 Received: from netops-testserver-3-out.sgi.com ([192.48.171.28]:34295 "EHLO relay.sgi.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751701AbXIDRG5 (ORCPT ); Tue, 4 Sep 2007 13:06:57 -0400 Date: Tue, 4 Sep 2007 09:58:34 -0700 (PDT) From: Christoph Lameter X-X-Sender: clameter@schroedinger.engr.sgi.com To: Marco Berizzi cc: linux-kernel@vger.kernel.org, David Chinner , xfs@oss.sgi.com, mel@skynet.ie Subject: Re: kernel BUG at mm/slab.c:2980 (was Re: [] xfs_bmap_search_multi_extents+0x6f/0xe0) In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1385 Lines: 38 On Tue, 4 Sep 2007, Marco Berizzi wrote: > After a week uptime I got this error. I hope it > will be useful for you. Yes indeed but this is a different type of failure. Looks like a higher allocation failure in the networking code. Someone created objects that required an order 2 allocations that failed. > SLUB: Genslabs=22, HWalign=32, Order=0-1, MinObjects=4, CPUs=1, Nodes=1 Slub is restricted to order 0 and 1 allocs. > PREFETCH window: e5c00000-e7cfffff > NET: Registered protocol family 2 > IP route cache hash table entries: 2048 (order: 1, 8192 bytes) > TCP established hash table entries: 8192 (order: 4, 65536 bytes) > TCP bind hash table entries: 8192 (order: 3, 32768 bytes) Hmmmm. > eth2: setting full-duplex. > swapper: page allocation failure. order:2, mode:0x4020 > [] __alloc_pages+0x1ed/0x2e0 > [] allocate_slab+0x4b/0x90 > [] new_slab+0x32/0x150 > [] __slab_alloc+0xcb/0x120 > [] __slab_alloc+0x79/0x120 > [] tcp_collapse+0x113/0x3b0 tcp_collapse? This is due to a network configuration that required an order 2 kmalloc block. Jumbo frames? - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/