From: Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>
To: Udo van den Heuvel <udovdh@xs4all.nl>
Cc: "Boris Ostrovsky" <boris.ostrovsky@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: Wed, 23 Jan 2013 09:00:03 -0600 [thread overview]
Message-ID: <50FFFAF3.7030107@amd.com> (raw)
In-Reply-To: <50FFF15E.7010403@xs4all.nl>
On 1/23/2013 8:19 AM, Udo van den Heuvel wrote:
> On 2013-01-23 00:29, Suravee Suthikulanit wrote:
>> I sent out a patch
>> (http://marc.info/?l=linux-kernel&m=135889686523524&w=2) which should
>> implement
>> the workaround for AMD processor family15h model 10-1Fh erratum 746 in
>> the IOMMU driver.
>> In your case, the output from "setpci -s 00:00.02 F4.w" is "0050" which
>> tells me that BIOS doesn't
>> implement the work around. After patching, you should see the following
>> message in "dmesg".
>>
>> "AMD-Vi: Applying erratum 746 for IOMMU at 0000:00:00.2"
> Thanks!
> I'll check for that after these messages.
>
>> The following patch slightly modify
>> the code to always issue "COMPLETION_WAIT" after every command. This
>> should help increasing the chance of reproducing
>> the issue.
> Should I test with these two patches together?
> Or should I apply the first one first and then see what the second can help?
Please try the first one first. If the issue doesn't reproduce, you can
use the second patch to try to trigger it.
Thank you,
Suravee
>
>
> Kind regards,
> Udo
>
next prev parent reply other threads:[~2013-01-23 15:00 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
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 [this message]
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=50FFFAF3.7030107@amd.com \
--to=suravee.suthikulpanit@amd.com \
--cc=boris.ostrovsky@amd.com \
--cc=bp@alien8.de \
--cc=jacob.shin@amd.com \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.org \
--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