Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
To: "Sasha Levin" <sashal@kernel.org>, "Iyán Méndez Veiga" <me@iyanmv.com>
Cc: Thorsten Leemhuis <regressions@leemhuis.info>,
	<stable@vger.kernel.org>, <regressions@lists.linux.dev>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [REGRESSION] drm/xe/guc: Lenovo Thinkpad X1 Carbon Gen 12 can't boot with 6.16.9 and Xe driver
Date: Tue, 30 Sep 2025 02:04:38 -0700	[thread overview]
Message-ID: <a6055d09-62e4-4c56-abcf-0fb2fedf42a3@intel.com> (raw)
In-Reply-To: <aNlW7ekiC0dNPxU3@laps>



On 9/28/2025 8:40 AM, Sasha Levin wrote:
> On Sun, Sep 28, 2025 at 01:16:34PM +0200, Iyán Méndez Veiga wrote:
>> On 27/09/2025 16:31, Thorsten Leemhuis wrote:
>>> Thx. Could you also try if reverting the patch from 6.16.y helps? Note,
>>> you might need to revert "drm/xe/guc: Set RCS/CCS yield policy" as 
>>> well,
>>> which apparently depends on the patch that causes your problems.
>>
>> Yes, reverting both dd1a415dcfd5 "drm/xe/guc: Set RCS/CCS yield 
>> policy" and 97207a4fed53 "drm/xe/guc: Enable extended CAT error 
>> reporting" from 6.16.y fixes the issue for me.
>
> Thanks for the report and investigation!
>
> I'll revert these two.
>

Hi,

Thanks for the bisect and the quick turnaround on this (and sorry for 
not replying earlier, I just came back from vacation :) ).
Just wanted to add a quick comment as the author of both patches. I have 
no idea why these patches would cause issues on 6.16 but not on 6.17, 
nothing significant should be different between the two releases in the 
impacted area. However, no one has actually ever reported hitting the 
starvation issue mitigated by the RCS/CCS patch (which has been there 
since 6.13), likely because it can only be reproduced if the GPU is 
heavily overloaded by multiple apps; therefore, given that 6.16 is not 
an LTS, I'm not going to attempt to reproduce and debug this and re-send 
the patches for that kernel version.
Please let me know if there are any concerns with this approach or if 
the issue pops up on 6.17.

Thanks
Daniele


      reply	other threads:[~2025-09-30  9:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-26 22:58 [REGRESSION] drm/xe/guc: Lenovo Thinkpad X1 Carbon Gen 12 can't boot with 6.16.9 and Xe driver Iyán Méndez Veiga
2025-09-27 12:52 ` Thorsten Leemhuis
2025-09-27 14:19   ` Iyán Méndez Veiga
2025-09-27 14:31     ` Thorsten Leemhuis
2025-09-28 11:16       ` Iyán Méndez Veiga
2025-09-28 15:40         ` Sasha Levin
2025-09-30  9:04           ` Daniele Ceraolo Spurio [this message]

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=a6055d09-62e4-4c56-abcf-0fb2fedf42a3@intel.com \
    --to=daniele.ceraolospurio@intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=me@iyanmv.com \
    --cc=regressions@leemhuis.info \
    --cc=regressions@lists.linux.dev \
    --cc=sashal@kernel.org \
    --cc=stable@vger.kernel.org \
    /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