From: Lovekesh Solanki <lovekeshsolanki00@gmail.com>
To: Mario Limonciello <mario.limonciello@amd.com>
Cc: Mathieu Fluhr <mathieu.fluhr@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: Tue, 25 Aug 2026 15:45:15 +0530 [thread overview]
Message-ID: <ao1qAlO8t9N3kfbZ@eggarch> (raw)
In-Reply-To: <226b2f34-fa25-4ca6-8afb-0b3dc942715c@amd.com>
On Mon, Aug 24, 2026 at 05:09:02PM -0500, Mario Limonciello wrote:
> The behavior that is described here sounds like a platform firmware bug to
> me. Are you on the latest BIOS available from your OEM?
>
> Can you please confirm:
>
> 1. Your CPU model number/codename
> 2. Your OEM (from /sys/class/dmi/id)
> 3. OEM BIOS version (from /sys/class/dmi/id)
> 4. AGESA version (see commit bc91133e260c8113c1119073c03b93c12aa41738 if the
> OEM didn't tear it out. Otherwise look in BIOS menus)?
Though the issue's only reproducible in kernels including commmit
8f5b7e2bec1c36, which their bisection showed too.
Could the trigger not be the 200ms SS hold?
Regards,
Lovekesh
next prev parent reply other threads:[~2026-08-25 10:15 UTC|newest]
Thread overview: 17+ 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
[not found] ` <07435e6b-ee30-4c85-8c8b-0ce3a4ead1d9@leemhuis.info>
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 6:59 ` Michal Pecio
2026-08-25 10:15 ` Lovekesh Solanki [this message]
2026-08-25 10:06 ` Lovekesh Solanki
2026-08-25 21:43 ` Mathieu Fluhr
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=ao1qAlO8t9N3kfbZ@eggarch \
--to=lovekeshsolanki00@gmail.com \
--cc=developer.slavik@gmail.com \
--cc=forestix@gaga.casa \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mario.limonciello@amd.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