public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alan Mackenzie <acm@muc.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Ramifications of memtest86.  Got it!
Date: Fri, 12 Feb 2010 19:25:24 +0000	[thread overview]
Message-ID: <20100212192524.GC1560@muc.de> (raw)
In-Reply-To: <4B756535.3050404@gmail.com>

Hi, Dale,

On Fri, Feb 12, 2010 at 08:27:01AM -0600, Dale wrote:

> Where the error is could depend on a single transistor that is maybe
> not as sensitive as the others.  It's sort of like a chain.  It's only
> as strong as its weakest link.  It could be that whatever is going
> wrong could be right on the edge of others not working either.  The
> one that is failing is just the first if it is a power problem.
> That's where the power problem thought comes from.  Have you had a
> look here for well tested power supplies?

> That said, it could be a lot of things.  It could be a bad chip on the 
> mobo, a piece of dust in the wrong place or any number of other things.  
> It's finding it that is so much fun.

The shop who sold me the components suggested running memtest86 with
just one RAM stick at a time.  It turns out, one was duff, the other's
just fine.  (It went ~20 minutes on memtest86 without any errors.)  So
it looks like I'll be running on 2Gb only until I get a replacement for
the broken one.

> Again, lots of things it could be.  So far, everybody has replied with
> good ideas to check.  There are lots of them.

Many thanks to all who helped me track this one down!

> Dale

> :-)  :-)

-- 
Alan Mackenzie (Nuremberg, Germany).



  reply	other threads:[~2010-02-12 19:18 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-12  8:54 [gentoo-user] New Gentoo system has become unstable and unusable - help, please! Alan Mackenzie
2010-02-12  8:50 ` Alan McKinnon
2010-02-12  9:13   ` William Kenworthy
2010-02-12  9:46   ` Alan Mackenzie
2010-02-12  9:49     ` Helmut Jarausch
2010-02-12  9:56     ` Lewis Handy
2010-02-12  9:57     ` Daniel Wagener
2010-02-12 10:05     ` Roy Wright
2010-02-12 10:10     ` Roy Wright
2010-02-12 10:33     ` Alan McKinnon
2010-02-12 11:22   ` Alan Mackenzie
2010-02-12 12:43     ` [gentoo-user] Ramifications of memtest86 Alan Mackenzie
2010-02-12 12:43       ` Dale
2010-02-12 13:23         ` Alan Mackenzie
2010-02-12 14:27           ` Dale
2010-02-12 19:25             ` Alan Mackenzie [this message]
2010-02-12 20:03               ` [gentoo-user] Re: Ramifications of memtest86. Got it! Nikos Chantziaras
2010-02-12 23:27               ` [gentoo-user] " Dale
2010-02-13 17:43                 ` Alan Mackenzie
2010-02-13 22:46                   ` Volker Armin Hemmann
2010-02-14  0:08                   ` Dale
2010-02-14  0:13                     ` Volker Armin Hemmann
2010-02-14  5:46                   ` Alan McKinnon
2010-02-12 13:00       ` [gentoo-user] Ramifications of memtest86 Alan McKinnon
2010-02-12 12:56     ` [gentoo-user] New Gentoo system has become unstable and unusable - help, please! Volker Armin Hemmann
2010-02-12 19:20       ` Alan Mackenzie
2010-02-12 12:17 ` Mark Knecht
2010-02-12 12:33 ` Helmut Jarausch
2010-02-12 15:24   ` Paul Hartman
2010-02-12 16:35   ` Volker Armin Hemmann
2010-02-13  1:02     ` [gentoo-user] " walt
2010-02-13  1:10       ` Dale
2010-02-13  1:11       ` Volker Armin Hemmann

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=20100212192524.GC1560@muc.de \
    --to=acm@muc.de \
    --cc=gentoo-user@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