From: Matthias Andree <matthias.andree@stud.uni-dortmund.de>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.4.18-pre9
Date: Sun, 10 Feb 2002 12:21:06 +0100 [thread overview]
Message-ID: <20020210112106.GA14779@merlin.emma.line.org> (raw)
In-Reply-To: <3C662264.9090207@telia.com.suse.lists.linux.kernel> <p738za122to.fsf@oldwotan.suse.de> <3C662896.4030303@telia.com>
In-Reply-To: <3C662896.4030303@telia.com>
On Sun, 10 Feb 2002, Pawel Worach wrote:
> This system has been running linux for about 2 years without any problem
> at all, the hardware configuration has not changed one bit so i have a
> hard time beliving this is hardware. booted back into -pre7 and
> everything worked fine.
At Dortmund University, one of the machines I look after had a rock
solid configuration, good board (UP), no-name memory (256 MB PC-100
DIMM) and it was rock solid for almost a year, and all of a sudden,
without even being touched, it started to mess things up have processes
crash, wind itself up, uppercaps some characters and so on, corrupt its
file systems with e2fsck and so on.
Memtest86 quickly turned up that some memory line was faulty.
Regretfully, at the time that DIMM was bought, only 6 months warranty
were obligatory in Germany, so bad luck :-(
Consequence: don't buy memory which doesn't come with extended
guarantees.
So, get memtest86 onto floppy with a different computer and check the
memory of that box that crashed before claiming it's not the hardware.
(Sure, memtest86 will only find some memory problems, but still, it's
useful.)
--
Matthias Andree
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety." Benjamin Franklin
next prev parent reply other threads:[~2002-02-10 11:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3C662264.9090207@telia.com.suse.lists.linux.kernel>
2002-02-10 7:50 ` 2.4.18-pre9 Andi Kleen
2002-02-10 8:00 ` 2.4.18-pre9 Pawel Worach
2002-02-10 11:21 ` Matthias Andree [this message]
2002-02-10 7:33 2.4.18-pre9 Pawel Worach
2002-02-10 7:50 ` 2.4.18-pre9 Andrew Morton
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=20020210112106.GA14779@merlin.emma.line.org \
--to=matthias.andree@stud.uni-dortmund.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®