mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: lsorense@csclub.uwaterloo.ca (Lennart Sorensen)
To: Grant Coady <grant_lkml@dodo.com.au>
Cc: Rog?rio Brito <rbrito@ime.usp.br>, linux-kernel@vger.kernel.org
Subject: Re: Strange disk corruption with Linux >= 2.6.13
Date: Tue, 27 Sep 2005 10:04:34 -0400	[thread overview]
Message-ID: <20050927140434.GL28578@csclub.uwaterloo.ca> (raw)
In-Reply-To: <9ncij11fqb4l70qrhb0a8nri5moohnkaaf@4ax.com>

On Tue, Sep 27, 2005 at 09:57:52PM +1000, Grant Coady wrote:
> Probably not, I had a similar problem recently and for a test case 
> copied a .iso image file then compared it to original (cp + cmp), 
> turned out to be bad memory, and yes, memtest86 did not find the 
> problem.  Check mobo datasheet if 2+ double-sided memory allowed, 
> you may need to stay at 1GB to reduce bus loading.

The board is allowed 1.5GB using 3 x 512M.  I believe the 512M modules
must be double sided to work but I am not 100% sure of that.

It is also generally unstable if set to anything over PC100 memory speed
in my experience (my machine has the same board).  The memory speed
detection doesn't work properly.  I have found it perfectly stable when
set to PC100 in bios and using PC133 memory.  It seems to prefer having
the extra margin.

I have never personally had more than 2 x 256M on mine.

Len Sorensen

  parent reply	other threads:[~2005-09-27 14:04 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-27 11:10 Rogério Brito
2005-09-27 11:34 ` Diego Calleja
2005-09-27 11:58   ` Rogério Brito
2005-09-27 12:10     ` Rogério Brito
2005-09-27 11:57 ` Grant Coady
2005-09-27 12:43   ` Ondrej Zary
2005-10-01 21:22     ` Rogério Brito
2005-09-27 14:04   ` Lennart Sorensen [this message]
2005-10-01 21:28     ` Rogério Brito
2005-10-03 16:20       ` Lennart Sorensen
     [not found] ` <Pine.LNX.4.63.0509271331590.21130@alpha.polcom.net>
2005-09-27 12:20   ` Rogério Brito
2005-09-27 12:38     ` Grzegorz Kulewski
2005-09-27 19:42       ` Guennadi Liakhovetski
2005-09-27 21:01         ` Erik Mouw
2005-09-27 21:44           ` Guennadi Liakhovetski
2005-10-01 21:15         ` Rogério Brito
2005-10-08 22:35           ` Guennadi Liakhovetski
2005-10-09  9:30             ` Rogério Brito
2005-10-01 21:02       ` Rogério Brito
2005-09-27 23:31 ` Nigel Cunningham
2005-10-01 21:36   ` Rogério Brito
2005-10-02  0:06     ` Grant Coady
2005-10-03  4:17       ` Rogério Brito
2005-10-03  4:20         ` Willy Tarreau
2005-10-03  4:55     ` Nigel Cunningham
2005-10-04 10:28     ` Sander
2005-10-04 12:42       ` Nigel Cunningham
2005-09-28  8:43 ` Ville Herva
2005-09-28 23:23   ` Alan Cox
2005-09-29  6:29     ` Ville Herva
2005-09-29 16:14       ` Alan Cox
2005-10-03  5:05         ` Rogério Brito
2005-10-03  5:15   ` Rogério Brito
     [not found] <4RlFC-2ev-17@gated-at.bofh.it>
     [not found] ` <4Rxdq-2Tc-19@gated-at.bofh.it>
     [not found]   ` <4SXfs-7hM-27@gated-at.bofh.it>
2005-10-02  3:37     ` Bodo Eggert
2005-10-03  4:30       ` Rogério Brito

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=20050927140434.GL28578@csclub.uwaterloo.ca \
    --to=lsorense@csclub.uwaterloo.ca \
    --cc=grant_lkml@dodo.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rbrito@ime.usp.br \
    /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

all inboxes | Powered by JetHome®