From: Jani Nikula <jani.nikula@linux.intel.com>
To: "Borah, Chaitanya Kumar" <chaitanya.kumar.borah@intel.com>,
"Hall, Christopher S" <christopher.s.hall@intel.com>
Cc: "intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"Keller, Jacob E" <jacob.e.keller@intel.com>,
"intel-wired-lan@lists.osuosl.org"
<intel-wired-lan@lists.osuosl.org>,
"Saarinen, Jani" <jani.saarinen@intel.com>,
"Kurmi, Suresh Kumar" <suresh.kumar.kurmi@intel.com>,
"De Marchi, Lucas" <lucas.demarchi@intel.com>,
regressions@lists.linux.dev,
"Linux regression tracking (Thorsten Leemhuis)"
<regressions@leemhuis.info>
Subject: [REGRESSION] v6.15-rc3: 1a931c4f5e68 ("igc: add lock preventing multiple simultaneous PTM transactions")
Date: Mon, 05 May 2025 13:53:24 +0300 [thread overview]
Message-ID: <87cycnwcpn.fsf@intel.com> (raw)
In-Reply-To: <SJ1PR11MB6129BBB9E38F6DB731604E94B9812@SJ1PR11MB6129.namprd11.prod.outlook.com>
On Mon, 28 Apr 2025, "Borah, Chaitanya Kumar" <chaitanya.kumar.borah@intel.com> wrote:
> Hello Christopher,
>
> This mail is regarding a regression we are seeing in our CI runs[1] on drm-tip[2] repository.
The regressing commit is in v6.15-rc3. Updated subject and Cc'd
regression tracking.
BR,
Jani.
>
> `````````````````````````````````````````````````````````````````````````````````
> <4>[ 7.891028] =============================
> <4>[ 7.891293] [ BUG: Invalid wait context ]
> <4>[ 7.891526] 6.15.0-rc3-CI_DRM_16443-gdc80d6a10c1c+ #1 Tainted: G W
> <4>[ 7.891792] -----------------------------
> <4>[ 7.892070] (udev-worker)/286 is trying to lock:
> <4>[ 7.892349] ffff88811671bcc8 (&adapter->ptm_lock){....}-{3:3}, at: igc_ptp_reset+0x155/0x320 [igc]
> <4>[ 7.892660] other info that might help us debug this:
> <4>[ 7.892943] context-{4:4}
> <4>[ 7.893226] 2 locks held by (udev-worker)/286:
> <4>[ 7.893515] #0: ffff888103bd41b0 (&dev->mutex){....}-{3:3}, at: __driver_attach+0x104/0x220
> <4>[ 7.893823] #1: ffff88811671bb70 (&adapter->tmreg_lock){....}-{2:2}, at: igc_ptp_reset+0x53/0x320 [igc]
> <4>[ 7.894134] stack backtrace:
> <4>[ 7.894439] CPU: 2 UID: 0 PID: 286 Comm: (udev-worker) Tainted: G W 6.15.0-rc3-CI_DRM_16443-gdc80d6a10c1c+ #1 PREEMPT(voluntary)
> <4>[ 7.894442] Tainted: [W]=WARN
> <4>[ 7.894443] Hardware name: Intel(R) Client Systems NUC11TNHi3/NUC11TNBi3, BIOS TNTGL357.0067.2022.0718.1742 07/18/2022
> `````````````````````````````````````````````````````````````````````````````````
> Detailed log can be found in [3].
>
> After bisecting the tree, the following patch [4] seems to be the first "bad"
> commit
>
> `````````````````````````````````````````````````````````````````````````````````````````````````````````
> commit 1a931c4f5e6862e61a4b130cb76b422e1415f644
> Author: Christopher S M Hall mailto:christopher.s.hall@intel.com
> Date: Tue Apr 1 16:35:34 2025 -0700
>
> igc: add lock preventing multiple simultaneous PTM transactions
> `````````````````````````````````````````````````````````````````````````````````````````````````````````
>
> 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?
>
> Thank you.
>
> Regards
>
> Chaitanya
>
> [1] https://intel-gfx-ci.01.org/tree/drm-tip/shard-tglu.html
> [2] https://cgit.freedesktop.org/drm-tip/tree/
> [3] https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_16443/fi-tgl-1115g4/boot0.txt
> [4] https://cgit.freedesktop.org/drm-tip/commit/?id=1a931c4f5e6862e61a4b130cb76b422e1415f644
>
--
Jani Nikula, Intel
next prev parent reply other threads:[~2025-05-05 10:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-28 6:02 Regression on drm-tip Borah, Chaitanya Kumar
2025-05-05 10:53 ` Jani Nikula [this message]
2025-05-06 16:24 ` [Intel-wired-lan] [REGRESSION] v6.15-rc3: 1a931c4f5e68 ("igc: add lock preventing multiple simultaneous PTM transactions") Tony Nguyen
2025-05-07 15:31 ` Jani Nikula
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=87cycnwcpn.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=chaitanya.kumar.borah@intel.com \
--cc=christopher.s.hall@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jacob.e.keller@intel.com \
--cc=jani.saarinen@intel.com \
--cc=lucas.demarchi@intel.com \
--cc=regressions@leemhuis.info \
--cc=regressions@lists.linux.dev \
--cc=suresh.kumar.kurmi@intel.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;
as well as URLs for NNTP newsgroup(s).