public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sergey Vlasov <vsu@altlinux.ru>
To: Christoph Anton Mitterer <calestyo@scientia.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: unexplainable read errors, copy/diff-issue
Date: Fri, 10 Nov 2006 13:56:49 +0300	[thread overview]
Message-ID: <20061110135649.16cccca0.vsu@altlinux.ru> (raw)
In-Reply-To: <4553DD90.1090604@scientia.net>

[-- Attachment #1: Type: text/plain, Size: 2061 bytes --]

On Fri, 10 Nov 2006 03:01:52 +0100 Christoph Anton Mitterer wrote:

> The original post may be found under:
> http://marc.theaimsgroup.com/?t=116291314500001&r=1&w=2
>
> First of all my software/hardware data:
> CPU: 2x DualCore Opteron 275
> Mainboard: Tyan Thunder K8WE (S2895)
> Chipsets: Nvidia nForce professional 2200, Nvidia nForce professional
> 2050, AMD 8131
> Memory: Kingston ValueRAM 4x 1GB Registered ECC
> Harddisks: 1x PATA IBM/Hitachi, 2x SATA IBM/Hitachi
> Additional Devices/Drives: Plextor PX760A DVD/CD, TerraTec Aureon 7.1
> Universe soundcard, Hauppage Nova 500T DualDVB-T card.
> Distribution: Debian sid
> Kernel: self-compiled 2.6.18.2 (see below for .config) with applied EDAC
> patches
>
> The system should be cooled enough so I don't think that this comes from
> overheating issues. Nothing is overclocked.
>
> Ok the problem is the following:
> I copy large amounts of data (>15GB in several files each about 80MB,
> but it happens even for smaller amounts so size does not seem to be
> related) from one location to another.
> Then I diff the two locations.
> There are differences found!!!
> When I do diff again I find again differences but mostly in other files
> (so not always in the same place).
> Sometimes there are not differences (but this is rare as I'm testing
> with > 15GB)

So you have 4GB RAM, and most likely some memory is remapped above the
4GB address boundary.  Could you show the full dmesg output after boot?

Other things you can try:

 - Boot with mem=3072M (or some larger value which is still less than
   the amount of RAM below the 4GB boundary - the exact value could be
   found from the dmesg output) and check whether you can reproduce the
   corruption in this configuration.

 - Look in the BIOS setup for memory remapping options (Google indicates
   that it may be called "Hammer Configuration/Memory Hole Mapping" on
   this board).  Maybe you need to try different values (AFAIR there
   were some complaints about unstabilities with software remapping;
   cannot find the exact page now).

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2006-11-10 10:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-10  2:01 unexplainable read errors, copy/diff-issue Christoph Anton Mitterer
2006-11-10 10:56 ` Sergey Vlasov [this message]
2006-11-11 16:35   ` Christoph Anton Mitterer
2006-11-12 20:44   ` Christoph Anton Mitterer
2006-11-12 23:32   ` Christoph Anton Mitterer
     [not found]     ` <20061113000120.09fd6174@localhost.localdomain>
2006-11-13 20:59       ` Christoph Anton Mitterer
2006-11-13  3:23   ` Christoph Anton Mitterer
2006-11-24 11:11   ` 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=20061110135649.16cccca0.vsu@altlinux.ru \
    --to=vsu@altlinux.ru \
    --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