public inbox for linux-usb@vger.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 220069] [6.13.9] regression USB controller dies
Date: Sun, 18 May 2025 23:37:59 +0000	[thread overview]
Message-ID: <bug-220069-208809-vLhBCBPPa7@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-220069-208809@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=220069

--- Comment #54 from Michał Pecio (michal.pecio@gmail.com) ---
avg_trb_len doesn't seem to be an issue for my ASMedia/Promontory HCs, they
still have their usual bugs after changing it to 8 as per spec.

By the way, the simplest way to break ASMedia chips is running
  while true ; do ifconfig ethN up ; ifconfig ethN down ; done
on a SuperSpeed NIC (AX88179 and RTL8153 known to work). This is what the limit
endpoint interval quirk appears to be helping with, though recently I found
some case (NIC behind a SuperSpeed hub) where it didn't help.

I am also not convinced that the "clearing xHC resources" patch is relevant,
because it's hard to explain why nothing bad happens when you run reset
manually. I found no problems resetting devices on my AMD B350, ASM3142 and
ASM1142, despite the dubious command sequence always being there. Your logs
show malfunction before we even get to this point. Indeed, the reason the hub
is being reset is because attempting to resume it normally suddenly failed.


So the outcome of testing is that the problem occurs if both the unlucky hub
and the unlucky webcam are present on the same X670 bus, and disappears if they
are on different X670 buses at the same time?

And it's happening on 6.13.9 or newer, but not on 6.13.7? I have no explanation
for that...

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2025-05-18 23:37 UTC|newest]

Thread overview: 65+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-29 14:28 [Bug 220069] New: [6.13.9] regression USB controller dies bugzilla-daemon
2025-04-29 20:07 ` [Bug 220069] " bugzilla-daemon
2025-04-29 20:43 ` bugzilla-daemon
2025-04-29 20:45 ` bugzilla-daemon
2025-04-30  5:57 ` bugzilla-daemon
2025-04-30  8:57 ` bugzilla-daemon
2025-04-30  9:42 ` bugzilla-daemon
2025-04-30  9:49 ` bugzilla-daemon
2025-04-30  9:53 ` bugzilla-daemon
2025-04-30 21:36 ` bugzilla-daemon
2025-04-30 22:36 ` bugzilla-daemon
2025-04-30 22:52 ` bugzilla-daemon
2025-05-01  7:29 ` bugzilla-daemon
2025-05-01  7:45 ` bugzilla-daemon
2025-05-01  9:48 ` bugzilla-daemon
2025-05-01 21:04 ` bugzilla-daemon
2025-05-01 21:43 ` bugzilla-daemon
2025-05-01 23:43 ` bugzilla-daemon
2025-05-02  0:07 ` bugzilla-daemon
2025-05-02  0:08 ` bugzilla-daemon
2025-05-02  9:28 ` bugzilla-daemon
2025-05-02 11:02 ` bugzilla-daemon
2025-05-02 11:03 ` bugzilla-daemon
2025-05-03  0:23 ` bugzilla-daemon
2025-05-03  8:08 ` bugzilla-daemon
2025-05-03 12:09 ` bugzilla-daemon
2025-05-03 12:10 ` bugzilla-daemon
2025-05-03 14:00 ` bugzilla-daemon
2025-05-03 17:49 ` bugzilla-daemon
2025-05-03 18:25 ` bugzilla-daemon
2025-05-03 19:09 ` bugzilla-daemon
2025-05-04 11:40 ` bugzilla-daemon
2025-05-04 12:41 ` bugzilla-daemon
2025-05-04 13:58 ` bugzilla-daemon
2025-05-04 14:17 ` bugzilla-daemon
2025-05-04 17:23 ` bugzilla-daemon
2025-05-05  8:49 ` bugzilla-daemon
2025-05-05  8:58 ` bugzilla-daemon
2025-05-05  9:13 ` bugzilla-daemon
2025-05-05  9:32 ` bugzilla-daemon
2025-05-05  9:40 ` bugzilla-daemon
2025-05-05  9:48 ` bugzilla-daemon
2025-05-05 10:53 ` bugzilla-daemon
2025-05-05 14:07 ` bugzilla-daemon
2025-05-05 21:22 ` bugzilla-daemon
2025-05-05 21:41 ` bugzilla-daemon
2025-05-07 23:02 ` bugzilla-daemon
2025-05-11 11:18 ` bugzilla-daemon
2025-05-11 12:49 ` bugzilla-daemon
2025-05-11 12:53 ` bugzilla-daemon
2025-05-11 12:58 ` bugzilla-daemon
2025-05-11 13:00 ` bugzilla-daemon
2025-05-15 10:05 ` bugzilla-daemon
2025-05-17 16:04 ` bugzilla-daemon
2025-05-18 23:37 ` bugzilla-daemon [this message]
2025-05-19  0:02 ` bugzilla-daemon
2025-05-19  0:13 ` bugzilla-daemon
2025-05-19  6:47 ` bugzilla-daemon
2025-05-19 12:08 ` bugzilla-daemon
2025-05-20 16:18 ` bugzilla-daemon
2025-05-20 16:22 ` bugzilla-daemon
2025-05-23 21:43 ` bugzilla-daemon
2025-05-23 21:44 ` bugzilla-daemon
2025-09-12 12:36 ` bugzilla-daemon
2025-09-12 20:41 ` bugzilla-daemon

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=bug-220069-208809-vLhBCBPPa7@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@kernel.org \
    --cc=linux-usb@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