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 221184] mouse/keyboard (connected via hub) usb reset under system load with weak cpu
Date: Wed, 11 Mar 2026 14:38:30 +0000	[thread overview]
Message-ID: <bug-221184-208809-Vyc2KHy5TS@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-221184-208809@https.bugzilla.kernel.org/>

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

--- Comment #40 from Alan Stern (stern@rowland.harvard.edu) ---
For USB-2, mismatched toggles usually don't hurt.  Mismatches occur when an ACK
packet is lost, so the sender thinks its data wasn't received but the receiver
thinks it was.  When this happens, the sender will resend the same data using
the old toggle value; the receiver will note the mismatch and ignore the
duplicate data while acknowledging it.  This is part of the reason why the USB
stack historically has not included much error handling for EPROTO errors.

USB-3 is more complicated, and the host controller hardware keeps track of more
information that USB-2 host controllers do.  Re-establishing correct
synchronization after an error is therefore all the more difficult.  It would
be worth some effort to find a solution that can work for both USB-2 and USB-3.

-- 
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:[~2026-03-11 14:38 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-07 11:55 [Bug 221184] New: mouse/keyboard (connected via hub) usb reset under system load with weak cpu bugzilla-daemon
2026-03-07 11:56 ` [Bug 221184] " bugzilla-daemon
2026-03-07 11:58 ` bugzilla-daemon
2026-03-07 16:51 ` bugzilla-daemon
2026-03-07 18:56 ` bugzilla-daemon
2026-03-07 18:57 ` bugzilla-daemon
2026-03-07 19:03 ` bugzilla-daemon
2026-03-07 22:44 ` bugzilla-daemon
2026-03-08  4:24 ` bugzilla-daemon
2026-03-08  5:49 ` bugzilla-daemon
2026-03-08 11:47 ` bugzilla-daemon
2026-03-08 15:02 ` bugzilla-daemon
2026-03-08 15:19 ` bugzilla-daemon
2026-03-08 15:39 ` bugzilla-daemon
2026-03-08 16:16 ` bugzilla-daemon
2026-03-08 21:28 ` bugzilla-daemon
2026-03-09  3:43 ` bugzilla-daemon
2026-03-09  5:04 ` bugzilla-daemon
2026-03-09  5:08 ` bugzilla-daemon
2026-03-09 11:32 ` bugzilla-daemon
2026-03-09 14:13 ` bugzilla-daemon
2026-03-09 15:31 ` bugzilla-daemon
2026-03-09 15:46 ` bugzilla-daemon
2026-03-09 15:58 ` bugzilla-daemon
2026-03-09 16:02 ` bugzilla-daemon
2026-03-09 16:08 ` bugzilla-daemon
2026-03-09 17:24 ` bugzilla-daemon
2026-03-09 18:56 ` bugzilla-daemon
2026-03-09 22:02 ` bugzilla-daemon
2026-03-10  5:31 ` bugzilla-daemon
2026-03-10  5:59 ` bugzilla-daemon
2026-03-10  9:54 ` bugzilla-daemon
2026-03-10 10:09 ` bugzilla-daemon
2026-03-10 14:48 ` bugzilla-daemon
2026-03-10 19:42 ` bugzilla-daemon
2026-03-10 21:41 ` bugzilla-daemon
2026-03-11  8:06 ` bugzilla-daemon
2026-03-11  9:23 ` bugzilla-daemon
2026-03-11 11:04 ` bugzilla-daemon
2026-03-11 12:54 ` bugzilla-daemon
2026-03-11 14:38 ` bugzilla-daemon [this message]
2026-03-11 18:37 ` 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-221184-208809-Vyc2KHy5TS@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