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: Fri, 12 Sep 2014 18:17:52 +0200 [thread overview]
Message-ID: <20140912161752.GV28786@8bytes.org> (raw)
In-Reply-To: <CAGou9Mg+5GhUUECM4qurF6UzhLMARgeCtbL020U9y0Vs7aFGoA@mail.gmail.com>
Hi Jason,
On Fri, Sep 05, 2014 at 10:28:01PM -0700, Jason Newton wrote:
> [ 0.021820] AMD-Vi: device: 00:00.2 cap: 0040 seg: 0 flags: b8 info 0000
> [ 0.021827] AMD-Vi: mmio-addr: 00000000feb80000
> [ 0.021844] AMD-Vi: DEV_SELECT_RANGE_START devid: 00:01.0 flags: 00
> [ 0.021848] AMD-Vi: DEV_RANGE_END devid: ff:1f.6
> [ 0.022730] AMD-Vi: DEV_ALIAS_RANGE devid: 02:00.0 flags: 00 devid_to: 00:14.4
> [ 0.022735] AMD-Vi: DEV_RANGE_END devid: 02:1f.7
> [ 0.022745] AMD-Vi: DEV_SPECIAL(HPET[0]) devid: 00:14.0
> [ 0.022749] AMD-Vi: DEV_SPECIAL(IOAPIC[5]) devid: 00:14.0
> [ 0.022753] AMD-Vi: DEV_SPECIAL(IOAPIC[6]) devid: 00:00.0
It is just a test, as I don't know how the hardware is actually wired in
your system, but can you try to boot with 'ivrs_ioapic[6]=00:00.1' on
the kernel command line and report if it makes any difference?
Thanks,
Joerg
next prev parent reply other threads:[~2014-09-12 16:17 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 ` ath9k and AMD IOMMU alias breakage on 3.16? Alex Williamson
2014-09-06 5:28 ` Jason Newton
2014-09-12 16:17 ` Joerg Roedel [this message]
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=20140912161752.GV28786@8bytes.org \
--to=joro@8bytes.org \
--cc=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).