From: Lovekesh Solanki <lovekeshsolanki00@gmail.com>
To: Mathieu Fluhr <mathieu.fluhr@gmail.com>
Cc: 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,
Mario Limonciello <mario.limonciello@amd.com>,
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 18:05:34 +0530 [thread overview]
Message-ID: <ao7aLXk9q_v_jEyX@eggarch> (raw)
In-Reply-To: <CAPyJwA-QALkCQn8J1+=U-nuE_7WSEPhVcUEKb+MMYMaA_1AVjQ@mail.gmail.com>
On Tue, Aug 25, 2026 at 11:43:22PM +0200, Mathieu Fluhr wrote:
> The patch you sent makes the issue go away. I am now running the exact same
> scenario for 2 hours, without any crash.
That's good, thanks for confirming.
> However, I am not sure if this can qualify for a proper fix, since I
> do not have any
> external hub connected to my motherboard: All my USB devices are directly
> plugged into root hubs (and at the moment, there is only a keyboard and a
> mouse).
Yeah that's the point it only skips the 200ms hold for root hubs. The
external hubs still get their fair hold since a parent exists for them.
So external hubs are completely unaffected by this patch.
On 'proper fix', I think it is, even if we keep this bug seperate for a
moment, it makes sense to not give root hubs hold they don't need.
I'd love to hear more thoughts on the patch.
Regards,
Lovekesh
next prev parent reply other threads:[~2026-08-26 12:35 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
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 [this message]
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=ao7aLXk9q_v_jEyX@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