From: Jason Gunthorpe <jgg@nvidia.com>
To: Tasmiya Nalatwad <tasmiya@linux.vnet.ibm.com>
Cc: linux-kernel@vger.kernel.org, linux-next@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-arm-msm@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
linux-block@vger.kernel.org, baolu.lu@linux.intel.com,
jsnitsel@redhat.com, jroedel@suse.de, joro@8bytes.org,
will@kernel.org, iommu@lists.linux.dev,
abdhalee@linux.vnet.ibm.com, mputtash@linux.vnet.com,
sachinp@linux.vnet.com
Subject: Re: [Bisected] [commit 2ad56efa80db] [Hotplug] WARNING while performing hotplug operation on 6.6-rc3-next
Date: Fri, 6 Oct 2023 08:36:44 -0300 [thread overview]
Message-ID: <20231006113644.GN682044@nvidia.com> (raw)
In-Reply-To: <92db426f-4a31-9c2c-e23a-85a8d353fbae@linux.vnet.ibm.com>
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
WARNING: multiple messages have this Message-ID (diff)
From: Jason Gunthorpe <jgg@nvidia.com>
To: Tasmiya Nalatwad <tasmiya@linux.vnet.ibm.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 08:36:44 -0300 [thread overview]
Message-ID: <20231006113644.GN682044@nvidia.com> (raw)
In-Reply-To: <92db426f-4a31-9c2c-e23a-85a8d353fbae@linux.vnet.ibm.com>
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
WARNING: multiple messages have this Message-ID (diff)
From: Jason Gunthorpe <jgg@nvidia.com>
To: Tasmiya Nalatwad <tasmiya@linux.vnet.ibm.com>
Cc: linux-kernel@vger.kernel.org, linux-next@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-arm-msm@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
linux-block@vger.kernel.org, baolu.lu@linux.intel.com,
jsnitsel@redhat.com, jroedel@suse.de, joro@8bytes.org,
will@kernel.org, iommu@lists.linux.dev,
abdhalee@linux.vnet.ibm.com, mputtash@linux.vnet.com,
sachinp@linux.vnet.com
Subject: Re: [Bisected] [commit 2ad56efa80db] [Hotplug] WARNING while performing hotplug operation on 6.6-rc3-next
Date: Fri, 6 Oct 2023 08:36:44 -0300 [thread overview]
Message-ID: <20231006113644.GN682044@nvidia.com> (raw)
In-Reply-To: <92db426f-4a31-9c2c-e23a-85a8d353fbae@linux.vnet.ibm.com>
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
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-10-06 11:36 UTC|newest]
Thread overview: 13+ 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 7:50 ` Tasmiya Nalatwad
2023-10-06 7:50 ` Tasmiya Nalatwad
2023-10-06 11:36 ` Jason Gunthorpe [this message]
2023-10-06 11:36 ` Jason Gunthorpe
2023-10-06 11:36 ` Jason Gunthorpe
2023-10-06 13:20 ` Tasmiya Nalatwad
2023-10-06 13:39 ` Jason Gunthorpe
2023-10-06 13:39 ` Jason Gunthorpe
2023-10-06 13:39 ` Jason Gunthorpe
2023-10-06 13:43 ` Tasmiya Nalatwad
2023-10-06 13:43 ` Tasmiya Nalatwad
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=20231006113644.GN682044@nvidia.com \
--to=jgg@nvidia.com \
--cc=abdhalee@linux.vnet.ibm.com \
--cc=baolu.lu@linux.intel.com \
--cc=iommu@lists.linux.dev \
--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=tasmiya@linux.vnet.ibm.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 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.