linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Rogério Brito" <rbrito@ime.usp.br>
To: Grant Coady <grant_lkml@dodo.com.au>
Cc: Nigel Cunningham <ncunningham@cyclades.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Strange disk corruption with Linux >= 2.6.13
Date: Mon, 3 Oct 2005 01:17:19 -0300	[thread overview]
Message-ID: <20051003041719.GA5576@ime.usp.br> (raw)
In-Reply-To: <oh8uj15lvipg3bshv7j82j27j11l67ds49@4ax.com>

Hi, Grant, Nigel and others following this thread.

On Oct 02 2005, Grant Coady wrote:
> On Sat, 1 Oct 2005 18:36:55 -0300, Rogério Brito <rbrito@ime.usp.br> wrote:
> >I removed what was extracted right away and tried again to extract
> >the tree (at this point, suspecting even that something in software
> >had problems). The problem with bzip2 occurred again. Then, I
> >rebooted the system an the problem magically went away.
> 
> This rings a bell, recently I reported a problem:
>   http://www.uwsg.iu.edu/hypermail/linux/kernel/0508.1/1332.html

Thanks for the information. I am on-and-off experimenting with
goldmemory and memtester86+ to see if I can find something with more
than 512MB that is stable.

I am, right now, using 512MB + 256MB slowed down to PC100 speeds. It
seems to be stable with this configuration (having survived some memory
tests, the decoding of lots of FLAC files in a row and using the machine
as usual---with low consumption things like mutt and browsing with
lynx).

> Turned out to be bad memory stick :o)

The thing is that any stick alone doesn't seem to generate a problem.
Only when they are used simultaneously

I will test it more to see what may be wrong with my setup. :-( I still
have not isolated and understood the problem completely. :-(


Thanks for the feedback, Rogério.

-- 
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/

  reply	other threads:[~2005-10-03  4:17 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
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 [this message]
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=20051003041719.GA5576@ime.usp.br \
    --to=rbrito@ime.usp.br \
    --cc=grant_lkml@dodo.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ncunningham@cyclades.com \
    /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).