Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1527307

Re: BUG at drivers/iommu/amd_iommu.c:1436!

From Joerg Roedel <joro@8bytes.org>
Newsgroups linux.kernel
Subject Re: BUG at drivers/iommu/amd_iommu.c:1436!
Date 2016-11-22 09:50 +0100
Message-ID <sGeW5-4Pc-5@gated-at.bofh.it> (permalink)
References (2 earlier) <sED2y-6D0-11@gated-at.bofh.it> <sED2y-6D0-15@gated-at.bofh.it> <sESbg-8gx-21@gated-at.bofh.it> <sFYRk-2Wx-27@gated-at.bofh.it> <sG4Do-6Da-21@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw

On Mon, Nov 21, 2016 at 04:47:59PM -0500, Mark Hounschell wrote:
> OK, I did get this message before the reported BUG message.
> 
> gpiohsd gpiohsd: DMA-API: device driver tries to free DMA memory it has not allocated [device address=0xffffffffffee8000] [size=8192 bytes]
> 
> But I've verified that the dma_addr_t that I get for the alloc, and
> also use for the free is 0x00000000ffee8000 in this case? Is device
> "address=0xffffffffffee8000" in that message a bug in the message or
> do we have a sign extended address problem? It seems strange to me,
> I've never seen a dma_addr_t given, when using the iommu, that
> high. In the past I've seen them as usually 0x00xxxxxx?
> 
> I have also verified that simply changing from
> pci_alloc/free_consistent to the newer DMA API fixes my issue and I
> get no such messages.

Yes, this looks like a sign-extension bug somewhere. But its not in the
amd-iommu driver, because dma-debug also sees it. And from what I can
tell the dma-api interface seems to be fine. It consistently uses
dma_addr_t to pass these values around.

Where can I find the source of the failing code? I need exactly the code
version that triggers the problem.



	Joerg

Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

BUG at drivers/iommu/amd_iommu.c:1436! Mark Hounschell <markh@compro.net> - 2016-11-17 20:30 +0100
  Re: BUG at drivers/iommu/amd_iommu.c:1436! Joerg Roedel <joro@8bytes.org> - 2016-11-17 22:50 +0100
    Re: BUG at drivers/iommu/amd_iommu.c:1436! Mark Hounschell <markh@compro.net> - 2016-11-17 23:10 +0100
      Re: BUG at drivers/iommu/amd_iommu.c:1436! Joerg Roedel <joro@8bytes.org> - 2016-11-17 23:10 +0100
        Re: BUG at drivers/iommu/amd_iommu.c:1436! Joerg Roedel <joro@8bytes.org> - 2016-11-21 16:40 +0100
          Re: BUG at drivers/iommu/amd_iommu.c:1436! Mark Hounschell <markh@compro.net> - 2016-11-21 22:50 +0100
            Re: BUG at drivers/iommu/amd_iommu.c:1436! Joerg Roedel <joro@8bytes.org> - 2016-11-22 09:50 +0100
              Re: BUG at drivers/iommu/amd_iommu.c:1436! Mark Hounschell <markh@compro.net> - 2016-11-22 21:00 +0100

csiph-web