From: Ted Deppner <ted@psyber.com>
To: Travis Shirk <travis@pobox.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Kernel Locking Up
Date: Wed, 22 Aug 2001 16:54:45 -0700 [thread overview]
Message-ID: <20010822165444.A25085@dondra.ofc.psyber.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0108220938390.1152-100000@puddy.travisshirk.net>
In-Reply-To: <Pine.LNX.4.33.0108220938390.1152-100000@puddy.travisshirk.net>
On Wed, Aug 22, 2001 at 09:46:14AM -0600, Travis Shirk wrote:
> Ever since I upgraded to the 2.4.x (currently running 2.4.8)
> kernels, my machine has been locking up every other day
> or so. Does anyone have any hints/tips for figuring out
> what is going on.
As another data point, I've had similar problems with one machine (the
heaviest utilized), but none others. I'm running about 20 2.4.x machines,
in various uses (I work for an ISP).
Kernels 2.4.6 through 2.4.7, and even a 2.4.7-ac8 I tried for good
measure.
The one running on a Dell PowerEdge 2450, dual P3-750s, 512mb ram, Mylex
ExcelRaid 2000, Intel EEPRO100, running a qmail setup transiting 20 to 40k
messages per day regularly locks up every 3 to 8 days. No dmesg, no error
logs, no oops, nothing on the console.
The death spiral didn't seem triggered by any particular thing, and
logged in ssh terminals were the still slightly usable for 2 to 5 commands
but then they'd stop working.
2.4.8 hasn't had any problems so far in 5 days, but I'm not holding my
breath too tightly.
The ONLY similarity in the death throws has been what looks like physical
cable or network card interrupt problems. The packets in my ssh session
seem to block until I hit enter 5 to 10 times, then I get a burst of
traffic. I've been able to do some simple commands in this situation, but
nothing complex.
ifconfig eth0 has shown millions of various errors (carrier, collisions),
and hundreds of thousands of them between typing the command in twice.
The Cisco 6000 series switch on the other side of the cable shows no such
errors.
--
Ted Deppner
http://www.psyber.com/~ted/
next prev parent reply other threads:[~2001-08-22 23:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-22 15:46 Travis Shirk
2001-08-22 15:51 ` Tim Waugh
2001-08-22 15:52 ` Admin Mailing Lists
2001-08-22 16:11 ` Tim Walberg
2001-08-22 16:01 ` Tim Walberg
2001-08-22 17:23 ` Alan Cox
2001-08-22 17:33 ` Tim Walberg
2001-08-22 22:23 ` Kevin Krieser
2001-08-22 21:46 ` Travis Shirk
2001-08-22 23:54 ` Ted Deppner [this message]
2001-08-23 1:01 ` Ben Greear
2001-08-23 2:27 ` Keith Owens
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=20010822165444.A25085@dondra.ofc.psyber.com \
--to=ted@psyber.com \
--cc=linux-kernel@vger.kernel.org \
--cc=travis@pobox.com \
/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®