mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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: Sat, 1 Oct 2005 18:15:43 -0300	[thread overview]
Message-ID: <20051001211543.GB6397@ime.usp.br> (raw)
In-Reply-To: <Pine.LNX.4.60.0509272139220.18464@poirot.grange>

Hi, Guennadi.

On Sep 27 2005, Guennadi Liakhovetski wrote:
> Version B here. It first had only 128MB, worked fine, I added 256MB,
> system become unstable, memtest86 found "bad memory" around the last
> megabytes.

This is *quite* similar to what I am seeing.

> Then I bought 512MB, hoping to use it with 256MB - no way.

Again, similar to what I see.

> Every module alone works, but not together. But in my case memtest86
> did find errors.

This is something puzzling: when I first installed the modules to get
1.25GB, things "worked", but I had problems with memtest86+ (not
memtest86).

I changed things (removing modules), got frustrated having only 512MB on
the system with all the other modules laying around here and put them
back.

This second time, I reduced the latency on the BIOS from 2-2-2 to 3-3-3
and it booted and memtest86+ did't find any errors. Yet, I saw some
corruption, which was what prompted me to send the original mail to
linux-kernel (since I didn't know if it was a hardware or a software
problem, as memtest86+ had not found any errors).

> 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. :-(

I suspect that the system is stable now, but I am not sure. If I
reinstall some packages with apt, it still gets some problems with the
md5sum signatures of *other* packages, which is highly weird. But I
don't see any other problems.

Puzzling, huh? I already run a SMART offline/long self-test on the disk
(to rule out it being a problem) and it passed with flying colors. I
also already used badblocks on this very disk (but in read-only mode),
and it also didn't find any problems.

I have a Quantum FIREBALLlct15 drive here.


Thanks,

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

  parent reply	other threads:[~2005-10-01 21:15 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
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 [this message]
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=20051001211543.GB6397@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

Powered by JetHome