Christoph Anton Mitterer wrote:
Ok,.. that sounds reasonable,.. so the whole thing might (!) actually be a hardware design error,... but we just don't use that hardware any longer when accessing devices via sata_nv. So this doesn't solve our problem with PATA drives or other devices (although we had until now no reports of errors with other devices) and we have to stick with iommu=soft. If one use iommu=soft the sata_nv will continue to use the new code for the ADMA, right?
Right, that shouldn't affect it. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- References:
- Re: data corruption with nvidia chipsets and IDE/SATA drives // memory hole mapping related bug?!
- From: Robert Hancock <[email protected]>
- Re: data corruption with nvidia chipsets and IDE/SATA drives // memory hole mapping related bug?!
- From: Christoph Anton Mitterer <[email protected]>
- Re: data corruption with nvidia chipsets and IDE/SATA drives // memory hole mapping related bug?!
- From: Christoph Anton Mitterer <[email protected]>
- Re: data corruption with nvidia chipsets and IDE/SATA drives // memory hole mapping related bug?!
- From: Robert Hancock <[email protected]>
- Re: data corruption with nvidia chipsets and IDE/SATA drives // memory hole mapping related bug?!
- From: Christoph Anton Mitterer <[email protected]>
- Re: data corruption with nvidia chipsets and IDE/SATA drives // memory hole mapping related bug?!
- Prev by Date: Re: 2.6.20-rc5: usb mouse breaks suspend to ram
- Next by Date: [PATCH -mm] uts namespace : remove CONFIG_UTS_NS
- Previous by thread: Re: data corruption with nvidia chipsets and IDE/SATA drives // memory hole mapping related bug?!
- Next by thread: Re: data corruption with nvidia chipsets and IDE/SATA drives (k8 cpu errata needed?)
- Index(es):
 |