linux-kernel - Re: 3.6.11 AMD-Vi: Completion-Wait loop timed out

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 22 Jan 2013 11:12:25 -0500
From:	Boris Ostrovsky <boris.ostrovsky@....com>
To:	Udo van den Heuvel <udovdh@...all.nl>
CC:	<suravee.suthikulpanit@....com>, Jacob Shin <jacob.shin@....com>,
	Borislav Petkov <bp@...en8.de>,
	Jörg Rödel <joro@...tes.org>,
	<linux-kernel@...r.kernel.org>
Subject: Re: 3.6.11  AMD-Vi: Completion-Wait loop timed out



On 01/22/2013 10:27 AM, Udo van den Heuvel wrote:
> On 2013-01-22 15:36, Boris Ostrovsky wrote:
>>> Gigabyte demonstrate that using ESX 5i IOMMU works fine. (with pictures
>>> attached).
>>
>> There are no attachments to your message.
>
> Correct, gigabyte did send them via their support web-interface.
> Do yo uneed to see them? They just show IOMMU enabled or similar.

No, I thought you ran this yourself.

>
>>> What can we bring against that?
>>
>> How reproducible is the problem that you are seeing?
>
> Seen once over here. Correlated with raid-check.

Then the answer from Gigabyte doesn't prove anything. You can also boot 
Linux without seeing this problem in most cases.

Your BIOS does not have the required erratum workaround. We will provide 
a patch to close that hole but since the problem is not easily 
reproducible (and the erratum is also not easy to trigger) it may be 
difficult to say whether it really helped with your problem.

-boris

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/