All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ondrej Zary <linux@rainbow-software.org>
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 14:43:34 +0200	[thread overview]
Message-ID: <43393E76.2050008@rainbow-software.org> (raw)
In-Reply-To: <9ncij11fqb4l70qrhb0a8nri5moohnkaaf@4ax.com>

Grant Coady wrote:
> On Tue, 27 Sep 2005 08:10:39 -0300, Rogério Brito <rbrito@ime.usp.br> wrote:
> 
> 
>>Hi there. I'm seeing a really strange problem on my system lately and I
>>am not really sure that it has anything to do with the kernels.
> 
> 
> 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.

I work a lot with hardware any my experience is that memtest is not very 
good at detecting errors. I have a Socket 7 board somewhere with bad L2 
cache - it was unstable but memtest was unable to find anything. 
However, GoldMemory found some errors - they disappeared after disabling 
L2 cache and crashes disappeared too. It's not free but at least 
shareware - you can find it at http://www.goldmemory.cz/ The older 
version (IIRC 5.07) was better, I had problems with some of the newer 
ones on perfectly OK hardware (when the test should start, it rebooted 
instead).

-- 
Ondrej Zary

  reply	other threads:[~2005-09-27 12:43 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 [this message]
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
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=43393E76.2050008@rainbow-software.org \
    --to=linux@rainbow-software.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.