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,
Linux-kernel
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: BUG at drivers/iommu/amd_iommu.c:1436!
Date: Thu, 17 Nov 2016 23:00:45 +0100 [thread overview]
Message-ID: <20161117220045.GD2078@8bytes.org> (raw)
In-Reply-To: <f4ababc2-64bf-fd0e-1d18-cb5963d23eb1-n2QNKt385d+sTnJN9+BGXg@public.gmane.org>
On Thu, Nov 17, 2016 at 04:53:24PM -0500, Mark Hounschell wrote:
> On 11/17/2016 04:41 PM, Joerg Roedel wrote:
> >Hi Mark,
> >
> >On Thu, Nov 17, 2016 at 02:13:59PM -0500, Mark Hounschell wrote:
> >>Kernel version is 4.8.0. No failure when the IOMMU is disabled. This
> >>is an out of tree GPL driver using
> >>pci_alloc_consistent/pci_free_consistent. The free causes this.
> >
> >Can you please run the driver with dma-api debugging enabled? Does it
> >trigger any warnings?
> >
>
> It's been a while since I've done that for ya. Kernel config
> options? Kernel cmd line you want?
Just enable CONFIG_DMA_API_DEBUG and boot the resulting kernel. Please
send me full dmesg when the issue happens again.
Joerg
next prev parent reply other threads:[~2016-11-17 22:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-17 19:13 BUG at drivers/iommu/amd_iommu.c:1436! Mark Hounschell
[not found] ` <838275de-6cac-93d8-ca04-54b06a24b3d4-n2QNKt385d+sTnJN9+BGXg@public.gmane.org>
2016-11-17 21:41 ` Joerg Roedel
[not found] ` <20161117214141.GC2078-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
2016-11-17 21:53 ` Mark Hounschell
[not found] ` <f4ababc2-64bf-fd0e-1d18-cb5963d23eb1-n2QNKt385d+sTnJN9+BGXg@public.gmane.org>
2016-11-17 22:00 ` Joerg Roedel [this message]
[not found] ` <20161117220045.GD2078-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
2016-11-18 14:04 ` Mark Hounschell
[not found] ` <b8260bfd-55c9-c029-1af1-e1ccc719dd3a-n2QNKt385d+sTnJN9+BGXg@public.gmane.org>
2016-11-21 15:32 ` Joerg Roedel
[not found] ` <20161121153250.GE2078-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
2016-11-21 21:47 ` Mark Hounschell
[not found] ` <4f6afa52-9634-79f4-01af-1ae047aa83f7-n2QNKt385d+sTnJN9+BGXg@public.gmane.org>
2016-11-22 8:45 ` Joerg Roedel
[not found] ` <20161122084522.GF2078-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
2016-11-22 19:53 ` Mark Hounschell
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=20161117220045.GD2078@8bytes.org \
--to=joro-zlv9swrftaidnm+yrofe0a@public.gmane.org \
--cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@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;
as well as URLs for NNTP newsgroup(s).