[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <SJ1PR11MB61290A3105C95E8C6BF171DFB9A22@SJ1PR11MB6129.namprd11.prod.outlook.com>
Date: Tue, 16 Jul 2024 15:02:38 +0000
From: "Borah, Chaitanya Kumar" <chaitanya.kumar.borah@...el.com>
To: Lai Jiangshan <jiangshanlai@...il.com>
CC: "jiangshan.ljs@...group.com" <jiangshan.ljs@...group.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "Nikula, Jani"
<jani.nikula@...el.com>, "Saarinen, Jani" <jani.saarinen@...el.com>, "Kurmi,
Suresh Kumar" <suresh.kumar.kurmi@...el.com>,
"intel-gfx@...ts.freedesktop.org" <intel-gfx@...ts.freedesktop.org>
Subject: RE: Regression on linux-next (next-20240709)
Hello Lai,
> -----Original Message-----
> From: Borah, Chaitanya Kumar
> Sent: Tuesday, July 16, 2024 11:10 AM
> To: Lai Jiangshan <jiangshanlai@...il.com>
> Cc: jiangshan.ljs@...group.com; linux-kernel@...r.kernel.org; Nikula, Jani
> <jani.nikula@...el.com>; Saarinen, Jani <jani.saarinen@...el.com>; Kurmi,
> Suresh Kumar <Suresh.Kumar.Kurmi@...el.com>; intel-
> gfx@...ts.freedesktop.org
> Subject: RE: Regression on linux-next (next-20240709)
>
>
>
> > -----Original Message-----
> > From: Lai Jiangshan <jiangshanlai@...il.com>
> > Sent: Friday, July 12, 2024 2:23 PM
> > To: Borah, Chaitanya Kumar <chaitanya.kumar.borah@...el.com>
> > Cc: jiangshan.ljs@...group.com; linux-kernel@...r.kernel.org; Nikula,
> > Jani <jani.nikula@...el.com>; Saarinen, Jani
> > <jani.saarinen@...el.com>; Kurmi, Suresh Kumar
> > <suresh.kumar.kurmi@...el.com>
> > Subject: Re: Regression on linux-next (next-20240709)
> >
> > Hello
> >
> > On Fri, Jul 12, 2024 at 1:42 PM Borah, Chaitanya Kumar
> > > commit 1726a17135905e2d2773f18d47bd4e17dd26e1ed
> > > Author: Lai Jiangshan mailto:jiangshan.ljs@...group.com
> > > Date: Thu Jul 4 11:49:13 2024 +0800
> > >
> > > workqueue: Put PWQ allocation and WQ enlistment in the same lock
> C.S.
> > > ````````````````````````````````````````````````````````````````````
> > > `````````````````````````````````````
> > >
> > > We could not revert the patch because of merge conflict but
> > > resetting to the
> > parent of the commit seems to fix the issue
> > >
> > > Could you please check why the patch causes this regression and
> > > provide a
> > fix if necessary?
> >
> >
> > It has been fixed and it is in wq/for-6.11.
> >
> > https://lore.kernel.org/lkml/ZpASNBN0hpTVcjE-@slm.duckdns.org/
> >
With this patch we are running into another regression.
```````````````````````````````````````````````````````````````````````````````
<4>[ 4.171372] WARNING: CPU: 11 PID: 283 at kernel/cpu.c:527 lockdep_assert_cpus_held.part.0+0x24/0x30
<4>[ 4.171377] Modules linked in: kvm_intel(+) mei_hdcp mei_pxp r8152(+) mii wmi_bmof kvm r8169 video crct10dif_pclmul crc32_pclmul ghash_clmulni_intel realtek i2c_i801 mei_me i2c_mux mei intel_lpss_pci(+) i2c_smbus wmi btusb btrtl btintel btbcm bluetooth
<4>[ 4.171385] CPU: 11 UID: 0 PID: 283 Comm: systemd-udevd Tainted: G W 6.10.0-next-20240715-next-20240715-g91e3b24eb7d2+ #1
<4>[ 4.171387] Tainted: [W]=WARN
<4>[ 4.171387] Hardware name: ASUS System Product Name/PRIME Z790-P WIFI, BIOS 0812 02/24/2023
<4>[ 4.171388] RIP: 0010:lockdep_assert_cpus_held.part.0+0x24/0x30
```````````````````````````````````````````````````````````````````````````````
Please find the full logs here.
https://gfx-ci.igk.intel.com/tree/linux-next/next-20240715/bat-rpls-4/boot0.txt
The issue was bisected to the commit you have mentioned above.
Reverting the patch resolves the issue.
Are you already looking into it?
Regards
Chaitanya
>
> Thank you Lai for your response.
>
> Regards
>
> Chaitanya
>
> > Thanks
> > Lai
Powered by blists - more mailing lists