Linux IOMMU Development
 help / color / mirror / Atom feed
From: Baolu Lu <baolu.lu@linux.intel.com>
To: Jason Gunthorpe <jgg@nvidia.com>
Cc: baolu.lu@linux.intel.com, Joerg Roedel <joro@8bytes.org>,
	Kevin Tian <kevin.tian@intel.com>,
	Robin Murphy <robin.murphy@arm.com>,
	iommu@lists.linux.dev
Subject: Re: lockdep splat with intel iommu
Date: Sun, 30 Oct 2022 16:41:58 +0800	[thread overview]
Message-ID: <fd26ae05-4c92-8756-e9b9-fa8041b07641@linux.intel.com> (raw)
In-Reply-To: <Y11PleKAgldyfKCi@nvidia.com>

On 2022/10/30 0:06, Jason Gunthorpe wrote:
> On Sat, Oct 29, 2022 at 04:22:32PM +0800, Baolu Lu wrote:
>> On 2022/10/27 21:59, Jason Gunthorpe wrote:
>>> I'm seeing this at every boot, on v6.1-rc2
>>>
>>> I've just realized it means lockdep is turned off for the actual
>>> testing I want to do. Very annoying
>>>
>>> Lu, is there a solution yet? I saw some patches for a different
>>> lockdep splat but not this one.
>>
>> Hi Jason,
>>
>> Possibly the same issue as this one?
>>
>> https://lore.kernel.org/linux-iommu/20220922101036.87457-1-janusz.krzysztofik@linux.intel.com/
> 
> No, this has nothing to do with coretemp and this one involves irq_domain_mutex

Can you please share a copy of the .config with me? I am trying to
reproduce this with a local machine.

Best regards,
baolu

  reply	other threads:[~2022-10-30  8:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-27 13:59 lockdep splat with intel iommu Jason Gunthorpe
2022-10-29  8:22 ` Baolu Lu
2022-10-29 16:06   ` Jason Gunthorpe
2022-10-30  8:41     ` Baolu Lu [this message]
2022-10-31 12:11       ` Jason Gunthorpe
2023-03-24 21:01 ` Jason Gunthorpe
2023-03-25  8:49   ` Baolu Lu

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=fd26ae05-4c92-8756-e9b9-fa8041b07641@linux.intel.com \
    --to=baolu.lu@linux.intel.com \
    --cc=iommu@lists.linux.dev \
    --cc=jgg@nvidia.com \
    --cc=joro@8bytes.org \
    --cc=kevin.tian@intel.com \
    --cc=robin.murphy@arm.com \
    /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