LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: andersen@codepoet.org
Cc: Chris Wedgwood <cw@f00f.org>,
Christoph Anton Mitterer <calestyo@scientia.net>,
Robert Hancock <hancockr@shaw.ca>,
linux-kernel@vger.kernel.org, knweiss@gmx.de, krader@us.ibm.com,
lfriedman@nvidia.com, linux-nforce-bugs@nvidia.com
Subject: Re: data corruption with nvidia chipsets and IDE/SATA drives (k8 cpu errata needed?)
Date: Fri, 19 Jan 2007 10:23:15 +1100 [thread overview]
Message-ID: <200701191023.15929.ak@suse.de> (raw)
In-Reply-To: <20070118110028.GA22407@codepoet.org>
On Thursday 18 January 2007 22:00, Erik Andersen wrote:
> I just tried again and while using iommu=soft does avoid the
> corruption problem, as with previous kernels with 2.6.20-rc5
> using iommu=soft still makes my pcHDTV HD5500 DVB cards not work.
This must be some separate bug and needs to be fixed anyways.
-Andi
next prev parent reply other threads:[~2007-01-18 23:24 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.E9jVXDLMKzMZNCbslzUxjMhsInE@ifi.uio.no>
2007-01-03 23:41 ` data corruption with nvidia chipsets and IDE/SATA drives // memory hole mapping related bug?! 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-01-16 18:01 ` data corruption with nvidia chipsets and IDE/SATA drives (k8 cpu errata needed?) Chris Wedgwood
2007-01-16 19:52 ` Christoph Anton Mitterer
2007-01-16 20:31 ` Chris Wedgwood
2007-01-16 21:29 ` Andi Kleen
2007-01-17 1:17 ` Christoph Anton Mitterer
2007-01-17 14:48 ` Chip Coldwell
2007-01-17 19:46 ` Chip Coldwell
2007-01-17 22:15 ` Andi Kleen
2007-01-18 21:57 ` Chip Coldwell
2007-01-18 22:49 ` Andi Kleen
2007-01-18 9:29 ` joachim
2007-01-18 14:34 ` Christoph Anton Mitterer
2007-01-18 16:42 ` Chris Wedgwood
2007-01-18 11:00 ` Erik Andersen
2007-01-18 14:43 ` Christoph Anton Mitterer
2007-01-18 16:36 ` Chris Wedgwood
2007-01-18 23:23 ` Andi Kleen [this message]
2007-02-21 17:03 ` Chip Coldwell
2007-01-16 21:54 ` Allen Martin
2007-01-17 1:12 ` Christoph Anton Mitterer
2007-01-16 20:16 ` Arkadiusz Miskiewicz
2007-01-16 20:21 ` Christoph Anton Mitterer
2007-01-16 20:31 ` Krzysztof Halasa
2007-01-16 20:35 ` Chris Wedgwood
2007-03-22 12:32 ` data corruption with nvidia chipsets and IDE/SATA drives // memory hole mapping related bug?! Christoph Anton Mitterer
[not found] <fa.Tb2r8Il/2H8l9dhmsGAAQB2WEZg@ifi.uio.no>
[not found] ` <fa.MydhQJqKsehLS9lIc2JSZC8Q77A@ifi.uio.no>
[not found] ` <fa.M9SCVAz1qZ6vrR9HTrRb95KdBSY@ifi.uio.no>
[not found] ` <fa.5WKg4jbSxjbUXedux14VStNyV+8@ifi.uio.no>
[not found] ` <fa.lphwLNvMksoBFaqfqCzMG1UVhsA@ifi.uio.no>
2007-03-05 6:25 ` data corruption with nvidia chipsets and IDE/SATA drives (k8 cpu errata needed?) Robert Hancock
2007-03-12 13:06 ` Andi Kleen
2007-03-12 14:56 ` Jeff Garzik
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=200701191023.15929.ak@suse.de \
--to=ak@suse.de \
--cc=andersen@codepoet.org \
--cc=calestyo@scientia.net \
--cc=cw@f00f.org \
--cc=hancockr@shaw.ca \
--cc=knweiss@gmx.de \
--cc=krader@us.ibm.com \
--cc=lfriedman@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nforce-bugs@nvidia.com \
/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;
as well as URLs for NNTP newsgroup(s).