From: "Rogério Brito" <rbrito@ime.usp.br>
To: Lennart Sorensen <lsorense@csclub.uwaterloo.ca>
Cc: Grant Coady <grant_lkml@dodo.com.au>, linux-kernel@vger.kernel.org
Subject: Re: Strange disk corruption with Linux >= 2.6.13
Date: Sat, 1 Oct 2005 18:28:06 -0300 [thread overview]
Message-ID: <20051001212806.GD6397@ime.usp.br> (raw)
In-Reply-To: <20050927140434.GL28578@csclub.uwaterloo.ca>
On Sep 27 2005, Lennart Sorensen wrote:
> 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.
Right now, I'm using just a single 512MB module, but it is single-sided
(I guess that by double-sided you guys mean that it has chips on both
sides of the module, right?). The only double-sided module that I have
here is the 256MB module.
OTOH, with just one 512MB everything *seems* to be working fine, but,
honestly, I'm not sure.
> It is also generally unstable if set to anything over PC100 memory speed
> in my experience (my machine has the same board).
Hummm, nice to see that you have also experienced this. With 256 + 128,
I had to use PC100 to have it work stably.
> 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'd obviously prefer to have everything working at PC133 speed, but
wouldn't mind running at PC100 speed if I could use everything, since I
sometimes need to use some large programs (for some dynamic programming
problems).
Thanks for sharing your experiences,
--
Rogério Brito : rbrito@ime.usp.br : http://www.ime.usp.br/~rbrito
Homepage of the algorithms package : http://algorithms.berlios.de
Homepage on freshmeat: http://freshmeat.net/projects/algorithms/
next prev parent reply other threads:[~2005-10-01 21:28 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-27 11:10 Strange disk corruption with Linux >= 2.6.13 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
2005-10-01 21:28 ` Rogério Brito [this message]
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=20051001212806.GD6397@ime.usp.br \
--to=rbrito@ime.usp.br \
--cc=grant_lkml@dodo.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=lsorense@csclub.uwaterloo.ca \
/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;
as well as URLs for NNTP newsgroup(s).