Linux USB
 help / color / mirror / Atom feed
From: Mario Limonciello <mario.limonciello@amd.com>
To: Mathieu Fluhr <mathieu.fluhr@gmail.com>
Cc: Lovekesh Solanki <lovekeshsolanki00@gmail.com>,
	Michal Pecio <michal.pecio@gmail.com>,
	Thorsten Leemhuis <regressions@leemhuis.info>,
	Mathias Nyman <mathias.nyman@linux.intel.com>,
	linux-usb@vger.kernel.org, regressions@lists.linux.dev,
	stable@vger.kernel.org, linux-kernel@vger.kernel.org,
	Forest <forestix@gaga.casa>,
	Slavik Dev <developer.slavik@gmail.com>
Subject: Re: [REGRESSION] 6.12.36+: usb: hub: post-resume delayed work triggers > uncorrected MCE / data fabric sync flood on Threadripper 7970X > (bisected to aec11e5f9c45)
Date: Wed, 26 Aug 2026 10:32:55 -0500	[thread overview]
Message-ID: <23682f17-e6d6-4fd6-86ae-823637e9c568@amd.com> (raw)
In-Reply-To: <CAPyJwA-DqScij982KfUQQ3ad2nHF4=SEBjjQhQGr1yCumdMXHA@mail.gmail.com>



On 8/26/26 01:27, Mathieu Fluhr wrote:
>> The workaround you can do for now is to disable runtime PM on the XHCI
>> controller to avoid triggering it.  But it's a platform issue.
> 
> So, long story short, the kernel source code is correct, and the issue comes
> from the BIOS/AGESA, correct?

Correct.

> 
>> For a proper fix you need to reach out to ASUS to get an AGESA upgrade.
>> You can ask them to reach out to AMD if they need assistance/guidance on
>> the versions that contain the fix for this.  You can share this thread
>> with them for reference.
> 
> I will. But this leaves me with a few questions here:
> 1. Do you already have a fixed AGESA on AMD side, that ASUS could use?

Yes; it's already fixed by AMD.  ASUS can get the fix from AMD.

> 2. Does this issue also affect other threadripper generations, like the 9970x?

It's only in Storm Peak CPUs, not in Chagall or Shimada Peak.
> 3. I guess not only ASUS is concerned but Also ASRock and Gigabyte which
> also produces TRX50 mainboards, correct?
> 
Yes; all board vendors are affected.  I know that some vendors already 
have the fixes out.

  reply	other threads:[~2026-08-26 15:33 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-23  9:55 Mathieu Fluhr
2026-08-23 10:12 ` Mathieu Fluhr
2026-08-23 10:15   ` [REGRESSION] 6.12.36+: usb: hub: post-resume delayed work triggers > uncorrected MCE / data fabric sync flood on Threadripper 7970X > (bisected to aec11e5f9c45) Mathieu Fluhr
2026-08-23 10:36     ` Thorsten Leemhuis
2026-08-23 11:44       ` Mathieu Fluhr
2026-08-23 16:10         ` Michal Pecio
2026-08-23 15:17       ` Lovekesh Solanki
2026-08-23 15:40         ` Michal Pecio
2026-08-23 17:05           ` Lovekesh Solanki
2026-08-24 19:37             ` Mathieu Fluhr
2026-08-24 22:09               ` Mario Limonciello
2026-08-25  8:57                 ` Mathieu Fluhr
2026-08-26  3:14                   ` Mario Limonciello
2026-08-26  6:27                     ` Mathieu Fluhr
2026-08-26 15:32                       ` Mario Limonciello [this message]
2026-08-26  6:59                     ` Michal Pecio
2026-08-25 10:15                 ` Lovekesh Solanki
2026-08-25 10:06               ` Lovekesh Solanki
2026-08-25 21:43                 ` Mathieu Fluhr
2026-08-26 12:35                   ` Lovekesh Solanki
2026-08-26 13:40                     ` Mathias Nyman
2026-08-26 16:03                       ` Mathieu Fluhr
2026-08-26 18:11                       ` Lovekesh Solanki
2026-08-27 19:34                         ` Mathias Nyman

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=23682f17-e6d6-4fd6-86ae-823637e9c568@amd.com \
    --to=mario.limonciello@amd.com \
    --cc=developer.slavik@gmail.com \
    --cc=forestix@gaga.casa \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=lovekeshsolanki00@gmail.com \
    --cc=mathias.nyman@linux.intel.com \
    --cc=mathieu.fluhr@gmail.com \
    --cc=michal.pecio@gmail.com \
    --cc=regressions@leemhuis.info \
    --cc=regressions@lists.linux.dev \
    --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