From: "Mario Limonciello (AMD) (kernel.org)" <superm1@kernel.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: stable@vger.kernel.org
Subject: Re: LR compute WA
Date: Mon, 6 Oct 2025 12:37:30 -0500 [thread overview]
Message-ID: <7bf4b055-d751-4a84-bfd0-a7df78c2a6d8@kernel.org> (raw)
In-Reply-To: <f2d82fa5-7eb3-4717-89ba-6568658e1bf4@kernel.org>
On 10/6/2025 8:56 AM, Mario Limonciello (AMD) (kernel.org) wrote:
>
>
> On 10/6/2025 5:04 AM, Greg KH wrote:
>> On Sat, Oct 04, 2025 at 01:41:29PM -0500, Mario Limonciello (AMD)
>> (kernel.org) wrote:
>>> Hi,
>>>
>>> We have some reports of long compute jobs on APUs hanging the system.
>>> This
>>> has been root caused and a workaround has been introduced in the
>>> mainline
>>> kernel. I didn't CC stable on the original W/A because I wanted to make
>>> sure we've had enough time to test it didn't have unintended side
>>> effects.
>>>
>>> I feel comfortable with the testing at this point and I think it's worth
>>> bringing back to any stable kernels it will apply to 6.12.y and
>>> newer. The
>>> commit is:
>>>
>>> 1fb710793ce2619223adffaf981b1ff13cd48f17
>>
>> It did not apply to 6.12.y, so if you want it there, can you provide a
>> working backport?
>>
>> thanks,
>>
>> greg k-h
>
> Thanks, I see 6.16 and 6.17 had no problem. I'll find the contextually
> missing patches and send out 6.12.y separately.
OK - here's the 3 patches needed for 6.12.y to cleanly cherry-pick:
ce4971388c79d36b3f50f607c3278dbfae6c789b
1c687c0da9efb7c627793483a8927554764e7a55
15d8c92f107c17c2e585cb4888c67873538f9722
Thanks!
next prev parent reply other threads:[~2025-10-06 17:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-04 18:41 LR compute WA Mario Limonciello (AMD) (kernel.org)
2025-10-06 10:04 ` Greg KH
2025-10-06 13:56 ` Mario Limonciello (AMD) (kernel.org)
2025-10-06 17:37 ` Mario Limonciello (AMD) (kernel.org) [this message]
2025-10-07 12:38 ` Greg KH
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=7bf4b055-d751-4a84-bfd0-a7df78c2a6d8@kernel.org \
--to=superm1@kernel.org \
--cc=gregkh@linuxfoundation.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