From: Alan Mackenzie <acm@muc.de>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Ramifications of memtest86
Date: Fri, 12 Feb 2010 12:43:30 +0000 [thread overview]
Message-ID: <20100212124330.GB1422@muc.de> (raw)
In-Reply-To: <20100212112221.GA1422@muc.de>
On Fri, Feb 12, 2010 at 11:22:21AM +0000, Alan Mackenzie wrote:
> On Fri, Feb 12, 2010 at 10:50:46AM +0200, Alan McKinnon wrote:
> > On Friday 12 February 2010 10:54:53 Alan Mackenzie wrote:
> > > Hi, Gentoo,
> > > My new Gentoo box has become unusably unstable.
> > > The first sign was when the compiler threw a segfault whilst
> > > emerging the xfce window manager. I "solved" this by emerging
> > > Openbox instead.
> > > Then I got another compiler segfault whilst emerging firefox (yes,
> > > I know there's a binary for this).
> > everything you mention below is indicative of failing hardware,
> > especially RAM closely followed by PSU.
> Yes, you're right. :-(
> When I run memtest86 from the gentoo boot disk, it signals millions of
> failures in b11 of 32 bit words.
> I'll try unplugging and replugging these.
No help. :-(
No matter how I plug in the RAM (4 combinations of 2 sticks into 2 pairs
of slots) it is always b11 which fails and always at an address ending
in (hex) 0 or 8.
How is this DDR3 Ram organised? Is each stick 64 bits wide, or are they
32 bits wide, being accessed by the motherboard pairwisely? If the
latter, I would have exected the failure to move to address ....4 and
....C when I swap the two sticks. Am I being prematurely pessimistic in
thinking the motherboard might be the fault?
> > alan dot mckinnon at gmail dot com
> --
> Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2010-02-12 12:36 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 ` Alan Mackenzie [this message]
2010-02-12 12:43 ` [gentoo-user] Ramifications of memtest86 Dale
2010-02-12 13:23 ` Alan Mackenzie
2010-02-12 14:27 ` Dale
2010-02-12 19:25 ` [gentoo-user] Ramifications of memtest86. Got it! Alan Mackenzie
2010-02-12 20:03 ` [gentoo-user] " 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=20100212124330.GB1422@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