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: Thu, 12 Feb 2015 22:08:46 +0100 [thread overview]
Message-ID: <20150212210846.GE29106@8bytes.org> (raw)
In-Reply-To: <54DD00FE.2050009-n2QNKt385d+sTnJN9+BGXg@public.gmane.org>
On Thu, Feb 12, 2015 at 02:37:34PM -0500, Mark Hounschell wrote:
> I've cleaned the machine of all our drivers and also the nvidia
> driver. If the problem is as you say, it is an in-kernel driver.
> I've attached a dmesg taken after it started. I used the dgap driver
> from the staging directory to unload and trigger this as I have one.
> That driver does NO dma. I know because I'm one of the maintainers
> and have done lots of work on it.
I have seen reports before with IOMMU problems and the NVidia driver.
Can you reproduce the problem without any out-of-tree stuff and without
staging modules ever loaded after boot? The Tainted flags in the warning
should be empty then.
> [ 122.810648] AMD-Vi: Event logged [IO_PAGE_FAULT device=0f:00.0 domain=0x0001 address=0x000000000007a260 flags=0x0020]
This indicates that the driver for device 0f:00.0 (or something behind
it if it is a bridge) could be the problem.
Joerg
next prev parent reply other threads:[~2015-02-12 21:08 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 [this message]
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
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=20150212210846.GE29106@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 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.