Re: kernel BUG in __cache_alloc_node at linux-2.6.git/mm/slab.c:3177!

From: Christoph Lameter
Date: Mon Oct 16 2006 - 15:25:40 EST


On Mon, 16 Oct 2006, Will Schmidt wrote:

> Node 1 MemTotal: 327680 kB
> Node 1 MemFree: 435704 kB

Too big.

> Node 1 MemUsed: 18446744073709443592 kB

Memused is going negative?

> Node 1 Active: 41412 kB
> Node 1 Inactive: 19976 kB
> Node 1 HighTotal: 0 kB
> Node 1 HighFree: 0 kB
> Node 1 LowTotal: 327680 kB
> Node 1 LowFree: 435704 kB
> Node 1 Dirty: 0 kB
> Node 1 Writeback: 0 kB
> Node 1 Mapped: 0 kB
> Node 1 Slab: 0 kB

zero slab??? That cannot be. The slab allocator always allocs on each
node. Or is this <2.6.18 with the strange counters that we had before?


> Node 0 MemTotal: 229376 kB
> Node 0 MemFree: 0 kB
> Node 0 MemUsed: 229376 kB

Node 0 is filled up during bootup?

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/