public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Scott Myron <samyron@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: Kevin <gentoo-dev@gnosys.biz>
Subject: Re: [gentoo-dev] memtest86 fails? (was Re: [gentoo-dev] Major MCE problem with SMP on Gentoo kernels)
Date: Wed, 12 May 2004 12:18:49 -0500	[thread overview]
Message-ID: <40A25C79.2010405@gentoo.org> (raw)
In-Reply-To: <20040512165939.GA12831@kroah.com>



Greg KH wrote:
> On Wed, May 12, 2004 at 12:22:15PM -0400, Kevin wrote:
> 
>>Any thoughts on this?
> 

You may also want to try removing all but one stick of memory, and rerun 
memtest. If that fails, replace that with another stick of memory, and 
rerun the test again. This will help you find out which stick of memory 
is bad. If you only have one stick of memory, borrow some from a friend, 
if possible...

You might also want to try testing your memory in a friend's machine, to 
verify the results. It's possible that there is a problem with the 
traces on the motherboard from the northbridge to the memory 
slots(unlikely, but possible).

Scott

--
gentoo-dev@gentoo.org mailing list


  reply	other threads:[~2004-05-12 17:17 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-11 18:07 [gentoo-dev] Major MCE problem with SMP on Gentoo kernels Kevin
2004-05-11 18:46 ` Greg KH
2004-05-11 18:55   ` Kevin
2004-05-11 19:04     ` Greg KH
2004-05-11 19:38       ` Kevin
2004-05-11 20:54         ` Chris Gianelloni
2004-05-11 21:31           ` Kevin
2004-05-11 19:38     ` Paul de Vrieze
2004-05-11 21:37       ` Kevin
2004-05-12  1:02         ` Georgi Georgiev
2004-05-12 10:23           ` [gentoo-dev] [OT] SuSE kernel on gentoo system (Was: Re: Major MCE problem with SMP on Gentoo kernels) sf
2004-05-12  2:42 ` [gentoo-dev] Major MCE problem with SMP on Gentoo kernels Josh Glover
2004-05-12  9:31   ` Dan Podeanu
2004-05-12 11:26     ` Kevin
2004-05-12 11:24   ` Kevin
2004-05-12 11:48     ` Josh Glover
2004-05-12 12:14       ` Ciaran McCreesh
2004-05-12 13:58       ` Kevin
2004-05-12 14:44         ` Chris Gianelloni
2004-05-12 15:17         ` tom_gall
2004-05-13 11:06           ` Kevin
2004-05-13 11:12             ` Senor Rodgman
2004-05-13 13:04             ` Chris Gianelloni
2004-05-13 15:04             ` Daniel Drake
2004-05-13 15:54             ` Greg KH
2004-05-18  8:29               ` Kevin
2004-05-18 10:59                 ` Alexander Futasz
2004-05-18 12:02                 ` Josh Glover
2004-05-19 17:48                   ` Kevin
2004-05-20 12:19                     ` [gentoo-dev] SOLVED: " Kevin
2004-05-20 21:16                     ` Kevin
2004-05-20 21:32                       ` Greg KH
2004-05-20 23:08                       ` Robin H. Johnson
2004-05-20 23:16                         ` Hasse Hagen Johansen
2004-05-21  2:46                           ` Kevin
2004-05-21 13:05                       ` Chris Gianelloni
2004-05-18 12:46                 ` [gentoo-dev] " Daniel Drake
     [not found]         ` <40A23987.9080104@gentoo.org>
2004-05-12 16:22           ` [gentoo-dev] memtest86 fails? (was Re: [gentoo-dev] Major MCE problem with SMP on Gentoo kernels) Kevin
2004-05-12 16:59             ` Greg KH
2004-05-12 17:18               ` Scott Myron [this message]
2004-05-12 17:15             ` Sven Vermeulen

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=40A25C79.2010405@gentoo.org \
    --to=samyron@gentoo.org \
    --cc=gentoo-dev@gnosys.biz \
    --cc=gentoo-dev@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