From: Boris Ostrovsky <boris.ostrovsky@amd.com>
To: Udo van den Heuvel <udovdh@xs4all.nl>
Cc: suravee.suthikulpanit@amd.com, "Jacob Shin" <jacob.shin@amd.com>,
"Borislav Petkov" <bp@alien8.de>, "Jörg Rödel" <joro@8bytes.org>,
linux-kernel@vger.kernel.org
Subject: Re: 3.6.11 AMD-Vi: Completion-Wait loop timed out
Date: Tue, 22 Jan 2013 11:12:25 -0500 [thread overview]
Message-ID: <50FEBA69.60106@amd.com> (raw)
In-Reply-To: <50FEAFEB.7020103@xs4all.nl>
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
next prev parent reply other threads:[~2013-01-22 16:12 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-20 10:33 3.6.11 AMD-Vi: Completion-Wait loop timed out Udo van den Heuvel
2013-01-20 10:36 ` Borislav Petkov
2013-01-20 10:40 ` Udo van den Heuvel
2013-01-20 11:19 ` Jörg Rödel
2013-01-20 11:25 ` Udo van den Heuvel
2013-01-20 11:40 ` Jörg Rödel
2013-01-20 11:48 ` Borislav Petkov
2013-01-20 11:50 ` Borislav Petkov
2013-01-20 11:59 ` Udo van den Heuvel
2013-01-20 12:24 ` Borislav Petkov
2013-01-20 11:52 ` Udo van den Heuvel
2013-01-20 11:57 ` Jörg Rödel
2013-01-21 13:09 ` Borislav Petkov
2013-01-21 14:10 ` Udo van den Heuvel
2013-01-21 14:55 ` Borislav Petkov
2013-01-21 15:10 ` Jörg Rödel
2013-01-21 15:32 ` Borislav Petkov
2013-01-21 15:34 ` Udo van den Heuvel
2013-04-21 1:03 ` Jake
2013-04-21 21:47 ` Borislav Petkov
2013-01-21 14:37 ` Boris Ostrovsky
2013-01-21 14:44 ` Udo van den Heuvel
2013-01-21 14:47 ` Jörg Rödel
2013-01-21 16:04 ` Jacob Shin
2013-01-21 22:35 ` Suravee Suthikulpanit
2013-01-22 3:22 ` Udo van den Heuvel
2013-01-22 14:13 ` Udo van den Heuvel
2013-01-22 14:36 ` Boris Ostrovsky
2013-01-22 15:16 ` Jörg Rödel
2013-01-22 15:27 ` Udo van den Heuvel
2013-01-22 16:12 ` Boris Ostrovsky [this message]
2013-01-22 16:29 ` Udo van den Heuvel
2013-01-22 23:29 ` Suravee Suthikulanit
2013-01-23 14:19 ` Udo van den Heuvel
2013-01-23 15:00 ` Suravee Suthikulpanit
2013-01-23 14:23 ` Udo van den Heuvel
2013-01-23 15:01 ` Suravee Suthikulpanit
2013-01-31 15:42 ` Udo van den Heuvel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=50FEBA69.60106@amd.com \
--to=boris.ostrovsky@amd.com \
--cc=bp@alien8.de \
--cc=jacob.shin@amd.com \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=suravee.suthikulpanit@amd.com \
--cc=udovdh@xs4all.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox