From: "Rogério Brito" <rbrito@ime.usp.br>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: Grzegorz Kulewski <kangur@polcom.net>, linux-kernel@vger.kernel.org
Subject: Re: Strange disk corruption with Linux >= 2.6.13
Date: Sun, 9 Oct 2005 06:30:00 -0300 [thread overview]
Message-ID: <20051009093000.GA4907@ime.usp.br> (raw)
In-Reply-To: <Pine.LNX.4.60.0510090031550.16544@poirot.grange>
Hi, Guennadi.
On Oct 09 2005, Guennadi Liakhovetski wrote:
> Sorry, was away for a week.
No problems. I've been quite busy also.
> On Sat, 1 Oct 2005, [iso-8859-1] Rog?rio Brito wrote:
>
> > > Try removing the 256MB module?...
> >
> > Right now, I'm only using one 512MB module, but after I have already
> > paid for the second one, and it wasn't cheap. :-(
>
> Wasn't it 512 + 512 + 256 MB modules that you had?
Exactly, but I didn't manage to get the 2x512MB modules useable in my
machine. In fact, sometimes the machine wouldn't even POST with the two
modules, but as soon as I removed any one of them, the machine was back
to normal.
> I just suggested removing only one 256MB module and testing with 2 x
> 512MB. Which on the one hand wouldn't be that bad as only having
> 512MB, and on the other hand just for a test...
Right now, I am using 512 + 256 running at PC100 speeds, with latencies
all set to 3-3-3. Now, it seems to run stably, but is slower than what I
would like it to run, of course.
I will still keep trying some combinations, but some of them seem
definitely ruled out (like having both 512 MB modules at the same time).
Thank you very much for your comments, Rogério Brito.
--
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-09 9:30 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
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 [this message]
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=20051009093000.GA4907@ime.usp.br \
--to=rbrito@ime.usp.br \
--cc=g.liakhovetski@gmx.de \
--cc=kangur@polcom.net \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).