From: Baolu Lu <baolu.lu@linux.intel.com>
To: "Borah, Chaitanya Kumar" <chaitanya.kumar.borah@intel.com>
Cc: baolu.lu@linux.intel.com,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>,
"iommu@lists.linux.dev" <iommu@lists.linux.dev>
Subject: Re: Regression on drm-tip
Date: Thu, 13 Mar 2025 17:30:07 +0800 [thread overview]
Message-ID: <9902ee4c-6223-4550-b25c-984629618f58@linux.intel.com> (raw)
In-Reply-To: <SJ1PR11MB612953431F94F18C954C4A9CB9D32@SJ1PR11MB6129.namprd11.prod.outlook.com>
On 2025/3/13 16:51, Borah, Chaitanya Kumar wrote:
> Hello Lu,
>
> Hope you are doing well. I am Chaitanya from the linux graphics team in Intel.
>
> This mail is regarding a regression we are seeing in our CI runs[1] on drm-tip repository.
>
> `````````````````````````````````````````````````````````````````````````````````
> <4>[ 2.856622] WARNING: possible circular locking dependency detected
> <4>[ 2.856631] 6.14.0-rc5-CI_DRM_16217-gc55ef90b69d3+ #1 Tainted: G I
> <4>[ 2.856642] ------------------------------------------------------
> <4>[ 2.856650] swapper/0/1 is trying to acquire lock:
> <4>[ 2.856657] ffffffff8360ecc8 (iommu_probe_device_lock){+.+.}-{3:3}, at: iommu_probe_device+0x1d/0x70
> <4>[ 2.856679]
> but task is already holding lock:
> <4>[ 2.856686] ffff888102ab6fa8 (&device->physical_node_lock){+.+.}-{3:3}, at: intel_iommu_init+0xea1/0x1220
> `````````````````````````````````````````````````````````````````````````````````
> Details log can be found in [2].
>
> After bisecting the tree, the following patch [3] seems to be the first "bad" commit
>
> `````````````````````````````````````````````````````````````````````````````````````````````````````````
> commit b150654f74bf0df8e6a7936d5ec51400d9ec06d8
> Author: Lu Baolumailto:baolu.lu@linux.intel.com
> Date: Fri Feb 28 18:27:26 2025 +0800
>
> iommu/vt-d: Fix suspicious RCU usage
>
> `````````````````````````````````````````````````````````````````````````````````````````````````````````
>
> We also verified that if we revert the patch the issue is not seen.
>
> Could you please check why the patch causes this regression and provide a fix if necessary?
Sure. I will look into this issue.
Thanks,
baolu
next prev parent reply other threads:[~2025-03-13 9:30 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-13 8:51 Regression on drm-tip Borah, Chaitanya Kumar
2025-03-13 9:30 ` Baolu Lu [this message]
2025-03-13 14:23 ` Baolu Lu
2025-03-14 9:04 ` Borah, Chaitanya Kumar
2025-03-16 2:33 ` Baolu Lu
2025-03-16 7:27 ` Borah, Chaitanya Kumar
2025-03-16 8:03 ` Baolu Lu
2025-03-16 10:01 ` Borah, Chaitanya Kumar
2025-03-17 4:04 ` Baolu Lu
2025-03-22 20:59 ` Lucas De Marchi
2025-03-13 14:28 ` ✗ CI.Patch_applied: failure for " Patchwork
2025-03-16 8:15 ` ✗ CI.Patch_applied: failure for Regression on drm-tip (rev2) Patchwork
2025-03-18 10:15 ` Patchwork
-- strict thread matches above, loose matches on Subject: below --
2025-04-28 6:02 Regression on drm-tip Borah, Chaitanya Kumar
2025-11-27 6:25 REGRESSION " Borah, Chaitanya Kumar
2025-11-27 16:01 ` Saarinen, Jani
2025-11-27 16:06 ` Saarinen, Jani
2025-11-27 23:04 ` Ville Syrjälä
2025-11-28 7:46 ` Borah, Chaitanya Kumar
2025-12-05 10:14 ` Christian Brauner
2025-12-01 16:13 ` Saarinen, Jani
2025-12-05 10:14 ` Christian Brauner
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=9902ee4c-6223-4550-b25c-984629618f58@linux.intel.com \
--to=baolu.lu@linux.intel.com \
--cc=chaitanya.kumar.borah@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=iommu@lists.linux.dev \
/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