From: Mark Hounschell <markh@compro.net>
To: Joerg Roedel <joro@8bytes.org>
Cc: "linux-scsi@vger.kernel.org >> SCSI development list"
<linux-scsi@vger.kernel.org>, Hannes Reinecke <hare@suse.de>,
linux-kernel@vger.kernel.org, iommu@lists.linux-foundation.org
Subject: Re: BUG: SCSI aic7xxx driver and AMD IOMMU
Date: Tue, 24 Mar 2015 07:57:49 -0400 [thread overview]
Message-ID: <5511513D.6090106@compro.net> (raw)
In-Reply-To: <20150323150304.GQ4441@8bytes.org>
On 03/23/2015 11:03 AM, Joerg Roedel wrote:
> Hi Mark,
>
> On Tue, Mar 03, 2015 at 02:36:19PM -0500, Mark Hounschell wrote:
>> It looks like this problem is NOT a bug with the SCSI aic7xxx driver
>> after all. I can duplicate this BUG very easily with other hardware.
>> Simply removing a driver module (whether it its self, has actually
>> used any of the DMA API or not) that is sitting on the same pci bus
>> as a card that is actually using DMA will cause this. And that card
>> that is in use and using DMA will no longer function. It "looks and
>> feels" like unloading a module causes the IOMMU to improperly unmap
>> valid mappings.
>
> You are right, I looked into the code and found the problem. I'll post a
> fix for testing this week.
>
I'll be happy to test it.
Regards
Mark
next prev parent reply other threads:[~2015-03-24 11:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-16 14:34 BUG: SCSI aic7xxx driver and AMD IOMMU Mark Hounschell
2015-03-03 19:36 ` Mark Hounschell
2015-03-23 15:03 ` Joerg Roedel
2015-03-24 11:57 ` Mark Hounschell [this message]
2015-03-25 13:59 ` Joerg Roedel
2015-03-25 15:13 ` Joerg Roedel
2015-03-25 16:36 ` Mark Hounschell
2015-03-26 12:45 ` Joerg Roedel
2015-03-26 14:58 ` Mark Hounschell
2015-03-26 15:52 ` Joerg Roedel
2015-03-26 17:09 ` 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=5511513D.6090106@compro.net \
--to=markh@compro.net \
--cc=hare@suse.de \
--cc=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.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).