All of lore.kernel.org
 help / color / mirror / Atom feed
From: yang.shi@linaro.org (Shi, Yang)
To: linux-arm-kernel@lists.infradead.org
Subject: SMMU problem found on LS2085A with 4.6-rc3
Date: Wed, 13 Apr 2016 12:31:53 -0700	[thread overview]
Message-ID: <570E9EA9.2070903@linaro.org> (raw)

Hi Will & Robin,

I just ran some quick test on my LS2085A board, which has 8 Cortex A57 
cores, with 4.6-rc3 kernel, but I found a regression issue with SMMU.

SMMU driver reports:

arm_smmu_global_fault: 297974 callbacks suppressed
arm_smmu_global_fault: 298561 callbacks suppressed
arm-smmu 5000000.iommu:         GFSR 0x80000004, GFSYNR0 0x00000008, 
GFSYNR1 0x00000300, GFSYNR2 0x00000000
arm-smmu 5000000.iommu:         GFSR 0x80000004, GFSYNR0 0x00000008, 
GFSYNR1 0x00000300, GFSYNR2 0x00000000
arm-smmu 5000000.iommu:         GFSR 0x80000004, GFSYNR0 0x00000008, 
GFSYNR1 0x00000300, GFSYNR2 0x00000000
arm-smmu 5000000.iommu:         GFSR 0x80000004, GFSYNR0 0x00000008, 
GFSYNR1 0x00000300, GFSYNR2 0x00000000
arm-smmu 5000000.iommu:         GFSR 0x80000004, GFSYNR0 0x00000008, 
GFSYNR1 0x00000300, GFSYNR2 0x00000000
arm-smmu 5000000.iommu:         GFSR 0x80000004, GFSYNR0 0x00000008, 
GFSYNR1 0x00000300, GFSYNR2 0x00000000
arm-smmu 5000000.iommu:         GFSR 0x80000004, GFSYNR0 0x00000008, 
GFSYNR1 0x00000300, GFSYNR2 0x00000000
arm-smmu 5000000.iommu:         GFSR 0x80000004, GFSYNR0 0x00000008, 
GFSYNR1 0x00000300, GFSYNR2 0x00000000
arm-smmu 5000000.iommu:         GFSR 0x80000004, GFSYNR0 0x00000008, 
GFSYNR1 0x00000300, GFSYNR2 0x00000000
arm-smmu 5000000.iommu:         GFSR 0x80000004, GFSYNR0 0x00000008, 
GFSYNR1 0x00000300, GFSYNR2 0x00000000
arm-smmu 5000000.iommu: Unexpected global fault, this could be serious
arm-smmu 5000000.iommu: Unexpected global fault, this could be serious
arm-smmu 5000000.iommu: Unexpected global fault, this could be serious
arm-smmu 5000000.iommu: Unexpected global fault, this could be serious
arm-smmu 5000000.iommu: Unexpected global fault, this could be serious
arm-smmu 5000000.iommu: Unexpected global fault, this could be serious
arm-smmu 5000000.iommu: Unexpected global fault, this could be serious
arm-smmu 5000000.iommu: Unexpected global fault, this could be serious
arm-smmu 5000000.iommu: Unexpected global fault, this could be serious
arm-smmu 5000000.iommu: Unexpected global fault, this could be serious


But, it is good with 4.5 kernel. I found the below commit causes it:

commit 9adb95949a343dac53b1cd81dc973b5f815c88d4
Author: Robin Murphy <robin.murphy@arm.com>
Date:   Tue Jan 26 18:06:36 2016 +0000

     iommu/arm-smmu: Support DMA-API domains

     With DMA mapping ops provided by the iommu-dma code, only a minimal
     contribution from the IOMMU driver is needed to create a suitable
     DMA-API domain for them to use. Implement this for the ARM SMMUs.

     Signed-off-by: Robin Murphy <robin.murphy@arm.com>
     Signed-off-by: Will Deacon <will.deacon@arm.com>

Any idea?

Thanks,
Yang

             reply	other threads:[~2016-04-13 19:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-13 19:31 Shi, Yang [this message]
2016-04-14 12:04 ` SMMU problem found on LS2085A with 4.6-rc3 Robin Murphy
2016-04-14 23:07   ` Shi, Yang
2016-04-15 12:30     ` Robin Murphy
2016-04-15 17:19       ` Shi, Yang
2016-04-15 17:44         ` Robin Murphy
2016-04-15 17:55           ` Shi, Yang

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=570E9EA9.2070903@linaro.org \
    --to=yang.shi@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.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.