Linux Input/HID development
 help / color / mirror / Atom feed
From: Michal Pecio <michal.pecio@gmail.com>
To: "Erik Håkansson" <erikhakan@gmail.com>
Cc: bentiss@kernel.org, jikos@kernel.org,
	linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] HID: steelseries: Add support for Arctis 7 (2018)
Date: Sun, 22 Nov 2026 23:02:29 +0100	[thread overview]
Message-ID: <20261122230229.1bdc3bd0.michal.pecio@gmail.com> (raw)
In-Reply-To: <Rv7nePC3RfOSidIKv_K-KQ@gmail.com>

On Sun, 22 Nov 2026 19:32:53 +0100, Erik Håkansson wrote:
> > URB status -75 is -EOVERFLOW: URB buffer too small for data returned
> > by the device or the device babbled (exceeded wMaxPacketSize).  
> 
> I can't reproduce this locally, neither with or without USB hub.
> 
> But it seems someone else is reporting the same on Bazzite:
> https://github.com/ublue-os/bazzite/issues/6344
> 
> It seems the hub itself reports that the port is disabled, both in
> this report and in the bazzite report:
> 
> "Nov 19 20:47:58 [REDACTED HOSTNAME] kernel: usb 4-1-port4: disabled
> by hub (EMI?), re-enabling..."
> 
> "Nov 15 16:05:59 [REDACTED HOSTNAME] kernel: usb usb1-port2: disabled
> by hub (EMI?), re-enabling..."

Per USB2 8.7.4 and 11.2.5, hubs are supposed to disable downstream
ports which are still receiving packet near the end of frame. So it
might be that the device (at some point) never terminates a packet
at all, or its packets are too long and occasionally reach EOF.

I suppose the latter could happen because the host schedules the
transfer near EOF believing that it will be shorter and complete
sooner. Scheduling may depend on host controller type and on other
periodic traffic to low/full-speed devices behind the same hub.

Or maybe you are missing some other detail. Just guessing.

Regards,
Michal

      reply	other threads:[~2026-11-22 22:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-01 20:30 [PATCH] HID: steelseries: Add support for Arctis 7 (2018) Erik Håkansson
2026-09-11 15:23 ` Jiri Kosina
2026-11-21 11:11 ` Michal Pecio
2026-11-22 18:32   ` Erik Håkansson
2026-11-22 22:02     ` Michal Pecio [this message]

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=20261122230229.1bdc3bd0.michal.pecio@gmail.com \
    --to=michal.pecio@gmail.com \
    --cc=bentiss@kernel.org \
    --cc=erikhakan@gmail.com \
    --cc=jikos@kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@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