Chris Wedgwood <[email protected]> writes: > right now i'm thinking if we can't figure out which cpu/bios > combinations are safe we might almost be better off doing iommu=soft > for *all* k8 stuff except for those that are whitelisted; though this > seems extremely drastic Do you (someone) have (maintain) a list of affected systems, including motherboard type and possibly version, BIOS version and CPU type? A similar list of unaffected systems with 4GB+ RAM could be useful, too. I'm afraid with default iommu=soft it will be a mystery forever. -- Krzysztof Halasa - 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?!
- From: Robert Hancock <[email protected]>
- Re: data corruption with nvidia chipsets and IDE/SATA drives (k8 cpu errata needed?)
- From: Chris Wedgwood <[email protected]>
- Re: data corruption with nvidia chipsets and IDE/SATA drives // memory hole mapping related bug?!
- Prev by Date: Re: [linux-usb-devel] 2.6.20-rc5: BUG: lock held at task exit time! (pm_mutex){--..}, at: [<c013bfff>] enter_state+0x3f/0x170
- Next by Date: Re: data corruption with nvidia chipsets and IDE/SATA drives (k8 cpu errata needed?)
- Previous by thread: Re: data corruption with nvidia chipsets and IDE/SATA drives (k8 cpu errata needed?)
- Next by thread: Re: data corruption with nvidia chipsets and IDE/SATA drives (k8 cpu errata needed?)
- Index(es):
 |