From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 218987] USB devices are not detected after Save/Restore error on Intel xHC
Date: Fri, 28 Jun 2024 08:51:05 +0000 [thread overview]
Message-ID: <bug-218987-208809-lHnUmlZ6k2@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-218987-208809@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=218987
--- Comment #10 from Mathias Nyman (mathias.nyman@linux.intel.com) ---
About SRE,
Logs show transfer errors due to disconnect. This normal.
Driver will however try to recover the transfer by resending the same transfer
3 times (soft-reset internal endpoint) before giving up and and doing a hard
reset of the endpoint.
Soft reset is useful if transfer error was caused by electrical interference,
but this case the soft rest if futile, device is gone.
Not sure if it makes a difference but could be worth testing if skipping the
soft reset impacts SRE.
Can be done by setting quirk:
xhci->quirks |= XHCI_NO_SOFT_RETRY
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2024-06-28 8:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-25 13:06 [Bug 218987] New: USB devices are not detected after Save/Restore error on Intel xHC bugzilla-daemon
2024-06-25 13:07 ` [Bug 218987] " bugzilla-daemon
2024-06-25 13:08 ` bugzilla-daemon
2024-06-26 9:10 ` bugzilla-daemon
2024-06-26 10:12 ` bugzilla-daemon
2024-06-27 13:04 ` bugzilla-daemon
2024-06-27 13:10 ` bugzilla-daemon
2024-06-27 14:03 ` bugzilla-daemon
2024-06-27 14:56 ` bugzilla-daemon
2024-06-27 15:36 ` bugzilla-daemon
2024-06-28 8:51 ` bugzilla-daemon [this message]
2024-06-28 17:00 ` 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-218987-208809-lHnUmlZ6k2@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