From: Pete Zaitcev <zaitcev@redhat.com>
To: "Gregory K. Ruiz-Ade" <gregory@castandcrew.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: system lockup issues w/ 2.4.19
Date: Wed, 5 Mar 2003 18:42:38 -0500 [thread overview]
Message-ID: <200303052342.h25Ngcs26177@devserv.devel.redhat.com> (raw)
In-Reply-To: <mailman.1046898841.30893.linux-kernel2news@redhat.com>
> About once a month or so (not very regular), one or the other of our Dell
> PowerEdge servers goes catatonic. Examining the system in this state, it
> seems to exhibit the symptoms of a full process table, in that no new
> processes can be started at all.
It is essential that you explained how you did the examining,
with relevant shell traces/snapshots, etc. If they are too
long, upload them somewhere. And use of stock kernels goes
without saying, or you have to go to your vendor (SuSE).
-- Pete
next parent reply other threads:[~2003-03-05 23:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1046898841.30893.linux-kernel2news@redhat.com>
2003-03-05 23:42 ` Pete Zaitcev [this message]
[not found] <13694.1047106361@ocs3.intra.ocs.com.au>
2003-03-10 18:12 ` system lockup issues w/ 2.4.19 Gregory K. Ruiz-Ade
2003-03-05 21:10 Gregory K. Ruiz-Ade
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=200303052342.h25Ngcs26177@devserv.devel.redhat.com \
--to=zaitcev@redhat.com \
--cc=gregory@castandcrew.com \
--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