public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Roger Heflin <rheflin@atipa.com>
To: Christoph Anton Mitterer <calestyo@scientia.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Strange write errors on FAT32 partition (maybe an FAT32 bug?!)
Date: Thu, 09 Nov 2006 14:54:32 -0600	[thread overview]
Message-ID: <45539588.7020504@atipa.com> (raw)
In-Reply-To: <45539366.7070809@scientia.net>


Christoph Anton Mitterer wrote:
> Roger Heflin wrote:
>> Christoph,
>>
>> Install then edac_mc module, and make sure  through the
>> sysctl command that pci parity checking is enabled.
>>
>> I have seen pci parity errors produce this sort of results,
>> ie make 100 identical 50MB files, and cksum them and one
>> will be wrong, do it a again, and the "wrong" one is now
>> right, but someone else is "wrong".
> Ah thx,... is it in the vanilla kernel?
> And do you know of any possible results that this issue has? When I just
> read data (see my original stuff with fat32) is it possible that this
> had been modified or damaged?
> Or are the only consequences that diff errors occur?
> 
> And what is responsible for that parity errors? Is it possible that any
> hardware is damaged?

The failure can manifest itself in many ways, I have
only seen it as a read failure, but there should be no
reason why it cannot also show as a write failure.

It should be in the later vanilla kernels, it won't
be in the earlier ones,  I would do a
find /lib/modules -name "*edac*" -ls

It is a hw issue, either something is running faster that
it should be (pci bus set to fast for the given hardware/config)
or something is broken.

                          Roger

  reply	other threads:[~2006-11-09 20:54 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-07 15:21 Strange write errors on FAT32 partition (maybe an FAT32 bug?!) Christoph Anton Mitterer
2006-11-07 18:55 ` OGAWA Hirofumi
2006-11-07 21:32   ` Christoph Anton Mitterer
2006-11-09 18:32   ` Christoph Anton Mitterer
     [not found]     ` <45539188.5080607@atipa.com>
2006-11-09 20:45       ` Christoph Anton Mitterer
2006-11-09 20:54         ` Roger Heflin [this message]
2006-11-09 20:59           ` Christoph Anton Mitterer
2006-11-09 21:02             ` Roger Heflin
2006-11-09 21:57               ` Christoph Anton Mitterer
2006-11-09 22:02                 ` Roger Heflin
2006-11-09 22:08                   ` Christoph Anton Mitterer
2006-11-09 22:14                     ` Roger Heflin
2006-11-09 22:24                       ` Christoph Anton Mitterer
2006-11-09 22:35                         ` Roger Heflin
2006-11-09 22:38                           ` Christoph Anton Mitterer
2006-11-09 22:42                             ` Roger Heflin
2006-11-10  0:45                               ` Christoph Anton Mitterer
2006-11-10 10:28                     ` Alan Cox
2006-11-11 16:01                       ` Christoph Anton Mitterer
2006-11-09 21:03             ` Roger Heflin
2006-11-09 21:11               ` Christoph Anton Mitterer
2006-11-09 22:23   ` Christoph Anton Mitterer
2006-11-10  1:49     ` OGAWA Hirofumi
2006-11-10  2:55       ` Christoph Anton Mitterer

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=45539588.7020504@atipa.com \
    --to=rheflin@atipa.com \
    --cc=calestyo@scientia.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