From: Kyle Liddell <kyle@foobox.homelinux.net>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] Incipient hardware failure?
Date: Tue, 05 Jul 2005 23:31:17 -0500 [thread overview]
Message-ID: <1120624277.23834.3.camel@athlon> (raw)
In-Reply-To: <42CA5774.9060907@gotadsl.co.uk>
Here's just an idea: You took out half your RAM, and then more recently
you tested the other half of the RAM that you left in the computer? How
about you swap the RAM around and run memtest86+ or some such. Perhaps
some of the RAM you took out of your system is bad, and you've got a
corrupted file or something lying around? I had this happen on my old
server...had very occasional weird errors, but worked enough to compile
a stage1 install, then when the RAM completely died and things went nuts
I checked it with memtest86 and found that a stick was bad, dumped it,
but still had strange crashes every once in a while. Completely
reinstalling (switching to debian actually) stopped the problems.
On Tue, 2005-07-05 at 10:48 +0100, Peter Humphrey wrote:
> Recently I've been seeing some strange events. First was random hangs of
> the whole system; this began as summer approached, and I fixed it by
> taking out half the RAM pro tem.
>
> Then, in the last week or so I've been getting random compilation
> errors, so I ran memtest86 for a few hours with no errors. Today I got a
--
gentoo-amd64@gentoo.org mailing list
next parent reply other threads:[~2005-07-06 4:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <42CA5774.9060907@gotadsl.co.uk>
2005-07-06 4:31 ` Kyle Liddell [this message]
2005-07-06 8:41 ` [gentoo-amd64] Incipient hardware failure? Peter Humphrey
2005-07-08 15:59 ` Peter Humphrey
2005-07-09 1:10 ` [gentoo-amd64] " Duncan
2005-07-09 8:27 ` Peter Humphrey
2005-07-09 8:49 ` Peter Humphrey
[not found] ` <42CA5930.7010508@tiscali.fr>
[not found] ` <42CA667E.7060701@gotadsl.co.uk>
[not found] ` <pan.2005.07.05.13.21.52.33248@cox.net>
[not found] ` <42CA9646.5060200@gotadsl.co.uk>
[not found] ` <pan.2005.07.05.16.33.27.506035@cox.net>
[not found] ` <42CABC63.7060007@gotadsl.co.uk>
[not found] ` <20050705182345.GA3876@crud.crud.mn.org>
[not found] ` <42CAE7B0.3050002@gotadsl.co.uk>
[not found] ` <20050705214000.GA25907@crud.crud.mn.org>
2005-07-05 22:40 ` [gentoo-amd64] " Peter Humphrey
[not found] ` <42CA9F34.1030305@gotadsl.co.uk>
[not found] ` <20050705155357.GA12533@jaa.iki.fi>
2005-07-06 2:19 ` [gentoo-amd64] PCI Wireless Cards with 64bit support and drivers Terry Ellis
2005-07-06 3:40 ` Benny Pedersen
2005-07-06 4:11 ` Terry Ellis
2005-07-06 7:22 ` Peter Humphrey
2005-07-06 10:39 ` [gentoo-amd64] " Duncan
2005-07-06 14:47 ` [gentoo-amd64] " Terry Ellis
2005-07-06 17:05 ` [gentoo-amd64] " Duncan
2005-07-13 9:42 ` [gentoo-amd64] Re: Incipient hardware failure? Peter Humphrey
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=1120624277.23834.3.camel@athlon \
--to=kyle@foobox.homelinux.net \
--cc=gentoo-amd64@lists.gentoo.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