From: Joerg Roedel <joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
To: AceLan Kao <acelan.kao-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org>
Cc: iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
Subject: Re: Any side effect if turn off amd_iommu
Date: Wed, 25 Mar 2015 15:04:10 +0100 [thread overview]
Message-ID: <20150325140410.GS4441@8bytes.org> (raw)
In-Reply-To: <CAFv23QmxQ3vJnMEGN0TNR3vLAx1MN7ptB0y3QQLKciqfT3OBsQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On Wed, Mar 25, 2015 at 11:30:20AM +0800, AceLan Kao wrote:
> We have some AMD machines(AMD cpu and graphics) that need to set
> amd_iommu=off to work.
> Some of them have wifi issue that it can't connect to any AP(no
> interrupt)(can set noapic to workaround it, too),
> and some of them have graphics issues.
> The only workaround we found is to set amd_iommu=off, and it fixes both issues.
>
> I have 2 questions.
> 1. What kind of these issues would be, are they a driver issue or a
> BIOS issue? If it's a BIOS issue, what we should tell the BIOS
> engineers, so that they know how to fix it?
> 2. Some of the machines may not have the chance to get a BIOS update,
> do you think it's okay to add a quirk in amd_iommu driver to blacklist
> out those machines? Are there any side effects if we do so?
Hard to tell what the issue is. Can you please boot the affected machine
with AMD IOMMU enabled and amd_iommu_dump on the command line and send
me dmesg of the machine after boot?
Thanks,
Joerg
next prev parent reply other threads:[~2015-03-25 14:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-25 3:30 Any side effect if turn off amd_iommu AceLan Kao
[not found] ` <CAFv23QmxQ3vJnMEGN0TNR3vLAx1MN7ptB0y3QQLKciqfT3OBsQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-03-25 14:04 ` Joerg Roedel [this message]
[not found] ` <20150325140410.GS4441-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
2015-03-26 2:26 ` AceLan Kao
[not found] ` <CAFv23Qn93z4pE6RtURgoiBADpgCWZ6gfpMPn3akfJibudRi+Qg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-03-26 12:05 ` Joerg Roedel
[not found] ` <20150326120547.GU4441-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
2015-03-27 0:48 ` AceLan Kao
[not found] ` <CAFv23QnUO+w0EXUx8DtgPx0W=fz37_R04EW6P-g+PF_y_U1dfA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-03-30 16:09 ` Joerg Roedel
[not found] ` <20150330160910.GZ4441-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
2015-03-31 0:30 ` AceLan Kao
[not found] ` <CAFv23QmOjFb9NgLY0aW55OpQSecFA83jNOU1TY7o3qWuft1_Cw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-04-23 2:15 ` AceLan Kao
[not found] ` <CAFv23Q==+tXTif9uQfyTHE28hxGt80WYS=A6qN7q0Q4q7re6kw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-05-04 2:27 ` AceLan Kao
2015-05-04 11:08 ` Joerg Roedel
[not found] ` <20150504110802.GE15736-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
2015-05-05 7:30 ` AceLan Kao
[not found] ` <CAFv23QkRouVJ6siu==-EjLndP2Z7inz+qVeKxLci3=R=9r8+zQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-05-05 15:13 ` Joerg Roedel
[not found] ` <20150505151319.GO15736-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
2015-05-13 7:37 ` AceLan Kao
[not found] ` <CAFv23Q=iU7X1EOcZDUh6NhcnuvyyNSKUGEot6ZhCg8uZ7kRNAQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-05-13 13:44 ` Joerg Roedel
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=20150325140410.GS4441@8bytes.org \
--to=joro-zlv9swrftaidnm+yrofe0a@public.gmane.org \
--cc=acelan.kao-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org \
--cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
/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