From: Joerg Roedel <joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
To: Jason Newton <nevion-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: Alex Williamson
<alex.williamson-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
iommu
<iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org>,
linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: ath9k and AMD IOMMU alias breakage on 3.16?
Date: Mon, 8 Sep 2014 12:32:03 +0200 [thread overview]
Message-ID: <20140908103203.GQ28786@8bytes.org> (raw)
In-Reply-To: <1409976104.2982.56.camel-85EaTFmN5p//9pzu0YdTqQ@public.gmane.org>
On Fri, Sep 05, 2014 at 10:01:44PM -0600, Alex Williamson wrote:
> 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]
This means that the device 00:00.1 is sending to the interrupt/EOI
address-range while interrupt remapping is enabled. You can boot with
intremap=off on the kernel command line to work around this problem.
This looks either like another PCI aliasing issue or a 00:00.1 hidden
device is sending interrupt requests (which it is not allowed to do).
Joerg
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Joerg Roedel <joro@8bytes.org>
To: Jason Newton <nevion@gmail.com>
Cc: Alex Williamson <alex.williamson@redhat.com>,
iommu <iommu@lists.linux-foundation.org>,
linux-wireless@vger.kernel.org
Subject: Re: ath9k and AMD IOMMU alias breakage on 3.16?
Date: Mon, 8 Sep 2014 12:32:03 +0200 [thread overview]
Message-ID: <20140908103203.GQ28786@8bytes.org> (raw)
In-Reply-To: <1409976104.2982.56.camel@ul30vt.home>
On Fri, Sep 05, 2014 at 10:01:44PM -0600, Alex Williamson wrote:
> 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]
This means that the device 00:00.1 is sending to the interrupt/EOI
address-range while interrupt remapping is enabled. You can boot with
intremap=off on the kernel command line to work around this problem.
This looks either like another PCI aliasing issue or a 00:00.1 hidden
device is sending interrupt requests (which it is not allowed to do).
Joerg
next prev parent reply other threads:[~2014-09-08 10:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAGou9MhCmRajqfh91rxbBUr9PBvJxo7U=g9p4Onp0pJk4BwBnA@mail.gmail.com>
[not found] ` <CAGou9MhCmRajqfh91rxbBUr9PBvJxo7U=g9p4Onp0pJk4BwBnA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-09-06 4:01 ` ath9k and AMD IOMMU alias breakage on 3.16? Alex Williamson
2014-09-06 4:01 ` Alex Williamson
[not found] ` <1409976104.2982.56.camel-85EaTFmN5p//9pzu0YdTqQ@public.gmane.org>
2014-09-06 5:28 ` Jason Newton
2014-09-06 5:28 ` Jason Newton
[not found] ` <CAGou9Mg+5GhUUECM4qurF6UzhLMARgeCtbL020U9y0Vs7aFGoA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-09-12 16:17 ` Joerg Roedel
2014-09-12 16:17 ` Joerg Roedel
[not found] ` <20140912161752.GV28786-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
2014-09-12 21:19 ` Jason Newton
2014-09-12 21:19 ` Jason Newton
2014-09-08 10:32 ` Joerg Roedel [this message]
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=20140908103203.GQ28786@8bytes.org \
--to=joro-zlv9swrftaidnm+yrofe0a@public.gmane.org \
--cc=alex.williamson-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=nevion-Re5JQEeQqe8AvxtiuMwx3w@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.