Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Wysocki, Rafael J" <rafael.j.wysocki@intel.com>
To: "Borah, Chaitanya Kumar" <chaitanya.kumar.borah@intel.com>
Cc: "intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>,
	"Kurmi, Suresh Kumar" <suresh.kumar.kurmi@intel.com>
Subject: Re: [Intel-gfx] Regression in linux-next
Date: Fri, 6 Oct 2023 22:30:33 +0200	[thread overview]
Message-ID: <27bf7758-61e0-2587-1800-5aa4be42fffe@intel.com> (raw)
In-Reply-To: <SJ1PR11MB6129E1EA583B3DA3B45E37A4B9CAA@SJ1PR11MB6129.namprd11.prod.outlook.com>

[-- Attachment #1: Type: text/plain, Size: 3148 bytes --]

Hi,

On 10/5/2023 5:58 PM, Borah, Chaitanya Kumar wrote:
>
> Hello Rafael,
>
> 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 
> linux-next repository.
>
Thanks for the report, I think that this is a lockdep assertion failing.

If that is correct, it should be straightforward to fix.

I'll take care of this early next week.

Thanks!


> On next-20231003 [2], we are seeing the following error
>
> ```````````````````````````````````````````````````````````````````````````````
>
> <4>[ 14.093075] ------------[ cut here ]------------
>
> <4>[ 14.097664] WARNING: CPU: 0 PID: 1 at 
> drivers/thermal/thermal_trip.c:18 for_each_thermal_trip+0x83/0x90
>
> <4>[ 14.106977] Modules linked in:
>
> <4>[ 14.110017] CPU: 0 PID: 1 Comm: swapper/0 Tainted: G W 
>       6.6.0-rc4-next-20231003-next-20231003-gc9f2baaa18b5+ #1
>
> <4>[ 14.121305] Hardware name: Intel Corporation Meteor Lake Client 
> Platform/MTL-P DDR5 SODIMM SBS RVP, BIOS 
> MTLPFWI1.R00.3323.D89.2309110529 09/11/2023
>
> <4>[ 14.134478] RIP: 0010:for_each_thermal_trip+0x83/0x90
>
> <4>[ 14.139496] Code: 5c 41 5d c3 cc cc cc cc 5b 31 c0 5d 41 5c 41 5d 
> c3 cc cc cc cc 48 8d bf f0 05 00 00 be ff ff ff ff e8 21 a2 2d 00 85 
> c0 75 9a <0f> 0b eb 96 66 0f 1f 84 00 00 00 00 00 90 90 90 90 90 90 90 
> 90 90
>
> Details log can be found in [3].
>
> After bisecting the tree, the following patch [4] seems to be causing 
> the regression.
>
> commit d5ea889246b112e228433a5f27f57af90ca0c1fb
>
> Author: Rafael J. Wysocki rafael.j.wysocki@intel.com
>
> Date:   Thu Sep 21 20:02:59 2023 +0200
>
>     ACPI: thermal: Do not use trip indices for cooling device binding
>
>     Rearrange the ACPI thermal driver's callback functions used for 
> cooling
>
>     device binding and unbinding, acpi_thermal_bind_cooling_device() and
>
>     acpi_thermal_unbind_cooling_device(), respectively, so that they 
> use trip
>
>     pointers instead of trip indices which is more straightforward and 
> allows
>
>     the driver to become independent of the ordering of trips in the 
> thermal
>
>     zone structure.
>
>     The general functionality is not expected to be changed.
>
>     Signed-off-by: Rafael J. Wysocki rafael.j.wysocki@intel.com
>
>     Reviewed-by: Daniel Lezcano daniel.lezcano@linaro.org
>
> We also verified by moving the head of the tree to the previous commit.
>
> Could you please check why this patch causes the regression and if we 
> can find a solution for it soon?
>
> [1] https://intel-gfx-ci.01.org/tree/linux-next/combined-alt.html?
>
> [2] 
> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20231003
>
> [3] 
> https://intel-gfx-ci.01.org/tree/linux-next/next-20231003/bat-mtlp-6/boot0.txt
>
> [4] 
> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20231003&id=d5ea889246b112e228433a5f27f57af90ca0c1fb 
> <https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20231003&id=d5ea889246b112e228433a5f27f57af90ca0c1fb>
>

[-- Attachment #2: Type: text/html, Size: 9430 bytes --]

  reply	other threads:[~2023-10-06 20:30 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-05 15:58 [Intel-gfx] Regression in linux-next Borah, Chaitanya Kumar
2023-10-06 20:30 ` Wysocki, Rafael J [this message]
2023-10-09  5:10   ` Borah, Chaitanya Kumar
2023-10-09 19:23     ` Wysocki, Rafael J
2023-10-11  4:00       ` Borah, Chaitanya Kumar
2023-10-11 16:14         ` Wysocki, Rafael J
2023-10-11 16:49           ` Borah, Chaitanya Kumar
2023-10-13 14:05             ` Borah, Chaitanya Kumar
2023-10-20  5:52 ` [Intel-gfx] Regression on linux-next (next-20231016) Borah, Chaitanya Kumar
2023-10-20  6:38   ` Lorenzo Stoakes
2023-10-20  7:58     ` Borah, Chaitanya Kumar
2023-10-25  6:32   ` [Intel-gfx] Regression on linux-next (next-20231013) Borah, Chaitanya Kumar
2023-10-25  7:32     ` Christian Brauner
2023-10-25 13:44       ` Borah, Chaitanya Kumar
2023-10-26 10:14         ` Borah, Chaitanya Kumar
2023-10-26 12:16           ` Christian Brauner
2023-11-09 17:00     ` [Intel-gfx] Regression on linux-next (next-20231107) Borah, Chaitanya Kumar
2023-11-09 20:40       ` Krister Johansen
2023-11-10  3:38         ` Borah, Chaitanya Kumar
2023-11-13  6:21           ` Borah, Chaitanya Kumar
     [not found]             ` <20231114174121.GA2064@templeofstupid.com>
2023-11-15  4:33               ` Borah, Chaitanya Kumar
2023-12-04 17:17       ` [Intel-gfx] Regression on linux-next (next-20231130) Borah, Chaitanya Kumar
2023-12-04 18:11         ` Berg, Johannes
2023-12-05  6:14           ` Borah, Chaitanya Kumar
2024-01-31  5:34         ` Regression on drm-tip Borah, Chaitanya Kumar
     [not found]           ` <b77d8588-6809-416c-b598-7a33a672c1e7@opensource.cirrus.com>
2024-02-01  5:13             ` Borah, Chaitanya Kumar
     [not found] <SJ1PR11MB6129592BDF5D06949F99816CB95B9@SJ1PR11MB6129.namprd11.prod.outlook.com>
     [not found] ` <SJ1PR11MB6129A7F5C08E2C47748F2BA5B97E9@SJ1PR11MB6129.namprd11.prod.outlook.com>
     [not found]   ` <SJ1PR11MB612980562220A376CA90E105B97E9@SJ1PR11MB6129.namprd11.prod.outlook.com>
2023-07-25  6:42     ` [Intel-gfx] Regression in linux-next Borah, Chaitanya Kumar
2023-07-25 10:53       ` Tvrtko Ursulin
2023-07-26  3:55         ` Borah, Chaitanya Kumar
2023-07-25 13:15       ` Alistair Popple
2023-07-26  3:53         ` Borah, Chaitanya Kumar

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=27bf7758-61e0-2587-1800-5aa4be42fffe@intel.com \
    --to=rafael.j.wysocki@intel.com \
    --cc=chaitanya.kumar.borah@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --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