7091@xxxxxxxxxx wrote: > That indeed seems to have fixed the problem - I've been pulling my hair > out forever about this! > Is this something I'll need to leave in forever, is it supposed to get > fixed, etc.? > I'm going to continue doing testing and really try to thrash it tonight > (I just did the 'copy an ISO 5 times' test that always failed before - > it succeeds now). > Thanks for the help. I think fix is included during 2.6.22 devel cycle which basically is turning off IOMMU by default on the affected chipset but I haven't really followed after that. -- tejun - To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
