On Wed, 5 Sep 2007, Marco Berizzi wrote: > > tcp_collapse? This is due to a network configuration that required an > > order 2 kmalloc block. Jumbo frames? > > I don't use jumbo frames. Hardware is > very old (celeron with 3com 3c905). Something must be doing allocations that requires between 8k and 16k that SLUB cannot satisfy from order 0 or order 1 allocations. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- References:
- Re: kernel BUG at mm/slab.c:2980 (was Re: [<c019c63f>] xfs_bmap_search_multi_extents+0x6f/0xe0)
- From: "Marco Berizzi" <[email protected]>
- Re: kernel BUG at mm/slab.c:2980 (was Re: [<c019c63f>] xfs_bmap_search_multi_extents+0x6f/0xe0)
- From: Christoph Lameter <[email protected]>
- Re: kernel BUG at mm/slab.c:2980 (was Re: [<c019c63f>] xfs_bmap_search_multi_extents+0x6f/0xe0)
- From: "Marco Berizzi" <[email protected]>
- Re: kernel BUG at mm/slab.c:2980 (was Re: [<c019c63f>] xfs_bmap_search_multi_extents+0x6f/0xe0)
- From: Christoph Lameter <[email protected]>
- Re: kernel BUG at mm/slab.c:2980 (was Re: [<c019c63f>] xfs_bmap_search_multi_extents+0x6f/0xe0)
- From: "Marco Berizzi" <[email protected]>
- Re: kernel BUG at mm/slab.c:2980 (was Re: [<c019c63f>] xfs_bmap_search_multi_extents+0x6f/0xe0)
- Prev by Date: Re: [pre-2.6.23 REGRESSION] 2.6.23-rc3-git1 crash/stuck on VIA CN700 system
- Next by Date: Re: building a specific in-tree module is currently a bit broken
- Previous by thread: Re: kernel BUG at mm/slab.c:2980 (was Re: [<c019c63f>] xfs_bmap_search_multi_extents+0x6f/0xe0)
- Next by thread: Re: kernel BUG at mm/slab.c:2980 (was Re: [<c019c63f>] xfs_bmap_search_multi_extents+0x6f/0xe0)
- Index(es):
 |