From: Marc Haber <mh+linux-kernel@zugschlus.de>
To: linux-kernel@vger.kernel.org
Subject: ethernet-ATM-Router freezing
Date: Sat, 22 Feb 2003 09:49:58 +0100 [thread overview]
Message-ID: <20030222084958.GC23827@torres.ka0.zugschlus.de> (raw)
Hi,
we use Linux to terminate ATM PVCs and to move the traffic coming in
on the ATM link to Ethernet. We have two parallel machines with
identical hardware (about two years old), in a Debian GNU/Linux setup
built in November 2002. Current kernel is 2.4.20-ac1, and the setup
hasn't been touched since December 2002. One of the machines does the
work, while the other is waiting to be activated in case of failure.
Max load is about 6 Mbit, the machines are mostly idle. At least I
won't call them loaded.
A few days ago, the "active" machine has started spontaneously
freezing. The freezes don't happen at times with especially high or
low load, they don't happan during the same time of day. The freezes
are complete:
- no network respose on the ATM link
- no network response on the Ethernet link
- no response at all on the system console
- no error or panic messages on the console
- no response to Magic SysRq
- atsar doesn't show any strange patterns in CPU/memory usage
- syslog doesn't show anything strange
- mrtg doesn't show anything strange in network load
Reset button is needed to revive the frozen box.
These freezes occur on the machine actually doing the work. If I move
the work to the other box, the freezes go with the work. Thus, I am
pretty confident that this is not faulty hardware. I don't believe
either that this is a incompatibility of the kernel since the systems
in question have been working in this software configuration for two
months before the problems started.
Are there any known problems in the current ATM code that might cause
these freezes? Any other kernel versions I could try?
I am currently thinking about splitting the load between both boxes,
and downgrading one of them to a 2.4.19 or 2.4.18 kernel, and
upgrading the other one to a 2.4.21pre kernel. Have there been any
relevant changes to the ATM code recently?
Any hints will be appreciated. Thanks!
Cheers
Marc
--
-----------------------------------------------------------------------------
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Karlsruhe, Germany | lose things." Winona Ryder | Fon: *49 721 966 32 15
Nordisch by Nature | How to make an American Quilt | Fax: *49 721 966 31 29
next reply other threads:[~2003-02-22 8:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-22 8:49 Marc Haber [this message]
2003-02-22 10:34 ` romieu
2003-02-22 11:25 ` Marc Haber
2003-02-22 11:59 ` romieu
2003-02-22 13:15 ` Marc Haber
2003-02-22 11:48 ` Benjamin Herrenschmidt
2003-02-22 13:07 ` Marc Haber
2003-02-22 16:33 ` Doug McNaught
2003-02-22 19:14 ` Marc Haber
2003-02-23 9:59 ` Benjamin Herrenschmidt
2003-06-08 10:38 ` stability issues with 2.4.20-ac1 (was: ethernet-ATM-Router freezing) Marc Haber
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=20030222084958.GC23827@torres.ka0.zugschlus.de \
--to=mh+linux-kernel@zugschlus.de \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®