From: Tasmiya Nalatwad <tasmiya@linux.vnet.ibm.com>
To: Jason Gunthorpe <jgg@nvidia.com>
Cc: sachinp@linux.vnet.com, jroedel@suse.de, will@kernel.org,
linux-arm-msm@vger.kernel.org, joro@8bytes.org,
jsnitsel@redhat.com, linux-kernel@vger.kernel.org,
linux-block@vger.kernel.org, abdhalee@linux.vnet.ibm.com,
iommu@lists.linux.dev, linux-next@vger.kernel.org,
mputtash@linux.vnet.com, linuxppc-dev@lists.ozlabs.org,
linux-arm-kernel@lists.infradead.org, baolu.lu@linux.intel.com
Subject: Re: [Bisected] [commit 2ad56efa80db] [Hotplug] WARNING while performing hotplug operation on 6.6-rc3-next
Date: Fri, 6 Oct 2023 18:50:00 +0530 [thread overview]
Message-ID: <7ce42090-a768-ba3d-bd27-e86bc076ee57@linux.vnet.ibm.com> (raw)
In-Reply-To: <20231006113644.GN682044@nvidia.com>
[-- Attachment #1: Type: text/plain, Size: 3975 bytes --]
Greetings,
Thanks Jason.
The fix provided by you works. It is not giving WARNING's but i am
seeing below logs. Would you please confirm on the logs.
https://lore.kernel.org/all/0-v1-2b52423411b9+164fc-iommu_ppc_defdomain_jgg@nvidia.com/
[ 152.342125] pci 0013:60:00.0: No hypervisor support for SR-IOV on
this device, IOV BARs disabled.
[ 152.344896] pci 0013:60:00.0: PME# supported from D0 D3hot D3cold
[ 152.348936] pci 0013:60:00.0: Adding to iommu group 0
[ 152.349944] pci 0013:60:00.1: No hypervisor support for SR-IOV on
this device, IOV BARs disabled.
[ 152.352701] pci 0013:60:00.1: PME# supported from D0 D3hot D3cold
[ 152.356520] pci 0013:60:00.1: Adding to iommu group 0
[ 152.356527] iommu_tce: it_map is not empty
[ 152.357501] pci 0013:60:00.2: No hypervisor support for SR-IOV on
this device, IOV BARs disabled.
[ 152.360247] pci 0013:60:00.2: PME# supported from D0 D3hot D3cold
[ 152.364070] pci 0013:60:00.2: Adding to iommu group 0
[ 152.364075] *iommu_tce: it_map is not empty*
[ 152.365043] pci 0013:60:00.3: No hypervisor support for SR-IOV on
this device, IOV BARs disabled.
[ 152.367790] pci 0013:60:00.3: PME# supported from D0 D3hot D3cold
[ 152.371635] pci 0013:60:00.3: Adding to iommu group 0
[ 152.371641] iommu_tce: it_map is not empty
[ 152.371720] pci 0013:60:00.0: of_irq_parse_pci: no interrupt-map
found, INTx interrupts not available
[ 152.408351] tg3 0013:60:00.0: iommu: 64-bit OK but direct DMA is
limited by 800002000000000
[ 152.408376] tg3 0013:60:00.0: iommu: 64-bit OK but direct DMA is
limited by 800002000000000
*[ 152.408404] tg3 0013:60:00.0: DMA engine test failed, aborting**
**[ 152.408557] tg3: probe of 0013:60:00.0 failed with error -12*
[ 152.408583] pci 0013:60:00.1: Adding to iommu group 0
[ 152.408589] iommu_tce: it_map is not empty
[ 152.408656] pci 0013:60:00.1: of_irq_parse_pci: no interrupt-map
found, INTx interrupts not available
[ 152.448321] tg3 0013:60:00.1: iommu: 64-bit OK but direct DMA is
limited by 800002000000000
[ 152.448339] tg3 0013:60:00.1: iommu: 64-bit OK but direct DMA is
limited by 800002000000000
[ 152.448360] tg3 0013:60:00.1: DMA engine test failed, aborting
[ 152.448497] tg3: probe of 0013:60:00.1 failed with error -12
[ 152.448519] pci 0013:60:00.2: Adding to iommu group 0
[ 152.448525] iommu_tce: it_map is not empty
[ 152.448586] pci 0013:60:00.2: of_irq_parse_pci: no interrupt-map
found, INTx interrupts not available
[ 152.488323] tg3 0013:60:00.2: iommu: 64-bit OK but direct DMA is
limited by 800002000000000
[ 152.488340] tg3 0013:60:00.2: iommu: 64-bit OK but direct DMA is
limited by 800002000000000
[ 152.488362] tg3 0013:60:00.2: DMA engine test failed, aborting
[ 152.488495] tg3: probe of 0013:60:00.2 failed with error -12
[ 152.488516] pci 0013:60:00.3: Adding to iommu group 0
[ 152.488523] iommu_tce: it_map is not empty
[ 152.488581] pci 0013:60:00.3: of_irq_parse_pci: no interrupt-map
found, INTx interrupts not available
[ 152.528342] tg3 0013:60:00.3: iommu: 64-bit OK but direct DMA is
limited by 800002000000000
[ 152.528359] tg3 0013:60:00.3: iommu: 64-bit OK but direct DMA is
limited by 800002000000000
[ 152.528381] tg3 0013:60:00.3: DMA engine test failed, aborting
[ 152.528515] tg3: probe of 0013:60:00.3 failed with error -12
On 10/6/23 17:06, Jason Gunthorpe wrote:
> On Fri, Oct 06, 2023 at 01:20:17PM +0530, Tasmiya Nalatwad wrote:
>> Greetings,
>>
>> [linux-next] [6.6.0-rc3-next-20230929] WARNING: CPU: 5 PID: 185612 at
>> drivers/iommu/iommu.c:3049 iommu_setup_default_domain+0x410/0x680
>>
>> --- Traces ---
>>
>> [ 6296.425934] WARNING: CPU: 5 PID: 185612 at drivers/iommu/iommu.c:3049
>> iommu_setup_default_domain+0x410/0x680
> Does this fix it too? I think it should?
>
> https://lore.kernel.org/r/0-v1-2b52423411b9+164fc-iommu_ppc_defdomain_jgg@nvidia.com
>
> Jason
--
Regards,
Tasmiya Nalatwad
IBM Linux Technology Center
[-- Attachment #2: Type: text/html, Size: 5471 bytes --]
next prev parent reply other threads:[~2023-10-07 23:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-06 7:50 [Bisected] [commit 2ad56efa80db] [Hotplug] WARNING while performing hotplug operation on 6.6-rc3-next Tasmiya Nalatwad
2023-10-06 11:36 ` Jason Gunthorpe
2023-10-06 13:20 ` Tasmiya Nalatwad [this message]
2023-10-06 13:39 ` Jason Gunthorpe
2023-10-06 13:43 ` Tasmiya Nalatwad
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=7ce42090-a768-ba3d-bd27-e86bc076ee57@linux.vnet.ibm.com \
--to=tasmiya@linux.vnet.ibm.com \
--cc=abdhalee@linux.vnet.ibm.com \
--cc=baolu.lu@linux.intel.com \
--cc=iommu@lists.linux.dev \
--cc=jgg@nvidia.com \
--cc=joro@8bytes.org \
--cc=jroedel@suse.de \
--cc=jsnitsel@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mputtash@linux.vnet.com \
--cc=sachinp@linux.vnet.com \
--cc=will@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).