All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: bridge@lists.osdl.org
Subject: Re: [Bridge] br: memory squeeze!
Date: Mon, 26 Apr 2004 09:20:28 -0700	[thread overview]
Message-ID: <408D36CC.10903@candelatech.com> (raw)
In-Reply-To: <20040426085941.0cb17f53@dell_ss3.pdx.osdl.net>

Stephen Hemminger wrote:
> On Wed, 21 Apr 2004 12:00:07 -0500
> TC Hough <tchough@austin.rr.com> wrote:
> 
> 
>>I set up a bridge for my network and I'm having some trouble.  At first 
>>everything worked great, but after about 3 days of continuous bridging, 
>>my bridge machine died.  Approximately once a second, the message: "br: 
>>memory squeeze!" would appear on the console.  Keyboard input was mostly 
>>frozen, as well.  I could switch virtual consoles, but I couldn't type.  
>>No traffic would pass through the bridge.  When I rebooted, everything 
>>seemed fine.
> 
> 
> 
> You have a memory leak in the kernel. What kernel and distro are you
> using.  Also, what kind of NIC's and other interfaces (tun, ppp, etc).
> 
> Also, what is the state of the bridge?	br showstp br0
> and the forwarding table?	br showmacs br0

I agree it is probably a memory leak, but it is *possible* to get this
error if you just run out of available memory.  I have been able to
reproduce this type of error by setting my send/receive packet socket
buffers very high and then flooding 200 connections with traffic, for example.
(I had a 256MB RAM machine)

You might want to make sure that your netdev-backlog settings are not too
big, for example.

Thanks,
Ben

-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com


      reply	other threads:[~2004-04-26 16:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-21 17:00 [Bridge] br: memory squeeze! TC Hough
2004-04-26 15:59 ` Stephen Hemminger
2004-04-26 16:20   ` Ben Greear [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=408D36CC.10903@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=bridge@lists.osdl.org \
    --cc=shemminger@osdl.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.