From: Joerg Roedel <joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
To: Mark Hounschell <markh-n2QNKt385d+sTnJN9+BGXg@public.gmane.org>
Cc: iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
Subject: Re: Kernel Oops: iommu related?
Date: Fri, 13 Feb 2015 23:27:01 +0100 [thread overview]
Message-ID: <20150213222701.GH29106@8bytes.org> (raw)
In-Reply-To: <54DE07DA.9050703-n2QNKt385d+sTnJN9+BGXg@public.gmane.org>
On Fri, Feb 13, 2015 at 09:19:06AM -0500, Mark Hounschell wrote:
> OK. Attached.
Thanks, the IVRS table looks good. Device 0f.00.0 is listed there as the
alias target for a group of other devices:
> [ 1.405719] AMD-Vi: DEV_ALIAS_RANGE devid: 0f:01.0 flags: 00 devid_to: 0f:00.0
> [ 1.405722] AMD-Vi: DEV_RANGE_END devid: 12:1f.7
> BTW when I blacklist the aic7xxx driver [last
> unloaded: aic7xxx] I can load and unload any module all day long.
Okay, this driver seems to be the problem, it has a bug somewhere in
using the DMA-API. This causes the iommu problems.
The device it serves is behind the alias range for 0f:00.0, so any
faults from that device will show up as coming from 0f:00.0, like in the
io-page-faults you see in dmesg.
Joerg
prev parent reply other threads:[~2015-02-13 22:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-12 17:53 Kernel Oops: iommu related? Mark Hounschell
[not found] ` <54DCE8A6.4000608-n2QNKt385d+sTnJN9+BGXg@public.gmane.org>
2015-02-12 18:08 ` Joerg Roedel
[not found] ` <20150212180846.GD29106-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
2015-02-12 18:25 ` Mark Hounschell
[not found] ` <54DCF024.30309-n2QNKt385d+sTnJN9+BGXg@public.gmane.org>
2015-02-12 19:37 ` Mark Hounschell
[not found] ` <54DD00FE.2050009-n2QNKt385d+sTnJN9+BGXg@public.gmane.org>
2015-02-12 19:59 ` Mark Hounschell
2015-02-12 21:08 ` Joerg Roedel
2015-02-12 21:13 ` Joerg Roedel
[not found] ` <20150212211340.GF29106-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
2015-02-13 14:19 ` Mark Hounschell
[not found] ` <54DE07DA.9050703-n2QNKt385d+sTnJN9+BGXg@public.gmane.org>
2015-02-13 22:27 ` Joerg Roedel [this message]
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=20150213222701.GH29106@8bytes.org \
--to=joro-zlv9swrftaidnm+yrofe0a@public.gmane.org \
--cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=markh-n2QNKt385d+sTnJN9+BGXg@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