From: "Jörg Rödel" <joro@8bytes.org>
To: Udo van den Heuvel <udovdh@xs4all.nl>
Cc: Borislav Petkov <bp@alien8.de>, linux-kernel@vger.kernel.org
Subject: Re: 3.6.11 AMD-Vi: Completion-Wait loop timed out
Date: Sun, 20 Jan 2013 12:40:11 +0100 [thread overview]
Message-ID: <20130120114011.GN25591@8bytes.org> (raw)
In-Reply-To: <50FBD413.1000406@xs4all.nl>
On Sun, Jan 20, 2013 at 12:25:07PM +0100, Udo van den Heuvel wrote:
> Hello Jörg,
>
> Hardware issue? What is wrong c.q. happening?
I think it falls under Erratum 455 (which does not mention IOMMU
specifically). Point is, there is a hardware workaround for this to make
the IOMMU work, but your BIOS does not enable it.
>
> I have this:
>
> # dmesg|grep IOMMU
> [ 0.000000] ACPI: IVRS 000000009dd12420 00070 (v02 AMD AMDIOMMU
> 00000001 AMD 00000000)
> [ 0.000000] Please enable the IOMMU option in the BIOS setup
> [ 1.125636] AMD-Vi: Found IOMMU at 0000:00:00.2 cap 0x40
>
> So kernel says I have no IOMMU but still one is found? (!?)
The "Please enable IOMMU ..." line tells you about the GART, not the AMD
IOMMU. This is a frequent source of confusion, we probably should remove
that line. Trinity has no GART, so there is nothing to find :)
> In PC-BIOS I assume?
> I did not yet find an option, but this is the first occurrence.
> Can the BIOS vendor fix this? If so: please explain so I cna contact
> Gigabyte (motherboard manufacturer)
Yes, the BIOS vendor can fix this issue. They need to disable NB clock
gating for the IOMMU.
> What is the impact of disabling the IOMMU?
Well, it has some security impact and if you have more than 4GB of RAM
maybe also some slight performance impact due to DMA bounce buffering.
But thats still better as a system that stops working after some time.
Joerg
next prev parent reply other threads:[~2013-01-20 11:40 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 [this message]
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
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=20130120114011.GN25591@8bytes.org \
--to=joro@8bytes.org \
--cc=bp@alien8.de \
--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