From: ivan <ivan@es.usyd.edu.au>
To: linux-mm@kvack.org
Subject: Memory leak.
Date: Sun, 14 Apr 2002 14:29:46 +1000 (EST) [thread overview]
Message-ID: <Pine.LNX.4.33.0204141413150.18941-100000@dipole.es.usyd.edu.au> (raw)
Hi guy,
I am running 7.2RedHat kernel 2.4.9-31 from respect on Dell 4400 PowerEdge
Server. Dual CPU 990MHz.
The machine was a lemon from the start. We paid for it 16000$, to find out
that one controller and two SCSI disk were broken out of the box.
Then it kept crushing a couple time a months with clear logs. Dell
replaced mum and both CPUs. Still going down. Refused to replace RAM
( 4Gb) Asked me to test memory buy swapping chips around despite all my
explanations that this is a production server. I even wrote a little add
for Dell. Buy DELL and you in Hell
10 Days ago I installed DNS and DHCP servers from RedHat and noticed that
"top" shows that the amount of consumed memory is slowly and constantly
growing. Machine become unstable and a few users complained that their
files disappeared. ( we have good backup ). I re-booted 4 days ago and now
it looks it is doing it again.
Could you please advice how can I detect memory leaks.
Any help will be appreciated.
Thank you in advance,
Ivan.
--
================================================================================
Ivan Teliatnikov,
F05 David Edgeworth Building,
Department of Geology and Geophysics,
School of Geosciences,
University of Sydney, 2006
Australia
e-mail: ivan@es.usyd.edu.au
ph: 061-2-9351-2031 (w)
fax: 061-2-9351-0184 (w)
===============================================================================
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/
reply other threads:[~2002-04-14 4:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=Pine.LNX.4.33.0204141413150.18941-100000@dipole.es.usyd.edu.au \
--to=ivan@es.usyd.edu.au \
--cc=linux-mm@kvack.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