On Sun, Jan 20, 2013 at 11:40:20AM +0100, Udo van den Heuvel wrote:
> Hello,
>
> On 2013-01-20 11:36, Borislav Petkov wrote:
> > I know just the guy, CCed. :-)
>
> Thanks for the quick response!
> I found this similar case:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1073384
Yes, this is a Hardware issue for which the BIOS does not apply the
workaround. The only solution for now is to disable the IOMMU on the
Trinity based chips. Unfortunatly I don't have access to the hardware
any longer to write a workaround in the AMD IOMMU driver.
The question is what to do now, I tend to disable the IOMMU if a
Trinity chip is detected. This is not the first report of this problem
I encountered.
Regards,
Joerg
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
