From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Ramifications of memtest86
Date: Fri, 12 Feb 2010 08:27:01 -0600 [thread overview]
Message-ID: <4B756535.3050404@gmail.com> (raw)
In-Reply-To: <20100212132335.GC1422@muc.de>
chrome://messenger/locale/messengercompose/composeMsgs.properties:
> Hi, Dale,
>
> On Fri, Feb 12, 2010 at 06:43:46AM -0600, Dale wrote:
>
>> chrome://messenger/locale/messengercompose/composeMsgs.properties:
>>
>>> On Fri, Feb 12, 2010 at 11:22:21AM +0000, Alan Mackenzie wrote:
>>>
>
>
>>>> 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?
>>>
>
>
>> Sounds to me like the mobo may have issues. If swapping the ram around
>> doesn't move the error, then the chips on the mobo that connect to the
>> ram may be bad.
>>
> So the RAM sticks are each 32 bits wide, then?
>
I run 32 bit here. Mine doesn't care where they are but yours may be
different.
>
>> I would still rule out power issues if you can. A bad power supply, or
>> a weak one, can cause some pretty weird problems.
>>
> The power supply is brand new, from a reputable manufacturer. Surely if
> the power supply were dicky, I'd get RAM errors in some other bit
> position inside a 32-bit word. Or maybe the RAM into which memtest86 is
> loaded is also faulty. ;-(
>
>
>> Dale
>>
>
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?
http://www.overclockers.com/forums/showthread.php?t=458204
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.
I would also check to see if it is a heat related issue. If it runs
fine cold, that could point to the "dust" theory since it is
consistently broke. If it only does it when hot, then that could be a
chip problem.
Again, lots of things it could be. So far, everybody has replied with
good ideas to check. There are lots of them.
Dale
:-) :-)
next prev parent reply other threads:[~2010-02-12 14:28 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 [this message]
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=4B756535.3050404@gmail.com \
--to=rdalek1967@gmail.com \
--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