Ethernet Bridge development
 help / color / mirror / Atom feed
From: TC Hough <tchough@austin.rr.com>
To: bridge@lists.osdl.org
Subject: [Bridge] br: memory squeeze!
Date: Wed, 21 Apr 2004 12:00:07 -0500	[thread overview]
Message-ID: <4086A897.50305@austin.rr.com> (raw)

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.

I don't have a whole lot of memory on the bridge machine, but I feel 
like it should be sufficient, since bridging is all it ever does and I 
have plenty of swap space.  The system log doesn't should anything I 
thought to be abnormal.  The memory squeeze messages were not logged.  
Here's the output of /proc/meminfo:

        total:    used:    free:  shared: buffers:  cached:
Mem:  29655040 28917760   737280        0 13750272  6123520
Swap: 67104768   434176 66670592
MemTotal:        28960 kB
MemFree:           720 kB
MemShared:           0 kB
Buffers:         13428 kB
Cached:           5700 kB
SwapCached:        280 kB
Active:           4344 kB
Inactive:        18036 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:        28960 kB
LowFree:           720 kB
SwapTotal:       65532 kB
SwapFree:        65108 kB

Any suggestions?

TC


             reply	other threads:[~2004-04-21 17:00 UTC|newest]

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

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=4086A897.50305@austin.rr.com \
    --to=tchough@austin.rr.com \
    --cc=bridge@lists.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox