Re: kernel BUG at mm/slab.c:2980 (was Re: [] xfs_bmap_search_multi_extents+0x6f/0xe0)

2007-09-05 Thread Marco Berizzi
Christoph Lameter wrote: > 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

Re: kernel BUG at mm/slab.c:2980 (was Re: [] xfs_bmap_search_multi_extents+0x6f/0xe0)

2007-09-05 Thread Christoph Lameter
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

Re: kernel BUG at mm/slab.c:2980 (was Re: [] xfs_bmap_search_multi_extents+0x6f/0xe0)

2007-09-05 Thread Marco Berizzi
"Christoph Lameter" wrote: > 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

Re: kernel BUG at mm/slab.c:2980 (was Re: [] xfs_bmap_search_multi_extents+0x6f/0xe0)

2007-09-04 Thread Christoph Lameter
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

Re: kernel BUG at mm/slab.c:2980 (was Re: [] xfs_bmap_search_multi_extents+0x6f/0xe0)

2007-09-04 Thread Marco Berizzi
Christoph Lameter wrote: > Could you try this with the SLUB allocator and then boot with > "slub_debug"? Hi Christoph, I have upgraded to 2.6.22.5 and I have selected the SLUB. I have also added append=slub_debug to lilo.conf After a week uptime I got this error. I hope it will be useful for

Re: kernel BUG at mm/slab.c:2980 (was Re: [] xfs_bmap_search_multi_extents+0x6f/0xe0)

2007-08-03 Thread Christoph Lameter
Could you try this with the SLUB allocator and then boot with "slub_debug"? - 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

Re: kernel BUG at mm/slab.c:2980 (was Re: [] xfs_bmap_search_multi_extents+0x6f/0xe0)

2007-08-03 Thread Marco Berizzi
Marco Berizzi wrote: > Marco Berizzi wrote: > > > Hello everybody. > > I'm running linux 2.6.22 on Slackware. > > This box is running openswan 2.4.9 > > and squid 2.6S13 > > I get tons of these messages: > > > > Jul 20 01:17:09 Gemini kernel: msnt_auth S 0 8356 > 819 > > (NOTLB)

kernel BUG at mm/slab.c:2980 (was Re: [] xfs_bmap_search_multi_extents+0x6f/0xe0)

2007-08-02 Thread Marco Berizzi
Marco Berizzi wrote: > Hello everybody. > I'm running linux 2.6.22 on Slackware. > This box is running openswan 2.4.9 > and squid 2.6S13 > I get tons of these messages: > > Jul 20 01:17:09 Gemini kernel: msnt_auth S 0 8356 819 > (NOTLB) > Jul 20 01:17:09 Gemini kernel: