RE: Out of memory + skbuff_head_cache

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Pradeep,

>Looks like a possible memory leak. Your interfaces suggest you are using Xen(?).
We are using OpenWrt on AP. 

>Did you add any code? If yes, check for memory leaks, 
I guess there may be leak in Bridge module associated with 2.6.21.5 kernel.

As when we attach the two interface with same bridge, only then we are facing this problem.

Say I have each port attached to there own bridge, and when I route traffic from one host to other, 
We will not face this behavior.


Any suggestion on how to debug/solve the problem.

Thanks,
Sharad.

 
-----Original Message-----
From: pradeep singh [mailto:pradeep.rautela@xxxxxxxxx] 
Sent: Tuesday, April 14, 2009 2:01 AM
To: Tekale Sharad-FHJN78
Cc: kernelnewbies@xxxxxxxxxxxx
Subject: Re: Out of memory + skbuff_head_cache

On Tue, Apr 14, 2009 at 8:37 AM, Tekale Sharad-FHJN78 <FHJN78@xxxxxxxxxxxx> wrote:
> Hi,
>
> I'm using linux 2.6.21.5 and our kernel is freeze.
>
> The problem I'm facing is, when I create a software bridge using 
> $brctl command. and add two interfaces say, eth0.0 and eth0.1, this way...
> $brctl addbr br-lan
> $brctl addif br-lan eth0.0
> $brctl addif br-lan eth0.1
>
> When I send traffic from a host connected to one port to host 
> connected at other at or above end 60Mbits/sec ,
>  soon all the memory is dried up/consumed and and system crashes.

Looks like a possible memory leak. Your interfaces suggest you are using Xen(?).
Did you add any code? If yes, check for memory leaks.

HTH
>
> Observation:
> On initial start up:
> $cat /proc/slabinfo | grep skbuff_head_cache skbuff_head_cache    120    
> 120    192   20    1 : tunables  120   60    0 :
> slabdata      6
>
> Before crash:
> $cat /proc/slabinfo | grep skbuff_head_cache skbuff_head_cache   4260   
> 4260    192   20    1 : tunables  120   60    0 :
> slabdata    213    213      0
> Can any one help me to refer to some patch or point to some location 
> in code from where memory is failed to deallocate.
>
> Thanks,
> Sharad.



--
Pradeep

--
To unsubscribe from this list: send an email with
"unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx
Please read the FAQ at http://kernelnewbies.org/FAQ



[Index of Archives]     [Newbies FAQ]     [Linux Kernel Mentors]     [Linux Kernel Development]     [IETF Annouce]     [Git]     [Networking]     [Security]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux SCSI]     [Linux ACPI]
  Powered by Linux