From: Alex Williamson <alex.williamson@redhat.com>
To: Jason Newton <nevion@gmail.com>
Cc: linux-wireless@vger.kernel.org, iommu <iommu@lists.linux-foundation.org>
Subject: Re: ath9k and AMD IOMMU alias breakage on 3.16?
Date: Fri, 05 Sep 2014 22:01:44 -0600 [thread overview]
Message-ID: <1409976104.2982.56.camel@ul30vt.home> (raw)
In-Reply-To: <CAGou9MhCmRajqfh91rxbBUr9PBvJxo7U=g9p4Onp0pJk4BwBnA@mail.gmail.com>
On Fri, 2014-09-05 at 20:00 -0700, Jason Newton wrote:
> Hi,
>
> I have an AR9462 connected over minipcie, it came with the ASRock
> FM2A88x-itx motherboard and I'm using an AMD A10-7850K cpu with it. When I
> have IOMMU enabled, and this is desirable for opencl related things, the
> AR9462 malfunctions with these two errors occurring:
>
> AMD-Vi: Event logged [INVALID_DEVICE_REQUEST device=00:00.1
> address=0x000000fdf8080020 flags=0x0a00]
>
> Followed by this looping error, which reoccurs shortly after associating
> and obtaining an IP. I've attached a large snippet from dmesg, due to it's
> length.
>
> I'm not sure where the error is coming from but I did see that Alex
> Williamson posted a patch that dealt with aliased devices (like pci
> bridges) and AMD's IOMMU issues, see
> e028a9e6b8a637af09ac4114083280df4a7045f1 for reference.
>
> I then disable IOMMU in the bios, and immediately the ath9k/AR9462 pair is
> working without flaw or retries. Bios is up to date btw, updated it after
> building the machine last friday.
>
> So anyone have a clue what's going on here?
Please boot with "amd_iommu_dump" on the kernel boot line and send the
full dmesg log and 'sudo lspci -vvv' output. Thanks,
Alex
next parent reply other threads:[~2014-09-06 4:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAGou9MhCmRajqfh91rxbBUr9PBvJxo7U=g9p4Onp0pJk4BwBnA@mail.gmail.com>
2014-09-06 4:01 ` Alex Williamson [this message]
2014-09-06 5:28 ` ath9k and AMD IOMMU alias breakage on 3.16? Jason Newton
2014-09-12 16:17 ` Joerg Roedel
2014-09-12 21:19 ` Jason Newton
2014-09-08 10:32 ` 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=1409976104.2982.56.camel@ul30vt.home \
--to=alex.williamson@redhat.com \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-wireless@vger.kernel.org \
--cc=nevion@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).