From: Erik Andersen <andersen@codepoet.org>
To: Karsten Weiss <K.Weiss@science-computing.de>
Cc: Christoph Anton Mitterer <calestyo@scientia.net>,
linux-kernel@vger.kernel.org, Chris Wedgwood <cw@f00f.org>
Subject: Re: data corruption with nvidia chipsets and IDE/SATA drives // memory hole mapping related bug?!
Date: Wed, 13 Dec 2006 12:53:05 -0700 [thread overview]
Message-ID: <20061213195305.GA3358@codepoet.org> (raw)
In-Reply-To: <Pine.LNX.4.61.0612111001240.23470@palpatine.science-computing.de>
On Mon Dec 11, 2006 at 10:24:02AM +0100, Karsten Weiss wrote:
> Last week we did some more testing with the following result:
>
> We could not reproduce the data corruption anymore if we boot the machines
> with the kernel parameter "iommu=soft" i.e. if we use software bounce
> buffering instead of the hw-iommu. (As mentioned before, booting with
> mem=2g works fine, too, because this disables the iommu altogether.)
>
> I.e. on these systems the data corruption only happens if the hw-iommu
> (PCI-GART) of the Opteron CPUs is in use.
>
> Christoph, Erik, Chris: I would appreciate if you would test and hopefully
> confirm this workaround, too.
What did you set the BIOS to when testing this setting?
Memory Hole enabled? IOMMU enabled?
-Erik
--
Erik B. Andersen http://codepoet-consulting.com/
--This message was written using 73% post-consumer electrons--
next prev parent reply other threads:[~2006-12-13 20:16 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.64.0612021202000.2981@addx.localnet>
2006-12-11 9:24 ` data corruption with nvidia chipsets and IDE/SATA drives // memory hole mapping related bug?! Karsten Weiss
2006-12-12 6:18 ` amd64 iommu causing corruption? (was Re: data corruption with nvidia chipsets and IDE/SATA drives // memory hole mapping related bug?!) Chris Wedgwood
2006-12-13 19:18 ` data corruption with nvidia chipsets and IDE/SATA drives // memory hole mapping related bug?! Christoph Anton Mitterer
2006-12-13 19:53 ` Chris Wedgwood
2006-12-13 20:34 ` Karsten Weiss
2006-12-14 9:22 ` Muli Ben-Yehuda
2006-12-14 11:38 ` [PATCH] " Karsten Weiss
2006-12-14 11:56 ` Muli Ben-Yehuda
2006-12-14 13:16 ` [PATCH 2nd try] " Karsten Weiss
2006-12-14 18:10 ` Muli Ben-Yehuda
2006-12-23 2:04 ` Christoph Anton Mitterer
2006-12-23 2:56 ` John A Chaves
2006-12-23 3:26 ` Christoph Anton Mitterer
2006-12-13 19:20 ` Christoph Anton Mitterer
2006-12-13 19:54 ` Chris Wedgwood
2006-12-13 19:57 ` Christoph Anton Mitterer
2006-12-13 22:39 ` Lennart Sorensen
2006-12-13 23:00 ` Christoph Anton Mitterer
2006-12-13 19:53 ` Erik Andersen [this message]
2006-12-13 19:59 ` Karsten Weiss
2006-12-13 20:02 ` Christoph Anton Mitterer
2006-12-13 20:29 ` Erik Andersen
2006-12-13 20:32 ` Christoph Anton Mitterer
2006-12-13 23:33 ` Christoph Anton Mitterer
2006-12-14 9:24 ` Muli Ben-Yehuda
2006-12-14 19:23 ` Christoph Anton Mitterer
2006-12-14 9:23 ` Muli Ben-Yehuda
2006-12-14 9:52 ` Erik Andersen
2006-12-14 9:56 ` Muli Ben-Yehuda
2007-01-03 15:02 ` Christoph Anton Mitterer
2007-01-04 13:04 ` Christoph Anton Mitterer
2007-03-22 14:48 Dan Halbert
[not found] <fa.E9jVXDLMKzMZNCbslzUxjMhsInE@ifi.uio.no>
2007-01-03 23:41 ` Robert Hancock
2007-01-15 22:56 ` Christoph Anton Mitterer
2007-01-15 23:05 ` Christoph Anton Mitterer
2007-01-16 0:23 ` Robert Hancock
2007-01-16 13:54 ` Christoph Anton Mitterer
2007-01-16 14:26 ` Robert Hancock
2007-03-22 12:32 ` Christoph Anton Mitterer
-- strict thread matches above, loose matches on Subject: below --
2006-12-15 15:57 Paul Slootman
2006-12-02 0:56 Christoph Anton Mitterer
2006-12-02 1:15 ` Erik Andersen
2006-12-02 1:28 ` Christoph Anton Mitterer
2006-12-02 5:17 ` Chris Wedgwood
2006-12-02 12:10 ` Christoph Anton Mitterer
[not found] ` <20061202111644.GF9995@vianova.fi>
2006-12-08 2:16 ` Christoph Anton Mitterer
2006-12-02 11:00 ` Karsten Weiss
2006-12-02 11:37 ` Alan
2006-12-02 11:39 ` Christoph Anton Mitterer
2006-12-13 18:52 ` Christoph Anton Mitterer
2006-12-13 19:56 ` Karsten Weiss
2006-12-13 20:11 ` Christoph Anton Mitterer
2006-12-14 9:34 ` Chris Wedgwood
2007-01-15 22:26 ` Christoph Anton Mitterer
2006-12-14 23:39 ` Dax Kelson
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=20061213195305.GA3358@codepoet.org \
--to=andersen@codepoet.org \
--cc=K.Weiss@science-computing.de \
--cc=calestyo@scientia.net \
--cc=cw@f00f.org \
--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